There is UFB that works like UFB and then there's Vodafone's UFB.

Forums › One New Zealand (including Vodafone, WxC, Farmside) › There is UFB that works like UFB and then there's Vodafone's UFB.

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8

850 posts

Ultimate Geek

ID Verified

Trusted

#1243316 20-Feb-2015 21:40

freitasm: I am of the opinion that if an ISP is not suitable, change providers (conditions apply, may have to pay termination fee, return modem).

I probably don't complain much because I haven't been doing online gaming for a while, but I would be pissed off too.

You were pretty rubbish anyway, it's a good thing you gave it up :-)

FierceGuppy

134 posts

Master Geek

#1243317 20-Feb-2015 21:40

FierceGuppy: And the ping times for the smörgåsbord of Aussie Battlefield 4 servers tonight:

Permission to swear, General Freitas?

Edit:

The tracert for one of the low(ish) ping BF4 servers.

PS C:\Windows\system32> tracert 203.26.94.188

Tracing route to gsd3.cmg.internode.on.net [203.26.94.188]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 9 ms 8 ms 17 ms 218.101.61.101
4 26 ms 24 ms 50 ms ie2-g-0-0-0.telstraclear.net [203.98.50.2]
5 23 ms 24 ms 23 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251]
6 31 ms 25 ms 27 ms unknown.telstraglobal.net [134.159.174.41]
7 50 ms 51 ms 50 ms 202.84.249.145
8 66 ms 51 ms 51 ms bundle-ether3.oxf-gw1.sydney.telstra.net [203.50.13.53]
9 50 ms 51 ms 51 ms bundle-ether2.oxf-gw2.sydney.telstra.net [203.50.6.86]
10 51 ms 49 ms 51 ms bundle-ether17.chw-core10.sydney.telstra.net [203.50.13.69]
11 64 ms 65 ms 66 ms bundle-ether8.exi-core10.melbourne.telstra.net [203.50.11.125]
12 82 ms 79 ms 79 ms bundle-ether5.way-core4.adelaide.telstra.net [203.50.11.92]
13 83 ms 83 ms 79 ms bundle-ether1.way33.adelaide.telstra.net [203.50.11.84]
14 78 ms 79 ms 78 ms opt1087651.lnk.telstra.net [139.130.189.210]
15 76 ms 72 ms 74 ms 61.88.9.14
16 74 ms 72 ms 81 ms te7-2.cor1.adl6.on.ii.net [150.101.225.230]
17 75 ms 73 ms 89 ms gsd3.cmg.internode.on.net [203.26.94.188]

Trace complete.

The tracert for one of the you-gonna-get-kicked-for-having-a-high-ping BF4 servers.

Tracing route to hosted-by-i3d.net [109.200.213.50]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 8 ms 9 ms 9 ms 218.101.61.101
4 24 ms 24 ms 24 ms ie2-g-0-0-0.telstraclear.net [203.98.50.2]
5 26 ms 25 ms 24 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251]
6 28 ms 25 ms 29 ms 134.159.174.37
7 56 ms 51 ms 51 ms 202.84.142.153
8 53 ms 59 ms 51 ms 202.84.223.45
9 171 ms 170 ms 171 ms i-0-1-0-7.siko-core04.bx.telstraglobal.net [202.84.141.193]
10 170 ms 169 ms 188 ms 64.215.195.206
11 171 ms 170 ms 170 ms 64.215.195.205
12 168 ms 165 ms 183 ms ae2-10G.ar1.SYD1.gblx.net [67.16.157.206]
13 166 ms 167 ms 166 ms interactive-3d-b-v.xe-0-1-1.ar1.syd1.gblx.net [64.214.226.150]
14 165 ms 169 ms 164 ms hosted-by-i3d.net [109.200.213.50]

Trace complete.

freitasm

BDFL - Memuneh
79263 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1243330 20-Feb-2015 21:59

Glassboy:
freitasm: I am of the opinion that if an ISP is not suitable, change providers (conditions apply, may have to pay termination fee, return modem).

I probably don't complain much because I haven't been doing online gaming for a while, but I would be pissed off too.

You were pretty rubbish anyway, it's a good thing you gave it up :-)

ROFL. What?

Aredwood

3885 posts

Uber Geek

#1243332 20-Feb-2015 22:02

Fully agree with Mauricio. Just change ISPs since the routing is a problem. I have seen plenty of threads on GZ from people complaining about weird routing on Vodafone / Telstraclear connections. Also AFAIK the former Telstraclear network still hasn't been fully merged with the Vodafone network yet. This is why you see people saying things like "it works on VDSL but not cable" or "Works on Fibre but not cable" ect. As due to the separate networks, often a fault would affect 1 of them but not both. Also the Cache servers that Vodafone uses sometimes start doing weird things. (This is what caused the "netflix doesn't work on Vodafone saga")

