Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


View this topic in a long page with up to 500 replies per page Create new topic
1 | 2 | 3 | 4 | 5
60 posts

Master Geek


  # 705989 24-Oct-2012 22:00

My latency has been up over the past week or so during the evenings, particularly in WoW, I have had five dc's on average a night, nothing major really but I thought I would post here.

I'm down in Dunedin, Maori Hill phone exchange I believe.

111 posts

Master Geek

Trusted

  # 709549 30-Oct-2012 23:13
Send private message

Hi gents,

Can you tell me if this has improved at all since today?

Cheers




“I do not think there is any thrill that can go through the human heart like that felt by the inventor as he sees some creation of the brain unfolding to success... Such emotions make a man forget food, sleep, friends, love, everything.” - Nikola Tesla

 


Disclaimer: Views expressed in my posts do not necessarily reflect those views of my employer.

 
 
 
 




3385 posts

Uber Geek

Trusted

  # 709562 30-Oct-2012 23:46
Send private message

Hi Tim,

Looks fine right now, though it's a little later than when I usually see the increased latency. I'll check again tomorrow night around 8-9pm.


C:\Users\Simon>ping 202.37.101.1 /t

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61

Ping statistics for 202.37.101.1:
Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 6ms, Average = 5ms
Control-C
^C
C:\Users\Simon>ping /t 202.162.73.2

Pinging 202.162.73.2 with 32 bytes of data:
Reply from 202.162.73.2: bytes=32 time=7ms TTL=250
Reply from 202.162.73.2: bytes=32 time=6ms TTL=250
Reply from 202.162.73.2: bytes=32 time=6ms TTL=250
Reply from 202.162.73.2: bytes=32 time=6ms TTL=250
Reply from 202.162.73.2: bytes=32 time=6ms TTL=250
Reply from 202.162.73.2: bytes=32 time=6ms TTL=250
Reply from 202.162.73.2: bytes=32 time=6ms TTL=250

Ping statistics for 202.162.73.2:
Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 7ms, Average = 6ms
Control-C
^C
C:\Users\Simon>


Looking at my Truenet graphs they're not showing an improvement, though they are averaged over a week I think so if the improvement is recent it probably won't show yet. Domestic ping is looking more as I would expect (not sure why last one was all over the place like that) but now:




3385 posts

Uber Geek

Trusted

  # 710146 31-Oct-2012 23:53
Send private message

It's possibly improved a bit, but not a huge amount. I left the following script running from 17:40 this afternoon to see what it looked like:

 
:TOP

(echo. && echo. && echo %date% %time%) >> "C:\PingLog.txt"

ping -n 10 202.37.101.1 >> "C:\PingLog.txt"

PING 1.1.1.1 -n 1 -w 20000 >NUL

GOTO TOP




It starts well enough, then around 20:00 starts to climb. From 21:00-22:40 it's at the worst then starts to drop back down. After 23:00 back to normal.


31/10/2012 17:40:52.31

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61

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

...............................

31/10/2012 20:05:23.81

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=7ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61

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


31/10/2012 20:05:52.81

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=22ms TTL=61
Reply from 202.37.101.1: bytes=32 time=20ms TTL=61
Reply from 202.37.101.1: bytes=32 time=19ms TTL=61
Reply from 202.37.101.1: bytes=32 time=18ms TTL=61
Reply from 202.37.101.1: bytes=32 time=19ms TTL=61
Reply from 202.37.101.1: bytes=32 time=14ms TTL=61
Reply from 202.37.101.1: bytes=32 time=12ms TTL=61
Reply from 202.37.101.1: bytes=32 time=8ms TTL=61
Reply from 202.37.101.1: bytes=32 time=7ms TTL=61
Reply from 202.37.101.1: bytes=32 time=10ms TTL=61

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


31/10/2012 20:06:21.81

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=24ms TTL=61
Reply from 202.37.101.1: bytes=32 time=23ms TTL=61
Reply from 202.37.101.1: bytes=32 time=35ms TTL=61
Reply from 202.37.101.1: bytes=32 time=23ms TTL=61
Reply from 202.37.101.1: bytes=32 time=19ms TTL=61
Reply from 202.37.101.1: bytes=32 time=13ms TTL=61
Reply from 202.37.101.1: bytes=32 time=14ms TTL=61
Reply from 202.37.101.1: bytes=32 time=13ms TTL=61
Reply from 202.37.101.1: bytes=32 time=11ms TTL=61
Reply from 202.37.101.1: bytes=32 time=8ms TTL=61

