My ISP refuses to take responsibility for a latency issue that is well documented.

Lunarijin

Commendable
Sep 19, 2016
3
0
1,510
I've been having consistent issues where my latency rises at the same time each night (around 8:05 pm), gradually increasing to a high point and then gradually decreases until it's back to working fine at the same point each night (around 10:35 pm). My ISP keeps claiming that the issue is with my computer or router; however, the issue arises regardless of the cables I used (which they tried to claim cat 6 instead of cat 5 was an issue), the computer I use, and it's becoming more and more frustrating. I've included two pictures which show the hop after my initial ip and private ip from the isp. I'm not sure how to deal with them or what to tell them, or what the issue could really be. Sometimes my maximum ping to google averages at 30-40 ms (instead of my normal 3-4 ms) and other times, it has exceeded 200ms as the average.

I spoke to Tier two last night (which was unnaturally rude, berating, argumentative, etc) and he said that he pinged google from the box on the outside of my house (hop 1) and that it showed no issues with google. This was during the peek and my average latency was 180ms from the a direct connection to the box. I also pinged two other websites which have identical, if not the exact same graphs with slightly different ping if needed. Even though Hop 1-4 is registered to my local isp, the guy said that there is no way that anything after the 2nd hop has anything to do with them. "Are you stupid? We don't control the internet."

I've tested it with almost no network activity, pulling no more than 20 Kb/s up/down and the issue is still there. My internet speed drops too. 10 Mb/s down/7 up instead of my advertised 50 up/down. I've tested other websites where Level 3 Communications didn't come as the hop after my isp and the same issue was present.

Thanks for any help that can be provided.
 
Solution
Not taking sides here: just more interested in understanding this situation.

Your ISP is responsible for the first 4 hops (1-4) as numbered in the green circles. Those IPs' being registered to them.

The latency is highest at Hop 6 as I am reading your graphs which would therefore be outside of your ISP's perview.

And the time frame coincides with what would likely be "busy times" for internet use with respect to evening hours computer use for gaming, Skyping, movie watching, downloading, etc.. The router at Hop 6 may just not be up to handling the traffic load or there is indeed some connectivity issue in that area.

You are in the Nashville area:

https://db-ip.com/4.69.140.229

I did a "Who is" on 4.69.140.229 and got this...

Ralston18

Titan
Moderator
Not taking sides here: just more interested in understanding this situation.

Your ISP is responsible for the first 4 hops (1-4) as numbered in the green circles. Those IPs' being registered to them.

The latency is highest at Hop 6 as I am reading your graphs which would therefore be outside of your ISP's perview.

And the time frame coincides with what would likely be "busy times" for internet use with respect to evening hours computer use for gaming, Skyping, movie watching, downloading, etc.. The router at Hop 6 may just not be up to handling the traffic load or there is indeed some connectivity issue in that area.

You are in the Nashville area:

https://db-ip.com/4.69.140.229

I did a "Who is" on 4.69.140.229 and got this:

https://db-ip.com/4.69.140.229

Being in New York - traffic and infrastructure could be a problem. (No disrespect intended.)

And the target IP (Google). What happens if you target 8.8.8.8 or 8.8.4.4?
 
Solution

Lunarijin

Commendable
Sep 19, 2016
3
0
1,510
Hop 6 isn't actually affecting the return time. I've run a trace route on google while my ping to google is 3ms, that hop reflected 100 ms. I don't understand why or how that works, but that particular hop didn't influence my 3-4ms to Google.com before or after my internet stabilized. I've added a picture of my trace route to google.com that i took last night in command prompt. It shows more clearly that the issue arises somewhere at or between hop 4 and 3. I may be mistaken, but the issue is consistent at that point and as ping to hop for increases or decreases, my return time to google.com shows the same.

I just pinged 8.8.8.8 and 8.8.4.4. and it shows 40ms right now and 3ms to google right now. I'll test those two ip addresses again after 8, when the issue has reoccurred. I agree that it could be a traffic handling issue if there is a bandwidth saturation. I am going to do a trace route tonight on two websites that do not go through Level 3.






 

Lunarijin

Commendable
Sep 19, 2016
3
0
1,510
I contacted my IP a few more times and after the ONT box was switched from one model to another, and the lines were cleared of being the cause, a new IP was assigned. This functionally resolved the issue. The trace route is showing that there are different IP's for the intermediate hops until the 4th; the 4th hop now has the same IP as the third hop (in the previously posted pictures) and that bothersome 4th hop isn't appearing at all in the trace. I have not found any notable issues yet with the newly assigned IP and I can only assume that it was a networking issue.

I hope that this can help someone in the future.