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

GitHub was down

github.com

Post reply on HN
Print view View original

121–130 of 288 posts

Re: GitHub was down

#121

Post by damiankennedy »

damiankennedy wrote: post #87
damiankennedy wrote: post #67

Earlier quoted context omitted.

Update - We are investigating reports of issues with GitHub.com and GitHub API. We will continue to keep users updated on progress towards mitigation. Aug 14, 2024 - 23:16 UTC EDIT: The reply link is no longer available. Update - Packages is experiencing degraded availability. We are continuing to investigate. Aug 14, 2024 - 23:18 UTC

The reply link is now available? Update - Issues is experiencing degraded availability. We are continuing to investigate. Aug 14, 2024 - 23:19 UTC Update - Git Operations is experiencing degraded availability. We are continuing to investigate. Aug 14, 2024 - 23:19 UTC EDIT: The reply link is no longer available again.

The reply link is now available again?

Everything is red now. Nearly lunch time in New Zealand.

Re: GitHub was down

#124

Post by rhabarba »

waveBidder wrote: post #107
rhabarba wrote: post #78

I love how the same people who try to drag me towards using Git are the only people who seem to have serious problems working on their code when a website goes down.

Git is not the same thing as github. It's designed to be decentralized, even if it isn't getting used that way atm

I am quite familiar with the basic functionality of Git. However, I am always amused by how it works in practice.

Re: GitHub was down

#126

Post by xuancanh »

purkka wrote: post #69
sebmellen wrote: post #7

I've never seen an outage this big. Even the homepage doesn't load. We've had recurrent issues with Actions not running, but this seems a lot bigger. The status page says all is well, though: https://www.githubstatus.com/ . Hilarious.

I have to wonder how a company at the scale of GitHub can be so bad at keeping track of their status. Now 4 out of 10 services are marked as "Incident", yet most of the others are also completely dead.

It's because of the way most companies build their status dashboards. There are usually at least 2 dashboards, one internal dashboard and one external dashboard. The internal dashboard is the actual monitoring dashboard, where it will be hooked up with other monitoring data sources. The external status dashboard is just for customer communication. Only after the outage/degradation is confirmed internally, then the external dashboard will be updated to avoid flaky monitors and alerts. It will also affect SLAs so it needs multiple levels of approval to change the status, that's why there are some delays.

Re: GitHub was down

#127

Post by croemer »

dghlsakjg wrote: post #104

https://www.githubstatus.com/ This is a pretty good place to check. The lag is pretty minimal traditionally. At the time of posting everything is broken.

Not sure what you mean by minimal lag. The status page showed all green for at least 10min while everyone got unicorns.

Re: GitHub was down

#130

Post by bitbasher »

red_Seashell_32 wrote: post #108
bitbasher wrote: post #14

The timing is pretty uncanny. I just deployed a github page and had a DNS issue because I configured it wrong. I hit "check again" and github went down. Hope I don't appear in the incident report.

Wait. You use github pages for something or actually work on it?

I use it for something.

I had a github page that was public, but it was made private and the DNS config was removed. Fast forward to today. I made the private repo public again and forced a deploy of the page without making a new commit. It said the DNS config was incomplete, so I tweaked it and hit "check again" and github went down.

Probably unrelated, but the timing was spooky.

Post reply on HN