Telecom Big Time plan trouble thread

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

1 | ... | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | ... | 120

728 posts

Ultimate Geek

#305152 7-Mar-2010 01:42

DravidDavid: I have a major issue with the Global Gateway aswell. Take a look at the tests I did on the other page. It never seems to be able to ping the global gateway and when it does the latency is in the high thousands.

I think this is were my ping/packet loss issue is occuring.

It could be a lot of things really.

One posability is that its overloaded and that you are being routed around (hence your ping issue).

Also to add to whats above, lowering the ping packet size does seem to slighly decrease the number of time outs.

Quic Broadband

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

DravidDavid

1907 posts

Uber Geek

#305153 7-Mar-2010 01:52

Trouble is, I have the same ping and the same kind of issue at 3PM 10PM 2AM and 6AM.

I don't know how to change the size of the packets.

ArcticSilver

728 posts

Ultimate Geek

#305157 7-Mar-2010 02:15

The packet loss has stopped (when pinging the US) now that it is after 2am.

So i guess it might be related to the shaping/contention ratio?

My main gripe is that the packet loss is very annoying in games that don't compensate for lag very well, you get jumped back quite majorly. On the other hand it also causes time outs when in game leaving you in the server (when your not) and unable to rejoin.

Any help would be greatly appreciated =)

ArcticSilver

728 posts

Ultimate Geek

#305158 7-Mar-2010 02:15

DravidDavid: Trouble is, I have the same ping and the same kind of issue at 3PM 10PM 2AM and 6AM.

I don't know how to change the size of the packets.

Are you getting issues after 2am?

DravidDavid

1907 posts

Uber Geek

#305159 7-Mar-2010 02:20

This was done just now...
C:\Users\David>ping -t telecom.co.nz

Pinging telecom.co.nz [146.171.18.242] with 32 bytes of data:
Request timed out.
Reply from 146.171.18.242: bytes=32 time=196ms TTL=122
Reply from 146.171.18.242: bytes=32 time=162ms TTL=122
Reply from 146.171.18.242: bytes=32 time=381ms TTL=122
Reply from 146.171.18.242: bytes=32 time=162ms TTL=122
Reply from 146.171.18.242: bytes=32 time=345ms TTL=122
Reply from 146.171.18.242: bytes=32 time=201ms TTL=122
Request timed out.
Reply from 146.171.18.242: bytes=32 time=344ms TTL=122
Reply from 146.171.18.242: bytes=32 time=226ms TTL=122
Reply from 146.171.18.242: bytes=32 time=258ms TTL=122
Reply from 146.171.18.242: bytes=32 time=251ms TTL=122
Reply from 146.171.18.242: bytes=32 time=197ms TTL=122
Reply from 146.171.18.242: bytes=32 time=321ms TTL=122
Reply from 146.171.18.242: bytes=32 time=287ms TTL=122
Reply from 146.171.18.242: bytes=32 time=330ms TTL=122

I get the same issues as posted before with the global gateway.

Just an FYI...

I have tried 3 different routers. Our lines have been given the green light by Telecom twice. Infact our exchange was repaired recently because I complained.

My friend is having similar issues. He lives 15Ks away from me (so he is obviously on a different exchange)

ArcticSilver

728 posts

Ultimate Geek

#305160 7-Mar-2010 02:37

No such issue here, anyway im off to sleep, i suggest you try and ping the first router off the block via a trace-route and go up from there. If you dont know how to do it ill help you tomorrow.

Detruire

1755 posts

Uber Geek

#305161 7-Mar-2010 02:57

