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: 126.96.36.199
draapefjes shaw-tony - Starting a new thread to ensure visibility
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 (188.8.131.52), 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.
Thanks for creating a new thread about this! Here's the traceroute as requested:
Tracing route to oldschool55.runescape.com [184.108.40.206]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 [220.127.116.11] 4 23 ms 23 ms 23 ms rc3no-be11-1.cg.shawcable.net [18.104.22.168] 5 29 ms 22 ms 25 ms rc3so-hge0-19-0-1.cg.shawcable.net [22.214.171.124] 6 51 ms 52 ms 62 ms rc4ec-be13.il.shawcable.net [126.96.36.199] 7 54 ms 56 ms 53 ms rc3ec-be6-1.il.shawcable.net [188.8.131.52] 8 72 ms 65 ms 57 ms lag-104.ear5.chicago2.level3.net [184.108.40.206] 9 * * * Request timed out. 10 76 ms 78 ms 75 ms 220.127.116.11 11 * * * Request timed out. 12 107 ms 96 ms 94 ms oldschool55.runescape.com [18.104.22.168]
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.
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
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 [22.214.171.124] 4 24 ms 15 ms 15 ms rc2wt-be50-1.wa.shawcable.net [126.96.36.199] 5 17 ms 14 ms 15 ms lag-111.ear3.seattle1.level3.net [188.8.131.52] 6 65 ms 48 ms 52 ms ae-1-4.bar1.lasvegas1.level3.net [184.108.40.206] 7 48 ms 47 ms 50 ms 220.127.116.11 8 49 ms * 79 ms oldschool55.runescape.com [18.104.22.168]
Pinging 22.214.171.124 with 32 bytes of data:Reply from 126.96.36.199: bytes=32 time=59ms TTL=57Reply from 188.8.131.52: bytes=32 time=52ms TTL=57Reply from 184.108.40.206: bytes=32 time=47ms TTL=57Reply from 220.127.116.11: bytes=32 time=206ms TTL=57
Ping statistics for 18.104.22.168: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 47ms, Maximum = 206ms, Average = 91ms
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.
Retrieving data ...