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.


Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › Really bad ping, anyone else?
alliao

321 posts

Ultimate Geek
+1 received by user: 19


#73628 17-Dec-2010 22:20
Send private message

Hi all,

just noticed really bad ping on orcon tonight,

2   405 ms   370 ms   576 ms  lo1.ras1.nct.orcon.net.nz [60.234.8.201]

this is my first hop.

I think this could be just jammed up Northcote (NCT?) but who knows, I've submitted a fault report to 

http://www.geekzone.co.nz/fault.asp

so get submitting if you will!

hopefully orcon picks up on this... 

Create new topic
pohutukawa
197 posts

Master Geek
+1 received by user: 9


  #418675 17-Dec-2010 22:25
Send private message

alliao: Hi all,

just noticed really bad ping on orcon tonight,

2 ? 405 ms ? 370 ms ? 576 ms ?lo1.ras1.nct.orcon.net.nz [60.234.8.201]

this is my first hop.

I think this could be just jammed up Northcote (NCT?) but who knows, I've submitted a fault report to?

http://www.geekzone.co.nz/fault.asp

so get submitting if you will!

hopefully orcon picks up on this...?


Very patchy.

PING google.com (66.102.11.104): 56 data bytes
64 bytes from 66.102.11.104: icmp_seq=0 ttl=58 time=589.399 ms
64 bytes from 66.102.11.104: icmp_seq=1 ttl=58 time=443.761 ms
64 bytes from 66.102.11.104: icmp_seq=2 ttl=58 time=336.178 ms
64 bytes from 66.102.11.104: icmp_seq=3 ttl=58 time=606.344 ms
64 bytes from 66.102.11.104: icmp_seq=4 ttl=58 time=334.524 ms
64 bytes from 66.102.11.104: icmp_seq=5 ttl=58 time=479.378 ms
64 bytes from 66.102.11.104: icmp_seq=6 ttl=58 time=356.805 ms
64 bytes from 66.102.11.104: icmp_seq=7 ttl=58 time=397.438 ms
64 bytes from 66.102.11.104: icmp_seq=8 ttl=58 time=590.359 ms
64 bytes from 66.102.11.104: icmp_seq=9 ttl=58 time=285.842 ms
64 bytes from 66.102.11.104: icmp_seq=10 ttl=58 time=536.333 ms
64 bytes from 66.102.11.104: icmp_seq=11 ttl=58 time=403.189 ms
64 bytes from 66.102.11.104: icmp_seq=12 ttl=58 time=359.528 ms
64 bytes from 66.102.11.104: icmp_seq=13 ttl=58 time=337.316 ms
64 bytes from 66.102.11.104: icmp_seq=14 ttl=58 time=428.686 ms
64 bytes from 66.102.11.104: icmp_seq=15 ttl=58 time=414.347 ms
64 bytes from 66.102.11.104: icmp_seq=16 ttl=58 time=279.419 ms
64 bytes from 66.102.11.104: icmp_seq=17 ttl=58 time=526.118 ms
64 bytes from 66.102.11.104: icmp_seq=18 ttl=58 time=373.536 ms
64 bytes from 66.102.11.104: icmp_seq=19 ttl=58 time=204.129 ms
64 bytes from 66.102.11.104: icmp_seq=20 ttl=58 time=214.913 ms
64 bytes from 66.102.11.104: icmp_seq=21 ttl=58 time=254.964 ms
64 bytes from 66.102.11.104: icmp_seq=22 ttl=58 time=584.912 ms
64 bytes from 66.102.11.104: icmp_seq=23 ttl=58 time=562.165 ms
64 bytes from 66.102.11.104: icmp_seq=24 ttl=58 time=360.965 ms
64 bytes from 66.102.11.104: icmp_seq=25 ttl=58 time=447.224 ms
64 bytes from 66.102.11.104: icmp_seq=26 ttl=58 time=227.589 ms
Request timeout for icmp_seq 27
64 bytes from 66.102.11.104: icmp_seq=28 ttl=58 time=322.516 ms
64 bytes from 66.102.11.104: icmp_seq=29 ttl=58 time=300.200 ms
64 bytes from 66.102.11.104: icmp_seq=30 ttl=58 time=245.904 ms
64 bytes from 66.102.11.104: icmp_seq=31 ttl=58 time=247.097 ms
64 bytes from 66.102.11.104: icmp_seq=32 ttl=58 time=222.334 ms

Even orcon.net.nz

