Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Disruption with Some GitHub Services – Resolved

githubstatus.com

Post reply on HN
Print view View original

51–60 of 176 posts

Re: Disruption with Some GitHub Services – Resolved

#52

Post by zaik »

tomw1808 wrote: post #36

Things can go wrong, but really, its been a lot and we're normalizing that to an unhealthy degree... I wonder if it was down that much, if users would get credits the way we pay when we use the services - its kind of ridiculous for a critical service to be down that much and all we do is "ah okay, its just github". Like, as if that was normal to be down that much...

I think the authors of SMTP had a healthy attitude towards server uptimes:

   Retries continue until the message is transmitted or the sender gives
   up; the give-up time generally needs to be at least 4-5 days.
https://datatracker.ietf.org/doc/html/rfc5321#section-4.5.4....

Re: Disruption with Some GitHub Services – Resolved

#53

Post by lbriner »

weli wrote: post #17
nr378 wrote: post #10

GitHub needs to completely bifurcate their enterprise/paid services from their free services at the infra level.

That's what I don't understand. They could mitigate their name so much if they just split free/paid/enterprise. It's already shown that enterprise is much more estable and is largely unaffected from service disruptions. Why don't they go one more layer? For sure it's worth the extra complexity.

There is no such thing as "just split" there is 20+ years of legacy decisions and even if the split is relatively clean it is still probably 1 years work for 200 people for maybe a marginal improvement.

The real money is going to go towards, "make this all more reliable".

Re: Disruption with Some GitHub Services – Resolved

#54

Post by roastedfunction »

sdetheridge wrote: post #19
nr378 wrote: post #10

GitHub needs to completely bifurcate their enterprise/paid services from their free services at the infra level.

According to their status pages (e.g. https://eu.githubstatus.com/ , https://us.githubstatus.com/ ), their Enterprise Cloud uptime for Actions is significantly higher.

“GitHub Enterprise Cloud with data residency” is hosted on separate infrastructure and dedicated subdomains under *.ghe.com. It’s been around since November 2024z

It’s not the same thing as GitHub Enterprise Cloud hosted on the shared global network on github.com.

https://docs.github.com/en/enterprise-cloud@latest/admin/dat...

Re: Disruption with Some GitHub Services – Resolved

#58

Post by vinnymac »

frenchie4111 wrote: post #11

I noticed earlier this week that my URL bar now pre-fills githubstatus.com instead of github.com when I type "gith"

For me this started happening when I type "stat" too.

Which surprised me because of the many hundreds of services I rely on regularly that also have status pages.

Re: Disruption with Some GitHub Services – Resolved

#59

Post by SingularCrane »

isaacdl wrote: post #48
98codes wrote: post #41

Earlier quoted context omitted.

Certificate expired over 100 days ago

Where do you see that? Common Name (CN) www.dayswithoutgithubincident.com Organization (O) Common Name (CN) YR1 Organization (O) Let's Encrypt Issued On Monday, August 10, 2026 at 10:01:51 AM Expires On Sunday, November 8, 2026 at 9:01:50 AM

also seeing an expired cert:

    Common Name
    R12
    Validity
    Not Before
    Tue, 10 Feb 2026 17:28:52 GMT
    Not After
    Mon, 11 May 2026 17:28:51 GMT

Re: Disruption with Some GitHub Services – Resolved

#60

Post by vinnymac »

sdetheridge wrote: post #19
nr378 wrote: post #10

GitHub needs to completely bifurcate their enterprise/paid services from their free services at the infra level.

According to their status pages (e.g. https://eu.githubstatus.com/ , https://us.githubstatus.com/ ), their Enterprise Cloud uptime for Actions is significantly higher.

Just to be clear, I am on Github Enterprise, and am also experiencing this disruption both privately and publicly on every org and project I have access to.
Post reply on HN