My internet routing is severely messed up

Hi,

Recently some of my connections to the US have been routed through Hong Kong and Japan causing latency and bandwidth issues. Other connections to AUS servers are also highly unstable. This wasn't the case until roughly a week ago.

Gaming:
It has affected my ability to play some online games. See below for tracert to a US Westcoast FFXIV server. I had 200~ ping a week ago, now it's a rough average of 300-400 when stable. You can see it hop from Japan, to Hong Kong, back to Japan, and then onto the US. I can mostly correct this by using my VPN to tunnel to a nearby US data center (resulting in 220~ ping).

Other games with AUS servers have often proven entirely unplayable, with massive packet loss and latency jumping into the hundreds or thousands frequently. None of this is 100% consistent, sometimes it's a little better or a little worse, but it's always a problem.

Streaming:
It has also affected my ability to watch Youtube and Twitch, presumably due to congestion somewhere on this bad route. I've had no bandwidth problems to their servers since joining with vivid. The same JP->HK->JP->US hop pattern can be seen in the tracert to twitch below. I can't fix this with my VPN as it's not great for bandwidth.

General:
I often find that webpages either fail to load or do so much slower than they should.

Note the following:

Initially I assumed there was a fault/cut in the Southern Cross link that was necessitating the re-route, but with positive results from my VPN, horrid AUS connections, and some other US location routing properly (tried a couple game servers and other websites), that seems unlikely.

My connection is currently so bad that I'll have no choice but to change provider if it persists.

I'd appreciate some assistance on this matter.

Thanks.

Comments

#1

Khada wrote 2 weeks ago

Tracert to US Westcost FFXIV server:

Tracing route to 204.2.229.10 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 56 ms 33 ms 43 ms melequbr02.bbn.unwired.net.au [49.3.255.2]
3 75 ms 39 ms 39 ms 220.101.87.13
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 91 ms 59 ms 39 ms 59.154.18.12
9 247 ms 234 ms 228 ms ix-xe-10-2-1-40.tcore1.TV2-Tokyo.as6453.net [180.87.180.73]
10 237 ms * 232 ms if-et-21-2.hcore1.KV8-Chiba.as6453.net [120.29.217.67]
11 287 ms 289 ms 289 ms if-ae-16-2.tcore1.HK2-Hong-Kong.as6453.net [116.0.67.33]
12 337 ms 279 ms 286 ms 180.87.112.154
13 301 ms 279 ms 279 ms ae-10.r00.tkokhk01.hk.bb.gin.ntt.net [129.250.2.129]
14 301 ms 286 ms 279 ms ae-2.r24.tkokhk01.hk.bb.gin.ntt.net [129.250.2.126]
15 288 ms 272 ms 269 ms ae-1.r25.tkokhk01.hk.bb.gin.ntt.net [129.250.2.115]
16 314 ms 292 ms 389 ms ae-1.r24.osakjp02.jp.bb.gin.ntt.net [129.250.2.80]
17 308 ms 287 ms 275 ms ae-2.r22.snjsca04.us.bb.gin.ntt.net [129.250.2.118]
18 333 ms 286 ms 282 ms ae-0.r23.snjsca04.us.bb.gin.ntt.net [129.250.2.183]
19 294 ms 279 ms 288 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
20 335 ms 279 ms 409 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
21 700 ms 1209 ms 649 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
22 * 462 ms 354 ms 204.2.229.234
23 280 ms 279 ms 339 ms 204.2.229.10

Trace complete.

#2

Khada wrote 2 weeks ago

Tracert to US Twitch.tv server:

Tracing route to video-edge-c62730.lax03.hls.ttvnw.net [52.223.247.123]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 61 ms 42 ms 59 ms melequbr02.bbn.unwired.net.au [49.3.255.2]
3 91 ms 39 ms 40 ms 220.101.87.13
4 * * * Request timed out.
5 * * * Request timed out.
6 69 ms 33 ms 38 ms 59.154.18.6
7 239 ms 249 ms 240 ms ix-xe-10-2-1-40.tcore1.TV2-Tokyo.as6453.net [180.87.180.73]
8 250 ms 228 ms 229 ms if-et-21-2.hcore1.KV8-Chiba.as6453.net [120.29.217.67]
9 318 ms 316 ms 299 ms if-ae-17-2.tcore1.HK2-Hong-Kong.as6453.net [116.0.67.61]
10 308 ms 286 ms 279 ms 180.87.112.154
11 312 ms 295 ms 288 ms ae-13.r01.tkokhk01.hk.bb.gin.ntt.net [129.250.5.31]
12 297 ms 299 ms 299 ms ae-3.r24.tkokhk01.hk.bb.gin.ntt.net [129.250.4.21]
13 329 ms 288 ms 320 ms ae-1.r25.tkokhk01.hk.bb.gin.ntt.net [129.250.2.115]
14 409 ms 450 ms 295 ms ae-1.r24.osakjp02.jp.bb.gin.ntt.net [129.250.2.80]
15 917 ms 1157 ms 318 ms ae-2.r22.snjsca04.us.bb.gin.ntt.net [129.250.2.118]
16 327 ms 319 ms 301 ms ae-0.r23.snjsca04.us.bb.gin.ntt.net [129.250.2.183]
17 341 ms 296 ms 291 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
18 437 ms 592 ms 722 ms ae-4.r05.plalca01.us.bb.gin.ntt.net [129.250.5.32]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

#3

Frosty-MODERATOR wrote 2 weeks ago

I would think, at first glance, that it is partly due to this:
http://www.news.com.au/technology/online/aussie-web-users-warned-to-expe...

There's a lot of extra traffic routing via the USA since about a week ago, so the timing matches. With a major cable break, I'd expect to see unusual routes.

If you've got maintenance nearby on Optus towers, then you will be getting a double-whammy, as loads from that tower will have shifted to others nearby, making them correspondingly slower.

Can you run a tracert to: www.berkeley.edu
and post result here? Run it at an off-peak time, say 7am Monday, or something like that, then comparison at 7pm Monday.

I just ran same over my ADSL service here in Melbourne and am getting to the other side of the Pacific in about 225ms at midday on Sat. Given the inherent overheads of the wireless connection, if you can get between 250ms-280ms that would be a good result I think.

#4

Khada wrote 2 weeks ago

Hi Frosty,

I agree regarding the timing of the damage to the HK link, though I can't fathom how that would result in some of my US connections being routed specifically and consistently through HK. Would it perhaps be worth having someone from Optus double check that some of their routs haven't been accidentally directed to HK instead of away from HK?)

For now I'll assume that strange and complicated things are taking place with regards to my routing which may be resolved once the HK link is repaired (or once my tower maintenance is complete).

I'll also assume that my horrid AUS connections are the result of my tower being under maintenance.

I'll report back after each repair has taken place to give a status update.

Thanks.

P.s. How mental is it that the HK link was damaged on the same day that my tower went down for maintenance =\

#5

ozzcaddy-MODERATOR wrote 2 weeks ago

My view is there would be increased internet traffic to the USA over the past month with what is happening with the weather specifically, that may require rerouting to accommodate the increased traffic.

#6

Frosty-MODERATOR wrote 1 week ago

Khada, where are you located? (which state)

#7

Khada wrote 1 week ago

Vic 3032. Nearest tower is to the north east of yellow marker on Optus coverage map (it went from red to orange today).

#8

ozzcaddy-MODERATOR wrote 1 week ago

If you haven't already done so, click on the tower icon that you are looking at, it will display the problem and length of time that the problem may last before it is fixed.

#9

Khada wrote 1 week ago

Yep, thanks ozz. I see we have a spam problem lol.

#10

Frosty-MODERATOR wrote 1 week ago

Spam has been a constant issue here. Our forum software is fairly old and due for an update.

Warning
In participating in this forum you agree not to post or authorise others to post any material that is in our opinion offensive, defamatory, inaccurate, harassing, threatening, invasive of the privacy of others, sexually explicit or illegal. You also agree that you will not post or authorise others to post any copyright material that is not owned or licensed to you. In the event of any breach of this Policy we reserve the right to remove the post without notice to you.

Disabling comments and removing posts
Should we consider a thread or comment in violation of this Policy, we reserve the right to immediately remove part of or entire posts. We also reserve the right to disable, remove or archive posts that have been dormant for 14 days.

Member Login