We continue working on the recovery of our services. githubstatus.com/incidents/j…
102
193
558
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. githubstatus.com/incidents/k…
105
123
441
109,046
We are investigating reports of increased errors and slow page load. githubstatus.com/incidents/d…
84
132
353
After 113 hours of sustained DDoS attacks our defenses are holding. We will keep our status at yellow until the threat has subsided.
31
398
281
We are investigating reports of issues with a number of services. bit.ly/2ObDBSA?utm_ts=156381…
69
134
283
We have identified the source of elevated errors and are working on recovery. githubstatus.com/incidents/d…
58
68
287
Everything operating normally. githubstatus.com/incidents/j…
10
90
292
We are investigating degradations to GitHub.com. bit.ly/3aq2gce?utm_ts=158748…
33
107
280
We're investigating errors affecting most GitHub services. We're actively investigating and will provide an update as soon as possible. githubstatus.com/incidents/r…
37
94
245
We're investigating connectivity problems on github.com.
40
267
227
We have identified the source of elevated errors and are working on recovery. githubstatus.com/incidents/j…
45
95
217
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-i….
16
114
224
We've been under continuous DDoS attack for 24+ hours. The attack is evolving, and we're all hands on deck mitigating.
41
611
199
We are investigating reports of service unavailability. bit.ly/3aDqCQH?utm_ts=158585…
41
61
202
We're working to address a widespread issue affecting all github.com services.
50
169
171
We are investigating reports of degraded performance for GitHub Actions. githubstatus.com/incidents/r…
62
37
171
We are investigating issues with our CDN rendering static assets. We are monitoring progress and will provide updates when we have them.
22
53
174
Investigating: We are currently experiencing an outage of GitHub products and are investigating. stspg.io/14946fbbn6n7?u=ry1x…
47
56
162
60,074
The majority of restore processes have completed. We anticipate all data stores will be fully consistent within the next hour.
32
61
164
We are investigating elevated error rates. githubstatus.com/incidents/y…
14
55
161
We are investigating reports of issues with GitHub.com and GitHub API. We will continue to keep users updated on progress towards mitigation. githubstatus.com/incidents/k…
49
45
160
26,864
GitHub Pages is experiencing degraded performance. We are still investigating and will provide an update when we have one. githubstatus.com/incidents/r…
34
35
142
We have identified the source of errors and are working on a fix. bit.ly/2VQFCUZ?utm_ts=158764…
38
46
149
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… to learn more about our plans to deprecate weak crypto standards.
8
69
140
We are currently in the later stages of a restore operation, with the aim of serving fully consistent data within the next 2 hours.
17
101
146
We are investigating reports of degraded performance for GitHub Actions, Issues, and Pull Requests. githubstatus.com/incidents/f…
35
21
126
We're continuing to investigate a significant network disruption affecting all github.com services.
16
230
127
Currently investigating increased error rate. bit.ly/2TeiRsN?utm_ts=158264…
24
44
123
87 hours in, our mitigation is deflecting most attack traffic. We're aware of intermittent issues and continue to adapt our response.
17
222
118
We are investigating reports of increased error rates and webhook delivery times. bit.ly/32f6aC7?utm_ts=158212…
49
36
115
We are continuing work to repair a data storage system for GitHub.com. You may see inconsistent results during this process.
44
69
114
Everything operating normally. githubstatus.com/incidents/d…
9
22
108
Work continues on the recovery of our services. githubstatus.com/incidents/j…
29
35
106
We are investigating reports of degraded availability for Issues and Pull Requests githubstatus.com/incidents/n…
32
18
107
20,028
We are investigating reports of degraded availability for Actions, Pages and Pull Requests githubstatus.com/incidents/k…
34
27
111
28,044
We continue to investigate elevated errors and timeouts across GitHub services
githubstatus.com/incidents/8…
25
47
106
We're investigating a significant network disruption affecting all github.com services.
25
169
91
We are investigating 500 error happening on github.com page.
10
35
102
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-o….
18
67
102
We are investigating errors when visiting github.com. bit.ly/2Dfz8Gu?utm_ts=157465…
3
83
99
Our services are recovering. githubstatus.com/incidents/d…
8
15
98
Pull Requests is experiencing degraded performance. We are continuing to investigate. githubstatus.com/incidents/s…
46
36
91
We are investigating issues loading stylesheets on GitHub.com.
15
42
85
Webhooks is experiencing degraded performance. We are continuing to investigate. githubstatus.com/incidents/r…
58
22
81
We continue to monitor restores which are taking longer than anticipated. We estimate they will be caught up in an hour and a half.
33
38
86
We have rolled out a fix and are monitoring recovery. bit.ly/3aDqCQH?utm_ts=158586…
7
18
84
We are failing over a data service, you may experience exceptions and delay while receiving notifications. Apologies for the inconvenience.
24
99
84
We are continuing to investigate reports of issues affecting a number of services. bit.ly/32B2dr8?utm_ts=156381…
31
42
81
We have identified a source for the elevated errors and are working on mitigation. bit.ly/3aq2gce?utm_ts=158748…
5
18
84
The database infrastructure change is being rolled back. We are seeing improvements in service health and are monitoring for full recovery. githubstatus.com/incidents/k…
11
25
84
11,483
Our restore operations are proceeding as expected, on track for serving fully consistent data within the next 1.5 hours.
18
23
87
API Requests is experiencing degraded availability. We are still investigating and will provide an update when we have one. githubstatus.com/incidents/r…
17
13
77
GitHub Actions, Issues, and Pull Requests are now experiencing degraded availability. We are continuing to investigate. githubstatus.com/incidents/f…
26
38
81
Everything operating normally. bit.ly/2ObDBSA?utm_ts=156381…
5
10
76
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.
7
13
74
We are continuing to investigate degradations in GitHub.com services. bit.ly/3aq2gce?utm_ts=158748…
11
28
75
We are validating the consistency of information across all data stores. Webhooks and Pages builds remain paused.
37
42
74
Pages is experiencing degraded availability. We are continuing to investigate. githubstatus.com/incidents/k…
8
9
67
12,122
A global event is affecting an upstream DNS provider. GitHub services may be intermittently available at this time.
7
121
63
"We're seeing high error rates on github.com and are investigating".
33
238
65
We are investigating reports of degraded performance. githubstatus.com/incidents/p…
20
22
67
GitHub.com is down for a scheduled database upgrade. We expect to be back in 15 minutes.
31
215
66
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.
2
20
68
Everything operating normally. bit.ly/3aq2gce?utm_ts=158748…
5
10
64
Codespaces is experiencing degraded availability. We are continuing to investigate. githubstatus.com/incidents/r…
30
15
61
We have migrated to an unaffected DNS provider. Some users may experience problems with cached results as the change propagates.
2
30
63
We are investigating reports of increased API errors and webhook latency. bit.ly/2PqOWMU?utm_ts=158281…
28
32
66
���We are investigating reports of degraded performance and increased error rates.”. githubstatus.com/incidents/j…
5
34
63