Sorry if this sounds like a "I hate Vodafone" post. I don't intend it to be. As the above things probably make no difference to at least 99% of Vodafone customers. Although to me it would. But because I:
* Don't use the ISP supplied router (I use a Ubiquity Edge Router Lite)
* Don't subscribe to SKY
* Don't have a landline
* Don't have an "On account" Vodafone mobile

I can't make use of any of the Vodafone package discounts. But If I did do the above things I most likely would be a happy Vodafone customer. In otherwords Im definitely not part of Vodafone's Target market. And Im guessing the OP is not part of the target market either.

At least 1 of my neighbours is on Vodafone UFB and they are happy with their connection. But they would fit into the "Target market".

Jase2985

13459 posts

Uber Geek

ID Verified

Lifetime subscriber

#1243334 20-Feb-2015 22:06

FYI on spark VDSL i get about 51ms to the first server in the above post and it takes 14 hops, my hops in Australia are completely different, not surprising though. but it looks like you are taking 50ms to just get to the first server in australia

im sure as hell not sure whats up with the second one as i get a massive 30ms to it.

it does seem like there is an issue in the way vodafone do their routing or one of their/australian counterparts servers slowing things down

Tracing route to gsd3.cmg.internode.on.net [203.26.94.188]
over a maximum of 30 hops:

1     2 ms     1 ms     1 ms 192.168.1.254
2    17 ms     7 ms     6 ms 125-239-205-1.jetstream.xtra.co.nz [125.239.205.
1]
3     *        *        *     Request timed out.
4     6 ms     6 ms     6 ms ae8-10.akbr6.global-gateway.net.nz [122.56.116.5
]
5     7 ms     6 ms     6 ms ae5-2.akbr7.global-gateway.net.nz [210.55.202.21
3]
6    30 ms    30 ms    30 ms xe7-0-2.sgbr3.global-gateway.net.nz [202.50.232.
10]
7    30 ms    29 ms    29 ms 122.56.127.214
8    30 ms    42 ms    29 ms as4739.syd.equinix.com [202.167.228.20]
9    53 ms    54 ms    68 ms ae3.cr1.mel8.on.ii.net [150.101.33.27]
10    52 ms    51 ms    56 ms ae0.cr1.mel4.on.ii.net [150.101.33.10]
11    53 ms    51 ms    54 ms ae1.cr1.adl2.on.ii.net [150.101.33.41]
12    53 ms    52 ms    52 ms ae0.cr1.adl6.on.ii.net [150.101.33.3]
13    53 ms     *       54 ms te7-2.cor1.adl6.on.ii.net [150.101.225.230]
14    52 ms    51 ms    51 ms gsd3.cmg.internode.on.net [203.26.94.188]

Trace complete.

Tracing route to gsd3.cmg.internode.on.net [203.26.94.188]
over a maximum of 30 hops:

1     2 ms     1 ms     1 ms 192.168.1.254
2    17 ms     7 ms     6 ms 125-239-205-1.jetstream.xtra.co.nz [125.239.205.
1]
3     *        *        *     Request timed out.
4     6 ms     6 ms     6 ms ae8-10.akbr6.global-gateway.net.nz [122.56.116.5
]
5     7 ms     6 ms     6 ms ae5-2.akbr7.global-gateway.net.nz [210.55.202.21
3]
6    30 ms    30 ms    30 ms xe7-0-2.sgbr3.global-gateway.net.nz [202.50.232.
10]
7    30 ms    29 ms    29 ms 122.56.127.214
8    30 ms    42 ms    29 ms as4739.syd.equinix.com [202.167.228.20]
9    53 ms    54 ms    68 ms ae3.cr1.mel8.on.ii.net [150.101.33.27]
10    52 ms    51 ms    56 ms ae0.cr1.mel4.on.ii.net [150.101.33.10]
11    53 ms    51 ms    54 ms ae1.cr1.adl2.on.ii.net [150.101.33.41]
12    53 ms    52 ms    52 ms ae0.cr1.adl6.on.ii.net [150.101.33.3]
13    53 ms     *       54 ms te7-2.cor1.adl6.on.ii.net [150.101.225.230]
14    52 ms    51 ms    51 ms gsd3.cmg.internode.on.net [203.26.94.188]

Trace complete.

C:\Users\USER>

FierceGuppy

134 posts

Master Geek

#1243367 20-Feb-2015 23:59

