User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 5 min ago. Last stored result reached it in 134 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 114 ms | 0 |
| Mon 22 | 0 | 0.0 | 129 ms | 0 |
| Tue 00 | 0 | 0.0 | 80 ms | 0 |
| Tue 02 | 0 | 0.0 | 201 ms | 0 |
| Tue 04 | 0 | 0.0 | 759 ms | 0 |
| Tue 06 | 0 | 0.0 | 159 ms | 0 |
| Tue 08 | 0 | 0.0 | 179 ms | 0 |
| Tue 11 | 0 | 0.0 | 39 ms | 0 |
| Tue 13 | 0 | 0.0 | 53 ms | 0 |
| Tue 15 | 0 | 0.0 | 272 ms | 0 |
| Tue 17 | 0 | 0.0 | 364 ms | 0 |
| Tue 20 | 0 | 0.0 | 1005 ms | 0 |
| Tue 22 | 0 | 0.0 | 39 ms | 0 |
| Wed 00 | 0 | 0.0 | 136 ms | 0 |
| Wed 02 | 0 | 0.0 | 241 ms | 0 |
| Wed 04 | 0 | 0.0 | 224 ms | 0 |
| Wed 07 | 0 | 0.0 | 109 ms | 0 |
| Wed 09 | 0 | 0.0 | 439 ms | 0 |
| Wed 11 | 0 | 0.0 | 275 ms | 0 |
| Wed 13 | 0 | 0.0 | 455 ms | 0 |
| Wed 15 | 0 | 0.0 | 291 ms | 0 |
| Wed 17 | 0 | 0.0 | 277 ms | 0 |
| Wed 20 | 0 | 0.0 | 124 ms | 0 |
| Wed 22 | 0 | 0.0 | 146 ms | 0 |
| Thu 00 | 0 | 0.0 | 211 ms | 0 |
| Thu 02 | 0 | 0.0 | 152 ms | 0 |
| Thu 04 | 0 | 0.0 | 175 ms | 0 |
| Thu 06 | 0 | 0.0 | 188 ms | 0 |
| Thu 08 | 0 | 0.0 | 206 ms | 0 |
| Thu 10 | 0 | 0.0 | 671 ms | 0 |
| Thu 13 | 0 | 0.0 | 326 ms | 0 |
| Thu 15 | 0 | 0.0 | 102 ms | 0 |
| Thu 17 | 0 | 0.0 | 43 ms | 0 |
| Thu 19 | 0 | 0.0 | 252 ms | 0 |
| Thu 21 | 0 | 0.0 | 1001 ms | 0 |
| Thu 23 | 0 | 0.0 | 54 ms | 0 |
| Fri 01 | 0 | 0.0 | 154 ms | 0 |
| Fri 03 | 0 | 0.0 | 171 ms | 0 |
| Fri 05 | 0 | 0.0 | 101 ms | 0 |
| Fri 07 | 0 | 0.0 | 109 ms | 0 |
| Fri 09 | 0 | 0.0 | 693 ms | 0 |
| Fri 10 | 0 | 0.0 | 56 ms | 0 |
| Fri 12 | 0 | 0.0 | 118 ms | 0 |
| Fri 14 | 0 | 0.0 | 405 ms | 0 |
| Fri 15 | 0 | 0.0 | 828 ms | 0 |
| Fri 17 | 0 | 0.0 | 67 ms | 0 |
| Fri 18 | 0 | 0.0 | 134 ms | 0 |
| Fri 20 | 0 | 0.0 | 399 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 Mappedin 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 Mappedin goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Mappedin alerts to Slack, Discord or a webhook — free.
Mappedin is listed in our AI category and checked at mappedin.com. Mappedin lets you create indoor maps using AI-powered tools and share them anywhere. Maps help make the indoors discoverable.
Mappedin publishes an official status page at status.mappedin.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 341 ms average, 54–1238 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 Mappedin incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
341 ms on average over the last 24 hours (54–1238 ms).
Yes, at https://status.mappedin.com.
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 Mappedin here at once, the problem is on Mappedin'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 Mappedin. 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.