[JOnAgain]

What is even the point? https://www.githubstatus.com/

Save money by just not having the page or the people pretending they do something useful by maintaining it.

[gtirloni]

"operational" comes with strings attached. We don't know what internal SLAs specify but most likely the service is meeting those agreements.

Should we get a refund? :)

[pavlov]

Maybe there's a business model here?

Sign up with Objective Uptime Inc. and tell them which vendors you have SLAs with. OU will monitor them on your behalf, compare the actual global availability to what's displayed on the vendor's status page, and if the outage exceeds agreed limits, OU can even automatically file suits on your behalf for breach of contract and misrepresentation (assuming the vendor's status page was showing all peachy).

[darkwater]

Yes, my company is paying for my GH user seat.

[srveale]

"When a metric becomes a target, it ceases to be a good metric"

I regret that uptime became a clause in SLAs, or a reputation/marketing thing. I don't care about how many 9s are after your decimal, I just want to know if your service is down or if something is wrong on my end.

[petercooper]

One of the many status page/"is it down" services could probably get some good PR out of having a GitHub status page that's based upon live results from several geographical locations..

[rozenmd]

Oh hey, I've got one right here: https://github.onlineornot.com/

Based out of Virginia, USA for the initial check, followed by a random sample of 19 locations around the world to confirm it's actually down.

[boarush]

They have reported incidents for the last two days but seem to limit it to a short amount of time which is clearly not the case for many folks out there.

[Karunamon]

I know over on AWS they are loath to update the status page since this is tied to SLA compensation. Does github have the same problem?