Aredwood: Fully agree with Mauricio. Just change ISPs since the routing is a problem. I have seen plenty of threads on GZ from people complaining about weird routing on Vodafone / Telstraclear connections. Also AFAIK the former Telstraclear network still hasn't been fully merged with the Vodafone network yet. This is why you see people saying things like "it works on VDSL but not cable" or "Works on Fibre but not cable" ect. As due to the separate networks, often a fault would affect 1 of them but not both. Also the Cache servers that Vodafone uses sometimes start doing weird things. (This is what caused the "netflix doesn't work on Vodafone saga")

Sorry if this sounds like a "I hate Vodafone" post. I don't intend it to be. As the above things probably make no difference to at least 99% of Vodafone customers. Although to me it would. But because I:
* Don't use the ISP supplied router (I use a Ubiquity Edge Router Lite)
* Don't subscribe to SKY
* Don't have a landline
* Don't have an "On account" Vodafone mobile

I can't make use of any of the Vodafone package discounts. But If I did do the above things I most likely would be a happy Vodafone customer. In otherwords Im definitely not part of Vodafone's Target market. And Im guessing the OP is not part of the target market either.

At least 1 of my neighbours is on Vodafone UFB and they are happy with their connection. But they would fit into the "Target market".

The package I upgraded to is Vodafone "Fastest" UFB (100Mbps), no data cap, and a landline + caller ID. $118.50. I have taken your point onboard about changing ISP but I MUST know if the problems with the Vodafone / telstra network will persist or soon be fixed. Keep in mind that the service was great until October or November last year. Then things went downhill. I have been with the same ISP for almost 12.5 years I don't want to make a rash decision and leave just before Vodafone and Telstra get their act together.

FierceGuppy

134 posts

Master Geek

#1243370 21-Feb-2015 00:12

Jase2985: FYI on spark VDSL i get about 51ms to the first server in the above post and it takes 14 hops, my hops in Australia are completely different, not surprising though. but it looks like you are taking 50ms to just get to the first server in australia

im sure as hell not sure whats up with the second one as i get a massive 30ms to it.

it does seem like there is an issue in the way vodafone do their routing or one of their/australian counterparts servers slowing things down

Tracing route to gsd3.cmg.internode.on.net [203.26.94.188]
over a maximum of 30 hops:

1     2 ms     1 ms     1 ms 192.168.1.254
2    17 ms     7 ms     6 ms 125-239-205-1.jetstream.xtra.co.nz [125.239.205.
1]
3     *        *        *     Request timed out.
4     6 ms     6 ms     6 ms ae8-10.akbr6.global-gateway.net.nz [122.56.116.5
]
5     7 ms     6 ms     6 ms ae5-2.akbr7.global-gateway.net.nz [210.55.202.21
3]
6    30 ms    30 ms    30 ms xe7-0-2.sgbr3.global-gateway.net.nz [202.50.232.
10]
7    30 ms    29 ms    29 ms 122.56.127.214
8    30 ms    42 ms    29 ms as4739.syd.equinix.com [202.167.228.20]
9    53 ms    54 ms    68 ms ae3.cr1.mel8.on.ii.net [150.101.33.27]
10    52 ms    51 ms    56 ms ae0.cr1.mel4.on.ii.net [150.101.33.10]
11    53 ms    51 ms    54 ms ae1.cr1.adl2.on.ii.net [150.101.33.41]
12    53 ms    52 ms    52 ms ae0.cr1.adl6.on.ii.net [150.101.33.3]
13    53 ms     *       54 ms te7-2.cor1.adl6.on.ii.net [150.101.225.230]
14    52 ms    51 ms    51 ms gsd3.cmg.internode.on.net [203.26.94.188]

Trace complete.

Tracing route to gsd3.cmg.internode.on.net [203.26.94.188]
over a maximum of 30 hops:

1     2 ms     1 ms     1 ms 192.168.1.254
2    17 ms     7 ms     6 ms 125-239-205-1.jetstream.xtra.co.nz [125.239.205.
1]
3     *        *        *     Request timed out.
4     6 ms     6 ms     6 ms ae8-10.akbr6.global-gateway.net.nz [122.56.116.5
]
5     7 ms     6 ms     6 ms ae5-2.akbr7.global-gateway.net.nz [210.55.202.21
3]
6    30 ms    30 ms    30 ms xe7-0-2.sgbr3.global-gateway.net.nz [202.50.232.
10]
7    30 ms    29 ms    29 ms 122.56.127.214
8    30 ms    42 ms    29 ms as4739.syd.equinix.com [202.167.228.20]
9    53 ms    54 ms    68 ms ae3.cr1.mel8.on.ii.net [150.101.33.27]
10    52 ms    51 ms    56 ms ae0.cr1.mel4.on.ii.net [150.101.33.10]
11    53 ms    51 ms    54 ms ae1.cr1.adl2.on.ii.net [150.101.33.41]
12    53 ms    52 ms    52 ms ae0.cr1.adl6.on.ii.net [150.101.33.3]
13    53 ms     *       54 ms te7-2.cor1.adl6.on.ii.net [150.101.225.230]
14    52 ms    51 ms    51 ms gsd3.cmg.internode.on.net [203.26.94.188]

