4 ms·
https://www.githubstatus.com/incidents/52z0j6phhnjs https://www.githubstatus.com/incidents/52z0j6phhnjs
by MattIPv4 4y ago
https://www.githubstatus.com/incidents/52z0j6phhnjs https://www.githubstatus.com/incidents/52z0j6phhnjs
- tyingq 4y agoSeems better done than a lot of status pages, runs on separate infra, updated, has a way to subscribe, etc. However, saying "degraded performance" when you know it's "down for everyone" is an industry phrasing thing that's irritating. AWS also has "elevated response times" when everyone is seeing 5xx errors, or infinite response times.
- MattIPv4 4y agoFor what it's worth, it's powered by statuspage.io, which is relatively industry standard for status pages.
- kachnuv_ocasek 4y agoIt's not down for everyone. I can browse just fine, but my pushes get rejected, so that qualifies as "degraded performance" for me.
- tyingq 4y agoIt's got many named granular services marked as "degraded performance" or "degraded availability" that seemed to be down for everyone.
- pizza234 4y agoIt seems accurate to me - after some time, several "degraded performance" flags have been changed to "major outage".
- glogla 4y ago> However, saying "degraded performance" when you know it's "down for everyone" is an industry phrasing thing that's irritating. AWS also has "elevated response times" when everyone is seeing 5xx errors, or infinite response times. Another popular one is "elevated API error rates" when the error rate is 1.
- efficax 4y agohaving been on the other side a number of times at a site with huge amounts of traffic, very often things can be down for a huge percentage but our logs will still show thousands of requests succeeding a minute. so it might be working well but slowly for some while not at all for many