GitHub Status
GitHub Status
5,064 posts
GitHub Status’s posts
We continue working on the recovery of our services.
We are experiencing interruptions in multiple public GitHub services. We suspect the impact is due to a database infrastructure related change that we are working on rolling back.
We are investigating reports of increased errors and slow page load.
After 113 hours of sustained DDoS attacks our defenses are holding. We will keep our status at yellow until the threat has subsided.
We are investigating reports of issues with a number of services. bit.ly/2ObDBSA?utm_ts
We have identified the source of elevated errors and are working on recovery.
Everything operating normally.
We're investigating errors affecting most GitHub services. We're actively investigating and will provide an update as soon as possible.
We have identified the source of elevated errors and are working on recovery.
All GitHub services are back to normal as of Monday (October 22) at 23:00 UTC. We’ve posted an update at blog.github.com/2018-10-22-inc.
We've been under continuous DDoS attack for 24+ hours. The attack is evolving, and we're all hands on deck mitigating.
We are investigating reports of service unavailability. bit.ly/3aDqCQH?utm_ts
We are investigating reports of degraded performance for GitHub Actions.
We are investigating issues with our CDN rendering static assets. We are monitoring progress and will provide updates when we have them.
Investigating: We are currently experiencing an outage of GitHub products and are investigating. stspg.io/14946fbbn6n7?u
The majority of restore processes have completed. We anticipate all data stores will be fully consistent within the next hour.
We are investigating elevated error rates.
Into hour 71 defending the attack. Mitigation is holding and service is stable.
We are investigating reports of issues with GitHub.com and GitHub API. We will continue to keep users updated on progress towards mitigation.
GitHub Pages is experiencing degraded performance. We are still investigating and will provide an update when we have one.
We have identified the source of errors and are working on a fix. bit.ly/2VQFCUZ?utm_ts
We've turned off TLS v1.0 and v1.1 for the next hour as we move toward permanently disabling them. Check out githubengineering.com/crypto-removal to learn more about our plans to deprecate weak crypto standards.
We are currently in the later stages of a restore operation, with the aim of serving fully consistent data within the next 2 hours.
We are investigating reports of degraded performance for GitHub Actions, Issues, and Pull Requests.
87 hours in, our mitigation is deflecting most attack traffic. We're aware of intermittent issues and continue to adapt our response.
We are investigating reports of increased error rates and webhook delivery times. bit.ly/32f6aC7?utm_ts
We are continuing work to repair a data storage system for GitHub.com. You may see inconsistent results during this process.
Everything operating normally.
Work continues on the recovery of our services.
We are investigating reports of degraded availability for Issues and Pull Requests
We are investigating reports of degraded availability for Actions, Pages and Pull Requests
We continue to investigate elevated errors and timeouts across GitHub services
Our restore operations are still on track to serve consistent data within the hour. We've posted an update at blog.github.com/2018-10-21-oct.
Our services are recovering.
Pull Requests is experiencing degraded performance. We are continuing to investigate.
Webhooks is experiencing degraded performance. We are continuing to investigate.