[2025-10-09] Incident Thread #176345
-
❗ An incident has been declared:Incident with Webhooks Subscribe to this Discussion for updates on this incident. Please upvote or emoji react instead of commenting +1 on the Discussion to avoid overwhelming the thread. Any account guidance specific to this incident will be shared in thread and on the Incident Status Page. |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 1 reply
-
UpdateWe are investigating widespread reports of delays and increased latency in various services. We will continue to keep users updated on progress toward mitigation. |
Beta Was this translation helpful? Give feedback.
-
UpdateWe identified a faulty network component and have removed it from the infrastructure. Recovery has started and we expect full recovery shortly. |
Beta Was this translation helpful? Give feedback.
-
UpdateWe are seeing full recovery in many of our systems, but delays are still expected for actions. We will continue to update as the system is fully restored to normal operation. |
Beta Was this translation helpful? Give feedback.
-
UpdateActions and Notifications are still experiencing delays as we process the backlog. We will continue to update as the system is fully restored to normal operation. |
Beta Was this translation helpful? Give feedback.
-
UpdateActions has fully recovered but Notifications is still experiencing delays. We will continue to update as the system is fully restored to normal operation. |
Beta Was this translation helpful? Give feedback.
-
|
Is there a related GitHub pages incident too? https://github.com/danielhjacobs/danielhjacobs.github.io/actions/runs/18382369347/job/52372055513 Running for 8 minutes now, still Current status: deployment_queued Edit: Finished now after 9 minutes |
Beta Was this translation helpful? Give feedback.
-
UpdateAll services have fully recovered. |
Beta Was this translation helpful? Give feedback.
-
Incident ResolvedThis incident has been resolved. |
Beta Was this translation helpful? Give feedback.

Incident Resolved
This incident has been resolved.