International transit issues on Vodafone at the moment?

Forums › One New Zealand (including Vodafone, WxC, Farmside) › International transit issues on Vodafone at the moment?

micsco

13 posts

Geek

#119107 20-May-2013 22:15

Since around 8.30 -9pm transit to servers in australia has seen a lot higher latency than usual.

Tracing route to google-public-dns-a.google.com [8.8.8.8]over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 20 ms 19 ms 36 ms be2-100.bras1ldv.akl.vf.net.nz.129.109.203.in-ad
dr.arpa [203.109.129.45]
3 24 ms 18 ms 19 ms be5-100.ppnzldv01.akl.vf.net.nz.129.109.203.in-a
ddr.arpa [203.109.129.46]
4 19 ms 19 ms 19 ms be7.ppnzldv02.akl.vf.net.nz [203.109.180.242]
5 19 ms 19 ms 19 ms be8.ppnzldv01.akl.vf.net.nz [203.109.180.241]
6 279 ms 278 ms 278 ms ggl-router.syd.vf.net.nz.130.109.203.in-addr.arp
a [203.109.130.2]
7 279 ms 278 ms 279 ms 72.14.237.21
8 279 ms 279 ms 279 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

Anyone else experiencing the same?

grkiwi

68 posts

Master Geek

#822717 20-May-2013 22:23

I just posted the same in the wrong thread... :)

2 24 ms 21 ms 21 ms be2-100.bras2ftc.akl.vf.net.nz [203.109.130.162]
3 21 ms 21 ms 21 ms be9-100.ppnzftc01.akl.vf.net.nz [203.109.130.161]
4 22 ms 20 ms 20 ms be7-188.ppnzftc02.akl.vf.net.nz.180.109.203.in-addr.arpa [203.109.180.226]
5 21 ms 21 ms 20 ms be8-188.ppnzftc02.akl.vf.net.nz.180.109.203.in-addr.arpa [203.109.180.225]
6 281 ms 280 ms 280 ms ggl-router.syd.vf.net.nz.130.109.203.in-addr.arpa [203.109.130.2]
7 280 ms 279 ms 280 ms 72.14.237.21
8 280 ms 279 ms 279 ms google-public-dns-a.google.com [8.8.8.8]

The following results show there clearly is a problem with Oz

insane

3239 posts

Uber Geek

ID Verified

Trusted

#822723 20-May-2013 22:38

Earlier in the day there was equipment failure on the southern cross cable leg between NZ and AU, leaving traffic to take the long way to AU via the US. That affected multiple ISPs / transit providers who's wavelengths went through the SXs one vendors hardware. I'm not sure if they have made a public announcement about it so won't go into more details, but know Vodafone would have been affected by that.

Not sure why traffic has switched paths now, issue was resolved earlier during the day.

grkiwi

68 posts

Master Geek

#822817 21-May-2013 10:10

Issue resolved

2 19 ms 18 ms 18 ms be2-100.bras2ftc.akl.vf.net.nz [203.109.130.162]
3 16 ms 16 ms 16 ms be9-100.ppnzftc01.akl.vf.net.nz [203.109.130.161]
4 17 ms 16 ms 17 ms be7-188.ppnzftc02.akl.vf.net.nz.180.109.203.in-addr.arpa [203.109.180.226]
5 16 ms 16 ms 16 ms be8-188.ppnzftc02.akl.vf.net.nz.180.109.203.in-addr.arpa [203.109.180.225]
6 39 ms 39 ms 39 ms ggl-router.syd.vf.net.nz.130.109.203.in-addr.arpa [203.109.130.2]
7 40 ms 39 ms 44 ms 72.14.237.21
8 39 ms 39 ms 38 ms google-public-dns-a.google.com [8.8.8.8]