News for hackers. Stuff that matters.
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.

Re:GitHub: October 21 Incident Report by lol768 on Monday October 22, 2018 @08:03AM (#18273930)
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.
Re:GitHub: October 21 Incident Report by Piskvorrr on Monday October 22, 2018 @11:42AM (#18275565)
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.

Re:GitHub: October 21 Incident Report by cotillion on Monday October 22, 2018 @09:30AM (#18274450)
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...