Pantheon incident

Dashboard Outage

Critical Resolved View vendor source →

Pantheon experienced a critical incident on September 1, 2026 affecting Customer Sites and Dashboard and 1 more component, lasting 5h 22m. The incident has been resolved; the full update timeline is below.

Started
Sep 01, 2026, 03:14 PM UTC
Resolved
Sep 01, 2026, 08:37 PM UTC
Duration
5h 22m
Detected by Pingoru
Sep 01, 2026, 03:14 PM UTC

Affected components

Customer SitesDashboardGlobal CDNSpinup OperationsWorkflow OperationsTerminus OperationsSite Certificate ProvisioningBilling OperationsAutopilotGit

Update timeline

  1. investigating Sep 01, 2026, 03:14 PM UTC

    Our Engineering team is currently investigating reports of degraded performance affecting the Dashboard interface. A subset of users may experience slow page loading times or intermittent issues opening site environments. Live hosted sites and environment uptime remain fully operational and unaffected. We are actively working to identify the root cause and restore normal performance as quickly as possible. Need Immediate Assistance? • General concerns: Open a chat with our support bot and request to open a ticket for urgent cases. • If the Dashboard is inaccessible: Email us directly at [email protected]. We will provide another update within 30–60 minutes, or as soon as new information becomes available. Thank you for your patience.

  2. investigating Sep 01, 2026, 03:38 PM UTC

    Our team is continuing its investigation into the degraded performance affecting the Dashboard interface. In addition, recent telemetry shows that a small subset of hosted sites is also experiencing performance degradation. We are actively working to mitigate the impact and restore full functionality.

  3. investigating Sep 01, 2026, 03:56 PM UTC

    Our investigation indicates that accessibility and performance issues are affecting a subset of hosted sites in addition to the Dashboard. We are treating this as a critical incident, and our engineering team is actively working to isolate the cause and restore service. If you require immediate assistance and the Dashboard is inaccessible, please email us directly at [email protected]. Thank you for your patience while we work to resolve this.

  4. identified Sep 01, 2026, 04:20 PM UTC

    We have identified the root cause of the issue and are actively applying a fix. Telemetry is showing performance improvements across the Dashboard and affected sites. If the Dashboard remains inaccessible and you require immediate assistance, please email us directly at [email protected]. We will share another update shortly as services continue to recover.

  5. identified Sep 01, 2026, 04:27 PM UTC

    Telemetry graphs continue to show steady performance recovery across all impacted services. We are adjusting component statuses to Degraded Performance and actively monitoring systems as they normalize. For urgent assistance, email [email protected].

  6. identified Sep 01, 2026, 05:40 PM UTC

    Most products have recovered and performance is normalizing. Our engineering team is actively validating a few remaining product impacts. For urgent assistance or Dashboard access issues, please contact [email protected].

  7. identified Sep 01, 2026, 06:43 PM UTC

    Our engineering team continues working to resolve the issue across the remaining impacted components. Overall performance across most services continues to improve, and we are actively working toward full recovery. If you are experiencing persistent issues or cannot access the Dashboard, please email us directly at [email protected].

  8. identified Sep 01, 2026, 07:33 PM UTC

    Following remediation efforts, telemetry graphs show that all platform components and hosted sites have recovered to normal operational levels. We have shifted the incident status to Monitoring while our engineering team closely tracks system health and performance. If you encounter persistent issues or the Dashboard remains inaccessible, please reach out directly to [email protected].

  9. monitoring Sep 01, 2026, 08:37 PM UTC

    A fix has been implemented and we are monitoring the results.

  10. resolved Sep 01, 2026, 08:37 PM UTC

    This incident has been resolved.