User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Entertainment
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 15 min ago. Last stored result reached it in 1210 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 444 ms | 0 |
| Mon 17 | 0 | 0.0 | 324 ms | 0 |
| Mon 19 | 0 | 0.0 | 450 ms | 0 |
| Mon 21 | 0 | 0.0 | 265 ms | 0 |
| Mon 23 | 0 | 0.0 | 403 ms | 0 |
| Tue 01 | 0 | 0.0 | 428 ms | 0 |
| Tue 03 | 0 | 0.0 | 409 ms | 0 |
| Tue 05 | 0 | 0.0 | 392 ms | 0 |
| Tue 07 | 0 | 0.0 | 383 ms | 0 |
| Tue 10 | 0 | 0.0 | 406 ms | 0 |
| Tue 12 | 0 | 0.0 | 418 ms | 0 |
| Tue 14 | 0 | 0.0 | 276 ms | 0 |
| Tue 16 | 0 | 0.0 | 445 ms | 0 |
| Tue 18 | 0 | 0.0 | 518 ms | 0 |
| Tue 21 | 0 | 0.0 | 469 ms | 0 |
| Tue 23 | 0 | 0.0 | 463 ms | 0 |
| Wed 01 | 0 | 0.0 | 432 ms | 0 |
| Wed 03 | 0 | 0.0 | 357 ms | 0 |
| Wed 06 | 0 | 0.0 | 464 ms | 0 |
| Wed 08 | 0 | 0.0 | 188 ms | 0 |
| Wed 10 | 0 | 0.0 | 389 ms | 0 |
| Wed 12 | 0 | 0.0 | 174 ms | 0 |
| Wed 14 | 0 | 0.0 | 410 ms | 0 |
| Wed 16 | 0 | 0.0 | 336 ms | 0 |
| Wed 19 | 0 | 0.0 | 182 ms | 0 |
| Wed 21 | 0 | 0.0 | 452 ms | 0 |
| Wed 23 | 0 | 0.0 | 364 ms | 0 |
| Thu 01 | 0 | 0.0 | 372 ms | 0 |
| Thu 03 | 0 | 0.0 | 352 ms | 0 |
| Thu 05 | 0 | 0.0 | 482 ms | 0 |
| Thu 07 | 0 | 0.0 | 180 ms | 0 |
| Thu 09 | 0 | 0.0 | 257 ms | 0 |
| Thu 12 | 0 | 0.0 | 439 ms | 0 |
| Thu 14 | 0 | 0.0 | 238 ms | 0 |
| Thu 16 | 0 | 0.0 | 367 ms | 0 |
| Thu 18 | 0 | 0.0 | 415 ms | 0 |
| Thu 20 | 0 | 0.0 | 436 ms | 0 |
| Thu 22 | 0 | 0.0 | 284 ms | 0 |
| Fri 00 | 0 | 0.0 | 3847 ms | 0 |
| Fri 02 | 0 | 0.0 | 395 ms | 0 |
| Fri 04 | 0 | 0.0 | 4298 ms | 0 |
| Fri 06 | 0 | 0.0 | 406 ms | 0 |
| Fri 08 | 0 | 0.0 | 418 ms | 0 |
| Fri 10 | 0 | 0.0 | 266 ms | 0 |
| Fri 11 | 0 | 0.0 | 416 ms | 0 |
| Fri 12 | 0 | 0.0 | 425 ms | 0 |
| Fri 14 | 0 | 0.0 | 1536 ms | 0 |
| Fri 16 | 0 | 0.0 | 1210 ms | 0 |
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.
No outages on record for Mapme yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Mapme goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Mapme alerts to Slack, Discord or a webhook — free.
Mapme is listed in our Entertainment category and checked at mapme.com. Create interactive maps in minutes with no code. Add locations, photos, video, categories and filters, then share or embed anywhere. Try Mapme free.
Mapme publishes an official status page at status.mapme.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with entertainment services: streams buffering or not starting, playback errors, and app sign-in problems.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 1104 ms average, 266–4298 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Mapme incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
1104 ms on average over the last 24 hours (266–4298 ms).
Yes, at https://status.mapme.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For entertainment services, watch for streams buffering or not starting, playback errors, and app sign-in problems. If many people report Mapme here at once, the problem is on Mapme'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 Mapme. 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.