Nearmap incident

ArcGIS Online Service disruption

Critical Resolved View vendor source →

Nearmap experienced a critical incident on June 26, 2025 affecting Australia / NZ AGOL and US / Canada AGOL, lasting 83d 22h. The incident has been resolved; the full update timeline is below.

Started
Jun 26, 2025, 02:03 AM UTC
Resolved
Sep 18, 2025, 12:26 AM UTC
Duration
83d 22h
Detected by Pingoru
Jun 26, 2025, 02:03 AM UTC

Affected components

Australia / NZ AGOLUS / Canada AGOL

Update timeline

  1. investigating Jun 26, 2025, 02:03 AM UTC

    We are currently investigating an issue affecting the Nearmap ArcGIS online service. The service is currently unavailable. We will provide updates about restoration of this service as and when information becomes available.

  2. investigating Jun 26, 2025, 04:01 AM UTC

    We are still investigating this issue and are working with Esri to identify the cause. We will provide an update as more information becomes available.

  3. investigating Jun 30, 2025, 01:05 AM UTC

    We are continuing to investigate this issue with Esri.

  4. identified Jul 02, 2025, 12:43 AM UTC

    The issue has been identified. Esri is working to resolve the issue and to implement a fix. We will update the status page when we have more information.

  5. identified Jul 14, 2025, 02:43 PM UTC

    We are continuing to work with ESRI on a fix for the ArcGIS Online service disruption and have identified some possible solutions. We do not have an ETA yet, but we will share updates as soon as more information is available. Thank you for your patience.

  6. monitoring Jul 15, 2025, 07:05 PM UTC

    Update: Service Access Restored with Caution July 15, 2025 We have applied a temporary workaround that is currently restoring access for ArcGIS Online content across Australia, the US, Canada, and New Zealand. Please note that while this solution is working for now, it is a temporary measure, and the service may remain sensitive to changes outside our control. We are actively monitoring the situation and will provide further updates as we continue working toward a more stable, long-term resolution. We encourage exploring our alternative APIs, which continue to operate normally. Thank you for your patience while we work through this with care.

  7. resolved Sep 18, 2025, 12:26 AM UTC

    This incident has been resolved, and the service has returned to a steady state.