4 ms·

Have anyone checked out the status page? It's actually way worse than I thought, I believe this is the first time I am actually witnessing a status page with tr

Have anyone checked out the status page? It's actually way worse than I thought, I believe this is the first time I am actually witnessing a status page with truly horrible results. https://mrshu.github.io/github-statuses https://mrshu.github.io/github-statuses

apetresc 7mo ago
Well then clearly you haven't taken a look at https://status.claude.com https://status.claude.com.
- bombcar 7mo ago
  This is ... surprisingly honest? The one above is "missing" status page; and most status pages would legally have to be filed in the "fiction" section of the library.
- dathinab 7mo ago
  At that 3rd party side GH is currently noticeable worse then claude ... Like they are down to one 9 availability and very very close to losing that to (90.2x%). This also fit more closely to my personal experience, then the 99.900-99.989 range the article indicates... Through honestly 99.9% means 8.76h downtime a year, if we say no more then 20min down time per 3 hours (sliding window), and no more then 1h a day, and >50% downtime being (localized) off-working hours (e.g. night, Sat,Sun) then 99.9% is something you can work with. Sure it would sometimes be slightly annoying. But should not cause any real issues. On the other hand 90.21%... That is 35.73h outage a year. Probably still fine if for each location the working hour availability is 99.95% and the previous constraints are there. But uh, wtf. that just isn't right for a company of that size.
  - kbelder 7mo ago
    You may have fumbled the calculator at one point. 20Min per 3 hours is 88.8% uptime. 99.9% uptime is 11 seconds down.
    - dathinab 7mo ago
      what I meant is having both at the same time - at most 20min per 3 hour - and 99.9% uptime on a yearly basis as in your yearly budged of outage is ~8.76h but that budged shouldn't happen all at once and if there is an outage it at most delays works by 20min at a time, and not directly again after you had a downtime but I did fumble the 90.21% part, which is ~35.73 days i.e. over 857 hours....
  - zahlman 7mo ago
    > On the other hand 90.21%... That is 35.73h outage a year. Days, not hours.
- ctmnt 7mo ago
  I get the email notifications from Anthropic’s status monitor, and I think they might be my most frequent emailer these days.
Octoth0rpe 7mo ago
And notably, that page makes this post's title inaccurate. As of this morning, it says `90.21% uptime`, which is a _single_ 9, not 3 (though that's for the platform as a whole, no individual component appears to achieve three 9s.)
- mminer237 7mo ago
  Note that it gets 90% largely off Copilot going down and Actions not working. Actual git has 98.98%, which is still just one 9 but a lot better.
  - PunchyHamster 7mo ago
    > 98.98% it's the 2 nines they aimed for
    - maverwa 7mo ago
      True! Technically even 9.99% would be three nines!
    - franktankbank 7mo ago
      Too bad they didn't find an irrational number, could have got infinite nines.
  - sc68cal 7mo ago
    As someone who was impacted by GitHub's git outage in late February, which caused us to cancel a feature release, I am more sensitive to the availability of their git service, than their chatbot.
  - maccard 7mo ago
    If all I want is actual git, I’m pretty sure I could get much much more than 98.98% uptime. The value of GitHub is actions, issues, PRs. To me, if actions is down GitHub is down
- graypegg 7mo ago
  Hey! At least that single 9 is in the ten's place. /sarcastic
raincole 7mo ago
It looks this bad because that includes 'degraded performance,' not just outrage.
- NooneAtAll3 7mo ago
  freudian slip
- ecshafer 7mo ago
  Degraded Performance is unavailable as far as I am concerned. If Github has "degraded performance" where it takes 5 minutes to load a PR then that is not good.
ruszki 7mo ago
Especially compared to its archive page: https://web.archive.org/web/20190510070456/https://www.githubstatus.com/ https://web.archive.org/web/20190510070456/https://www.githu... 1-4 incidents per month compared to about 1 daily.

apetresc 7mo ago

Well then clearly you haven't taken a look at https://status.claude.com https://status.claude.com.

bombcar 7mo ago
This is ... surprisingly honest? The one above is "missing" status page; and most status pages would legally have to be filed in the "fiction" section of the library.
dathinab 7mo ago
At that 3rd party side GH is currently noticeable worse then claude ... Like they are down to one 9 availability and very very close to losing that to (90.2x%). This also fit more closely to my personal experience, then the 99.900-99.989 range the article indicates... Through honestly 99.9% means 8.76h downtime a year, if we say no more then 20min down time per 3 hours (sliding window), and no more then 1h a day, and >50% downtime being (localized) off-working hours (e.g. night, Sat,Sun) then 99.9% is something you can work with. Sure it would sometimes be slightly annoying. But should not cause any real issues. On the other hand 90.21%... That is 35.73h outage a year. Probably still fine if for each location the working hour availability is 99.95% and the previous constraints are there. But uh, wtf. that just isn't right for a company of that size.
- kbelder 7mo ago
  You may have fumbled the calculator at one point. 20Min per 3 hours is 88.8% uptime. 99.9% uptime is 11 seconds down.
  - dathinab 7mo ago
    what I meant is having both at the same time - at most 20min per 3 hour - and 99.9% uptime on a yearly basis as in your yearly budged of outage is ~8.76h but that budged shouldn't happen all at once and if there is an outage it at most delays works by 20min at a time, and not directly again after you had a downtime but I did fumble the 90.21% part, which is ~35.73 days i.e. over 857 hours....
- zahlman 7mo ago
  > On the other hand 90.21%... That is 35.73h outage a year. Days, not hours.
ctmnt 7mo ago
I get the email notifications from Anthropic’s status monitor, and I think they might be my most frequent emailer these days.

Octoth0rpe 7mo ago

And notably, that page makes this post's title inaccurate. As of this morning, it says `90.21% uptime`, which is a _single_ 9, not 3 (though that's for the platform as a whole, no individual component appears to achieve three 9s.)

mminer237 7mo ago
Note that it gets 90% largely off Copilot going down and Actions not working. Actual git has 98.98%, which is still just one 9 but a lot better.
- PunchyHamster 7mo ago
  > 98.98% it's the 2 nines they aimed for
  - maverwa 7mo ago
    True! Technically even 9.99% would be three nines!
  - franktankbank 7mo ago
    Too bad they didn't find an irrational number, could have got infinite nines.
- sc68cal 7mo ago
  As someone who was impacted by GitHub's git outage in late February, which caused us to cancel a feature release, I am more sensitive to the availability of their git service, than their chatbot.
- maccard 7mo ago
  If all I want is actual git, I’m pretty sure I could get much much more than 98.98% uptime. The value of GitHub is actions, issues, PRs. To me, if actions is down GitHub is down
graypegg 7mo ago
Hey! At least that single 9 is in the ten's place. /sarcastic

raincole 7mo ago

It looks this bad because that includes 'degraded performance,' not just outrage.

NooneAtAll3 7mo ago
freudian slip
ecshafer 7mo ago
Degraded Performance is unavailable as far as I am concerned. If Github has "degraded performance" where it takes 5 minutes to load a PR then that is not good.

ruszki 7mo ago

Especially compared to its archive page: https://web.archive.org/web/20190510070456/https://www.githubstatus.com/ https://web.archive.org/web/20190510070456/https://www.githu... 1-4 incidents per month compared to about 1 daily.