Telus → telus network screwed! details inside!

K, I did some research online. Here's the result from my tests

1 1 ms 1 ms 1 ms 192.168.1.254
2 43 ms 19 ms 20 ms 10.145.134.1
3 64 ms 64 ms 64 ms 154.11.10.249
4 * * * Request timed out.
5 78 ms 65 ms 64 ms ae1-60g.cr1.lax1.us.nlayer.net [69.31.127.129]
6 91 ms 91 ms 91 ms xe-2-2-1.cr2.ord1.us.nlayer.net [69.22.142.255]

7 92 ms 91 ms 108 ms po6.ar2.ord1.us.scnet.net [69.31.111.6]
8 91 ms 91 ms 91 ms 44.ae2.cr2.ord1.us.scnet.net [216.246.95.145]
9 82 ms 82 ms 81 ms ae4.cr2.ord6.us.scnet.net [204.93.204.87]
10 83 ms 83 ms 83 ms ae4.ar6.ord6.us.scnet.net [204.93.204.67]
11 92 ms 95 ms 94 ms as36352.xe-2-0-2.ar6.ord6.us.scnet.net [50.31.15
4.182]
12 83 ms 83 ms 82 ms 10ge-1-3-1.fz146.cr1.chi.colocrossing.com [206.2
17.130.114]
13 82 ms 82 ms 82 ms host.colocrossing.com [205.234.152.250]
14 82 ms 82 ms 82 ms host.colocrossing.com [198.144.179.104]

I'm playing CS1.6 on ESEA servers now.
Basically, the ping is around 45 to an Illinois server 2 months ago.

But now, it is 80 from Calgary to an Illinois Server. And it spikes from 80 to 130 from 9pm to 1am everyday!

154.11.10.249 this IP is located @ the up east corner of Manitoba. ( check the link to google map for details »www.ip-adress.com/ip_tra ··· 9)That's why TELUS users in AB stuck in the routing shit. Cuz TELUS lost the route from AB to BC for us in AB. The route goes all the way up to the Northwest Territory. And then come back down to Buffalo. The route is all the way across Canada, and back to US. That is why the ping to an Chicago server is around 90 now. Also, for AB users, we know, the route used to go from Calgary or Edmonton to Vancouver, and then Seattle servers, finally to other servers in the US. But, now, U know what? AB users are in dip-shit!

The TELUS agent's ping and trace result @ their side is better than ours. And they got 45 ping to the Chicago server. It is true that, they are having a better route than ours in AB. And they said, there's nothing they can do about it!

Guys! Especially whoever in AB, it's time to fight together against that! We are paying our bloody money to TELUS, and they just changed the route without caring about us!

Sorry to burst your bubble, but just because one site says the IP is in Manitoba, doesn't mean that the gear is actually there. The reason it is showing as such, is that the only geo-data for the IP the site has is that it is in Canada, thus it automatically places it in the geographic center of Canada.

The only way to know where the device that IP represents is if Telus updates their geo-data for it, or if someone with knowledge of this device mentions the location.The first might take some time, and I doubt the second will happen.

Tiberius

And what I see here is the major jump of the ping is from 10.145.134.1 to 154.11.10.249. Do the math, 90-44= 46.

46 is the ping I should get two month ago.
I think now u see the picture here.

And also the 2 gears.
gw02.wlfdle.phub.net.cable.rogers.com
Canada (Ontario)
and
anguhub14.net.ubc.ca
Canada (Vancouver)

Both of the two's packet loss are 100%

They are close by TELUS side. And they didn't tell me why they close the two bridges. It is like we are cut from the best way out.

Please realize that

And also. If u r working for TELUS, please please do something rather than question about my info. Being a TELUS customer for three years. This did happen before. But not like this time. Why I got 45 ping to an Chicago server 2 months ago, but, now it is 90? It is doubled for no reason? I don't think so.

Dude, I called TELUS tech yesterday. Technicasl~ Not agents or customer service. They confirmed that. All my information from my results are proved by TELUS technicals

You appear to be incorrectly blaming this on Telus, when in reality, it appears to be caused by either scnet.net or nlayer.net

It would appear that nlayer is advertising a better route in LA to scnet than either of them are advertising at chicago equinox (both claim to be peering there).

If you trace route to nlayer's equinox connection in chicago(206.223.119.61), it routes just fine, so theres nothing wrong with TELUS's peering in chicago.

I hear nlayer and I cringe. Just a terrible backbone provider in the states. Only the cheapest seem to buy their bandwidth from them, as from what I've heard it's dirty cheap.

ya, they changed that, and our prices are all the way up~

dude, it's not a Chicago server, it's in California~

California sucks. Period. High pings to that area are almost expected.

I think people need to read up on BGP and / or routing protocols. Telus or anyone else does NOT change routing, it is dynamically managed! I'm sure some routes are manual but things usually change because of better advertised routes and / or down paths and what not.

No matter how much you all think, Telus isn't out to "Get us" by giving us crappy routes!

You are right, they are dynamically setup. However, it all depends on the peers as to which routes are better or not. For instance, Shaw directly peers with Internap in Seattle, therefore I get 15-20ms to anything running on them. Switch to something on Mzima or Nlayer, and it's terrible. They don't "control" the routes, however some providers do provide a better route for traffic overall.