Telecom Big Time plan trouble thread

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

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

521 posts

Ultimate Geek

#315237 6-Apr-2010 09:32

crazed: 9am? Thought it was 8am the shaping turns back on?

It has been until 9am for me for the last week or so apart from today that is

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

Mobile Phone: iPhone 5 32gb Graphite.

ArranH

161 posts

Master Geek

#315238 6-Apr-2010 09:36

System:
crazed: 9am? Thought it was 8am the shaping turns back on?

It has been until 9am for me for the last week or so apart from today that is

I've always noticed offpeak as being between 2am and 9am, except for the past 3 weeks.

shadybrothers

236 posts

Master Geek

#315277 6-Apr-2010 12:00

@System rip your windows media to an iso and set it up on a USB stick.

this is a slap in the face!

System

521 posts

Ultimate Geek

#315286 6-Apr-2010 12:40

What does that have to do with anything?

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

Mobile Phone: iPhone 5 32gb Graphite.

shadybrothers

236 posts

Master Geek

#315289 6-Apr-2010 12:49

Apologies, that should have been directed @crazed

this is a slap in the face!

boykunk

32 posts

Geek

#315324 6-Apr-2010 14:00

back in this thread again. speed is just impossible to go on facebook or play games. one minute the latency in cs1.6 would be <20ms, next minute it would jump to >300ms. rediculious. have been with telecom for 10 years and is really thinking about ditching them (going on blacklist).

i guess thats how slow telecom resolves problems.

Talkiet

4792 posts

Uber Geek

Trusted

#315327 6-Apr-2010 14:09

Next time someone notices increased latency to a site like telecom.co.nz (specifically something national) with some apparent packetloss, could you please try the following command?

ping -n 100 -w 10000 telecom.co.nz

What this does (on most windows versions) is increase the wait period for each reply to 10 seconds, and send 100 packets instead of 4.

I would like to see if the packet loss currently observed is actually a lost packet, or if some packets are just being delayed over the default windows timeout period.

This may point to one of the causes of problems.

Regards
Neil G

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.

Tradepub

Free professional, reference and technical white papers (affiliate link).

crazed

484 posts

Ultimate Geek

Trusted

#315328 6-Apr-2010 14:12

shadybrothers: Apologies, that should have been directed @crazed

Yes have done that afew times with linux installs works well, although windows does throw alittle fit now and then.

CraZeD,
Your friendly Southern Geeky Fellow :P

ArranH

161 posts

Master Geek

#315331 6-Apr-2010 14:22

boykunk: back in this thread again. speed is just impossible to go on facebook or play games. one minute the latency in cs1.6 would be <20ms, next minute it would jump to >300ms. rediculious. have been with telecom for 10 years and is really thinking about ditching them (going on blacklist).

i guess thats how slow telecom resolves problems.

I wouldn't be to quick to change until you read of others experiences of which ever ISP you go to. I've been with most ISPs in NZ over the years (so some may have improved) and Telecom, up until recently, was the best. I know I'd hate to change and find what I changed to was even worse.

Savageone

44 posts

Geek

#315340 6-Apr-2010 14:56

System:
crazed: 9am? Thought it was 8am the shaping turns back on?

It has been until 9am for me for the last week or so apart from today that is

yeah shaping has started at 8am (possibly due to the clocks going back the system not being updated?)

System

521 posts

Ultimate Geek

#315343 6-Apr-2010 15:00

Savageone:
System:
crazed: 9am? Thought it was 8am the shaping turns back on?

It has been until 9am for me for the last week or so apart from today that is

yeah shaping has started at 8am (possibly due to the clocks going back the system not being updated?)

Didn't think about that, thats probably it

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

Mobile Phone: iPhone 5 32gb Graphite.

pasho

72 posts

Master Geek

#315478 6-Apr-2010 19:46

yeah. probably i was correct yesterday saying that too many people at home downloading... now, 8pm Auckland, torrent going at ~300kb/s

Sheagae

