Telecom Big Time plan trouble thread

Forums › Spark New Zealand › Telecom Big Time plan trouble thread

1 | ... | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | ... | 120

60 posts

Master Geek

# 310966 24-Mar-2010 20:40

Still pretty bad tonight. Got a constant ping going to bbc.com

Reply from 212.58.224.138: bytes=32 time=345ms TTL=110
Reply from 212.58.224.138: bytes=32 time=348ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=344ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=345ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=344ms TTL=110
Reply from 212.58.224.138: bytes=32 time=349ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=344ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=344ms TTL=110
Reply from 212.58.224.138: bytes=32 time=345ms TTL=110
Reply from 212.58.224.138: bytes=32 time=345ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=345ms TTL=110

And anywhere international is very similar.

And connection to a citrix poral in ozzie drops out every minute or so. I realise this plan is managed, but until 2 weeks ago I was able to work from home fine.

pasho

72 posts

Master Geek

# 310969 24-Mar-2010 20:46

Ragic: Managed to raid tonight for the first time in 2 weeks :) I'm happy

feel happy for you dude. i havent been able to play at all during last 2 weeks. wow wont login or if it manages to log in pings are above 1000 and nothing really works. ^) maybe there is an issue with ssh tunnels because it just time outs =\

would you please post your pings to LA or seattle during different times of the day, i keep getting 30%+ packet loss

pasho

72 posts

Master Geek

# 310972 24-Mar-2010 20:52

so um yeah, i dont know how this can be explained. 20:55 pm Auckland

and wow lags crazy/wont log me in/ping above 1000 =\

Sheagae

191 posts

Master Geek

# 310975 24-Mar-2010 20:55

ping 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=23ms TTL=120
Reply from 146.171.18.242: bytes=32 time=34ms TTL=120
Reply from 146.171.18.242: bytes=32 time=48ms TTL=120
Reply from 146.171.18.242: bytes=32 time=31ms TTL=120

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

Sorry doozy, things still ain't right.

CrushKill

67 posts

Master Geek

# 310984 24-Mar-2010 21:22

