Xtra access issues

[pete376403]

Seems to be some sort of hold up in Sydney (hop 6)

Tracing route to www.kiwibiker.co.nz [216.237.127.134]
over a maximum of 30 hops:

1 16 ms 15 ms 15 ms 203-97-216-1.cable.telstraclear.net [203.97.216.1]
2 14 ms 10 ms 14 ms ae0-840.ie4.telstraclear.net [203.167.223.114]
3 24 ms 23 ms 26 ms ge-1-2-0-843.ie1.telstraclear.net [218.101.61.105]
4 20 ms 22 ms 25 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251]
5 20 ms 21 ms 26 ms 203.167.233.10
6 146 ms 145 ms 146 ms i-7-2.syd-core01.net.reach.com [202.84.219.117]
7 146 ms 146 ms 147 ms i-7-8.tlot03.net.reach.com [202.84.251.238]
8 146 ms 148 ms 149 ms laiix.he.net [198.32.146.50]
9 158 ms 156 ms 162 ms 10gigabitethernet1-3.core1.pao1.he.net [72.52.92.21]
10 163 ms 160 ms 163 ms 10gigabitethernet3-4.core1.sjc1.he.net [72.52.92.113]
11 159 ms 158 ms 158 ms 64.62.133.170
12 161 ms 159 ms 163 ms 10.193.125.2
13 158 ms 162 ms 158 ms 216-237-127-134.infortech.net [216.237.127.134]

[riffer]

Still causing problems.

My result same as Pete's with the exception of my Smoothwall router:

Tracing route to www.kiwibiker.co.nz [216.237.127.134]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms smoothwall [192.168.0.1]
2 16 ms 10 ms 12 ms xxx-xx-xx-x.cable.telstraclear.net [xxx.xx.xx.x]

3 16 ms 19 ms 9 ms ae0-840.ie4.telstraclear.net [203.167.223.114]
4 19 ms 21 ms 19 ms ge-1-2-0-843.ie1.telstraclear.net [218.101.61.10
5]
5 21 ms 20 ms 19 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.
50.251]
6 20 ms 20 ms 20 ms 203.167.233.10
7 149 ms 145 ms 146 ms i-10-3.wil-core02.net.reach.com [202.84.219.113]

8 144 ms 145 ms 144 ms static.net.reach.com [202.84.251.234]
9 148 ms 144 ms 144 ms he.net.crgwest.com [206.223.143.122]
10 144 ms 153 ms 143 ms 10gigabitethernet2-1.core1.lax1.he.net [72.52.92
.121]
11 157 ms 161 ms 158 ms 10gigabitethernet1-3.core1.pao1.he.net [72.52.92
.21]
12 156 ms 156 ms 161 ms 10gigabitethernet3-4.core1.sjc1.he.net [72.52.92
.113]
13 154 ms 154 ms 156 ms 64.62.133.170
14 156 ms 159 ms 155 ms 10.193.125.2
15 160 ms 156 ms 157 ms 216-237-127-134.infortech.net [216.237.127.134]

[sinfull]

Still causing problems.

My result same as Pete's with the exception of my Smoothwall router:

Tracing route to www.kiwibiker.co.nz [216.237.127.134]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms smoothwall [192.168.0.1]
2 16 ms 10 ms 12 ms xxx-xx-xx-x.cable.telstraclear.net [xxx.xx.xx.x]

3 16 ms 19 ms 9 ms ae0-840.ie4.telstraclear.net [203.167.223.114]
4 19 ms 21 ms 19 ms ge-1-2-0-843.ie1.telstraclear.net [218.101.61.10
5]
5 21 ms 20 ms 19 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.
50.251]
6 20 ms 20 ms 20 ms 203.167.233.10
7 149 ms 145 ms 146 ms i-10-3.wil-core02.net.reach.com [202.84.219.113]

8 144 ms 145 ms 144 ms static.net.reach.com [202.84.251.234]
9 148 ms 144 ms 144 ms he.net.crgwest.com [206.223.143.122]
10 144 ms 153 ms 143 ms 10gigabitethernet2-1.core1.lax1.he.net [72.52.92
.121]
11 157 ms 161 ms 158 ms 10gigabitethernet1-3.core1.pao1.he.net [72.52.92
.21]
12 156 ms 156 ms 161 ms 10gigabitethernet3-4.core1.sjc1.he.net [72.52.92
.113]
13 154 ms 154 ms 156 ms 64.62.133.170
14 156 ms 159 ms 155 ms 10.193.125.2
15 160 ms 156 ms 157 ms 216-237-127-134.infortech.net [216.237.127.134]

Now ya see that shit just confuses the hell out of me ! I tried to ring telecum only to be put on hold for twenty min, spoke pigeon engrish to some indian and got nowhere ! But hey thats xtra for ya !
Wonder if vbulleten have shares in xtra's opposition ? Oh yeah what opposition !

[Ixion]

First tracert is Xtra
Second is Vodafone


C:\>tracert 216.237.127.134

