Telecom Big Time plan trouble thread

Forums › Spark New Zealand (including Skinny and BigPipe) › Telecom Big Time plan trouble thread

1 | ... | 74 | 75 | 76 | 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | ... | 120

729 posts

Ultimate Geek

#315510 6-Apr-2010 21:15

Mines abnormally high too (locally).

Here is a ping with the -w 10000 modifier:

Pinging telecom.co.nz [146.171.18.242] with 32 bytes of data:
Reply from 146.171.18.242: bytes=32 time=79ms TTL=121
Reply from 146.171.18.242: bytes=32 time=90ms TTL=121
Reply from 146.171.18.242: bytes=32 time=99ms TTL=121
Request timed out.
Reply from 146.171.18.242: bytes=32 time=55ms TTL=121
Reply from 146.171.18.242: bytes=32 time=102ms TTL=121
Reply from 146.171.18.242: bytes=32 time=38ms TTL=121
Reply from 146.171.18.242: bytes=32 time=44ms TTL=121
Reply from 146.171.18.242: bytes=32 time=53ms TTL=121
Reply from 146.171.18.242: bytes=32 time=134ms TTL=121
Reply from 146.171.18.242: bytes=32 time=81ms TTL=121
Reply from 146.171.18.242: bytes=32 time=88ms TTL=121
Reply from 146.171.18.242: bytes=32 time=96ms TTL=121
Reply from 146.171.18.242: bytes=32 time=65ms TTL=121
Reply from 146.171.18.242: bytes=32 time=84ms TTL=121
Reply from 146.171.18.242: bytes=32 time=115ms TTL=121
Reply from 146.171.18.242: bytes=32 time=100ms TTL=121
Reply from 146.171.18.242: bytes=32 time=104ms TTL=121
Reply from 146.171.18.242: bytes=32 time=104ms TTL=121
Reply from 146.171.18.242: bytes=32 time=98ms TTL=121

Ping statistics for 146.171.18.242:
Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 134ms, Average = 85ms

The lowest is higher that my normal average.

Im not usually one to say this but this is just getting silly.

Its getting to the point where im going to be forced to change providers. I want to stay, but at the moment i cant evern update steam to access my games.

I can do more on my XT stick.

DravidDavid

1907 posts

Uber Geek

#315514 6-Apr-2010 21:25

I get 9 to 11. No loss.

Gaming still works perfectly fine for me. Bar VoIP.

Talkiet

4793 posts

Uber Geek

Trusted

#315516 6-Apr-2010 21:27

Cool... ok, now for something a little more interesting...

Run a tracert to telecom.co.nz... I'm not interested in the number of hops, or the latency to any of the intermediate steps, I just want you to be able to identify what the first responding hop is... Here's a tracert from my bigtime connection in Chch as an example...

Tracing route to telecom.co.nz [146.171.18.242]
over a maximum of 30 hops:
1     2 ms     1 ms     1 ms homeportal [192.168.199.246]
2    12 ms    11 ms    11 ms 210.55.69.112
3     *        *        *     Request timed out.
4    29 ms    30 ms    29 ms ae4-20.akcr10.global-gateway.net.nz [202.50.238.49]
5    29 ms    29 ms    31 ms g0-1-0-4.akcr8.global-gateway.net.nz [210.55.202.49]
6    28 ms    29 ms    29 ms telecom-sdn-ak1-dom.akcr8.global-gateway.net.nz [203.96.65.198]
7    28 ms    29 ms    27 ms 146.171.18.210
8    29 ms    31 ms    29 ms 146.171.18.242
Trace complete.

See the first hop outside of my network? It's 210.55.69.112

Now, could you try running the ping command with that IP address... So like this...

C:\Users\neil>ping -n 100 -w 10000 210.55.69.112

