|
|
|
|
|
by StanAngeloff
3685 days ago
|
|
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". [1] https://github.com/blog/2106-january-28th-incident-report |
|