Dear SHAW support. Can you guys please help me with this issue?
I have been noticing high latency issues recently, and from performing WINMTR(tracert) trace, I noticed that shaw's traffic is being routed from west coast to east coast then back to the west coast, then the destination IP
The orginating request is from west coast and destination is west coast
I tried contacting shaw and cogent, and they are not both helping me.
Is there anything SHAW can do to not force the routing to west-east-west?
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| WEST COAST HOME IP - 0 | 8 | 8 | 15 | 44 | 166 | 86 |
| WEST COAST HOME IP- 0 | 8 | 8 | 14 | 44 | 166 | 88 |
| rc1st-tge0-9-0-20-1.vc.shawcable.net - 0 | 8 | 8 | 15 | 44 | 157 | 91 |
| rc3no-be11-1.cg.shawcable.net - 0 | 8 | 8 | 25 | 53 | 165 | 98 |
| rc3so-hge0-19-0-1.cg.shawcable.net - 0 | 8 | 8 | 23 | 53 | 166 | 104 |
| rc4ec-be13.il.shawcable.net - 0 | 8 | 8 | 55 | 85 | 212 | 131 |
| be4225.ccr41.ord03.atlas.cogentco.com - 0 | 8 | 8 | 63 | 93 | 219 | 136 |
| be2765.ccr41.ord01.atlas.cogentco.com - 20 | 5 | 4 | 64 | 103 | 212 | 66 |
| be2717.ccr21.cle04.atlas.cogentco.com - 25 | 4 | 3 | 74 | 123 | 221 | 74 |
| be2889.ccr41.jfk02.atlas.cogentco.com - 0 | 8 | 8 | 79 | 111 | 224 | 158 |
| be3362.ccr31.jfk04.atlas.cogentco.com - 0 | 8 | 8 | 82 | 110 | 224 | 158 |
| 38.88.194.210 - 0 | 8 | 8 | 162 | 192 | 312 | 237 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| 80.95.144.165 - 0 | 8 | 8 | 222 | 252 | 364 | 300 |
| 80.95.152.98 - 0 | 8 | 8 | 224 | 253 | 364 | 306 |
| 85.190.157.162 - 0 | 8 | 8 | 222 | 250 | 364 | 296 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
How is that going west coast to east coast to west coast? It looks to me like it is going directly west coast to east coast. I think you may be reading it wrong somehow?
The destination IP you are tracerouting to, 85.190.157.162, is in Germany, so I don't see how you can get much better latency than that.
It is taking the path Vancouver->Calgary->Chicago->Cleveland->NYC->Germany. I think that's pretty much a direct line West to East, give or take in a few places?
the destination server is not present anymore. But it was located in LA. I have other servers that is located in LA where it's routing to east first, then back to west
LOOK AT this one
85.190.157.162 is located in LA
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 174.7.0.1 - 0 | 61 | 61 | 10 | 80 | 2054 | 11 |
| 174.7.0.1 - 0 | 61 | 61 | 10 | 79 | 1982 | 13 |
| rc1st-tge0-9-0-20-1.vc.shawcable.net - 0 | 63 | 63 | 12 | 17 | 38 | 19 |
| rc3no-be11-1.cg.shawcable.net - 0 | 63 | 63 | 22 | 27 | 69 | 27 |
| rc3so-hge0-19-0-1.cg.shawcable.net - 0 | 63 | 63 | 22 | 27 | 33 | 25 |
| rc4ec-be13.il.shawcable.net - 2 | 59 | 58 | 53 | 57 | 64 | 56 |
| be4225.ccr41.ord03.atlas.cogentco.com - 0 | 63 | 63 | 60 | 64 | 75 | 65 |
| be2765.ccr41.ord01.atlas.cogentco.com - 0 | 63 | 63 | 61 | 65 | 74 | 65 |
| be2717.ccr21.cle04.atlas.cogentco.com - 0 | 63 | 63 | 68 | 72 | 79 | 76 |
| be2889.ccr41.jfk02.atlas.cogentco.com - 0 | 63 | 63 | 82 | 86 | 98 | 87 |
| be3362.ccr31.jfk04.atlas.cogentco.com - 2 | 59 | 58 | 80 | 84 | 90 | 87 |
| 38.88.194.210 - 0 | 63 | 63 | 152 | 157 | 189 | 158 |
| No response from host - 100 | 12 | 0 | 0 | 0 | 0 | 0 |
| 80.95.144.165 - 2 | 59 | 58 | 215 | 220 | 238 | 217 |
| 80.95.152.98 - 2 | 59 | 58 | 216 | 223 | 245 | 220 |
| 85.190.157.162 - 2 | 59 | 58 | 214 | 218 | 223 | 220 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
No - 85.190.157.162 is located in Germany, not LA
Here is the whois entry: Webupdates — RIPE Network Coordination Centre
It belongs to a company called marbis GMBH
It says Los Angeles in part of the description, but it is being advertised through Germany, so they must have some kind of layer 2 tunnel from Germany to Los Angeles. Either that or they were advertising it using BGP via Los Angeles but stopped. There is nothing that Shaw could do about that.
Webupdates — RIPE Network Coordination Centre
It looks like a company in Los Angeles that is connected to the Internet via an ISP in Germany. Perhaps the company in LA is not advertising their network via BGP locally and so the route failed over to routing through Germany. There is nothing that Shaw or Cogent can do about that. Contact Nitrado.
Update:
It looks like Nitrado is advertising both out of LA and out of Germany, but because of the route distances, Cogent thinks the Germany path is shorter than the LA path. Nitrado probably needs to prepend their AS number in the routes going out of Germany so they are not preferred.