208 posts

Master Geek

#315480 6-Apr-2010 19:57

Talkiet: Next time someone notices increased latency to a site like telecom.co.nz (specifically something national) with some apparent packetloss, could you please try the following command?

ping -n 100 -w 10000 telecom.co.nz

What this does (on most windows versions) is increase the wait period for each reply to 10 seconds, and send 100 packets instead of 4.

I would like to see if the packet loss currently observed is actually a lost packet, or if some packets are just being delayed over the default windows timeout period.

This may point to one of the causes of problems.

Regards
Neil G

All over the place at the moment. Normal ping to telecom.co.nz is around 12ms.

ping -n 100 -w 10000 telecom.co.nz

Pinging telecom.co.nz [146.171.18.242] with 32 bytes of data:
Reply from 146.171.18.242: bytes=32 time=14ms TTL=120
Reply from 146.171.18.242: bytes=32 time=59ms TTL=120
Reply from 146.171.18.242: bytes=32 time=35ms TTL=120
Reply from 146.171.18.242: bytes=32 time=40ms TTL=120
Reply from 146.171.18.242: bytes=32 time=63ms TTL=120
Reply from 146.171.18.242: bytes=32 time=87ms TTL=120
Reply from 146.171.18.242: bytes=32 time=342ms TTL=120
Reply from 146.171.18.242: bytes=32 time=92ms TTL=120
Reply from 146.171.18.242: bytes=32 time=44ms TTL=120
Reply from 146.171.18.242: bytes=32 time=59ms TTL=120
Reply from 146.171.18.242: bytes=32 time=99ms TTL=120
Reply from 146.171.18.242: bytes=32 time=97ms TTL=120
Reply from 146.171.18.242: bytes=32 time=57ms TTL=120
Reply from 146.171.18.242: bytes=32 time=31ms TTL=120
Reply from 146.171.18.242: bytes=32 time=69ms TTL=120
Reply from 146.171.18.242: bytes=32 time=55ms TTL=120
Reply from 146.171.18.242: bytes=32 time=95ms TTL=120
Reply from 146.171.18.242: bytes=32 time=82ms TTL=120
Reply from 146.171.18.242: bytes=32 time=88ms TTL=120
Reply from 146.171.18.242: bytes=32 time=97ms TTL=120
Reply from 146.171.18.242: bytes=32 time=26ms TTL=120
Reply from 146.171.18.242: bytes=32 time=35ms TTL=120
Reply from 146.171.18.242: bytes=32 time=94ms TTL=120
Reply from 146.171.18.242: bytes=32 time=102ms TTL=120
Reply from 146.171.18.242: bytes=32 time=97ms TTL=120
Reply from 146.171.18.242: bytes=32 time=74ms TTL=120

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

Talkiet

4792 posts

Uber Geek

Trusted

#315483 6-Apr-2010 20:07

Sheagae:
All over the place at the moment. Normal ping to telecom.co.nz is around 12ms.

ping -n 100 -w 10000 telecom.co.nz

Pinging telecom.co.nz [146.171.18.242] with 32 bytes of data:
Reply from 146.171.18.242: bytes=32 time=14ms TTL=120

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

Thanks... I'd be interested to know if at any point any of the latencies get above a second, and if you see packet loss with the -w 10000 modifier.

Cheers - Neil G

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

#315508 6-Apr-2010 21:09

Talkiet: Next time someone notices increased latency to a site like telecom.co.nz (specifically something national) with some apparent packetloss, could you please try the following command?

ping -n 100 -w 10000 telecom.co.nz

What this does (on most windows versions) is increase the wait period for each reply to 10 seconds, and send 100 packets instead of 4.

I would like to see if the packet loss currently observed is actually a lost packet, or if some packets are just being delayed over the default windows timeout period.

This may point to one of the causes of problems.

Regards
Neil G

Here is my result of testing that tonight when my ping skyrocketed

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

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

Mobile Phone: iPhone 5 32gb Graphite.

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