...........................

31/10/2012 20:16:01.81

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=21ms TTL=61
Reply from 202.37.101.1: bytes=32 time=23ms TTL=61
Reply from 202.37.101.1: bytes=32 time=24ms TTL=61
Reply from 202.37.101.1: bytes=32 time=24ms TTL=61
Reply from 202.37.101.1: bytes=32 time=33ms TTL=61
Reply from 202.37.101.1: bytes=32 time=33ms TTL=61
Reply from 202.37.101.1: bytes=32 time=30ms TTL=61
Reply from 202.37.101.1: bytes=32 time=37ms TTL=61
Reply from 202.37.101.1: bytes=32 time=36ms TTL=61
Reply from 202.37.101.1: bytes=32 time=34ms TTL=61

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


31/10/2012 20:16:30.81

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=20ms TTL=61
Reply from 202.37.101.1: bytes=32 time=17ms TTL=61
Reply from 202.37.101.1: bytes=32 time=11ms TTL=61
Reply from 202.37.101.1: bytes=32 time=17ms TTL=61
Reply from 202.37.101.1: bytes=32 time=15ms TTL=61
Reply from 202.37.101.1: bytes=32 time=20ms TTL=61
Reply from 202.37.101.1: bytes=32 time=27ms TTL=61
Reply from 202.37.101.1: bytes=32 time=28ms TTL=61
Reply from 202.37.101.1: bytes=32 time=31ms TTL=61
Reply from 202.37.101.1: bytes=32 time=22ms TTL=61

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


..........................

31/10/2012 21:00:04.81

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=37ms TTL=61
Reply from 202.37.101.1: bytes=32 time=39ms TTL=61
Reply from 202.37.101.1: bytes=32 time=41ms TTL=61
Reply from 202.37.101.1: bytes=32 time=42ms TTL=61
Reply from 202.37.101.1: bytes=32 time=44ms TTL=61
Reply from 202.37.101.1: bytes=32 time=46ms TTL=61
Reply from 202.37.101.1: bytes=32 time=47ms TTL=61
Reply from 202.37.101.1: bytes=32 time=45ms TTL=61
Reply from 202.37.101.1: bytes=32 time=47ms TTL=61
Reply from 202.37.101.1: bytes=32 time=48ms TTL=61

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


31/10/2012 21:00:33.81

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=41ms TTL=61
Reply from 202.37.101.1: bytes=32 time=47ms TTL=61
Reply from 202.37.101.1: bytes=32 time=41ms TTL=61
Reply from 202.37.101.1: bytes=32 time=37ms TTL=61
Reply from 202.37.101.1: bytes=32 time=44ms TTL=61
Reply from 202.37.101.1: bytes=32 time=41ms TTL=61
Reply from 202.37.101.1: bytes=32 time=47ms TTL=61
Reply from 202.37.101.1: bytes=32 time=45ms TTL=61
Reply from 202.37.101.1: bytes=32 time=42ms TTL=61
Reply from 202.37.101.1: bytes=32 time=38ms TTL=61

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


31/10/2012 21:01:02.81

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=43ms TTL=61
Reply from 202.37.101.1: bytes=32 time=46ms TTL=61
Reply from 202.37.101.1: bytes=32 time=42ms TTL=61
Reply from 202.37.101.1: bytes=32 time=38ms TTL=61
Reply from 202.37.101.1: bytes=32 time=42ms TTL=61
Reply from 202.37.101.1: bytes=32 time=42ms TTL=61
Reply from 202.37.101.1: bytes=32 time=42ms TTL=61
Reply from 202.37.101.1: bytes=32 time=43ms TTL=61
Reply from 202.37.101.1: bytes=32 time=41ms TTL=61
Reply from 202.37.101.1: bytes=32 time=40ms TTL=61

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


.............................