Reply from 146.171.18.242: bytes=32 time=70ms TTL=122
Reply from 146.171.18.242: bytes=32 time=138ms TTL=122
Reply from 146.171.18.242: bytes=32 time=94ms TTL=122
Reply from 146.171.18.242: bytes=32 time=50ms TTL=122
Reply from 146.171.18.242: bytes=32 time=39ms TTL=122
Reply from 146.171.18.242: bytes=32 time=38ms TTL=122
Reply from 146.171.18.242: bytes=32 time=117ms TTL=122
Reply from 146.171.18.242: bytes=32 time=49ms TTL=122
Reply from 146.171.18.242: bytes=32 time=70ms TTL=122
Reply from 146.171.18.242: bytes=32 time=39ms TTL=122
Reply from 146.171.18.242: bytes=32 time=38ms TTL=122
Reply from 146.171.18.242: bytes=32 time=120ms TTL=122
Reply from 146.171.18.242: bytes=32 time=73ms TTL=122
Reply from 146.171.18.242: bytes=32 time=38ms TTL=122
Reply from 146.171.18.242: bytes=32 time=132ms TTL=122
Reply from 146.171.18.242: bytes=32 time=132ms TTL=122
Reply from 146.171.18.242: bytes=32 time=127ms TTL=122
Reply from 146.171.18.242: bytes=32 time=39ms TTL=122
Reply from 146.171.18.242: bytes=32 time=87ms TTL=122
Reply from 146.171.18.242: bytes=32 time=102ms TTL=122
Reply from 146.171.18.242: bytes=32 time=178ms TTL=122

Does look oddly spastic.

rm *

Magitek

7 posts

Wannabe Geek

#305215 7-Mar-2010 14:47

DravidDavid: This was done just now...
C:\Users\David>ping -t telecom.co.nz

Pinging telecom.co.nz [146.171.18.242] with 32 bytes of data:
Request timed out.
Reply from 146.171.18.242: bytes=32 time=196ms TTL=122
Reply from 146.171.18.242: bytes=32 time=162ms TTL=122
Reply from 146.171.18.242: bytes=32 time=381ms TTL=122
Reply from 146.171.18.242: bytes=32 time=162ms TTL=122
Reply from 146.171.18.242: bytes=32 time=345ms TTL=122
Reply from 146.171.18.242: bytes=32 time=201ms TTL=122
Request timed out.
Reply from 146.171.18.242: bytes=32 time=344ms TTL=122
Reply from 146.171.18.242: bytes=32 time=226ms TTL=122
Reply from 146.171.18.242: bytes=32 time=258ms TTL=122
Reply from 146.171.18.242: bytes=32 time=251ms TTL=122
Reply from 146.171.18.242: bytes=32 time=197ms TTL=122
Reply from 146.171.18.242: bytes=32 time=321ms TTL=122
Reply from 146.171.18.242: bytes=32 time=287ms TTL=122
Reply from 146.171.18.242: bytes=32 time=330ms TTL=122

I get the same issues as posted before with the global gateway.

Just an FYI...

I have tried 3 different routers. Our lines have been given the green light by Telecom twice. Infact our exchange was repaired recently because I complained.

My friend is having similar issues. He lives 15Ks away from me (so he is obviously on a different exchange)

I get this issue from time to time also. Let me know if you ever stumble onto a solution.
I still refuse to believe it's the line.

aionwannabe

147 posts

Master Geek

#305223 7-Mar-2010 15:53

Yes 3 and 10 pm are definite ping nightmares but i mean as more people join bigtime telecom will have to set stuff up to accomidate it better? right?

DravidDavid

1907 posts

Uber Geek

#305226 7-Mar-2010 16:13

As more people join bigtime telecom will have to set stuff up to accomidate it better? right?

In a perfect world...yea.

I was thinking...Would it be possible to shape only those who abuse the crap out of the connection? Like put a soft cap of 350GB on the connection and severly shape those who go over?

There are a lot of people who will go well over 60GB but will never exceed 100. Or is what I am suggesting "Go large" all over again?

Lias

5567 posts

Uber Geek

ID Verified

Trusted

Lifetime subscriber

#305745 9-Mar-2010 18:31

It does look like there are issues at the moment

Perfect pings nationally, but constant packet loss internationally (15% as of this post)

Doozy?

I'm a geek, a gamer, a dad, a Quic user, and an IT Professional. I have a full rack home lab, size 15 feet, an epic beard and Asperger's. I'm a bit of a Cypherpunk, who believes information wants to be free and the Net interprets censorship as damage and routes around it. If you use my Quic signup you can also use the code R570394EKGIZ8 for free setup.

