Yep, i've been experiencing packetloss too.. -----Original Message----- From: Chris Hodgetts [mailto:chris(a)archnetnz.com] Sent: Tuesday, 13 May 2008 6:47 p.m. To: nznog Subject: [nznog] Orcon Bandwidth Issues today.. Hello, I am just wondering if anyone else is experiencing issues with Orcon's bandwidth as of late. We seem to be getting about 87% packet loss from the following hop. 3. ge-0-3-0-200.cr1.nct.orcon.net.nz 87% 69 520 2 2 4 47 This seems to be causing issues more for download than upload, upload speeds +1.5mbit download speeds about 20 - 40kbps.... but that makes sense because out of the 520 packets, only 69 have been returned. I have noticed these issues for both National and International, however International more noticeable. Orcon advised that: Update (2008-05-12): The expected fix is taking slightly longer to deploy than we had originally anticipated. This should be resolved this week. ...This week... anyway.... I don't actually think that status was in relation to this, but I loved the "should be resolved this week". great estimate. I called Orcon today at about 16:45, but by the time anyone answered me it was just on 17:00 and all corp. support had gone home, but they assured it was being looked into, but could not give me a reference number. Anyway........... it's about time for a beer.... (not that I drink) _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

On 13/05/2008, at 6:46 PM, Chris Hodgetts wrote:

We seem to be getting about 87% packet loss from the following hop.

3. ge-0-3-0-200.cr1.nct.orcon.net.nz 87% 69 520 2 2 4 47

Looking at a single hop in a traceroute is generally not very indicative of the performance of a path. There are many common reasons that an intermediate router might not be sending ICMP messages back to you that often - ie. there's an administrative filter in place so that traceroute style messages do not impact router performance, etc. Generally end to end performance is the metric you should be looking at first, as that's what counts. Then if end to end is poor, consider traceroute as one of several tools to figure out where problems are. So, you probably want to give more info than poor performance on a single hop :-) Incidentally, and perhaps more useful to you, I see poor performance[1] on Asia Netcom from several places I have gear stashed, who Orcon use for at least some of their international transit. -- Nathan Ward [1] High packet loss