31/10/2012 22:15:41.82

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=46ms TTL=61
Reply from 202.37.101.1: bytes=32 time=38ms TTL=61
Reply from 202.37.101.1: bytes=32 time=46ms TTL=61
Reply from 202.37.101.1: bytes=32 time=35ms TTL=61
Reply from 202.37.101.1: bytes=32 time=46ms TTL=61
Reply from 202.37.101.1: bytes=32 time=43ms TTL=61
Reply from 202.37.101.1: bytes=32 time=47ms TTL=61
Reply from 202.37.101.1: bytes=32 time=37ms TTL=61
Reply from 202.37.101.1: bytes=32 time=41ms TTL=61
Reply from 202.37.101.1: bytes=32 time=45ms TTL=61

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


31/10/2012 22:16:10.81

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=46ms TTL=61
Reply from 202.37.101.1: bytes=32 time=45ms TTL=61
Reply from 202.37.101.1: bytes=32 time=30ms TTL=61
Reply from 202.37.101.1: bytes=32 time=35ms TTL=61
Reply from 202.37.101.1: bytes=32 time=43ms TTL=61
Reply from 202.37.101.1: bytes=32 time=43ms TTL=61
Reply from 202.37.101.1: bytes=32 time=41ms TTL=61
Reply from 202.37.101.1: bytes=32 time=44ms TTL=61
Reply from 202.37.101.1: bytes=32 time=39ms TTL=61
Reply from 202.37.101.1: bytes=32 time=46ms TTL=61

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

.................................

31/10/2012 22:47:43.81

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=31ms TTL=61
Reply from 202.37.101.1: bytes=32 time=26ms TTL=61
Reply from 202.37.101.1: bytes=32 time=25ms TTL=61
Reply from 202.37.101.1: bytes=32 time=25ms TTL=61
Reply from 202.37.101.1: bytes=32 time=21ms TTL=61
Reply from 202.37.101.1: bytes=32 time=27ms TTL=61
Reply from 202.37.101.1: bytes=32 time=31ms TTL=61
Reply from 202.37.101.1: bytes=32 time=30ms TTL=61
Reply from 202.37.101.1: bytes=32 time=34ms TTL=61
Reply from 202.37.101.1: bytes=32 time=29ms TTL=61

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


31/10/2012 22:48:12.81

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=17ms TTL=61
Reply from 202.37.101.1: bytes=32 time=14ms TTL=61
Reply from 202.37.101.1: bytes=32 time=15ms TTL=61
Reply from 202.37.101.1: bytes=32 time=9ms TTL=61
Reply from 202.37.101.1: bytes=32 time=9ms TTL=61
Reply from 202.37.101.1: bytes=32 time=7ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=11ms TTL=61
Reply from 202.37.101.1: bytes=32 time=13ms TTL=61
Reply from 202.37.101.1: bytes=32 time=15ms TTL=61

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


31/10/2012 22:48:41.81

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=17ms TTL=61
Reply from 202.37.101.1: bytes=32 time=21ms TTL=61
Reply from 202.37.101.1: bytes=32 time=17ms TTL=61
Reply from 202.37.101.1: bytes=32 time=13ms TTL=61
Reply from 202.37.101.1: bytes=32 time=8ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=7ms TTL=61
Reply from 202.37.101.1: bytes=32 time=13ms TTL=61
Reply from 202.37.101.1: bytes=32 time=11ms TTL=61
Reply from 202.37.101.1: bytes=32 time=17ms TTL=61


..........


31/10/2012 23:02:42.81

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=7ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=8ms TTL=61

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


31/10/2012 23:03:11.82

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61

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

29 posts

Geek


  # 712524 5-Nov-2012 19:28
Send private message

Just coming back to this thread now, connected to Three Kings Exchange.  Jitter still around but a wee bit better.

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=18ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=20ms TTL=61
Reply from 202.37.101.1: bytes=32 time=7ms TTL=61
Reply from 202.37.101.1: bytes=32 time=7ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=20ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=25ms TTL=61
Reply from 202.37.101.1: bytes=32 time=7ms TTL=61
Reply from 202.37.101.1: bytes=32 time=17ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=22ms TTL=61
Reply from 202.37.101.1: bytes=32 time=9ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61

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

111 posts

Master Geek

Trusted

  # 712601 5-Nov-2012 22:09
Send private message

Sidefx: Just a quick update --

I've started continuous latency testing to a number of business sites we have connected via the same handover (using something called 'smokeping').

I'll post an update by Wednesday (I want a couple of nights' data).





“I do not think there is any thrill that can go through the human heart like that felt by the inventor as he sees some creation of the brain unfolding to success... Such emotions make a man forget food, sleep, friends, love, everything.” - Nikola Tesla

 


