User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is MetaMap down?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: [Incident] Brazilian CPF Government Validation | [Incident] Colombian Unified Legal Government Validation | [Incident] Mexican INE Government Validation | [Incident] Bolivian OE...
Source: the vendor's status page · We are not affiliated with MetaMap.
What to try while MetaMap is having problems
Estimated fix: Not enough MetaMap history yet; similar AI outages lasted 27 min (median, typically 9 min–2 h; 41 outages).
- Try the mobile app or a private window, or the API; another assistant can cover urgent work.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → metamap.com—
Your browser → us—
Our checksReaching it
Official · ReportsMajor incident · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 68 ms.
Official status
Major incident
[Incident] Brazilian CPF Government Validation | [Incident] Colombian Unified Legal Government Validation | [Incident] Mexican INE Government Validation | [Incident] Bolivian OEP Government Validation Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 03 | 0 | 0.0 | 222 ms | 0 |
| Tue 05 | 0 | 0.0 | 37 ms | 0 |
| Tue 07 | 0 | 0.0 | 137 ms | 0 |
| Tue 10 | 0 | 0.0 | 74 ms | 0 |
| Tue 12 | 0 | 0.0 | 136 ms | 0 |
| Tue 14 | 0 | 0.0 | 131 ms | 0 |
| Tue 16 | 0 | 0.0 | 75 ms | 0 |
| Tue 18 | 0 | 0.0 | 86 ms | 0 |
| Tue 21 | 0 | 0.0 | 69 ms | 0 |
| Tue 23 | 0 | 0.0 | 140 ms | 0 |
| Wed 01 | 0 | 0.0 | 149 ms | 0 |
| Wed 03 | 0 | 0.0 | 130 ms | 0 |
| Wed 06 | 0 | 0.0 | 74 ms | 0 |
| Wed 08 | 0 | 0.0 | 89 ms | 0 |
| Wed 10 | 0 | 0.0 | 85 ms | 0 |
| Wed 12 | 0 | 0.0 | 139 ms | 0 |
| Wed 14 | 0 | 0.0 | 268 ms | 0 |
| Wed 17 | 0 | 0.0 | 127 ms | 0 |
| Wed 19 | 0 | 0.0 | 115 ms | 0 |
| Wed 21 | 0 | 0.0 | 72 ms | 0 |
| Wed 23 | 0 | 0.0 | 141 ms | 0 |
| Thu 00 | 0 | 0.0 | 56 ms | 0 |
| Thu 02 | 0 | 0.0 | 133 ms | 0 |
| Thu 04 | 0 | 0.0 | 118 ms | 0 |
| Thu 06 | 0 | 0.0 | 120 ms | 0 |
| Thu 08 | 0 | 0.0 | 104 ms | 0 |
| Thu 10 | 0 | 0.0 | 37 ms | 0 |
| Thu 12 | 0 | 0.0 | 137 ms | 0 |
| Thu 14 | 0 | 0.0 | 123 ms | 0 |
| Thu 16 | 0 | 0.0 | 174 ms | 0 |
| Thu 18 | 0 | 0.0 | 181 ms | 0 |
| Thu 20 | 0 | 0.0 | 79 ms | 0 |
| Thu 22 | 0 | 0.0 | 78 ms | 0 |
| Fri 00 | 0 | 0.0 | 151 ms | 0 |
| Fri 02 | 0 | 0.0 | 94 ms | 0 |
| Fri 05 | 0 | 0.0 | 138 ms | 0 |
| Fri 07 | 0 | 0.0 | 78 ms | 0 |
| Fri 09 | 0 | 0.0 | 59 ms | 0 |
| Fri 10 | 0 | 0.0 | 73 ms | 0 |
| Fri 11 | 0 | 0.0 | 145 ms | 0 |
| Fri 14 | 0 | 0.0 | 239 ms | 0 |
| Fri 15 | 0 | 0.0 | 87 ms | 0 |
| Fri 17 | 0 | 0.0 | 78 ms | 0 |
| Fri 18 | 0 | 0.0 | 172 ms | 0 |
| Fri 19 | 0 | 0.0 | 68 ms | 0 |
| Fri 20 | 0 | 0.0 | 128 ms | 0 |
| Fri 22 | 0 | 0.0 | 87 ms | 0 |
| Sat 00 | 0 | 0.0 | 68 ms | 0 |
Reliability
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live MetaMap badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
Having trouble with MetaMap?
One report per service every 10 minutes from this network. No account.
Follow MetaMap
Get an email when MetaMap goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send MetaMap alerts to Slack, Discord or a webhook — free.
About MetaMap
MetaMap is listed in our AI category and checked at metamap.com. MetaMap has joined Incode. Incode's AI-first identity verification platform and MetaMap's midmarket expertise now work together for stronger protection against AI-fueled fraud and deepfakes.
MetaMap publishes an official status page at status.metamap.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. We logged 1 public incident since monitoring began 8 days ago.
Response time over the last 24 hours: 108 ms average, 59–239 ms range across 14 successful checks.
Questions
Is MetaMap down right now?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: [Incident] Brazilian CPF Government Validation | [Incident] Colombian Unified Legal Government Validation | [Incident] Mexican INE Government Validation | [Incident] Bolivian OE...
When was MetaMap last down?
The most recent public incident we recorded started 2026-11-06 and lasted 3 days 12 h. 1 incident since monitoring began 8 days ago.
What is MetaMap's uptime?
From our own checks: 100% over 8 days of checks.
How fast does MetaMap respond?
108 ms on average over the last 24 hours (59–239 ms).
Does MetaMap have an official status page?
Yes, at https://status.metamap.com.
MetaMap not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report MetaMap here at once, the problem is on MetaMap's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with MetaMap. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.