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 1137 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 20:15 | 0 | 0.0 | 436 ms | 0 |
| 22:15 | 0 | 0.0 | 284 ms | 0 |
| 00:15 | 0 | 0.0 | 3847 ms | 0 |
| 02:30 | 0 | 0.0 | 395 ms | 0 |
| 04:30 | 0 | 0.0 | 4298 ms | 0 |
| 06:45 | 0 | 0.0 | 406 ms | 0 |
| 08:45 | 0 | 0.0 | 418 ms | 0 |
| 10:30 | 0 | 0.0 | 266 ms | 0 |
| 11:00 | 0 | 0.0 | 416 ms | 0 |
| 12:30 | 0 | 0.0 | 425 ms | 0 |
| 14:30 | 0 | 0.0 | 1536 ms | 0 |
| 16:30 | 0 | 0.0 | 1210 ms | 0 |
| 17:15 | 0 | 0.0 | 1137 ms | 0 |
| 18:45 | 0 | 0.0 | 1257 ms | 0 |
| 19:00 | 0 | 0.0 | 1390 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: 1181 ms average, 266–4298 ms range across 15 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.
1181 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.