MailgunEvent Log Delays in US Region
Event queues have caught up and events are processing normally.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
Event queues have caught up and events are processing normally.
Resolved
This incident has been resolved.
Resolved
Please refer to the combined summary in this related incident: https://www.githubstatus.com/incidents/y1t7p9fzrlj2
Resolved
Between 14:24 and 14:53 UTC on 13 August 2026, a routine background job to delete an organization overwhelmed a key shared database, causing multiple GitHub services to briefly return elevated errors and slower responses. Most affected was the webhook management API, with smaller impact to Git operations, pull requests, issues, packages, sign-in, and Copilot. Impact cleared on its own at about 14:53 UTC once the job finished; we resolved the incident at 15:36 UTC. <br /><br />Affected users may have experienced a brief increase in errors and slower responses, primarily when creating, listing, or updating webhooks, with smaller impacts to pull requests, issues, packages, and Git operations. Failures peaked at about 1% for several minutes around 14:37 UTC. <br /><br />To prevent future incidents, we've already shipped an update that turns on the safer deletion path for organizations, along with caps on deletion holds on databases. Building on these changes, we're auditing all bulk deletion and cleanup jobs that write to shared databases to prevent similar issues in future.
Resolved
The issue affecting Claude Code has been resolved. Impact occurred from 16∶55 to 19∶16 UTC.
Resolved
This incident is now resolved. Between 19:16 and 20:11 UTC, customers experienced request latency and timeouts affecting package downloads and API requests in the US East region. We have confirmed that these services have now returned to normal operations.
Resolved
All impacted services have now fully recovered.
Resolved
Project creation has returned to baseline consistently.
Resolved
Inbox behavior (Conversation Counts, SLAs, Routing, and Sentiment issue) is stable across the board, so we're closing this out. Thank you for your patience while we worked on this one!
Resolved
This incident has now been resolved and the service is now fully operational.
Resolved
This incident has been resolved.
Resolved
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. <b>Start time :</b> 31/08/2026 16:49 UTC <b>End time :</b> 31/08/2026 17:47 UTC <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Resolved
This issue has been resolved.
Resolved
This issue has been resolved.
Resolved
This incident has been resolved, and service is operating normally again. Thanks for your patience.
Resolved
This incident has been resolved, and all activities have caught up to realtime. Front will continue to monitor application performance.
Resolved
Full 8/25–8/27 recovery is complete. For the gates with no metrics attached, exposures for 8/25–8/27 should now be available in the warehouse!
Resolved
Response times have recovered in all regions. This issue is now resolved.
Resolved
The issue affecting user registrations and logins has been resolved. Normal system operations have resumed.
Resolved
A configuration update caused temporary failures for incoming HTTP/2 traffic for Fly Machines located on a subset of hosts for a few minutes. This incident has since been resolved. Managed Postgres depends on HTTP/2 and some control plane ops may have been affected as well. However, downstream Postgres connections were unlikely to have been affected by this since they do not use the HTTP2 handler.
Resolved
API performance has remained stable following mitigation. This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This degradation in delivery was limited to upstream testing infrastructure which has since recovered. There was no external impact.
Resolved
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We’ll mark this incident as resolved. Our ticketing system is operational again, though the outage materially affected its setup. We’re working with the team to restore full functionality, but capacity is sufficient to consider the incident resolved.
Resolved
The issue affecting syncing and editing content has been resolved. Performance has recovered and services are operating normally.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved and the affected services have been restored.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
Our team has resolved the issue impacting Australian customers trying to lodge tax returns in Xero Tax. This issue was due to an underlying product dependency with Xero Tax and our team worked to restore service. We apologise for any inconvenience this has caused.
Resolved
We experienced an issue with PLN payments. Clients may have seen delayed settlements. The issue is resolved, and payments are settling as normal. Impact start time: 30/08/2026, 23:55 UTC Impact end time: 31/08/2026, 00:47 UTC Client actions: None
Resolved
This issue is resolved now.
Resolved
We saw Sprite deletion jobs failing between 21:18 and 22:05 UTC. This issue has been resolved.
Resolved
ATO has resolved the issue causing errors for AU customers when using prefill or lodge tax returns from Xero Tax.
Resolved
The issue has been resolved.
Resolved