According to Metrist monitoring (disclosure: I work there), the errors were very rare, and didn't happen enough for us to call the product "down." Looks like around 1% of requests.
GitHub Outage
81–87 of 87 posts
Re: GitHub Outage
#82They’ve been having issues since yesterday.
I'd say since Friday night Pacific time.
Re: GitHub Outage
#83Earlier quoted context omitted.
This is so wrong that it makes me wonder if it's satire. "The whole point" (as you put it) of status pages was to publish high-level monitoring data to users. The monitoring process should occur outside the system that is being monitored, perhaps even on a different cloud. Eventually, many companies realized this revealed expensive SLA violations and ended that level of transparency. Your status page can and should r…
not satire. no company will put any amount of monitoring online for anyone to see, no matter how high level. for it to be useful info, it must contain details, and information about infrastructure is usually well guarded for very good reasons.
> no company will put any amount of monitoring online for anyone to see, no matter how high level
Many companies used to do this. I remember the first time someone on HN commented, "Hey, is it possible this status page is just a useless blog now?" And people were trying to figure it out.
Companies arguably have a contractual obligation to be transparent about this data with their customers anyway, so a company like Github (where such a huge percentage of the industry is a customer) is going to leak the data one way or another.
Re: GitHub Outage
#84Earlier quoted context omitted.
Yet Discord has an “API Response Time” graph[0] and Reddit has a “5xx error rate” graph[1]. No, it doesn’t automatically create incidents, but it’s nice to confirm an issue is happening site-wide after experiencing it. Actually looks like the metrics part of Reddit’s status page broke over 2 weeks ago 0: https://discordstatus.com/ 1: https://www.redditstatus.com/
> Yet Discord has an “API Response Time” graph[0] and Reddit has a “5xx error rate” graph[1]. that's awesome. doesn't exist for github, yet. would be nice if it does come.
Re: GitHub Outage
#85Earlier quoted context omitted.
not satire. no company will put any amount of monitoring online for anyone to see, no matter how high level. for it to be useful info, it must contain details, and information about infrastructure is usually well guarded for very good reasons.
> no company will put any amount of monitoring online for anyone to see, no matter how high level Many companies used to do this. I remember the first time someone on HN commented, "Hey, is it possible this status page is just a useless blog now?" And people were trying to figure it out. Companies arguably have a contractual obligation to be transparent about this data with their customers anyway, so a company like G…
Re: GitHub Outage
#86Earlier quoted context omitted.
gitlab
GitLab is not P2P/Local First software like Git itself. It suffers from exactly the same problem as GitHub, reliance on a central server (which is run either by the company making the product, or by your own team). What I'm talking about is being able to access everything like issues, wikis, PRs and whatever, even when you're 100% offline.
fair, i'd love that!
Re: GitHub Outage
#87Still getting this same error for past 10-12 hours. Tried in different times.
{ "code": 500, "message": "internal server error" }
Does anyone have luck? Any workaround to fix it?