Well, whatever has been done, I think my connection is actually worse. :(

Sheagae

191 posts

Master Geek

# 310985 24-Mar-2010 21:23

I admit it is better than last night, but still as soon as 9pm rolls around, latency goes right up, and speeds fall dramatically.

Finch

2646 posts

Uber Geek

# 310986 24-Mar-2010 21:24

In all my years (6+) of playing "runescape" ive never had such bad lag. Lately, it has been terrible. Wether it be 2pm or 2am lag is generally always there and it has been for the past few days. No matter what world, lag lag lag. Making the game near on un playable.

System

521 posts

Ultimate Geek

# 310989 24-Mar-2010 21:27

For the first night in a while i have had bad pings:

Pinging telecom.co.nz [146.171.18.242] with 32 bytes of data:
Reply from 146.171.18.242: bytes=32 time=863ms TTL=121
Reply from 146.171.18.242: bytes=32 time=525ms TTL=121
Reply from 146.171.18.242: bytes=32 time=454ms TTL=121
Reply from 146.171.18.242: bytes=32 time=542ms TTL=121

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

So if anything the solution to fix it has only made the problem bigger

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

Mobile Phone: iPhone 5 32gb Graphite.

Sheagae

191 posts

Master Geek

# 310991 24-Mar-2010 21:29

System: For the first night in a while i have had bad pings:

Pinging telecom.co.nz [146.171.18.242] with 32 bytes of data:
Reply from 146.171.18.242: bytes=32 time=863ms TTL=121
Reply from 146.171.18.242: bytes=32 time=525ms TTL=121
Reply from 146.171.18.242: bytes=32 time=454ms TTL=121
Reply from 146.171.18.242: bytes=32 time=542ms TTL=121

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

So if anything the solution to fix it has only made the problem bigger

You sound suprised? Why would you be suprised??

System

521 posts

Ultimate Geek

# 311002 24-Mar-2010 21:42

Sheagae:
System: For the first night in a while i have had bad pings:

Pinging telecom.co.nz [146.171.18.242] with 32 bytes of data:
Reply from 146.171.18.242: bytes=32 time=863ms TTL=121
Reply from 146.171.18.242: bytes=32 time=525ms TTL=121
Reply from 146.171.18.242: bytes=32 time=454ms TTL=121
Reply from 146.171.18.242: bytes=32 time=542ms TTL=121

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

So if anything the solution to fix it has only made the problem bigger

You sound suprised? Why would you be suprised??

Because unlike what seems like everyone on here i have had no issues with my connection during the last few nights and all of a sudden i have been dragged into the problem

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

Mobile Phone: iPhone 5 32gb Graphite.

doozy

245 posts

Master Geek

Trusted

# 311004 24-Mar-2010 21:44

System: For the first night in a while i have had bad pings:

Pinging telecom.co.nz [146.171.18.242] with 32 bytes of data:
Reply from 146.171.18.242: bytes=32 time=863ms TTL=121
Reply from 146.171.18.242: bytes=32 time=525ms TTL=121
Reply from 146.171.18.242: bytes=32 time=454ms TTL=121
Reply from 146.171.18.242: bytes=32 time=542ms TTL=121

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

So if anything the solution to fix it has only made the problem bigger

I should have added the problem device is right on the edge of the network so pings to Telecom.co would not be affected, this is not related

Tarawera Ultra 2015 done, bring on 2016

scobb

10 posts

Wannabe Geek

# 311017 24-Mar-2010 21:56

WallySimmonds: Still pretty bad tonight. Got a constant ping going to bbc.com

Reply from 212.58.224.138: bytes=32 time=345ms TTL=110
Reply from 212.58.224.138: bytes=32 time=348ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=344ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=345ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=344ms TTL=110
Reply from 212.58.224.138: bytes=32 time=349ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=344ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=344ms TTL=110
Reply from 212.58.224.138: bytes=32 time=345ms TTL=110
Reply from 212.58.224.138: bytes=32 time=345ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=345ms TTL=110

And anywhere international is very similar.

I'm a Telecom Broadband Pro user, having given up on BigTime as unusable for any form of streaming media from sites like the BBC. Here are my stats for bbc.com @ 9:47pm:

Reply from 212.58.224.138: bytes=32 time=606ms TTL=110
Reply from 212.58.224.138: bytes=32 time=605ms TTL=110
Reply from 212.58.224.138: bytes=32 time=648ms TTL=110
Reply from 212.58.224.138: bytes=32 time=628ms TTL=110
Reply from 212.58.224.138: bytes=32 time=653ms TTL=110
Reply from 212.58.224.138: bytes=32 time=644ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=631ms TTL=110
Reply from 212.58.224.138: bytes=32 time=622ms TTL=110
Reply from 212.58.224.138: bytes=32 time=591ms TTL=110
Reply from 212.58.224.138: bytes=32 time=614ms TTL=110
Reply from 212.58.224.138: bytes=32 time=611ms TTL=110

At the same time as I was getting the above pings from my home Telecom link, I connected in via VPN to my office where we have a 20mbps link with Telstra Clear. Here are those results:

Reply from 212.58.224.138: bytes=32 time=283ms TTL=116
Reply from 212.58.224.138: bytes=32 time=282ms TTL=116
Reply from 212.58.224.138: bytes=32 time=282ms TTL=116
Reply from 212.58.224.138: bytes=32 time=291ms TTL=116
Reply from 212.58.224.138: bytes=32 time=283ms TTL=116
Reply from 212.58.224.138: bytes=32 time=282ms TTL=116
Reply from 212.58.224.138: bytes=32 time=285ms TTL=116
Reply from 212.58.224.138: bytes=32 time=288ms TTL=116
Reply from 212.58.224.138: bytes=32 time=282ms TTL=116
Reply from 212.58.224.138: bytes=32 time=283ms TTL=116
Reply from 212.58.224.138: bytes=32 time=283ms TTL=116
Reply from 212.58.224.138: bytes=32 time=282ms TTL=116

What is going on here Telecom?