Remix.run Logo
▲ mkagenius 2 days ago

Why doesn't https://www.githubstatus.com reflect this accurately?

I usually check this and then doubt my network might be at fault if they don't show outages.

▲skissane 2 days ago | parent | next [-]

I think that page only displays outages if some manager at GitHub decides it is "sufficiently major" to display there.

GitHub has outages all the time without that page showing anything.

Another comment pointed to a third party alternative which is more accurate – https://mrshu.github.io/github-statuses/ – but that alternative isn't showing an outage right now either, since I believe it is being fed by GitHub.com's incident data.

▲mrshu 2 days ago | parent [-]

> I believe it is being fed by GitHub.com's incident data.

This is indeed correct.

▲skissane 2 days ago | parent [-]

Now https://www.githubstatus.com/ is declaring an incident but your page doesn’t have it

Maybe I spoke too soon in labelling your page “more accurate”?

▲mrshu 2 days ago | parent [-]

It is only being updated once per day. In an ongoing incident it is indeed not necessarily more accurate.

▲skissane 2 days ago | parent [-]

It might be good to put a disclaimer to that effect at the top of the page, to avoid confusion.

▲adrian_b 2 days ago | parent | prev | next [-]

Yes githubstatus shows all OK for Europe, where I am, but when trying to open the Web page of a repository I receive:

  503 Service Unavailable

  No server is available to handle this request.
▲bheztio 2 days ago | parent | next [-]

They updated the status page now, it says they are "investigating degraded performance". Like, their web is 100 % down. But no, have to call it "degraded performance for some users, some services" etc.

▲hurfdurf 2 days ago | parent | prev [-]

Same here. What's the point of a status page at this stage? "Copilot Ali"?

▲exploraz 2 days ago | parent | prev | next [-]

Delayed:

https://www.githubstatus.com/incidents/pyynvrm1vskw

▲egorfine 2 days ago | parent | prev [-]

It never does.