Other than the Oceania server that has its own topic, has anyone had issues connecting to NA and EU?
Who owns the routes seen when we do Tracerts?
![](https://static.mwomercs.com/forums//public/style_images/master/icon_users.png)
![](https://static.mwomercs.com/img/house/lonewolf.png)
Tracerts, Server Problems And Who Owns The Routes
Started by Wildstreak, Oct 13 2017 04:55 PM
General
8 replies to this topic
#1
Posted 13 October 2017 - 04:55 PM
#2
Posted 13 October 2017 - 05:12 PM
In the USA, the backbone is mostly AT&T, Verizon, Sprint, Centurylink, L3, Cogent, and a few other T1 providers. Local ISPs will be backhauling between you and these backbone providers. PGI probably has a T1 provider that services their datacenter.
#3
Posted 13 October 2017 - 07:41 PM
Problem afaik is that there is no interconnect agreement for data only telephony, so issues beyond your immediate provider are not obligated to be investigated
#4
Posted 14 October 2017 - 06:13 PM
Ace Selin, on 13 October 2017 - 07:41 PM, said:
Problem afaik is that there is no interconnect agreement for data only telephony, so issues beyond your immediate provider are not obligated to be investigated
Not true.
According to arrangements I learned when I worked telecom, whichever telecom company has the customer has to contact the others. If Verizon has a customer with problems, first they test their own stuff to be sure it works then contact other companies on the route to check theirs.
But according to one of my ISP's tech guys, he claims PGI owns the routes so it is their responsibility.
Someone owns them thus has responsibility.
#5
Posted 14 October 2017 - 07:56 PM
Wildstreak, on 14 October 2017 - 06:13 PM, said:
Not true.
According to arrangements I learned when I worked telecom, whichever telecom company has the customer has to contact the others. If Verizon has a customer with problems, first they test their own stuff to be sure it works then contact other companies on the route to check theirs.
But according to one of my ISP's tech guys, he claims PGI owns the routes so it is their responsibility.
Someone owns them thus has responsibility.
According to arrangements I learned when I worked telecom, whichever telecom company has the customer has to contact the others. If Verizon has a customer with problems, first they test their own stuff to be sure it works then contact other companies on the route to check theirs.
But according to one of my ISP's tech guys, he claims PGI owns the routes so it is their responsibility.
Someone owns them thus has responsibility.
Either your buddy is pulling your leg or he is not qualified for his job. PGI is not a telecom, they are only responsible for the networking equipment that runs their datacenter. I believe they actually use INAP to host the NA game servers, so they wouldn't even technically be responsible for the equipment in the datacenter. If you are seeing drops or latency in a trace route you can use a whois service to look up who owns the IP that is the weak link and you may be able to contact them.
#6
Posted 14 October 2017 - 08:02 PM
Is it time to petition congress for national wire (ISP as a utility not a service) sharing between ISPs?
I feel like alot of the problems in the world of the actual web stem from the fact that the major providers build and use their own network and does not share their network with other providers.
I feel like alot of the problems in the world of the actual web stem from the fact that the major providers build and use their own network and does not share their network with other providers.
#7
Posted 15 October 2017 - 12:53 AM
I am now seeing 350 to 400 ms pings to the NA servers, from my 200 to 230ms, which makes the game unplayable for me. Oceanic is around 203 ms for now but feels a lot more and has too long waiting times. If this doesn't change in the near future, I am going to hang up my boots for good. I still get better and much more playable pings to the NA servers of other games.
#8
Posted 15 October 2017 - 06:31 PM
Lostdragon, on 14 October 2017 - 07:56 PM, said:
If you are seeing drops or latency in a trace route you can use a whois service to look up who owns the IP that is the weak link and you may be able to contact them.
Can't look up time outs when they have no address.
I do know 2 of the 4 but it does no good.
Level 3 Communications told me what I already knew, as I am not their customer, they cannot do anything for me. Only their customer can request a fix to the problem and that is who owns the route.
The Québec company said they passed me to another Québec company, last I heard of it.
Anjian, on 15 October 2017 - 12:53 AM, said:
I am now seeing 350 to 400 ms pings to the NA servers, from my 200 to 230ms, which makes the game unplayable for me. Oceanic is around 203 ms for now but feels a lot more and has too long waiting times. If this doesn't change in the near future, I am going to hang up my boots for good. I still get better and much more playable pings to the NA servers of other games.
Did tracerts?
Notice if your routes changed or have strange paths?
#9
Posted 16 October 2017 - 05:11 AM
Wildstreak, on 15 October 2017 - 06:31 PM, said:
Can't look up time outs when they have no address.
I do know 2 of the 4 but it does no good.
Level 3 Communications told me what I already knew, as I am not their customer, they cannot do anything for me. Only their customer can request a fix to the problem and that is who owns the route.
The Québec company said they passed me to another Québec company, last I heard of it.
Did tracerts?
Notice if your routes changed or have strange paths?
I do know 2 of the 4 but it does no good.
Level 3 Communications told me what I already knew, as I am not their customer, they cannot do anything for me. Only their customer can request a fix to the problem and that is who owns the route.
The Québec company said they passed me to another Québec company, last I heard of it.
Did tracerts?
Notice if your routes changed or have strange paths?
Don't use the Windows tracert command, it uses ICMP Echo packets and a lot of equipment won't accept those now for security reasons. Get a trace tool that uses SYN packets, just Google it and you can find free ones.
4 user(s) are reading this topic
0 members, 4 guests, 0 anonymous users