Please turn JavaScript on

GitHub Status - Incident History

Receive updates from GitHub Status - Incident History for free, starting right now.

We can deliver them by email, via your phone or you can read them from a personalised news page on follow.it.

This way you won't miss any new article from GitHub Status - Incident History. Unsubscribe at any time.

Site title: GitHub Status

Is this your feed? Claim it!

Publisher:  Unclaimed!
Message frequency:  0.85 / day

Message History

Aug 13, 16:21 UTC
Update - GHEC Team Sync is currently degraded for enterprises with personal accounts, causing delays when syncing teams to IdP groups. We have identified the cause of the delays and are working on a mitigation. We will provide an update on our progress at 20:00 UTC.

Aug 13, 16:21 UTC
Investigating - We ...


Read full story

Aug 13, 15:47 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Aug 13, 15:47 UTC
Update - The issues with our upstream model provider have been resolved, and Fable 5 is once a...


Read full story

Aug 13, 15:36 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Aug 13, 15:33 UTC
Update - We have temporarily disabled a background job which caused the impact. At this time t...


Read full story

Aug 12, 22:22 UTC
Update - We have identified the root cause and are working on mitigation. Errors on the login page and downloading release assets have decreased, but we are not fully mitigated. We will continue to provide updates.

Aug 12, 21:43 UTC
Update - We are investigating issues with Login and when downloading Re...


Read full story

Aug 12, 16:24 UTC
Update - We are investigating reports of errors affecting Pull Requests and Issues on GitHub.com. Some users may encounter 500 errors when loading pull request and issue pages. Our engineering teams are actively investigating the root cause, which appears to be related to a database infrastructure issue. We will provide an update as s...


Read full story