Pinging 210.55.69.112 with 32 bytes of data:
Reply from 210.55.69.112: bytes=32 time=17ms TTL=126
Reply from 210.55.69.112: bytes=32 time=12ms TTL=126
Reply from 210.55.69.112: bytes=32 time=10ms TTL=126
Reply from 210.55.69.112: bytes=32 time=11ms TTL=126
Reply from 210.55.69.112: bytes=32 time=11ms TTL=126
Reply from 210.55.69.112: bytes=32 time=11ms TTL=126
Reply from 210.55.69.112: bytes=32 time=10ms TTL=126
Reply from 210.55.69.112: bytes=32 time=11ms TTL=126
Reply from 210.55.69.112: bytes=32 time=10ms TTL=126
Reply from 210.55.69.112: bytes=32 time=11ms TTL=126

Ping statistics for 210.55.69.112:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 10ms, Maximum = 17ms, Average = 11ms

So here you can see at the moment I have pretty perfect performance to the first visible hop outside of my network. When you guys have performance issues, please try this and let me know (either PM or through a post here) what the performance to that first hop is like.

Oh, I need to mention, please be 100% sure that your connection is otherwise idle while running this... no downloading, no windows updates, no P2P, no VoIP... Something ultra light like IRC in the background is ok - but I want to make sure you measure what I am trying to measure. Also make sure no other PCs connected to the router are doing anything at the time on the net...

Cheers - N

Please note all comments are from my own brain and don't necessarily represent the position or opinions of my employer, previous employers, colleagues, friends or pets.

System

521 posts

Ultimate Geek

#315517 6-Apr-2010 21:28

ArcticSilver: Mines abnormally high too (locally).

Here is a ping with the -w 10000 modifier:

Pinging telecom.co.nz [146.171.18.242] with 32 bytes of data:
Reply from 146.171.18.242: bytes=32 time=79ms TTL=121
Reply from 146.171.18.242: bytes=32 time=90ms TTL=121
Reply from 146.171.18.242: bytes=32 time=99ms TTL=121
Request timed out.
Reply from 146.171.18.242: bytes=32 time=55ms TTL=121
Reply from 146.171.18.242: bytes=32 time=102ms TTL=121
Reply from 146.171.18.242: bytes=32 time=38ms TTL=121
Reply from 146.171.18.242: bytes=32 time=44ms TTL=121
Reply from 146.171.18.242: bytes=32 time=53ms TTL=121
Reply from 146.171.18.242: bytes=32 time=134ms TTL=121
Reply from 146.171.18.242: bytes=32 time=81ms TTL=121
Reply from 146.171.18.242: bytes=32 time=88ms TTL=121
Reply from 146.171.18.242: bytes=32 time=96ms TTL=121
Reply from 146.171.18.242: bytes=32 time=65ms TTL=121
Reply from 146.171.18.242: bytes=32 time=84ms TTL=121
Reply from 146.171.18.242: bytes=32 time=115ms TTL=121
Reply from 146.171.18.242: bytes=32 time=100ms TTL=121
Reply from 146.171.18.242: bytes=32 time=104ms TTL=121
Reply from 146.171.18.242: bytes=32 time=104ms TTL=121
Reply from 146.171.18.242: bytes=32 time=98ms TTL=121

Ping statistics for 146.171.18.242:
Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 134ms, Average = 85ms

The lowest is higher that my normal average.

Im not usually one to say this but this is just getting silly.

Its getting to the point where im going to be forced to change providers. I want to stay, but at the moment i cant evern update steam to access my games.

I can do more on my XT stick.

My result is alot higher than average also, i normally get 23ms to telecom

PC: 3.3ghz Core i5-2500, 8gb DDR3, ATI Radeon 5850, 27" QHD IPS Monitor

Mobile Phone: iPhone 5 32gb Graphite.

crazed

484 posts

Ultimate Geek

Trusted

#315518 6-Apr-2010 21:28

Mine at present, seems ok Will try again when I have issues

Ping statistics for 146.171.18.242:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 56ms, Average = 28ms

