Yeah but their recovery estimates were completely off. Pulls, hooks, checks and issues still are unusable
Re:GitHub: October 21 Incident Report
by LeoNatan25 on Monday October 22, 2018 @08:36AM
(#18274102)
Releasss and gh pages are still completely broken too.
Re:GitHub: October 21 Incident Report
by AdamJacobMuller on Monday October 22, 2018 @07:57AM
(#18273900)
> very up-to-date and informative
Is that satire? It said 2-hour ETA 5 hours ago and the last update was over two hours ago.
I see an update 7 minutes ago.
>12:56 British Summer Time
>The majority of restore processes have completed. We anticipate all data stores will be fully consistent within the next hour.
Re:GitHub: October 21 Incident Report
by LeoNatan25 on Monday October 22, 2018 @08:36AM
(#18274096)
Every hour they promise something will be done until the next hour. I haven’t been able to work all day so far.
Consider this a lesson on serverlessness. (We have been similarly afflicted, but their git backend seems to be up; and even further, we have rediscovered what we stopped paying attention to: that with Git, a centralized repo is just a convenience, not a requirement.)
Re:GitHub: October 21 Incident Report
by LeoNatan25 on Monday October 22, 2018 @11:49AM
(#18275638)
Yes, I agree, but here it’s not up to me to choose the infrastructure.
I wonder what the total cost of this ordeal must be. Surely in the tens of millions.
The latest message appears to be:
"We are validating the consistency of information across all data stores. Webhooks and Pages builds remain paused."
Which is a bit scary. Half my requests appear to hit some storage which is still many hours behind. They should be seeing that...
Also, while they haven't updated this blog post for a while, their status page has been very up-to-date and informative: https://status.github.com/messages