News for hackers. Stuff that matters.

A comment on Another GitHub outage in the same day.

Re:Another GitHub outage in the same day by ChrisArchitect on Monday February 09, 2026 @03:24PM (#46950686)
[dupe] Earlier: https://news.ycombinator.com/item?id=46946827
[ Parent | on HN ]
Re:Another GitHub outage in the same day by rpns on Monday February 09, 2026 @03:57PM (#46951178)
Not quite, that one is an earlier outage while this one started at (or a bit before) 19:01 UTC.

The history for today is a bit of a mess really: https://www.githubstatus.com/history

[ Parent | on HN ]
Re:Another GitHub outage in the same day by ChrisArchitect on Monday February 09, 2026 @04:51PM (#46952001)
They are all being discussed in that thread, the submitted url is just one of the various incident links on the day. Duplicate discussion.
[ Parent | on HN ]
Re:Another GitHub outage in the same day by esafak on Monday February 09, 2026 @03:57PM (#46951169)
No, it's a new outage -- that's the point! -- check the URLs.
[ Parent | on HN ]
Re:Another GitHub outage in the same day by ChrisArchitect on Monday February 09, 2026 @04:52PM (#46952008)
That's not the point. The point is it's a duplicate discussion of one of a number of incident links being discussed, all over there.
[ Parent | on HN ]
Re:Another GitHub outage in the same day by bigstrat2003 on Monday February 09, 2026 @07:58PM (#46953919)
The point is that when a second, independent event occurs, a new thread is not a duplicate.
[ Parent | on HN ]
Re:Another GitHub outage in the same day by rcakebread on Monday February 09, 2026 @09:33PM (#46954613)
I'll bet you're fun at... nowhere.
[ Parent | on HN ]