User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
indooratlas.com · Cloud & developer
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 9 min ago. Last stored result reached it in 244 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 18 | 0 | 0.0 | 263 ms | 0 |
| Tue 21 | 0 | 0.0 | 248 ms | 0 |
| Tue 23 | 0 | 0.0 | 237 ms | 0 |
| Wed 01 | 0 | 0.0 | 209 ms | 0 |
| Wed 03 | 0 | 0.0 | 242 ms | 0 |
| Wed 05 | 0 | 0.0 | 210 ms | 0 |
| Wed 07 | 0 | 0.0 | 270 ms | 0 |
| Wed 10 | 0 | 0.0 | 237 ms | 0 |
| Wed 12 | 0 | 0.0 | 207 ms | 0 |
| Wed 14 | 0 | 0.0 | 218 ms | 0 |
| Wed 16 | 0 | 0.0 | 217 ms | 0 |
| Wed 18 | 0 | 0.0 | 293 ms | 0 |
| Wed 20 | 0 | 0.0 | 269 ms | 0 |
| Wed 23 | 0 | 0.0 | 210 ms | 0 |
| Thu 01 | 0 | 0.0 | 222 ms | 0 |
| Thu 03 | 0 | 0.0 | 247 ms | 0 |
| Thu 05 | 0 | 0.0 | 198 ms | 0 |
| Thu 07 | 0 | 0.0 | 199 ms | 0 |
| Thu 09 | 0 | 0.0 | 232 ms | 0 |
| Thu 11 | 0 | 0.0 | 225 ms | 0 |
| Thu 13 | 0 | 0.0 | 228 ms | 0 |
| Thu 15 | 0 | 0.0 | 229 ms | 0 |
| Thu 17 | 0 | 0.0 | 230 ms | 0 |
| Thu 19 | 0 | 0.0 | 222 ms | 0 |
| Thu 22 | 0 | 0.0 | 252 ms | 0 |
| Fri 00 | 0 | 0.0 | 191 ms | 0 |
| Fri 02 | 0 | 0.0 | 209 ms | 0 |
| Fri 04 | 0 | 0.0 | 222 ms | 0 |
| Fri 05 | 0 | 0.0 | 215 ms | 0 |
| Fri 07 | 0 | 0.0 | 232 ms | 0 |
| Fri 09 | 0 | 0.0 | 265 ms | 0 |
| Fri 11 | 0 | 0.0 | 218 ms | 0 |
| Fri 13 | 0 | 0.0 | 239 ms | 0 |
| Fri 15 | 0 | 0.0 | 340 ms | 0 |
| Fri 17 | 0 | 0.0 | 274 ms | 0 |
| Fri 18 | 0 | 0.0 | 237 ms | 0 |
| Fri 19 | 0 | 0.0 | 215 ms | 0 |
| Fri 21 | 0 | 0.0 | 243 ms | 0 |
| Fri 23 | 0 | 0.0 | 228 ms | 0 |
| Sat 01 | 0 | 0.0 | 262 ms | 0 |
| Sat 03 | 0 | 0.0 | 219 ms | 0 |
| Sat 05 | 0 | 0.0 | 249 ms | 0 |
| Sat 07 | 0 | 0.0 | 188 ms | 0 |
| Sat 09 | 0 | 0.0 | 214 ms | 0 |
| Sat 11 | 0 | 0.0 | 232 ms | 0 |
| Sat 13 | 0 | 0.0 | 232 ms | 0 |
| Sat 16 | 0 | 0.0 | 281 ms | 0 |
| Sat 18 | 0 | 0.0 | 244 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 IndoorAtlas 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 IndoorAtlas goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
We track IndoorAtlas (indooratlas.com) as part of the Cloud & developer group. Indoor positioning SDK for mobile apps. IndoorAtlas combines the magnetic field, Wi-Fi, Bluetooth and motion sensors, and works offline. Free 30-day trial.
IndoorAtlas publishes an official status page at status.indooratlas.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 233 ms average, 188–281 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 IndoorAtlas incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
233 ms on average over the last 24 hours (188–281 ms).
Yes, at https://status.indooratlas.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report IndoorAtlas here at once, the problem is on IndoorAtlas'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 IndoorAtlas. 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.