Greetings,
Our apologies for this issue - this is due to core2.dca2 router being
down (a Cisco router being down is something that almost never
happens). The issue is being worked on right now, and if it can't be
brought up soon (which will bring back the Level 3 & AT&T transits,
and another 1G circuit to IAD1), then the effected circuits will be
temporarily moved over to core1.dca2 thus bypassing this issue.
We are aware of this issue - the most severe issue we've ever had on
our network - and are working promptly to resolve it, with both a
"plan A" and a back-up "plan B."
On 10 Nov 07 at 15:41, *****wrote:
> Dear Sir/Madam
>
> As there is no Technical contact email address, i hope to be able to
> contact the relevant people in this way.
>
> There is a severe issue with your router, when trying to access
> 66.36.241.110 from my computer.
>
> This is a traceroute from your own site to my computer
> http://www.hopone.net/cgi-bin/tracer...i?************
>
> Note the 600ms latency being introduced at step 4, can you explain
> why this is happening.
>
> Additionally about 10-20% of UDP packets are being dropped.
>
> traceroute to ************ 64 hops max, 40 byte
> packets
> 1 cluster-fw1 (66.148.93.2) 0.332 ms 0.308 ms 0.270 ms
> 2 vlan7-d3.acc.dca2..hopone.net (209.160.62.2) 0.420 ms 0.487 ms
> 0.403 ms 3 gec2.core2.dca2.hopone.net (66.36.224.233) 0.413 ms
> 0.341 ms 0.274 ms 4 ge5-2.core1.iad1.hopone.net (66.36.224.54)
> 634.851 ms 641.501 ms 636.504 ms 5
> ge-4-1-0.mpr1.iad10.us.mfnx.net (206.223.115.86) 650.911 ms
> 648.447 ms 650.537 ms 6 so-4-0-0.mpr1.iad2.us.above.net
> (64.125.30.118) 654..572 ms 646.411 ms * 7
> so-4-0-0.mpr2.iad1.us.above.net (64.125.29.133) 668.026 ms *
> 673.275 ms 8 so-1-0-0.mpr2.dca2.us.above.net (64.125.27..210)
> 662.392 ms * 666.607 ms 9 so-0-1-0.mpr1.lhr3.uk.above.net
> (64.125.27.166) 739.278 ms 749.256 ms 734.929 ms
> 10 213.161.72.70 (213.161..72.70) 748.046 ms 741.069 ms 750.313
> ms 11 ************ 736.555 ms * 745.421 ms 12
> ************ 759..687 ms 759.669 ms
> 761.654 ms
>
> Please ensure you do not release my IP to third parties.
>
> Please can you let us know what the problem is, as its causing a
> severe problems.
>
> Thanks,
>
> ********
>
>
>
>
>
> __________________________________________________ _________
> Yahoo! Answers - Got a question? Someone out there knows the answer.
> Try it now. http://uk.answers.yahoo.com/
>
>
--
Haralds Jass - HJass@HOPONE.NET
HopOne Internet Corporation
"The Foundation of Internet Success"(R)
Our apologies for this issue - this is due to core2.dca2 router being
down (a Cisco router being down is something that almost never
happens). The issue is being worked on right now, and if it can't be
brought up soon (which will bring back the Level 3 & AT&T transits,
and another 1G circuit to IAD1), then the effected circuits will be
temporarily moved over to core1.dca2 thus bypassing this issue.
We are aware of this issue - the most severe issue we've ever had on
our network - and are working promptly to resolve it, with both a
"plan A" and a back-up "plan B."
On 10 Nov 07 at 15:41, *****wrote:
> Dear Sir/Madam
>
> As there is no Technical contact email address, i hope to be able to
> contact the relevant people in this way.
>
> There is a severe issue with your router, when trying to access
> 66.36.241.110 from my computer.
>
> This is a traceroute from your own site to my computer
> http://www.hopone.net/cgi-bin/tracer...i?************
>
> Note the 600ms latency being introduced at step 4, can you explain
> why this is happening.
>
> Additionally about 10-20% of UDP packets are being dropped.
>
> traceroute to ************ 64 hops max, 40 byte
> packets
> 1 cluster-fw1 (66.148.93.2) 0.332 ms 0.308 ms 0.270 ms
> 2 vlan7-d3.acc.dca2..hopone.net (209.160.62.2) 0.420 ms 0.487 ms
> 0.403 ms 3 gec2.core2.dca2.hopone.net (66.36.224.233) 0.413 ms
> 0.341 ms 0.274 ms 4 ge5-2.core1.iad1.hopone.net (66.36.224.54)
> 634.851 ms 641.501 ms 636.504 ms 5
> ge-4-1-0.mpr1.iad10.us.mfnx.net (206.223.115.86) 650.911 ms
> 648.447 ms 650.537 ms 6 so-4-0-0.mpr1.iad2.us.above.net
> (64.125.30.118) 654..572 ms 646.411 ms * 7
> so-4-0-0.mpr2.iad1.us.above.net (64.125.29.133) 668.026 ms *
> 673.275 ms 8 so-1-0-0.mpr2.dca2.us.above.net (64.125.27..210)
> 662.392 ms * 666.607 ms 9 so-0-1-0.mpr1.lhr3.uk.above.net
> (64.125.27.166) 739.278 ms 749.256 ms 734.929 ms
> 10 213.161.72.70 (213.161..72.70) 748.046 ms 741.069 ms 750.313
> ms 11 ************ 736.555 ms * 745.421 ms 12
> ************ 759..687 ms 759.669 ms
> 761.654 ms
>
> Please ensure you do not release my IP to third parties.
>
> Please can you let us know what the problem is, as its causing a
> severe problems.
>
> Thanks,
>
> ********
>
>
>
>
>
> __________________________________________________ _________
> Yahoo! Answers - Got a question? Someone out there knows the answer.
> Try it now. http://uk.answers.yahoo.com/
>
>
--
Haralds Jass - HJass@HOPONE.NET
HopOne Internet Corporation
"The Foundation of Internet Success"(R)
Comment