51–59 of 59 posts
> We've recovered from an internal DNS outage, and are working to restore service to all repositories. status.github.com DNS, eh? Related to the recent CDN changes?
Not external, which would fall into the CDN-managed territory.
Those graphs are kinda useless - detailed time series information for what's pretty clearly reduce to a 0/1 state for outages.
Well some problems are slow downs instead of outright outages, and thats what the graphs are for since "response time" doesn't make much sense when no response is being sent at all.
␄
Tangential graph criticism:
If you aren't going to put "zero" at the bottom of the Y axis, and you have graphs with only a single numbered data tick, then I have no idea whatsoever the value that correlates to a Y axis position. (except when it hits your label.) If you have fewer than 3 labeled data ticks then I don't even know if you are linear.
Starting your data at zero is a really good idea unless you really mean to be graphing the derivative, in which case, maybe you should just graph the derivative. The exception is when you have a constant offset in the concept you are graphing. Like atmospheric pressure on earth. But please give me at least three ticks and try to leave them consistently spaced if I'm every going to see another graph of them from you.
Including unlabeled ticks, evenly spaced, is a terse visual language that you are a linear graph.
I don't understand how anyone could outsource something as mission critical to their business as git hosting, issue tracking, etc to a third-party. If anything happened to github half the developer community would be hosed. Let's hope that never happens.
I don't understand how anyone could outsource something as mission critical to their business as git hosting, issue tracking, etc to a third-party. If anything happened to github half the developer community would be hosed. Let's hope that never happens.
I don't understand how anyone could outsource something as mission critical to their business as git hosting, issue tracking, etc to a third-party. If anything happened to github half the developer community would be hosed. Let's hope that never happens.
Downtime is inevitable, and sometimes the thing that fails will cause huge problems and it's almost entirely unavoidable.
I'd much rather trust their team, which they've built to design the best service possible, to handle the infrastructure than having to use an internal team to design a competing product (albeit internal) with the same uptime requirements.
Anyone know what the difference is between status.github.com and github.com/status? /status just says "Github Lives!" with a timestamp.