141–150 of 194 posts
Everytime github goes down, and my push/pull is rejected, I immediately assume they’ve discovered I’m incompetent and fired me. And I’m the head of engineering at my company.
I think the same thing every time my credentials to our issue tracker expires and I have to log in again. I am the lead dev on two projects.
Earlier quoted context omitted.
Pretty much every company has been shown to have fake status pages at this point.
Status pages are updated by humans and the humans need to (1) realize there's a problem and (2) understand the magnitude of the problem and (3) put that on the status page. It's not fake, it's just a human process. And automating this would be error prone just the same.
often people point out how unreliable self-hosted services are, well, hosted services are just as unreliable if not more. this, ladies and gentlemen, is why you should always self host critical infrastructure
If you are down for 1 hour a year on self hosting, but Office 364 is down 3 days a year, your CEO is going to be more understanding of the Office outage as all his golf buddies have the same problem, and he reads about it in the NYT.
But in any case zero downtime is difficult, that's why you need two independent systems. I had a a 500 microsecond outage at the weekend when a circuit failed which caused an business affecting incident, not a big one fortunately, as it was only some singers, but it was still one that was unacceptable -- had it happened at a couple of other events in the last 12 months it would have been far more problematic. Work has started to ensure it doesn't happen next year.
Earlier quoted context omitted.
Your requests made it farther than mine - mine get to charter in nyc and die there 6 lag-26.nycmny837aw-bcr00.netops.charter.com (24.30.201.130) 158.033 ms lag-16.nycmny837aw-bcr00.netops.charter.com (66.109.6.74) 29.575 ms lag-416.nycmny837aw-bcr00.netops.charter.com (66.109.6.10) 30.077 ms 7 lag-1.pr2.nyc20.netops.charter.com (66.109.9.5) 81.351 ms 37.879 ms 27.877 ms 8 * * *
I’m in US east coast with a dev box in Helsinki. My dev box can still hit github.com, but I can’t at home.
Earlier quoted context omitted.
github.com for me returns 140.82.121.3 which routes fine in the uk, returning from lb-140-82-121-3-fra.github.com which from the distance and name I would assume is a frankfurt based load balancer. I get there from BT -> Zayo I can reach that IP from Washington too, but github returns 140.82.114.3 and 140.82.114.4 from DNS at 1.1.1.1 on a Level3 handoff in Washington Spot checks around the place show the first return…
Same from Finland, and same route. (Except my ISP instead of BT).