Nearmap Outage History
8 incidents recorded over the last 365 days, 4 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Nearmap Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 10, 2026 | Service Investigation - Share The Advantage outageThe issue affecting the Nearmap MyAccount - Share the advantage service has been resolved. If you experience any issues with Nearmap services, please <a href="https://www.nearmap.com/contact-support">click here</a> to… | 87h 11m | Resolved |
| Aug 13, 2026 | Betterview Loading DelayThis incident has been resolved. | 1h 30m | Resolved |
| Jul 10, 2026 | Scheduled Maintenance - BetterviewThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| May 18, 2026 | Betterview Platform DisruptionThis incident has been resolved. | 5h 6m | Resolved |
| Mar 22, 2026 | Scheduled Maintenance - Database UpdateThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Jan 14, 2026 | Betterview Service ResolvedA system that process non-Nearmap assets for real-time results caused a backup in order processing, time range = 9:20am PT - 11:39am PT. The issue has been corrected. Work is being done to prevent this particular asset… | -258 min | Resolved |
| Dec 2, 2025 | US/CA ArcGIS Online Critical Service UpdateThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Dec 1, 2025 | AU/NZ ArcGIS Online Critical Service UpdateThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Nearmap incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Nearmap Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Nearmap acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Nearmap outage in this window ran 3d 15h, against a mean recovery of 14h 41m. If you depend on Nearmap in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.