I'm contemplating switching back to Sonic now that they (may) have finally run fiber in my neighborhood, but would like to check if the horridness I'm experiencing accessing github.com (specifically) on AT&T Fiber is limited to them. What I've been seeing for the last 6 mo. or so is git session (e.g. repo or submodule clone) performance sometimes at very acceptable 40 MB/s speeds - and sometimes at 40 kB/s speeds, literally 3 orders of magnitude slower. What limited analysis I can conduct with mtr and the like, together with talking with co-workers who have no difficulty accessing github at the same times, strongly suggests that AT&T has some persistent internal routing issues causing this to happen(*).
But, it is not inconceivable that github itself has infrastructure issues causing these problems. So I'm wondering if anyone running on Sonic fiber has seen anything like this, to github or elsewhere? And if you managed an acceptable resolution, if so?
(*) Good luck getting any actual help - their L1 CSRs deny that AT&T *has* network engineers and their managers don't, but do say that I am not permitted to speak to them, but sure, they can swap my modem.
But, it is not inconceivable that github itself has infrastructure issues causing these problems. So I'm wondering if anyone running on Sonic fiber has seen anything like this, to github or elsewhere? And if you managed an acceptable resolution, if so?
(*) Good luck getting any actual help - their L1 CSRs deny that AT&T *has* network engineers and their managers don't, but do say that I am not permitted to speak to them, but sure, they can swap my modem.
Statistics: Posted by oddhack — Sat Oct 19, 2024 7:12 pm