exportgoldman

1202 posts

Uber Geek

Trusted

#305751 9-Mar-2010 18:50

Lias: It does look like there are issues at the moment

Perfect pings nationally, but constant packet loss internationally (15% as of this post)

Doozy?

No problems here

Pinging www.theregister.co.uk [212.100.234.54] with 32 bytes of data:
Reply from 212.100.234.54: bytes=32 time=306ms TTL=46
Reply from 212.100.234.54: bytes=32 time=307ms TTL=46
Reply from 212.100.234.54: bytes=32 time=311ms TTL=46
Reply from 212.100.234.54: bytes=32 time=309ms TTL=46

Pinging www.telecom.co.nz [146.171.18.242] with 32 bytes of data:
Reply from 146.171.18.242: bytes=32 time=8ms TTL=121
Reply from 146.171.18.242: bytes=32 time=14ms TTL=121
Reply from 146.171.18.242: bytes=32 time=11ms TTL=121
Reply from 146.171.18.242: bytes=32 time=16ms TTL=121

Tyler - Parnell Geek - iPhone 3G - Lenovo X301 - Kaseya - Great Western Steak House, these are some of my favourite things.

Talkiet

4786 posts

Uber Geek

Trusted

#305755 9-Mar-2010 18:57

Ditto ok here:

C:\Users\user>ping -t www.theregister.co.uk

Pinging www.theregister.co.uk [212.100.234.54] with 32 bytes of data:
Reply from 212.100.234.54: bytes=32 time=347ms TTL=42
Reply from 212.100.234.54: bytes=32 time=334ms TTL=42
Reply from 212.100.234.54: bytes=32 time=329ms TTL=42
Reply from 212.100.234.54: bytes=32 time=325ms TTL=42
Reply from 212.100.234.54: bytes=32 time=348ms TTL=42
Reply from 212.100.234.54: bytes=32 time=333ms TTL=42
Reply from 212.100.234.54: bytes=32 time=346ms TTL=42
Reply from 212.100.234.54: bytes=32 time=353ms TTL=42
Reply from 212.100.234.54: bytes=32 time=328ms TTL=42
Reply from 212.100.234.54: bytes=32 time=343ms TTL=42
Reply from 212.100.234.54: bytes=32 time=332ms TTL=42
Reply from 212.100.234.54: bytes=32 time=374ms TTL=42
Reply from 212.100.234.54: bytes=32 time=353ms TTL=42
Reply from 212.100.234.54: bytes=32 time=329ms TTL=42
Reply from 212.100.234.54: bytes=32 time=327ms TTL=42
Reply from 212.100.234.54: bytes=32 time=334ms TTL=42
Reply from 212.100.234.54: bytes=32 time=355ms TTL=42
Reply from 212.100.234.54: bytes=32 time=350ms TTL=42
Reply from 212.100.234.54: bytes=32 time=366ms TTL=42
Reply from 212.100.234.54: bytes=32 time=326ms TTL=42
Reply from 212.100.234.54: bytes=32 time=339ms TTL=42
Reply from 212.100.234.54: bytes=32 time=327ms TTL=42
Reply from 212.100.234.54: bytes=32 time=339ms TTL=42

Ping statistics for 212.100.234.54:
Packets: Sent = 23, Received = 23, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 325ms, Maximum = 374ms, Average = 340ms

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.

DravidDavid

1907 posts

Uber Geek

#305775 9-Mar-2010 19:40

C:\Users\David>ping -t www.theregister.co.uk

Pinging www.theregister.co.uk [212.100.234.54] with 32 bytes of data:
Reply from 212.100.234.54: bytes=32 time=357ms TTL=41
Reply from 212.100.234.54: bytes=32 time=357ms TTL=41
Request timed out.
Reply from 212.100.234.54: bytes=32 time=365ms TTL=41
Request timed out.
Reply from 212.100.234.54: bytes=32 time=354ms TTL=41
Reply from 212.100.234.54: bytes=32 time=360ms TTL=41
Reply from 212.100.234.54: bytes=32 time=354ms TTL=41
Request timed out.
Reply from 212.100.234.54: bytes=32 time=355ms TTL=41
Reply from 212.100.234.54: bytes=32 time=355ms TTL=41
Reply from 212.100.234.54: bytes=32 time=356ms TTL=41
Reply from 212.100.234.54: bytes=32 time=355ms TTL=41
Reply from 212.100.234.54: bytes=32 time=359ms TTL=41

