Degraded Dashboard and Terminus Performance

What to do

• Check whether you use Pantheon Dashboard, Terminus Operations. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1d 11h it lasted.

  Anything that failed between 2026-03-26 12:22 UTC and 2026-03-27 23:41 UTC may need a replay.

• Subscribe to Pantheon's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=pantheon works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Pantheon 13

1. investigatingMar 26, 2026, 12:22 PM UTC

   We're currently investigating an issue affecting the loading of the Dashboard and Terminus-related workflows. We apologize for any inconvenience this has caused. If you're experiencing an urgent issue, please contact support at helpdesk@pantheon.io

   provider

2. investigatingMar 26, 2026, 1:18 PM UTC

   We are continuing to investigate this issue.

   provider

3. investigatingMar 26, 2026, 2:36 PM UTC

   Our team is still actively investigating the issue. Thank you for your patience.

   provider

4. investigatingMar 26, 2026, 4:15 PM UTC

   We are continuing to investigate the issue affecting Dashboard performance and Terminus workflows. If you're experiencing any related issues, please reach out to Support via chat or ticket, and our team will investigate immediately. We will provide another update within the next 30 minutes to an hour or as soon as more details become available.

   provider

5. investigatingMar 26, 2026, 6:11 PM UTC

   Our Engineering team is actively investigating the issue. We will provide another update within the next 2-3 hours or sooner if new information becomes available. Thank you for your continued patience and understanding.

   provider

6. investigatingMar 26, 2026, 10:54 PM UTC

   We are continuing to work on a fix for this issue with the Dashboard and Terminus-related workflows. We will share another update in 2 to 3 hours, or as soon as more information becomes available.

   provider

7. investigatingMar 27, 2026, 2:15 AM UTC

   We are continuing to investigate the issue. Thank you for your patience and understanding.

   provider

8. investigatingMar 27, 2026, 8:27 AM UTC

   We are still investigating the issue. We will post another update in 3 hours or once a major update is available.

   provider

9. investigatingMar 27, 2026, 12:16 PM UTC

   No major updates. We are still investigating the issue. We will post another update in 3 hours or once a major update is available.

   provider

10. investigatingMar 27, 2026, 3:16 PM UTC

    We understand the urgency, and our Engineers remain fully focused on this case. While there are no major developments yet, we are actively testing potential fixes. Expect our next update in 3 hours.

    provider

11. investigatingMar 27, 2026, 5:53 PM UTC

    Performance has improved but remains above the pre-incident baseline. We have transitioned this case from Resolved back to Investigating as a precaution. All internal team code deployments are currently on hold to ensure platform stability. Our Engineering teams are performing a deep dive into core data storage performance and asynchronous job runner behavior to isolate the root cause. Multiple teams are dedicated to a real-time synchronized response to return latency to normal levels. Next Update: In 2-3 hours, or as soon as a significant change in status occurs.

    provider

12. identifiedMar 27, 2026, 10:11 PM UTC

    The issue has been identified and a fix is being implemented.

    provider

13. resolvedMar 27, 2026, 11:41 PM UTC

    This incident has been resolved. All Dashboard and Terminus operations are operational now.

    provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.