PING orcon.net.nz (60.234.4.77): 56 data bytes
64 bytes from 60.234.4.77: icmp_seq=0 ttl=61 time=334.478 ms
64 bytes from 60.234.4.77: icmp_seq=1 ttl=61 time=593.276 ms
64 bytes from 60.234.4.77: icmp_seq=2 ttl=61 time=337.210 ms
Request timeout for icmp_seq 3
64 bytes from 60.234.4.77: icmp_seq=4 ttl=61 time=632.990 ms
64 bytes from 60.234.4.77: icmp_seq=5 ttl=61 time=347.087 ms
Request timeout for icmp_seq 6
64 bytes from 60.234.4.77: icmp_seq=7 ttl=61 time=204.792 ms
64 bytes from 60.234.4.77: icmp_seq=8 ttl=61 time=565.862 ms
64 bytes from 60.234.4.77: icmp_seq=9 ttl=61 time=270.932 ms
64 bytes from 60.234.4.77: icmp_seq=10 ttl=61 time=341.775 ms
64 bytes from 60.234.4.77: icmp_seq=11 ttl=61 time=556.594 ms
64 bytes from 60.234.4.77: icmp_seq=12 ttl=61 time=294.375 ms
64 bytes from 60.234.4.77: icmp_seq=13 ttl=61 time=271.150 ms
64 bytes from 60.234.4.77: icmp_seq=14 ttl=61 time=233.283 ms
64 bytes from 60.234.4.77: icmp_seq=15 ttl=61 time=257.165 ms
64 bytes from 60.234.4.77: icmp_seq=16 ttl=61 time=416.693 ms
64 bytes from 60.234.4.77: icmp_seq=17 ttl=61 time=431.910 ms
64 bytes from 60.234.4.77: icmp_seq=18 ttl=61 time=400.497 ms
64 bytes from 60.234.4.77: icmp_seq=19 ttl=61 time=484.269 ms
64 bytes from 60.234.4.77: icmp_seq=20 ttl=61 time=186.753 ms
64 bytes from 60.234.4.77: icmp_seq=21 ttl=61 time=247.615 ms
64 bytes from 60.234.4.77: icmp_seq=22 ttl=61 time=504.440 ms
64 bytes from 60.234.4.77: icmp_seq=23 ttl=61 time=427.272 ms
64 bytes from 60.234.4.77: icmp_seq=24 ttl=61 time=226.715 ms
64 bytes from 60.234.4.77: icmp_seq=25 ttl=61 time=528.203 ms
64 bytes from 60.234.4.77: icmp_seq=26 ttl=61 time=462.529 ms
64 bytes from 60.234.4.77: icmp_seq=27 ttl=61 time=545.823 ms
64 bytes from 60.234.4.77: icmp_seq=28 ttl=61 time=415.522 ms
64 bytes from 60.234.4.77: icmp_seq=29 ttl=61 time=366.267 ms
64 bytes from 60.234.4.77: icmp_seq=30 ttl=61 time=543.661 ms
^C
--- orcon.net.nz ping statistics ---
31 packets transmitted, 29 packets received, 6.5% packet loss
round-trip min/avg/max/stddev = 186.753/394.108/632.990/127.335 ms





pohutukawa ... turning with the seasons ... 



alliao

321 posts

Ultimate Geek
+1 received by user: 19


  #418678 17-Dec-2010 22:33
Send private message

I keep tracerting, looks like they're in big trouble.. it was ok for a few minutes, and I thought they've fixed it, but now it's back to it's 500ms glory.

I would suggest do a "tracert orcon.net.nz" ..

pohutukawa
197 posts

Master Geek
+1 received by user: 9


  #418679 17-Dec-2010 22:35
Send private message

alliao: I keep tracerting, looks like they're in big trouble.. it was ok for a few minutes, and I thought they've fixed it, but now it's back to it's 500ms glory.

I would suggest do a "tracert orcon.net.nz" ..



traceroute to orcon.net.nz (60.234.4.77), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 1.062 ms 0.729 ms 0.731 ms
2 lo1.ras1.nct.orcon.net.nz (60.234.8.201) 635.514 ms 520.799 ms 331.419 ms
3 xe-1-0-0.cre1.nct.orcon.net.nz (121.98.9.13) 342.603 ms 364.061 ms 436.335 ms
4 60.234.4.77 (60.234.4.77) 590.854 ms 407.936 ms 535.733 ms





pohutukawa ... turning with the seasons ... 



pohutukawa
197 posts

Master Geek
+1 received by user: 9


  #418680 17-Dec-2010 22:36
Send private message

traceroute to orcon.net.nz (60.234.4.77), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 1.102 ms 0.616 ms 2.383 ms
2 * lo1.ras1.nct.orcon.net.nz (60.234.8.201) 649.601 ms 432.772 ms
3 xe-1-0-0.cre1.nct.orcon.net.nz (121.98.9.13) 750.854 ms 516.724 ms 544.688 ms
4 60.234.4.77 (60.234.4.77) 622.594 ms * 672.885 ms





pohutukawa ... turning with the seasons ... 

maceman
1 post

Wannabe Geek


  #419382 20-Dec-2010 12:27
Send private message

Check out the status - On the website for orcon.
Orcon net nz       support    Network Status


We've had ongoing speed issues with a number of our clients on Orcon in Whitianga.
Noted Telecom was experiencing issues at the same time as Orcon.
Telstra seems fine.

Create new topic








Geekzone Live »

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


Updates »

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.








RSS feeds
Main feed
Forums feed
Copyright
©2002-2026 Geekzone®
Site features
Geekzone BI dashboard
Geekzone Badges
Geekzone Status Page

 

Site Information
Subscribe to Geekzone
Privacy Statement
Forum Usage Guidelines (FUG)
Advertising
Trademark and copyright