Telecom Big Time plan trouble thread

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

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

1907 posts

Uber Geek

#315757 7-Apr-2010 13:56

Not for me.

It certainly isn't like it was three weeks ago.

Mighty Ape

Shop Mighty Ape for electronics, games, computers books and more (affiliate link).

pasho

72 posts

Master Geek

#315790 7-Apr-2010 15:34

did some testing after 3am last night. it appears that ssh/ssl is throttled even after that time. every server that uses https had extremely long waiting time. some - just timeout. tested exactly the same servers that have both http and https. http works flawlessly, https is a no go at all.

ArranH

161 posts

Master Geek

#315793 7-Apr-2010 15:46

I'm finding the same thing now, trying to access my education provider in Australia via https and its timing out. That is just stupid.

And they definitely shouldn't be throttling it at 3am.

https is in VERY common usage, to throttle it to the level it is is ridiculous.

DravidDavid

1907 posts

Uber Geek

#315795 7-Apr-2010 15:51

Yahoo Xtra is one of Telecom's home pages right?

Since Telecom and Xtra are plastered all over it and you log into your Xtra mail there, I would expect that everything on that page be at least usable. I can't watch a video at 50k let alone 1500k. The page itself takes long enough to load up. The email log in works fine though.

Ugh.

Talkiet

4689 posts

Uber Geek

Trusted

#315798 7-Apr-2010 15:53

DravidDavid: Yahoo Xtra is one of Telecom's home pages right?

Since Telecom and Xtra are plastered all over it and you log into your Xtra mail there, I would expect that everything on that page be at least usable. I can't watch a video at 50k let alone 1500k. The page itself takes long enough to load up. The email log in works fine though.

Ugh.

I'm not defending the performance, but you probably know that a lot of the information on that page is international and therefore is hit by the current big time management rules.

Cheers - N

Please note all comments are the product of 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

#315802 7-Apr-2010 15:57

Talkiet:
DravidDavid: Yahoo Xtra is one of Telecom's home pages right?

Since Telecom and Xtra are plastered all over it and you log into your Xtra mail there, I would expect that everything on that page be at least usable. I can't watch a video at 50k let alone 1500k. The page itself takes long enough to load up. The email log in works fine though.

Ugh.

I'm not defending the performance, but you probably know that a lot of the information on that page is international and therefore is hit by the current big time management rules.

Cheers - N

True...But its Telecoms. I think its kinda silly. Even though they probably won't be able to do anything about it.

l43a2

1746 posts

Uber Geek

ID Verified

Trusted

#315833 7-Apr-2010 18:10

finally off BigTime, Real internet is so so nice :)

crazed

484 posts

Ultimate Geek

Trusted

#315851 7-Apr-2010 19:11

Well I have logged my second call to telecom and given them a deadline to fix it or I'm off to another provider. When it starts affecting everyday aspects of my internet use like internet banking, thats it!

hehe told them I would like to upgrade to dialup, I got silence lol

CraZeD,
Your friendly Southern Geeky Fellow :P

System

521 posts

Ultimate Geek

#315857 7-Apr-2010 19:35

Talkiet: 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...

Cheers - N

Here is my trace route:
Tracing route to 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    68 ms    61 ms    83 ms 210-55-64-32.adsl.netgate.net.nz [210.55.64.32]
3     *        *        *     Request timed out.
4    92 ms   127 ms   100 ms ae4-20.akcr10.global-gateway.net.nz [202.50.238.49]
5   287 ms   173 ms   148 ms g0-1-0-4.akcr8.global-gateway.net.nz [210.55.202.49]
6    34 ms    27 ms    32 ms telecom-sdn-ak1-dom.akcr8.global-gateway.net.nz [203.96.65.198]
7   104 ms    63 ms    50 ms 146.171.18.210
8    31 ms    30 ms    29 ms 146.171.18.242

Here is the ping result that you asked for pinging the first hop (210.55.64.32) although i think the problem stopped by the time i got there, i will try again when it comes back again and give you a second result.

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

I did a ping to telecom.co.nz after the ping to the first hop was done and the ping had got back to normal before i could test it, tonight dosn't seem to be bad so far for ping, speeds are terrible

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

#315861 7-Apr-2010 19:46

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

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

Trace complete.

Ping statistics for 210.55.67.1:
   Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
   Minimum = 9ms, Maximum = 74ms, Average = 10ms

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

Anybody seen my packets? telecom lost them? lol

CraZeD,
Your friendly Southern Geeky Fellow :P

DravidDavid

1907 posts

Uber Geek

#315862 7-Apr-2010 19:51

crazed:told them I would like to upgrade to dialup, I got silence lol

Nice one! What did they say when you gave them a dead-line?

It is getting pretty rediculous.

crazed

484 posts

Ultimate Geek

Trusted

#315865 7-Apr-2010 19:57

DravidDavid:
crazed:told them I would like to upgrade to dialup, I got silence lol

Nice one! What did they say when you gave them a dead-line?

It is getting pretty rediculous.

Not a great deal actually but then it was a trained monkey, probably had a cue card that says "When given deadline, act like robot"

CraZeD,
Your friendly Southern Geeky Fellow :P

System

521 posts

Ultimate Geek

#315867 7-Apr-2010 20:02

I did another one of the trace routes and ping tests once the problem came back, here is a better result:

