Everything operating normally.
GitHub Status
@githubstatus
githubstatus.comSeit August 2012 bei Twitter
Posts von GitHub Status
We continue working on the recovery of our services.
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've been under continuous DDoS attack for 24+ hours. The attack is evolving, and we're all hands on deck mitigating.
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 are investigating reports of service unavailability.
The majority of restore processes have completed. We anticipate all data stores will be fully consistent within the next hour.
The site is recovering. We're continuing to monitor the situation.
Into hour 71 defending the attack. Mitigation is holding and service is stable.
We are investigating reports of degraded performance for GitHub Actions.
GitHub Pages is experiencing degraded performance. We are still investigating and will provide an update when we have one.
We are investigating issues with our CDN rendering static assets. We are monitoring progress and will provide updates when we have them.
We have identified the source of errors and are working on a fix.
Investigating: We are currently experiencing an outage of GitHub products and are investigating. stspg.io/14946fbbn6n7?u
We are investigating elevated error rates.
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'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.
Everything operating normally.
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 degraded performance for GitHub Actions, Issues, and Pull Requests.
Currently investigating increased error rate.
We are investigating reports of increased error rates and webhook delivery times.
We are continuing work to repair a data storage system for GitHub.com. You may see inconsistent results during this process.
Everything operating normally.
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.
We continue to investigate elevated errors and timeouts across GitHub services
Work continues on the recovery of our services.
Webhooks is experiencing degraded performance. We are continuing to investigate.
All systems reporting at 100%. Attack traffic continues, so we remain on high alert.
We continue to monitor restores which are taking longer than anticipated. We estimate they will be caught up in an hour and a half.
We are continuing to investigate reports of issues affecting a number of services. bit.ly/32B2dr8?utm_ts
Pull Requests is experiencing degraded performance. We are continuing to investigate.
Our restore operations are proceeding as expected, on track for serving fully consistent data within the next 1.5 hours.
We have rolled out a fix and are monitoring recovery.
We have identified a source for the elevated errors and are working on mitigation.
We are failing over a data service, you may experience exceptions and delay while receiving notifications. Apologies for the inconvenience.
GitHub Actions, Issues, and Pull Requests are now experiencing degraded availability. We are continuing to investigate.
We are validating the consistency of information across all data stores. Webhooks and Pages builds remain paused.
We have migrated to an unaffected DNS provider. Some users may experience problems with cached results as the change propagates.
API Requests is experiencing degraded availability. We are still investigating and will provide an update when we have one.
A global event is affecting an upstream DNS provider. GitHub services may be intermittently available at this time.
For a period of time today (~3 hours), some of our servers recorded incorrect time zone information during a routine update. We’ve remediated the issue and are currently working to correct any inaccurate timestamps. Apologies for any issues this may have caused.
GitHub.com is down for a scheduled database upgrade. We expect to be back in 15 minutes.
���We are investigating reports of degraded performance and increased error rates.”. githubstatus.com/incidents/j597
We are investigating reports of degraded performance.
We have discovered the source of the errors and have just rolled out a potential fix. We are now monitoring recovery and will update soon.
Codespaces is experiencing degraded availability. We are continuing to investigate.
Git Operations is experiencing degraded performance. We are continuing to investigate.
We've discovered the issue causing connectivity failures and are remediating.
We identified the cause of the problem and are working on remediation.
