Very inconsistent latency (20ms-1000ms)

[xvi]

Woah, what is that 10.50.0.1 network. I see two private subnets here which confuse me and consider they seem to begin with the 10.50.x.x address. 10.x.x.x is a private class A network. It is not used on the internet, just in local networks behind the NAT. The same is true of the 192.168.x.x network which is private and a class B network, as well as a special off case 172.16.0.0/12 (255.240.0.0) which contains 16 class Cs.

The point is that I see nested private networks which is confusing. Could you explain your *entire* network setup. I suspect your modem is not providing you with that 10.50.x.x address but rather something one the internet and that you have nested private networks in your own network and that you're dropping packets between your modem/router and another device server up another private subnet. Something feels like it may be configured incorrectly.

Edit: I would be super pissed off if my ISP wasn't giving me a real IP on the internet. That, in my personal opinion, is unacceptable.

It's very possible that they're using 10. for management and internal routing. Normally, this is blocked by a firewall rule on the modem or gateway. Public IP merely routes through 10.x.x.x and comes out where peering happens. As long as you're assigned a public IP, it's nothing to worry about.

Notice that latency jumps up considerably between Tele Danmark (tdc.net) and gtt.net, granted that it's not jumping up much. This implies that the peering connection between Tele Danmark peers and gtt.net is oversaturated. If in the future you see sub-100 ms latency up to that point and 1000+ ms latencies after it hands off to gtt.net, the issue is very likely due to Tele Danmark being out of bandwidth at that peering point. If that's the case, submit that screenshot to them and inform them you are seeing excessive latency and slow speeds and that traceroute reveals that the excessive latency starts between them and gtt.net.

 

[g0aky]

It's very possible that they're using 10. for management and internal routing. Normally, this is blocked by a firewall rule on the modem or gateway. Public IP merely routes through 10.x.x.x and comes out where peering happens. As long as you're assigned a public IP, it's nothing to worry about.



Notice that latency jumps up considerably between Tele Danmark (tdc.net) and gtt.net, granted that it's not jumping up much. This implies that the peering connection between Tele Danmark peers and gtt.net is oversaturated. If in the future you see sub-100 ms latency up to that point and 1000+ ms latencies after it hands off to gtt.net, the issue is very likely due to Tele Danmark being out of bandwidth at that peering point. If that's the case, submit that screenshot to them and inform them you are seeing excessive latency and slow speeds and that traceroute reveals that the excessive latency starts between them and gtt.net.

When you say that the latency jumps up between tdc.net and gtt.net do you mean the 7th hop? Also I am not sure how to go about checking when exactly the latency sky rockets, since whenever I ping servers the high ping doesn't really show. I think I am going to need some step by step if I am to do what you're saying.

Not sure if this is at all relevant but here is a newer traceroute where it shows gtt.net at the 7th hop:



I'm going to head to bed for now. I will look at the thread when I wake up. I really appreciate this help, you guys seem to know what you're talking about!

 

[Aquinus]

Notice that latency jumps up considerably between Tele Danmark (tdc.net) and gtt.net, granted that it's not jumping up much. This implies that the peering connection between Tele Danmark peers and gtt.net is oversaturated.

You mean the link that's going over submarine cable across the ocean from Denmark to NYC? Yeah, I would expect 100ms round trip on something like that. If you didn't notice he's losing packets on the 10.x.x.x network. I suspect there is a problem closer to home.

 

[g0aky]

I just talked to my ISP and the woman I talked to said that the readings from the modem could indicate some sort of problem with it. I'll update after the technician has been here which will probably take a few days.

 

[g0aky]

I borrowed a modem so I could narrow down the problem, and it seems my modem was the root of the problem. I tried with the borrowed modem and everything was completely fine. I also tried my old coax cable with the new modem and it still ran smoothly. I then talked to my again, and they will be sending me a new modem free of charge.

I thank you all for the help, I appreciate it very much!