1    <1 ms    <1 ms    <1 ms 192.168.1.1
2   327 ms   341 ms   451 ms 210-55-64-32.adsl.netgate.net.nz [210.55.64.32]
3     *        *        *     Request timed out.
4   705 ms   932 ms   746 ms ae4-20.akcr10.global-gateway.net.nz [202.50.238.49]
5   547 ms   554 ms   836 ms g0-1-0-4.akcr8.global-gateway.net.nz [210.55.202.49]
6   745 ms   694 ms   425 ms telecom-sdn-ak1-dom.akcr8.global-gateway.net.nz [203.96.65.198]
7   558 ms   622 ms   615 ms 146.171.18.210
8 1035 ms   778 ms   745 ms 146.171.18.242

Pinging 210.55.64.32 with 32 bytes of data:
Reply from 210.55.64.32: bytes=32 time=303ms TTL=126
Reply from 210.55.64.32: bytes=32 time=268ms TTL=126
Reply from 210.55.64.32: bytes=32 time=152ms TTL=126
Reply from 210.55.64.32: bytes=32 time=15ms TTL=126
Reply from 210.55.64.32: bytes=32 time=28ms TTL=126
Reply from 210.55.64.32: bytes=32 time=40ms TTL=126
Reply from 210.55.64.32: bytes=32 time=62ms TTL=126
Reply from 210.55.64.32: bytes=32 time=118ms TTL=126
Reply from 210.55.64.32: bytes=32 time=107ms TTL=126
Reply from 210.55.64.32: bytes=32 time=181ms TTL=126
Reply from 210.55.64.32: bytes=32 time=127ms TTL=126
Reply from 210.55.64.32: bytes=32 time=19ms TTL=126
Reply from 210.55.64.32: bytes=32 time=65ms TTL=126
Reply from 210.55.64.32: bytes=32 time=132ms TTL=126
Reply from 210.55.64.32: bytes=32 time=238ms TTL=126
Reply from 210.55.64.32: bytes=32 time=391ms TTL=126
Reply from 210.55.64.32: bytes=32 time=337ms TTL=126
Reply from 210.55.64.32: bytes=32 time=288ms TTL=126
Reply from 210.55.64.32: bytes=32 time=154ms TTL=126
Reply from 210.55.64.32: bytes=32 time=357ms TTL=126
Reply from 210.55.64.32: bytes=32 time=349ms TTL=126
Reply from 210.55.64.32: bytes=32 time=348ms TTL=126
Reply from 210.55.64.32: bytes=32 time=393ms TTL=126
Reply from 210.55.64.32: bytes=32 time=292ms TTL=126
Reply from 210.55.64.32: bytes=32 time=315ms TTL=126
Reply from 210.55.64.32: bytes=32 time=376ms TTL=126
Reply from 210.55.64.32: bytes=32 time=384ms TTL=126
Reply from 210.55.64.32: bytes=32 time=332ms TTL=126
Reply from 210.55.64.32: bytes=32 time=211ms TTL=126
Reply from 210.55.64.32: bytes=32 time=157ms TTL=126
Reply from 210.55.64.32: bytes=32 time=191ms TTL=126
Reply from 210.55.64.32: bytes=32 time=133ms TTL=126
Reply from 210.55.64.32: bytes=32 time=118ms TTL=126
Reply from 210.55.64.32: bytes=32 time=139ms TTL=126
Reply from 210.55.64.32: bytes=32 time=88ms TTL=126
Reply from 210.55.64.32: bytes=32 time=57ms TTL=126

Ping statistics for 210.55.64.32:
    Packets: Sent = 100, Received = 100, Lost = 0 (0%
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 501ms, Average = 141ms

I don't have the packet loss, just massive ping

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

Mobile Phone: iPhone 5 32gb Graphite.

nate

6469 posts

Uber Geek

Moderator

Trusted

Lifetime subscriber

#315905 7-Apr-2010 21:12

System: I don't have the packet loss, just massive ping

Not sure what's changed but I'm also getting very high ping (wasn't like this last night):

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

Reply from 146.171.18.242: bytes=32 time=290ms TTL=121
Reply from 146.171.18.242: bytes=32 time=415ms TTL=121
Reply from 146.171.18.242: bytes=32 time=335ms TTL=121
Reply from 146.171.18.242: bytes=32 time=358ms TTL=121
Reply from 146.171.18.242: bytes=32 time=279ms TTL=121
Reply from 146.171.18.242: bytes=32 time=291ms TTL=121
Reply from 146.171.18.242: bytes=32 time=418ms TTL=121
Reply from 146.171.18.242: bytes=32 time=441ms TTL=121
Reply from 146.171.18.242: bytes=32 time=469ms TTL=121
Reply from 146.171.18.242: bytes=32 time=487ms TTL=121
Reply from 146.171.18.242: bytes=32 time=305ms TTL=121

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

skewt

705 posts

Ultimate Geek

#315917 7-Apr-2010 21:27

my tracert reports my first hop as kc.net.nz, must be a reused ip

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

1    70 ms    99 ms    99 ms dsldevice.lan [192.168.1.254]
2    30 ms    31 ms    35 ms 210.55.69.248
3     *        *        *     Request timed out.
4    53 ms    53 ms    54 ms ae4-20.akcr10.global-gateway.net.nz [202.50.238.49]
5    53 ms    53 ms    54 ms g0-1-0-4.akcr8.global-gateway.net.nz [210.55.202.49]
6    54 ms    54 ms    53 ms telecom-sdn-ak1-dom.akcr8.global-gateway.net.nz [203.96.65.198]
7    54 ms    54 ms    54 ms 146.171.18.210
8    54 ms    53 ms    54 ms 146.171.18.242

Trace complete.

Name:    ip210-55-69-248.kc.net.nz
Address: 210.55.69.248
Aliases: 248.69.55.210.in-addr.arpa

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