Didn't Github comment on their blog recently [1] on how they were improving and reducing failure detection times? Doesn't speak well for them if it's first on Hacker News and not their own Status page.
tl;dr; > One of the biggest customer-facing effects of this delay was that status.github.com wasn't set to status red until 00:32am UTC, eight minutes after the site became inaccessible. We consider this to be an unacceptably long delay, and will ensure faster communication to our users in the future.
EDIT: "We're investigating some issues with our databases".
StanAngeloff|9 years ago
tl;dr; > One of the biggest customer-facing effects of this delay was that status.github.com wasn't set to status red until 00:32am UTC, eight minutes after the site became inaccessible. We consider this to be an unacceptably long delay, and will ensure faster communication to our users in the future.
EDIT: "We're investigating some issues with our databases".
[1] https://github.com/blog/2106-january-28th-incident-report
griffinheart|9 years ago
tauchunfall|9 years ago
Update:
>10:03 CEST "Everything operating normally."
eterm|9 years ago
chris_wot|9 years ago
Nandiin|9 years ago