Tracing route to 216-237-127-134.infortech.net [216.237.127.134]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.10.10.1
2 44 ms 44 ms 45 ms 219-89-54-1.adsl.xtra.co.nz [219.89.54.1]
3 * * * Request timed out.
4 43 ms 48 ms 41 ms xe6-0-0-10.akbr5.global-gateway.net.nz [202.37.2
44.221]
5 41 ms 46 ms 45 ms xe0-0-0-2.akbr4.global-gateway.net.nz [202.50.23
2.77]
6 45 ms 46 ms 48 ms so1-1-1.tkbr9.global-gateway.net.nz [203.96.120.
194]
7 186 ms * 168 ms so0-3-1.labr5.global-gateway.net.nz [202.50.232.
254]
8 168 ms 182 ms 188 ms so0-0-1.lebr6.global-gateway.net.nz [202.50.232.
98]
9 186 ms 187 ms 185 ms gi1-13.mpd01.lax05.atlas.cogentco.com [154.54.12
.141]
10 191 ms 186 ms 186 ms te4-2.mpd02.lax01.atlas.cogentco.com [154.54.6.1
89]
11 187 ms 195 ms 187 ms te9-3.mpd01.sjc01.atlas.cogentco.com [154.54.25.
190]
12 188 ms 186 ms 186 ms te4-3.mpd01.sjc05.atlas.cogentco.com [154.54.6.7
4]
13 359 ms 197 ms 216 ms infortech-corp.demarc.cogentco.com [38.104.134.5
0]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * ^C
C:\>tracert 216.237.127.134

Tracing route to 216-237-127-134.infortech.net [216.237.127.134]
over a maximum of 30 hops:

1 353 ms 369 ms 409 ms 172.26.74.38
2 99 ms 99 ms 129 ms 172.26.66.91
3 112 ms 129 ms 119 ms 172.26.65.124
4 100 ms 129 ms 109 ms 172.26.71.162
5 98 ms 109 ms 109 ms 172.26.65.188
6 106 ms 109 ms 109 ms 172.26.86.35
7 105 ms 119 ms 109 ms 172.26.86.66
8 102 ms 119 ms 119 ms gi3-13-1103.akl-sky-bdr1.ihug.net [203.109.143.2
2]
9 90 ms 129 ms 119 ms Gi15-2.gw1.akl1asianetcom.net [203.192.166.41]
10 257 ms 249 ms 239 ms po2-0.gw1.lax1.asianetcom.net [202.147.61.189]
11 234 ms 239 ms 269 ms po0-1-0.gw3.lax1.asianetcom.net [202.147.61.202]

12 273 ms 279 ms 269 ms 10gigabitethernet2-3.core1.lax1.he.net [216.218.
223.205]
13 249 ms 259 ms 259 ms 10gigabitethernet1-3.core1.pao1.he.net [72.52.92
.21]
14 234 ms 260 ms 248 ms 10gigabitethernet3-4.core1.sjc1.he.net [72.52.92
.113]
15 283 ms 279 ms 279 ms 64.62.133.170
16 * * * Request timed out.
17 488 ms 539 ms 569 ms 216-237-127-134.infortech.net [216.237.127.134]


Trace complete.

C:\>

I don't care if the munter router is an Xtra one or an offshore one. I pay Xtra good coin for a service, I expect them to deliver.Thye are the ones who decide who and where to outsource to , and what third parties to use for off shore services. If they are using dodgy routes (usually, cos they are cheaper) then that is up to them to rectify. Right smartish.

[Mom]

New thread for what I see as an ongoing problem for some of us.

We could not access KB on Friday, like many of you. I rang Xtra and reported it using my last case number from December as a reference point. Usual unhelpful help desk response that ended with, someone will call you 5:30pm Sunday to let you know what is happening.

Amazingly enough I did get a call, (we had regained access by then, but have been away and have no idea when it came back). This bloke suggested to me it was a firewall problem my end! Please, this is ongoing, many xtra broadband user issue, nothing to do with my PC!

We have this problem off and on, and quite regularly too, just sometimes it lasts longer than other times. I have been advised to report every instance of this problem.

SO...
Lets use this thread as a place to post our ping traces, many of us collectively complaining might actually get them to investigate the problem.

POST YOUR XTRA CASE NUMBERS AS WELL PLEASE

[rottiguy]

sorry but no, they will only give a shit if you don't pay them. Divide your monthly bill into hours then add up how many hours you can't access KB and deduct that from what you pay them, that will definitely get some action

[The Pastor]

im with xtra and we had no problems

[discotex]

We have this problem off and on, and quite regularly too, just sometimes it lasts longer than other times. I have been advised to report every instance of this problem.

SO...
Lets use this thread as a place to post our ping traces, many of us collectively complaining might actually get them to investigate the problem.

That isn't gonna work for the reasons I've explained before.

How about this.....

Post up the traces and those of us here who know how it works can:

a) say if it's something the ISP involved can fix (as it's often not just Xtra people affected this should be for all ISPs)

b) point you in the direction of the right people to contact if it's a problem deep in the interweb.

sorry but no, they will only give a shit if you don't pay them. Divide your monthly bill into hours then add up how many hours you can't access KB and deduct that from what you pay them, that will definitely get some action

Ahhh yeah... It'll get some disconnected phone line action