User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Nearmap down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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 → nearmap.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · 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 45 min ago. Last stored result reached it in 73 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 111 ms | 0 |
| Tue 00 | 0 | 0.0 | 146 ms | 0 |
| Tue 02 | 0 | 0.0 | 81 ms | 0 |
| Tue 04 | 0 | 0.0 | 93 ms | 0 |
| Tue 06 | 0 | 0.0 | 201 ms | 0 |
| Tue 08 | 0 | 0.0 | 98 ms | 0 |
| Tue 11 | 0 | 0.0 | 123 ms | 0 |
| Tue 13 | 0 | 0.0 | 63 ms | 0 |
| Tue 15 | 0 | 0.0 | 114 ms | 0 |
| Tue 16 | 0 | 0.0 | 147 ms | 0 |
| Tue 18 | 0 | 0.0 | 73 ms | 0 |
| Tue 20 | 0 | 0.0 | 72 ms | 0 |
| Tue 22 | 0 | 0.0 | 127 ms | 0 |
| Wed 01 | 0 | 0.0 | 121 ms | 0 |
| Wed 03 | 0 | 0.0 | 71 ms | 0 |
| Wed 05 | 0 | 0.0 | 376 ms | 0 |
| Wed 07 | 0 | 0.0 | 132 ms | 0 |
| Wed 10 | 0 | 0.0 | 124 ms | 0 |
| Wed 12 | 0 | 0.0 | 138 ms | 0 |
| Wed 14 | 0 | 0.0 | 439 ms | 0 |
| Wed 16 | 0 | 0.0 | 217 ms | 0 |
| Wed 18 | 0 | 0.0 | 59 ms | 0 |
| Wed 20 | 0 | 0.0 | 75 ms | 0 |
| Wed 23 | 0 | 0.0 | 226 ms | 0 |
| Thu 01 | 0 | 0.0 | 148 ms | 0 |
| Thu 03 | 0 | 0.0 | 526 ms | 0 |
| Thu 04 | 0 | 0.0 | 90 ms | 0 |
| Thu 06 | 0 | 0.0 | 378 ms | 0 |
| Thu 08 | 0 | 0.0 | 92 ms | 0 |
| Thu 10 | 0 | 0.0 | 238 ms | 0 |
| Thu 12 | 0 | 0.0 | 199 ms | 0 |
| Thu 14 | 0 | 0.0 | 110 ms | 0 |
| Thu 16 | 0 | 0.0 | 116 ms | 0 |
| Thu 18 | 0 | 0.0 | 183 ms | 0 |
| Thu 20 | 0 | 0.0 | 81 ms | 0 |
| Thu 22 | 0 | 0.0 | 94 ms | 0 |
| Fri 00 | 0 | 0.0 | 63 ms | 0 |
| Fri 02 | 0 | 0.0 | 266 ms | 0 |
| Fri 05 | 0 | 0.0 | 74 ms | 0 |
| Fri 07 | 0 | 0.0 | 200 ms | 0 |
| Fri 09 | 0 | 0.0 | 112 ms | 0 |
| Fri 11 | 0 | 0.0 | 89 ms | 0 |
| Fri 12 | 0 | 0.0 | 43 ms | 0 |
| Fri 14 | 0 | 0.0 | 32 ms | 0 |
| Fri 16 | 0 | 0.0 | 116 ms | 0 |
| Fri 18 | 0 | 0.0 | 115 ms | 0 |
| Fri 20 | 0 | 0.0 | 142 ms | 0 |
| Fri 22 | 0 | 0.0 | 73 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 Nearmap 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
No outages on record for Nearmap yet. Outages of 10 minutes or more get their own page here.
Having trouble with Nearmap?
One report per service every 10 minutes from this network. No account.
Follow Nearmap
Get an email when Nearmap goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Nearmap alerts to Slack, Discord or a webhook — free.
About Nearmap
Nearmap is listed in our AI category and checked at nearmap.com. Current high-resolution aerial imagery of the U.S., captured by proprietary cameras, plus 130+ AI-derived insights for every property decision.
Nearmap publishes an official status page at status.nearmap.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. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 111 ms average, 32–266 ms range across 13 successful checks.
Questions
Is Nearmap down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Nearmap last down?
We have not recorded a public Nearmap incident since monitoring began 8 days ago.
What is Nearmap's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Nearmap respond?
111 ms on average over the last 24 hours (32–266 ms).
Does Nearmap have an official status page?
Yes, at https://status.nearmap.com.
Nearmap 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 Nearmap here at once, the problem is on Nearmap'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 Nearmap. 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.