Disclaimer: Views expressed in my posts do not necessarily reflect those views of my employer.



3385 posts

Uber Geek

Trusted

  # 712627 5-Nov-2012 22:55
Send private message

Thanks, you guys rock. :)

 
 
 
 


68 posts

Master Geek


  # 713146 6-Nov-2012 20:44
Send private message

Connected Glen Eden

06 Nov 20:44

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=199ms TTL=61
Reply from 202.37.101.1: bytes=32 time=35ms TTL=61
Reply from 202.37.101.1: bytes=32 time=183ms TTL=61
Reply from 202.37.101.1: bytes=32 time=116ms TTL=61
Reply from 202.37.101.1: bytes=32 time=101ms TTL=61
Reply from 202.37.101.1: bytes=32 time=142ms TTL=61
Reply from 202.37.101.1: bytes=32 time=121ms TTL=61
Reply from 202.37.101.1: bytes=32 time=180ms TTL=61
Reply from 202.37.101.1: bytes=32 time=234ms TTL=61
Reply from 202.37.101.1: bytes=32 time=66ms TTL=61
Reply from 202.37.101.1: bytes=32 time=95ms TTL=61
Reply from 202.37.101.1: bytes=32 time=151ms TTL=61
Reply from 202.37.101.1: bytes=32 time=149ms TTL=61

111 posts

Master Geek

Trusted

  # 713158 6-Nov-2012 21:07
Send private message

That's quite bad. Are you guys happy to PM me your Snap usernames? I want to set up pings directly to you (and some traffic graphs of your connection at the same time). I'm keen to catch/fix this ASAP!




“I do not think there is any thrill that can go through the human heart like that felt by the inventor as he sees some creation of the brain unfolding to success... Such emotions make a man forget food, sleep, friends, love, everything.” - Nikola Tesla

 


Disclaimer: Views expressed in my posts do not necessarily reflect those views of my employer.

111 posts

Master Geek

Trusted

  # 713198 6-Nov-2012 21:45
Send private message

Right, I've found something. Two completely unrelated sites I monitor, in Manukau, show almost identical latency deviation, despite both links being idle at the time this is occuring.

The vast majority of graphs do show a flat latency response 24/7 so this will be isolated to a small number of users. At this stage, I'm guessing it's contained to users on MAB-RAN, but that's just a guess.

Thanks to the community for pointing this out. I'll start pursuing this from our end.

Manukau - ADSL site A:


Manukau - ADSL site B:







“I do not think there is any thrill that can go through the human heart like that felt by the inventor as he sees some creation of the brain unfolding to success... Such emotions make a man forget food, sleep, friends, love, everything.” - Nikola Tesla

 


Disclaimer: Views expressed in my posts do not necessarily reflect those views of my employer.

29 posts

Geek


  # 713476 7-Nov-2012 12:37
Send private message

If you're still interested in Snap usernames I have PM'd you directly.  I am connected to TIS/Exchange.

Cheers.

68 posts

Master Geek


  # 713706 7-Nov-2012 18:41
Send private message

quakeguy: That's quite bad. Are you guys happy to PM me your Snap usernames? I want to set up pings directly to you (and some traffic graphs of your connection at the same time). I'm keen to catch/fix this ASAP!


sent username

updated ping test
18:41  07/11/2012
Pinging 202.37.101.1 with 32 bytes of data:

Reply from 202.37.101.1: bytes=32 time=120ms TTL=61
Reply from 202.37.101.1: bytes=32 time=57ms TTL=61
Reply from 202.37.101.1: bytes=32 time=10ms TTL=61
Reply from 202.37.101.1: bytes=32 time=39ms TTL=61
Reply from 202.37.101.1: bytes=32 time=162ms TTL=61
Reply from 202.37.101.1: bytes=32 time=49ms TTL=61
Reply from 202.37.101.1: bytes=32 time=40ms TTL=61
Reply from 202.37.101.1: bytes=32 time=99ms TTL=61
Reply from 202.37.101.1: bytes=32 time=71ms TTL=61
Reply from 202.37.101.1: bytes=32 time=152ms TTL=61
Reply from 202.37.101.1: bytes=32 time=264ms TTL=61
Reply from 202.37.101.1: bytes=32 time=110ms TTL=61
Reply from 202.37.101.1: bytes=32 time=184ms TTL=61

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