Trace complete.

C:\Users\USER>

The number of hops is of no importance. What's important is that the path between the you and the target server is fast, and 51ms is pretty sweet. Did you mean to tracert the same server twice?

GoodSync

GoodSync. Easily back up and sync your files with GoodSync. Simple and secure file backup and synchronisation software will ensure that your files are never lost (affiliate link).

Aredwood

3885 posts

Uber Geek

#1243376 21-Feb-2015 00:58

And here are some tracerts from my Snap connection. They will be similar to Spark/Telecom/Xtra for stuff to the US. Because Snap use Spark Global Gateway for their international. But they really shine for connections to Australia.

Tracing route to twitch.tv [192.16.71.181]
over a maximum of 30 hops:

1     1 ms    <1 ms    <1 ms 192.168.1.1
2     1 ms     1 ms     1 ms 57.35.69.111.static.snap.net.nz [111.69.35.57]
3    12 ms     1 ms     1 ms 56.35.69.111.static.snap.net.nz [111.69.35.56]
4     1 ms     1 ms     1 ms 32.27.69.111.static.snap.net.nz [111.69.27.32]
5     1 ms     1 ms     1 ms 33.27.69.111.static.snap.net.nz [111.69.27.33]
6     2 ms     1 ms     1 ms ae5-2.akbr7.global-gateway.net.nz [210.55.202.21
3]
7     1 ms     1 ms     1 ms ae1-10.tkbr12.global-gateway.net.nz [202.50.232.
37]
8   125 ms   126 ms   125 ms 203.96.120.142
9   129 ms   158 ms   129 ms ae3-10.sjbr3.global-gateway.net.nz [122.56.127.2
5]
10   157 ms   157 ms   157 ms ae0.pabr5.global-gateway.net.nz [203.96.120.74]

11     *        *        *     Request timed out.
12     *        *        *     Request timed out.
13     *        *        *     Request timed out.
14     *        *        *     Request timed out.
15     *        *        *     Request timed out.
16     *        *        *     Request timed out.
17     *        *        *     Request timed out.
18     *        *        *     Request timed out.
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.

Here is your good server.

Tracing route to gsd3.cmg.internode.on.net [203.26.94.188]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms 192.168.1.1
2     1 ms    <1 ms     1 ms 57.35.69.111.static.snap.net.nz [111.69.35.57]
3     1 ms     1 ms    <1 ms 56.35.69.111.static.snap.net.nz [111.69.35.56]
4    24 ms    24 ms    24 ms as23655.brisbane.megaport.com [103.26.70.9]
5    36 ms    36 ms    36 ms as4739.brisbane.megaport.com [103.26.70.17]
6    58 ms    58 ms    65 ms ae1.br1.syd7.on.ii.net [150.101.33.20]
7    55 ms    55 ms    54 ms ae4.cr1.adl6.on.ii.net [150.101.33.35]
8    54 ms    55 ms    54 ms te7-2.cor1.adl6.on.ii.net [150.101.225.230]
9    54 ms    54 ms    54 ms gsd3.cmg.internode.on.net [203.26.94.188]

Trace complete.

And here is your "high ping server"

Tracing route to hosted-by-i3d.net [109.200.213.50]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms 192.168.1.1
2     4 ms     1 ms     1 ms 57.35.69.111.static.snap.net.nz [111.69.35.57]
3     1 ms     1 ms     2 ms 56.35.69.111.static.snap.net.nz [111.69.35.56]
4    25 ms    26 ms    24 ms 4.56.69.111.static.snap.net.nz [111.69.56.4]
5    25 ms    24 ms    24 ms 5.56.69.111.static.snap.net.nz [111.69.56.5]
6    24 ms    24 ms    24 ms ten-0-0-0-3.cor03.syd03.nsw.VOCUS.net.au [114.31
.192.208]
7    24 ms    24 ms    24 ms ten-1-1-0.bdr03.syd03.nsw.VOCUS.net.au [175.45.7
2.116]
8    25 ms    25 ms    27 ms as49544.nsw.ix.asn.au [218.100.52.60]
9    26 ms    26 ms    26 ms hosted-by-i3d.net [109.200.213.50]

