Forum Discussion

Jp420's avatar
Jp420
Friendly Neighbour
2 years ago
Solved

How to Report WAN routing issue for seattle.bb.telus.com?

For the past 3 days I've been experiencing packet loss at the interface from TELUS in Seattle to Level3 - who do I report this to at TELUS? How? I'm connecting to some servers in NYC and I don't have...
  • Nighthawk's avatar
    Nighthawk
    2 years ago

    Seattle is the closest major US hub to you, in the lower mainland, that has the most direct route to the east coast. It's not unusual to see traffic routed through Seattle or in some cases Chicago if you're in parts of Alberta. Ignoring the ICMP loss to Telus's Seattle node, are you seeing some sort of noticeable or quantifiable problem connecting to the New Jersey server?

     

    When doing MTRs, traceroutes or even pinging IPs directly, it's not unusual for them to not respond or not respond 100% of the time. It just depends on how the device or its firewall is configured. It doesn't mean traffic isn't passing through to the next device.

     

    I get similar MTR results to yours though with lower packet loss on the one you're concerned with. The latency to the target IP seems pretty normal for what I see to an east coast server / IP and is similar to what you are getting. My latency is slightly higher to Seattle since I'm in Alberta.

    |------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                           192.168.1.254 -    2 |   65 |   64 |    0 |    0 |    3 |    0 |
|                             10.137.48.1 -    2 |   64 |   63 |    0 |    1 |    3 |    1 |
|                           154.11.15.111 -    6 |   58 |   55 |    0 |   27 |   52 |   26 |
|          ae57.edge6.Seattle1.Level3.net -    2 |   65 |   64 |    0 |   59 |   80 |   56 |
|           Destination host unreachable. -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                               4.36.9.86 -    2 |   64 |   63 |    0 |   85 |  107 |   84 |
|d93f2776-b79d-4039-a940-48c2d7fc5a76.lb.civo.com -    6 |   57 |   54 |    0 |   81 |   89 |   81 |
|________________________________________________|______|______|______|______|______|______|

     

mstoneman1's avatar
mstoneman1
Neighbour
2 years ago

Hello,

 

  I'm a Telus fiber customer with servers in a Montreal data center.  For the past few months, about once or twice a week there is are 2-3 minute outages to my servers in a Montreal data center.   The server logs show no interruption in traffic during these outages.

 

  I added website monitors in a few cities worldwide and waited.  As soon as there was an outage the server in Seattle began reporting a loss of connectivity to my servers. 

 

  So it seems the problem is somewhere between Seattle and Montreal, perhaps Level-3 or other company. I'm hoping Telus is big enough and has enough clout to follow this down the line and find some kind of resolution.  I host a business platform for corporate clients , many who also use Telus and they have started calling each time there is an outage. There have been 2 today.   I've inquired with my clients on Shaw internet and they have not had issues, perhaps Shaw uses an alternative route to whatever feeds Seattle.

 

Fingers crossed!

Thank you

Mike

Related Content