29 posts

Geek


  # 713787 7-Nov-2012 20:30
Send private message

Edit:  8:30pm 7/11/2012.  Not sure what's up with the post date/time counter.

Not too bad tonight.

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=18ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=13ms TTL=61
Reply from 202.37.101.1: bytes=32 time=7ms TTL=61
Reply from 202.37.101.1: bytes=32 time=7ms TTL=61
Reply from 202.37.101.1: bytes=32 time=7ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=31ms TTL=61

Ping statistics for 202.37.101.1:
Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 31ms, Average = 8ms

29 posts

Geek


  # 713857 7-Nov-2012 21:57
Send private message

okay, last post given that it is hopefully being looked into.

9:56pm on 07/11/2012.  You can see it's a fair bit worse and uncharacteristic of earlier in the evening.

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=39ms TTL=61
Reply from 202.37.101.1: bytes=32 time=31ms TTL=61
Reply from 202.37.101.1: bytes=32 time=24ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=40ms TTL=61
Reply from 202.37.101.1: bytes=32 time=11ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=47ms TTL=61
Reply from 202.37.101.1: bytes=32 time=22ms TTL=61
Reply from 202.37.101.1: bytes=32 time=10ms TTL=61
Reply from 202.37.101.1: bytes=32 time=40ms TTL=61
Reply from 202.37.101.1: bytes=32 time=22ms TTL=61

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



3385 posts

Uber Geek

Trusted

  # 713859 7-Nov-2012 22:13
Send private message

Yup, I understand they are looking into what my line looks like this evening, possibly others too. Currently looking something like this here, which matches what I've been seeing around this time of evening previously very closely. Hopefully it shows up on their monitoring\testing tools :)


07/11/2012 21:59:00.31

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=45ms TTL=61
Reply from 202.37.101.1: bytes=32 time=39ms TTL=61
Reply from 202.37.101.1: bytes=32 time=37ms TTL=61
Reply from 202.37.101.1: bytes=32 time=40ms TTL=61
Reply from 202.37.101.1: bytes=32 time=44ms TTL=61
Reply from 202.37.101.1: bytes=32 time=37ms TTL=61
Reply from 202.37.101.1: bytes=32 time=41ms TTL=61
Reply from 202.37.101.1: bytes=32 time=44ms TTL=61
Reply from 202.37.101.1: bytes=32 time=40ms TTL=61
Reply from 202.37.101.1: bytes=32 time=35ms TTL=61

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



1 | 2 | 3 | 4 | 5
View this topic in a long page with up to 500 replies per page Create new topic



Switch your broadband provider now - compare prices


Twitter and LinkedIn »



Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:





News »

Netflix releases 21 Studio Ghibli works
Posted 22-Jan-2020 11:42


Vodafone integrates eSIM into device and wearable roadmap
Posted 17-Jan-2020 09:45


Do you need this camera app? Group investigates privacy implications
Posted 16-Jan-2020 03:30


JBL launches headphones range designed for gaming
Posted 13-Jan-2020 09:59


Withings introduces ScanWatch wearable combining ECG and sleep apnea detection
Posted 9-Jan-2020 18:34


NZ Police releases public app
Posted 8-Jan-2020 11:43


Suunto 7 combine sports and smart features on new smartwatch generation
Posted 7-Jan-2020 16:06


Intel brings innovation with technology spanning the cloud, network, edge and PC
Posted 7-Jan-2020 15:54


AMD announces high performance desktop and ultrathin laptop processors
Posted 7-Jan-2020 15:42


AMD unveils four new desktop and mobile GPUs including AMD Radeon RX 5600
Posted 7-Jan-2020 15:32


Consolidation in video streaming market with Spark selling Lightbox to Sky
Posted 19-Dec-2019 09:09


Intel introduces cryogenic control chip to enable quantum computers
Posted 10-Dec-2019 21:32


Vodafone 5G service live in four cities
Posted 10-Dec-2019 08:30


Samsung Galaxy Fold now available in New Zealand
Posted 6-Dec-2019 00:01


NZ company oDocs awarded US$ 100,000 Dubai World Expo grant
Posted 5-Dec-2019 16:00



Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.


Support Geekzone »

Our community of supporters help make Geekzone possible. Click the button below to join them.

Support Geezone on PressPatron



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.