Trace complete.

And I had a stream running on the highest quality from twitch.tv as a test while I ran the last tracert. It was using approx 5mbit of my bandwidth.

As for pricing, Im on a legacy promotional offer that means I get 200/200 with unlimited data for $150/month, 2 year contract. It would have included a VOIP landline But I told Snap that I don't want the landline. So yes it costs more but you are getting better speed and service.

Jase2985

13459 posts

Uber Geek

ID Verified

Lifetime subscriber

#1243394 21-Feb-2015 07:05

FierceGuppy:

The number of hops is of no importance. What's important is that the path between the you and the target server is fast, and 51ms is pretty sweet. Did you mean to tracert the same server twice?

no i didnt sorry

didn't realise i had messed up the copy and paste

Sounddude

I fix stuff!
1928 posts

Uber Geek

Trusted

2degrees

Lifetime subscriber

#1243418 21-Feb-2015 08:40

FierceGuppy:

The tracert for one of the you-gonna-get-kicked-for-having-a-high-ping BF4 servers.

Tracing route to hosted-by-i3d.net [109.200.213.50]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 8 ms 9 ms 9 ms 218.101.61.101
4 24 ms 24 ms 24 ms ie2-g-0-0-0.telstraclear.net [203.98.50.2]
5 26 ms 25 ms 24 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251]
6 28 ms 25 ms 29 ms 134.159.174.37
7 56 ms 51 ms 51 ms 202.84.142.153
8 53 ms 59 ms 51 ms 202.84.223.45
9 171 ms 170 ms 171 ms i-0-1-0-7.siko-core04.bx.telstraglobal.net [202.84.141.193]
10 170 ms 169 ms 188 ms 64.215.195.206
11 171 ms 170 ms 170 ms 64.215.195.205
12 168 ms 165 ms 183 ms ae2-10G.ar1.SYD1.gblx.net [67.16.157.206]
13 166 ms 167 ms 166 ms interactive-3d-b-v.xe-0-1-1.ar1.syd1.gblx.net [64.214.226.150]
14 165 ms 169 ms 164 ms hosted-by-i3d.net [109.200.213.50]

Trace complete.

One of the issues with TelstraGlobal, is they won't peer at Peering exchanges. They only peer with Tier1 providers.

Alot of Game servers are hosted on smaller non-Tier1 ISP's. So its quite common for paths to go strange places to smaller ISP's.

The best answer is to choose another ISP who uses upstreams who peer on peering exchanges. There are quite a few ISP's whcih have their own routers in Sydney who activley peer in Australia.

dwl

371 posts

Ultimate Geek

#1243464 21-Feb-2015 09:42

Sounddude: One of the issues with TelstraGlobal, is they won't peer at Peering exchanges. They only peer with Tier1 providers.

Alot of Game servers are hosted on smaller non-Tier1 ISP's. So its quite common for paths to go strange places to smaller ISP's.

The best answer is to choose another ISP who uses upstreams who peer on peering exchanges. There are quite a few ISP's whcih have their own routers in Sydney who activley peer in Australia.

Another challenge is knowing which path the return traffic is taking. Unless you can initiate the trace from the far end you won't know if it is taking the same path as from your end and asymmetric paths do occur.

yitz

2075 posts

Uber Geek

#1243484 21-Feb-2015 09:55

In this case "siko-core04" is within the Shin-Nikko building in Tokyo Japan which is the peering location tier-1 ISPs.

Telstra Global are suppose to have access to Australian domestic (Telstra/Optus) connectivity through Australian subsidary Telstra however that doesn't always work as can be seen here.

AsylumSkitzo

13 posts

Geek
Inactive user

#1243795 21-Feb-2015 17:42

I am on Vodafone cable and also affected by this. The US WoT servers latency has almost doubled from being routed through Hong Kong.

FierceGuppy

134 posts

Master Geek

#1243906 21-Feb-2015 20:24

AsylumSkitzo: I am on Vodafone cable and also affected by this. The US WoT servers latency has almost doubled from being routed through Hong Kong.

What sort of ping times do you normally see for the U.S WoT servers you use? The nearest BF4 server is 148ms on a good day and I use it as a last resort when too few people are playing on the Oceania servers.

What have the Aussie WoT servers been like over the past three days?

AsylumSkitzo

13 posts

Geek
Inactive user

#1243953 21-Feb-2015 22:55

West 170ms up to 310ms since Friday 13th
East 200ms up to 250ms Saturday 21st (not sure why this one is lower)

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8