Tracing route to telecom.co.nz [146.171.18.242]
over a maximum of 30 hops:

  1 98 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
  2 12 ms 11 ms 11 ms 210-55-67-1.adsl.netgate.net.nz [210.55.67.1]
  3 * * * Request timed out.
  4 28 ms 28 ms 28 ms ae4-20.akcr10.global-gateway.net.nz [202.50.238.
49]
  5 29 ms 30 ms 28 ms g0-1-0-4.akcr8.global-gateway.net.nz [210.55.202
.49]
  6 29 ms 28 ms 29 ms telecom-sdn-ak1-dom.akcr8.global-gateway.net.nz
[203.96.65.198]
  7 35 ms 29 ms 29 ms 146.171.18.210
  8 29 ms 28 ms 28 ms 146.171.18.242

Trace complete.

CraZeD,
Your friendly Southern Geeky Fellow :P

Doctor

39 posts

Geek

#315520 6-Apr-2010 21:35

Still encountering problems here, mostly with international sites. New Zealand servers are fine
It often takes a few refreshes to get gizmodo to load. Twitter over iPhones WiFi times out. Want to download VLC? Forget it

Still the same router pool affecting us too.
Good ol so6 over in the Global Gateway hive somewhere

Tracing route to cisco.netacad.net [128.107.229.50]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms unknown [10.10.1.2]
2     1 ms     1 ms     1 ms 10.10.2.1
3     *        *        *     Request timed out.
4     *        *        *     Request timed out.
5    44 ms    40 ms    36 ms ae4-10.akbr5.global-gateway.net.nz [202.37.244.221]
6    23 ms    22 ms    22 ms 122.56.127.90
7    23 ms    24 ms    24 ms xe0-0-0-2.akbr4.global-gateway.net.nz [202.50.232.77]
8    23 ms    24 ms    23 ms ae1-10.tkbr9.global-gateway.net.nz [202.50.232.37]
9   147 ms   148 ms   157 ms so6-0-3.labr5.global-gateway.net.nz [122.56.127.34]
10   148 ms   149 ms   148 ms so1-0-1.lebr6.global-gateway.net.nz [202.50.232.174]
11   148 ms   148 ms   148 ms ex1-g0-0-1.eqlaca.sbcglobal.net [206.223.123.79]
12   182 ms   194 ms   181 ms ded4-g8-3-0.sntc01.pbi.net [151.164.41.165]
13   188 ms   183 ms   182 ms Cisco-Systems-1152786.cust-rtr.pacbell.net [64.161.0.62]
14   197 ms   184 ms   186 ms sjc12-dmzbb-gw1-gig1-42.cisco.com [128.107.224.109]
15   187 ms   183 ms   182 ms sjc12-dmzdc-gw1-gig5-2.cisco.com [128.107.224.22]
16   182 ms   182 ms   182 ms cna-prod-nv.cisco.com [128.107.229.50]

Trace complete.

