-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David Coulson wrote: > > About 20mins ago my connection to Cogent in Cleveland just went totally > nuts. I can't even get to www.cogentco.com over their circuit: > > Packets > Pings > Host Loss% Snt Last > Avg Best Wrst StDev > 1. v129.l3sw1.n2net.net 0.0% 1 1.1 > 1.1 1.1 1.1 0.0 > 2. v401.core1.n2net.net 0.0% 1 0.4 > 0.4 0.4 0.4 0.0 > 3. fa0-2.na01.b002352-3.cle01.atlas.cogentco.com 0.0% 1 1.5 > 1.5 1.5 1.5 0.0 > 4. g1-0-3501.core01.cle01.atlas.cogentco.com 0.0% 1 1.6 > 1.6 1.6 1.6 0.0 > 5. p6-0.core01.buf02.atlas.cogentco.com 0.0% 1 5.5 > 5.5 5.5 5.5 0.0 > 6. p6-0.core01.cle01.atlas.cogentco.com 0.0% 1 6.1 > 6.1 6.1 6.1 0.0 > 7. p6-0.core01.buf02.atlas.cogentco.com 0.0% 1 10.5 > 10.5 10.5 10.5 0.0 > 8. p6-0.core01.cle01.atlas.cogentco.com 0.0% 1 9.9 > 9.9 9.9 9.9 0.0 > 9. p6-0.core01.buf02.atlas.cogentco.com 0.0% 1 14.7 > 14.7 14.7 14.7 0.0 > 10. p6-0.core01.cle01.atlas.cogentco.com 0.0% 1 14.7 > 14.7 14.7 14.7 0.0 > 11. p6-0.core01.buf02.atlas.cogentco.com 0.0% 1 19.1 > 19.1 19.1 19.1 0.0 - -------------------------------- As someone mentioned, it appears that cogent is having major peering issues.
I'm still waiting for Cogent's ip sla site to be updated w/ updated information. regards, /virendra -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGL83CpbZvCIJx1bcRAvwxAJ9H3UtZfs8txjbVlWam3ir58KjBygCfdapA JubmrXU3kfPN3mlDqGAq/TU= =FNWR -----END PGP SIGNATURE-----