Connections time out. Web browsing is even hard let alone playing the odd game.

Trace routs are crap:

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 45 ms 46 ms 43 ms 122-62-240-4.jetstream.xtra.co.nz [122.62.240.4]

3 * * * Request timed out.
4 * * * Request timed out.
5 45 ms 44 ms 43 ms ae4-20.akcr10.global-gateway.net.nz [202.50.238.
49]
6 47 ms 43 ms 43 ms g0-1-0-4.akcr8.global-gateway.net.nz [210.55.202
.49]
7 45 ms 44 ms 45 ms telecom-sdn-ak1-dom.akcr8.global-gateway.net.nz
[203.96.65.198]
8 44 ms 45 ms 44 ms 146.171.18.210
9 44 ms 44 ms 52 ms 146.171.18.242

Trace complete.

It must be exchange. When I complained about slow internet speed with my old provider, Telecom looked at our exchange and replaced a "bad cell". I'm not sure exactly what that means, but whatever it was, it bumped my connection from 52b/s back up to 7.2Mb/s. Maybe it is faulty again...

I am re-testing my connection with the router they gave me, just incase.

EDIT:

Looks like the Telecom router may be faulty:

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

1     4 ms    99 ms    99 ms 192.168.1.254
2    47 ms    46 ms    46 ms 122-62-240-4.jetstream.xtra.co.nz [122.62.240.4]

3     *        *        *     Request timed out.
4     *        *        *     Request timed out.
5    45 ms    45 ms    48 ms ae4-20.akcr10.global-gateway.net.nz [202.50.238.
49]
6    47 ms    47 ms    46 ms g0-1-0-4.akcr8.global-gateway.net.nz [210.55.202
.49]
7    47 ms    46 ms    46 ms telecom-sdn-ak1-dom.akcr8.global-gateway.net.nz
[203.96.65.198]
8    46 ms    46 ms    46 ms 146.171.18.210
9    45 ms    45 ms    45 ms 146.171.18.242

Trace complete.

I am investigating other network issues as we speak. It may not be Telecom's fault after all. My Asus motherboard might be kicking the bucket :(

Lias

5567 posts

Uber Geek

ID Verified

Trusted

Lifetime subscriber

#305806 9-Mar-2010 23:10

International:

Pinging games.on.net [203.26.94.250] with 32 bytes of data:

Request timed out.
Reply from 203.26.94.250: bytes=32 time=65ms TTL=45
Reply from 203.26.94.250: bytes=32 time=65ms TTL=45
Reply from 203.26.94.250: bytes=32 time=64ms TTL=45
Request timed out.
Reply from 203.26.94.250: bytes=32 time=65ms TTL=45
Reply from 203.26.94.250: bytes=32 time=64ms TTL=45
Reply from 203.26.94.250: bytes=32 time=64ms TTL=45
Reply from 203.26.94.250: bytes=32 time=64ms TTL=45
Reply from 203.26.94.250: bytes=32 time=65ms TTL=45

Ping statistics for 203.26.94.250:
    Packets: Sent = 10, Received = 8, Lost = 2 (20% loss),
Approximate round trip times in milli-seconds:
    Minimum = 64ms, Maximum = 65ms, Average = 64ms

Pinging patch.everquest.com [64.37.129.60] with 32 bytes of data:

Reply from 64.37.129.60: bytes=32 time=138ms TTL=117
Request timed out.
Reply from 64.37.129.60: bytes=32 time=137ms TTL=117
Reply from 64.37.129.60: bytes=32 time=137ms TTL=117
Reply from 64.37.129.60: bytes=32 time=137ms TTL=117
Request timed out.
Reply from 64.37.129.60: bytes=32 time=137ms TTL=117
Reply from 64.37.129.60: bytes=32 time=137ms TTL=117
Reply from 64.37.129.60: bytes=32 time=138ms TTL=117
Reply from 64.37.129.60: bytes=32 time=138ms TTL=117

