4 ms·
Yeah, we're still facing issues with, erm, Github issues. Also, while they haven't updated this blog post for a while, their status page has been very up-to-da
by shashwat986 8y ago
Yeah, we're still facing issues with, erm, Github issues.
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 https://status.github.com/messages
- AdamJacobMuller 8y ago> 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.
- lol768 8y agoI 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.
- LeoNatan25 8y agoEvery hour they promise something will be done until the next hour. I haven’t been able to work all day so far.
- Piskvorrr 8y agoConsider 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.)
- LeoNatan25 8y agoYes, 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.
- cotillion 8y agoThe 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...
- bauerd 8y agoYeah but their recovery estimates were completely off. Pulls, hooks, checks and issues still are unusable
- LeoNatan25 8y agoReleasss and gh pages are still completely broken too.