So quick summary of my situation
AT&T U-verse customer for about 8 months (zero problems, zero packet loss)
Starting about 10 days ago, I suddenly found pretty much everything I did online, being consistently interrupted. My remote desktop sessions would lag, my video streaming would halt, id get booted from any online game I was in, downloads would take longer, despite showing the download speed being maxed.
I ran a quick repeating ping test to www.google.com just to see.
Immediately I noticed I was seeing packet loss a LOT. Anywhere from 10-20% packet loss. Yes, every 5-10 pings, would result in a timed out error.
So I started running some scans, to see where the loss was originating from.
My trace to google looked like this:
1. My DSL AT&T router ------>
2. AT&T CO IP address ------>
3. AT&T IP address --------->
4. AT&T IP address --------->
5. Outside of AT&T network IP --->
6. Googles first IP address ----->
7. Googles next IP address ----->
8. Googles final IP address
I started seeing issues between #2, and #4, no where else, no matter how many times i ran the test.
I ran another consistent ping test to the AT&T CO IP address, which would test the line from my house, to the very first location that my line goes to. It ran FLAWLESSLY. 5ms response times, no timeouts/packet loss. I let it run for a full day with ZERO problems.
Had an AT&T line tech come out and check the wiring inside and outside of my house for noise and other problems. No issues.
So this leads me to think one thing: This isnt a problem existing anywhere from my house, all the way to the CO. That this is a problem that starts from the CO itself.
I submitted an issue with AT&T, and the responded saying that the issues I was seeing was normal DNS resolution of multiple IPs owned by someone like google and possible ICMP. Yet, my scans werent showing that any of the outside hops were slow, being timed out, or not resolving.
So, I started running more tests to AT&T own network. Starting with att.com and att.net. And then using just ips of AT&T hardware that I got from various past scans. When staying entirely IN AT&T's network, I was still getting the errors.
AT&T seems to be ignoring this issue, and Im at a loss as to what to do, or if its even something that I CAN do. Im pretty tech savy, so this is pretty frustrating. As much as I can determine, this isnt an issue on my end, and is only something AT&T can fix. And yet, they say there isnt a real problem, and offer me no solution.
In the meantime, my net is only good enough right now for basic web browsing, nothing more.
Thoughts? Advice? Or help?
Much appreciated.
Zewks
↧