From 23ms up to 157 and (I'm assuming here) we haven't left the country yet
I realise patience is a virtue and Telecom techs are working on it. But patience only stretches so far

ArcticSilver

729 posts

Ultimate Geek

#315527 6-Apr-2010 21:46

Doctor - That's a pretty normal ping time to some where in the US.

Quic Broadband

Move to New Zealand's best fibre broadband service (affiliate link). Free setup code: R587125ERQ6VE. Note that to use Quic Broadband you must be comfortable with configuring your own router.

ArcticSilver

729 posts

Ultimate Geek

#315548 6-Apr-2010 22:33

Things seem to have gotten better. I wonder if it was the peek time that amplified the issue?

I'm still jumping a little (ping wise) but its still 10x better than before.

Steams still not updating though. Which is a major issue.

Doctor

39 posts

Geek

#315564 6-Apr-2010 22:59

ArcticSilver: Doctor - That's a pretty normal ping time to some where in the US.

I'm not expecting a low ping to the US, far from it. I'm questioning the spike in ping between 2 routers within the Global Gateway. (Between 8 and 9 on the trace route)
This is what we were asked to provide to 2nd tier support a few weeks ago (Albeit not a traceroute to Cisco)
The explanation given was those routers were causing the grief and apparently they were told it had been sorted.

Ragnor

8222 posts

Uber Geek

Trusted

#315567 6-Apr-2010 23:09

Doctor:
ArcticSilver: Doctor - That's a pretty normal ping time to some where in the US.

I'm not expecting a low ping to the US, far from it. I'm questioning the spike in ping between 2 routers within the Global Gateway. (Between 8 and 9 on the trace route)
This is what we were asked to provide to 2nd tier support a few weeks ago (Albeit not a traceroute to Cisco)
The explanation given was those routers were causing the grief and apparently they were told it had been sorted.

What makes you think the the 9th hop is not in the US, looks like the Global Gateway router in LA or San Jose to me.

Doctor

39 posts

Geek

#315568 6-Apr-2010 23:11

Talkiet: Cool... ok, now for something a little more interesting...

Woops sorry Neil, I got distracted and didn't see your post.

The first hop outside my network is nothing actually, it timed out.
Not sure if ping responses are simply disabled on it or it actually timed out

Tracing route to telecom.co.nz [146.171.18.242]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms unknown [10.10.1.2]
2     1 ms     1 ms     1 ms 10.10.2.1
3     *        *        *     Request timed out.
4     *        *        *     Request timed out.
5    22 ms    22 ms    22 ms ae4-20.akcr10.global-gateway.net.nz [202.50.238.49]
6    22 ms    23 ms    22 ms g0-1-0-4.akcr8.global-gateway.net.nz [210.55.202.49]
7    22 ms    23 ms    23 ms telecom-sdn-ak1-dom.akcr8.global-gateway.net.nz[203.96.65.198]
8    23 ms    22 ms    23 ms 146.171.18.210
9    23 ms    23 ms    23 ms 146.171.18.242

Trace complete.

Single computer just running IRC

Doctor

39 posts

Geek

#315579 6-Apr-2010 23:25

Ragnor:
Doctor:
ArcticSilver: Doctor - That's a pretty normal ping time to some where in the US.

I'm not expecting a low ping to the US, far from it. I'm questioning the spike in ping between 2 routers within the Global Gateway. (Between 8 and 9 on the trace route)
This is what we were asked to provide to 2nd tier support a few weeks ago (Albeit not a traceroute to Cisco)
The explanation given was those routers were causing the grief and apparently they were told it had been sorted.

What makes you think the the 9th hop is not in the US, looks like the Global Gateway router in LA or San Jose to me.

I'm not sure to be quite honest, I was somewhat under the impression we went to the US via Australia and that to get to the US the jump would be more of a staggered increment rather than something so sudden.
That and I imagined Global Gateway routers to be around NZ and Australia rather than in the US.

Ragnor

8222 posts

Uber Geek

Trusted

#315608 7-Apr-2010 01:45

Doctor:

I'm not sure to be quite honest, I was somewhat under the impression we went to the US via Australia and that to get to the US the jump would be more of a staggered increment rather than something so sudden.
That and I imagined Global Gateway routers to be around NZ and Australia rather than in the US.

http://en.wikipedia.org/wiki/Southern_Cross_Cable
http://www.telegeography.com/product-info/map_cable/images/cable_map_2010_large.png

ArranH

161 posts

Master Geek

#315611 7-Apr-2010 05:03

5am and ran a test and almost at the speeds I used to get :) I can live with this, so hopefully whatever mysterious change/fault with gateway/complication/fault coincidentally affecting all of our routers at once/voodoo has now been corrected and its back to the good old days of me praising the post-Gattung Telecom to anyone that will listen.

Touch a whole lot of wood.

crazed

484 posts

Ultimate Geek

Trusted

#315619 7-Apr-2010 07:38

ArranH: 5am and ran a test and almost at the speeds I used to get :) I can live with this, so hopefully whatever mysterious change/fault with gateway/complication/fault coincidentally affecting all of our routers at once/voodoo has now been corrected and its back to the good old days of me praising the post-Gattung Telecom to anyone that will listen.

Touch a whole lot of wood.

Tend to agree mine returned to normal overnight, time will tell if its fixed tho. Will wait and see before praising someone...

CraZeD,
Your friendly Southern Geeky Fellow :P

1 | ... | 74 | 75 | 76 | 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | ... | 120