Ping statistics for 64.37.129.60:
    Packets: Sent = 10, Received = 8, Lost = 2 (20% loss),
Approximate round trip times in milli-seconds:
    Minimum = 137ms, Maximum = 138ms, Average = 137ms

Pinging www.cybergamer.com.au [72.32.147.161] with 32 bytes of data:

Reply from 72.32.147.161: bytes=32 time=176ms TTL=50
Reply from 72.32.147.161: bytes=32 time=175ms TTL=50
Reply from 72.32.147.161: bytes=32 time=175ms TTL=50
Reply from 72.32.147.161: bytes=32 time=175ms TTL=50
Reply from 72.32.147.161: bytes=32 time=175ms TTL=50
Request timed out.
Reply from 72.32.147.161: bytes=32 time=176ms TTL=50
Request timed out.
Reply from 72.32.147.161: bytes=32 time=175ms TTL=50
Reply from 72.32.147.161: bytes=32 time=175ms TTL=50

Ping statistics for 72.32.147.161:
    Packets: Sent = 10, Received = 8, Lost = 2 (20% loss),
Approximate round trip times in milli-seconds:
    Minimum = 175ms, Maximum = 176ms, Average = 175ms

etc vs National

Pinging www.telecom.co.nz [146.171.18.242] with 32 bytes of data:

Reply from 146.171.18.242: bytes=32 time=12ms TTL=121
Reply from 146.171.18.242: bytes=32 time=11ms TTL=121
Reply from 146.171.18.242: bytes=32 time=12ms TTL=121
Reply from 146.171.18.242: bytes=32 time=12ms TTL=121
Reply from 146.171.18.242: bytes=32 time=11ms TTL=121
Reply from 146.171.18.242: bytes=32 time=12ms TTL=121
Reply from 146.171.18.242: bytes=32 time=12ms TTL=121
Reply from 146.171.18.242: bytes=32 time=12ms TTL=121
Reply from 146.171.18.242: bytes=32 time=11ms TTL=121
Reply from 146.171.18.242: bytes=32 time=11ms TTL=121

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

Pinging www.stuff.co.nz [202.21.128.102] with 32 bytes of data:

Reply from 202.21.128.102: bytes=32 time=24ms TTL=57
Reply from 202.21.128.102: bytes=32 time=24ms TTL=57
Reply from 202.21.128.102: bytes=32 time=23ms TTL=57
Reply from 202.21.128.102: bytes=32 time=23ms TTL=57
Reply from 202.21.128.102: bytes=32 time=24ms TTL=57
Reply from 202.21.128.102: bytes=32 time=24ms TTL=57
Reply from 202.21.128.102: bytes=32 time=23ms TTL=57
Reply from 202.21.128.102: bytes=32 time=24ms TTL=57
Reply from 202.21.128.102: bytes=32 time=23ms TTL=57
Reply from 202.21.128.102: bytes=32 time=23ms TTL=57

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

Pinging www.gamerhub.co.nz [210.48.63.145] with 32 bytes of data:

Reply from 210.48.63.145: bytes=32 time=11ms TTL=120
Reply from 210.48.63.145: bytes=32 time=11ms TTL=120
Reply from 210.48.63.145: bytes=32 time=12ms TTL=120
Reply from 210.48.63.145: bytes=32 time=11ms TTL=120
Reply from 210.48.63.145: bytes=32 time=11ms TTL=120
Reply from 210.48.63.145: bytes=32 time=11ms TTL=120
Reply from 210.48.63.145: bytes=32 time=12ms TTL=120
Reply from 210.48.63.145: bytes=32 time=11ms TTL=120
Reply from 210.48.63.145: bytes=32 time=12ms TTL=120
Reply from 210.48.63.145: bytes=32 time=13ms TTL=120

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

1 | ... | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | ... | 120