Internet Latency Issues

I've had a very similiar issue for the last 10 weeks or so. But it's at the same time every night. From around 8pm to 11pm my latency triples and I get a bunch of packet loss.

The only way I've been able to get AT&T's attention was by filing an FCC report with data included. I'll warn you though. It's been almost 30 days since I've done so and they have yet to fix it, or really even try to. They just keep blaming it on my equipment.

They've sent out 3 techs, who did all the things you mentioned. I've factory reset my modem and unplugged every device in my house except for one via Ethernet directly to the gateway and monitored it. Same results.

Recently they said they "came out during the time I'm reporting problems and monitored the line" which was last night. Guess what, it's the only night in the last 10 weeks where I didn't see wild latency/packet loss. But it's back again tonight.

They really claim there is no problem, but if you want to get any attention on it at all, I highly suggest filing an FCC Complaint.

When doing these tests, use a single computer hardwired to gateway.  Use the test built into the gateway’s management console, and another using speedtest defaults on the PC itself.  If you still see only 3Mbps on a 1G fiber connection, you’ve got something to talk about.  

^This advice is always floating around and is not the right way to measure things. The Speedtest within the gateway itself is only checking the link speed between the gateway and 1st or 2nd hop. This is why the speeds are always maxed out. Its not an accurate representation of peering to the internet which is where AT&T experiences the majority of their problems.

Measure connectivity to the actual internet outside of AT&T's network is the right way to measure these types of problems. Yes you should use a hardwired device, but just because the speedtest works in the gateway does NOT mean you're internet is performing as it should be. Make sure you measure multiple endpoints to multiple different places on the internet. If they all experience the same latency packet loss pattern then the problem is AT&T's.

We pay for access to the internet, not access to their splitters and routers within their own network only.

I've had a very similiar issue for the last 10 weeks or so. But it's at the same time every night. From around 8pm to 11pm my latency triples and I get a bunch of packet loss.

We may or may not be having the same issue but it's not at a particular time or day for me. It's very random and when it occurs it usually will last a majority of a day sadly. I honestly got lucky the last month and it only happened two days but some months it happens more often.

When doing these tests, use a single computer hardwired to gateway.  Use the test built into the gateway’s management console, and another using speedtest defaults on the PC itself.  If you still see only 3Mbps on a 1G fiber connection, you’ve got something to talk about.  

I'm sure the results will be different there too but I'll surely look into it. I typically use Speedtest.net (Which is what AT&T uses to for their speedtest via app/site) and I select an AT&T server. Multiple devices are impacted when the issues occurs and the main device I use for gathering results is hardwired.  It's not even a matter of the speedtest, it's very noticeable on regular browsing, VOIP, games, and etc. when it occurs, I don't even have to look at a speedtest. The speedtest is just a nice way for me to prove I'm not insane.

What reason is there to not trust connection to gateway?   Should the ISP be liable for what happens on a user’s network?   The ISP is responsible for service up to and including gateway.  The suggestion made was specifically to ensure this is the case.  

The question always is, how far does the paying customer have to go to prove it's not their network?

^This advice is always floating around and is not the right way to measure things. The Speedtest within the gateway itself is only checking the link speed between the gateway and 1st or 2nd hop. This is why the speeds are always maxed out. Its not an accurate representation of peering to the internet which is where AT&T experiences the majority of their problems.

That advice tests what AT&T is obligated to provide.  It goes a little further than the 1st or 2nd hop.  AT&T does not promise any particular bandwidth or latency to any particular destination on the Internet.  It also allows you to isolate the issue to issues near or within your home to issues with peering connections.  We can argue about whether or how fast AT&T should react to peering partner issues, but knowing that it is that, vs a local AT&T network issue is helpful in directing traffic at AT&T.  Because, make no mistake, their troubleshooting processes leave a whole lot to be desired.  They will run techs out to polish ends, replace gateways, swap fibers, etc. for days on end rather than find out that the exact same problem the customer is experiencing is also happening to 2 customers in the next neighborhood and also happened to customers in two other cities and has already been resolved.

So, you first have to know where the problem is so you can help direct traffic.  It helps to make absolutely sure that it's not inside your house: why waste your time waiting on AT&T to fix a problem that doesn't belong to them at all?  It also helps to find out if the issue is between your gateway and the first hop: you share your fiber with up to 64 other customers; two or three of which could be running Torrent servers.  The solution to that problem is a lot different to that of a peering issue.  Or a network routing issue inside AT&T's network near your home.

So,youfirst have to know where the problem is so you can help direct traffic.  It helps to make absolutely sure that it's not inside your house: why waste your time waiting on AT&T to fix a problem that doesn't belong to them at all?  It also helps to find out if the issue is between your gateway and the first hop: you share your fiber with up to 64 other customers; two or three of which could be running Torrent servers.  The solution to that problem is a lot different to that of a peering issue.  Or a network routing issue inside AT&T's network near your home.

I've tried everything from resets, replacements, and changing devices on my end, I'm about 100% sure it's not on my end. Any suggestions I'll gladly try.

I would suggest using pingplotter or similar (smokeping, winmtr), or just a few windows running "ping -t "continuously if you go look at them when you have an issue.  I would track latency to several different hops along the way to your favorite destinations.  Especially the very first hop past your gateway in a traceroute, the AT&T DNS address is a good choice because it's normally at the nearest major AT&T PoP, Google (8.8.8.8) or Cloudflare (1.1.1.1) DNS servers.  Anyway, When there is an issue, you want to see which of these servers you have latency issues with: (a) All, (b) some or (c) none.