Routing to Runescape going to Chicago

[clockwise]

Runescape connectivity appears to have started going via Chicago as part of a known routing issue with Level3. Issue started recently (within 2 ?months?).

Runescape IP in question: 8.26.41.203

draapefjes‌ shaw-tony‌ - Starting a new thread to ensure visibility

[clockwise]

Initial findings show routing changes on or around the start of February. Connectivity to Level3 was 'updated' around that time and Shaw can see routing changes.

draapefjes‌ - If you have a traceroute to Runescape (8.26.41.203), that would be very helpful. We will begin conversations with Level3 and discuss a work around to resolve this issue for Shaw customers until a final agreement can be made with Level3 on why this issue is occurring and how to resolve it permanently.

[#3]

Thanks for creating a new thread about this! Here's the traceroute as requested:

Tracing route to oldschool55.runescape.com [8.26.41.203]
over a maximum of 30 hops:

1 2 ms 3 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 12 ms 11 ms 10 ms rc1st-be111-1.vc.shawcable.net [64.59.147.181]
4 23 ms 23 ms 23 ms rc3no-be11-1.cg.shawcable.net [66.163.72.69]
5 29 ms 22 ms 25 ms rc3so-hge0-19-0-1.cg.shawcable.net [66.163.71.118]
6 51 ms 52 ms 62 ms rc4ec-be13.il.shawcable.net [66.163.65.18]
7 54 ms 56 ms 53 ms rc3ec-be6-1.il.shawcable.net [66.163.65.69]
8 72 ms 65 ms 57 ms lag-104.ear5.chicago2.level3.net [4.14.14.97]
9 * * * Request timed out.
10 76 ms 78 ms 75 ms 4.31.104.58
11 * * * Request timed out.
12 107 ms 96 ms 94 ms oldschool55.runescape.com [8.26.41.203]

Trace complete.

[clockwise]

Can you do me a favour and do that trace again / test your game.

We've implemented a temporary work around to get you back to gaming until we have a formal conversation with Level3 so I'd like to ensure you're back up and running as expected.

[#5]

Looks like it works!! That was extremely fast, I didn't expect that. Thanks so much for the expedient help! My ping is back down in the 50's on the game, like it used to be  now i can't use lag as an excuse when i die on bosses haha

Tracing route to oldschool55.runescape.com [8.26.41.203]
over a maximum of 30 hops:

1 3 ms 3 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 10 ms 12 ms 12 ms rc1st-be111-1.vc.shawcable.net [64.59.147.181]
4 24 ms 15 ms 15 ms rc2wt-be50-1.wa.shawcable.net [66.163.70.106]
5 17 ms 14 ms 15 ms lag-111.ear3.seattle1.level3.net [4.71.152.133]
6 65 ms 48 ms 52 ms ae-1-4.bar1.lasvegas1.level3.net [4.69.133.109]
7 48 ms 47 ms 50 ms 205.129.17.98
8 49 ms * 79 ms oldschool55.runescape.com [8.26.41.203]

Trace complete.

Pinging 8.26.41.203 with 32 bytes of data:
Reply from 8.26.41.203: bytes=32 time=59ms TTL=57
Reply from 8.26.41.203: bytes=32 time=52ms TTL=57
Reply from 8.26.41.203: bytes=32 time=47ms TTL=57
Reply from 8.26.41.203: bytes=32 time=206ms TTL=57

Ping statistics for 8.26.41.203:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 206ms, Average = 91ms

[clockwise]

Excellent, glad you were up and gaming again for the weekend!

I'll close off this thread, but please create a new thread and feel free to tag me if you have any more issues in the future. Shaw will have a discussion with Level3 to have this re-routed permanently but these types of conversations can take time so we will leave the temporary workaround in place until that happens.

Happy Gaming!