Cogent has had a issue for a few days now, causing extreme latency across the network; be2437.ccr21.alb02.atlas.cogentco.com (66.28.4.197) 38.219 ms 10 te0-0-2-0.agr11.alb02.atlas.cogentco.com (154.54.5.161) 37.838 ms te0-0-2-2.agr11.alb02.atlas.cogentco.com (154.54.28.82) 37.968 ms te0-0-2-0.agr11.alb02.atlas.cogentco.com (154.54.5.161) 38.100 ms 11 te0-0-2-0.agr11.alb02.atlas.cogentco.com (154.54.5.161) 4645.684 ms !H 4503.251 ms !H te0-0-2-2.agr11.alb02.atlas.cogentco.com (154.54.28.82) 4581.944 ms !H Can anyone verify what is going on? I called them a few weeks ago so I'm hoping this might hit some admins who work there. --Kyle
I have a 100Mb Cogent fiber line out of downtown Syracuse, NY and are not experiencing any issues. But their tech support has always been pretty good, you should reach out to them again. 2 2 ms 2 ms 1 ms fa0-3.na11.b017044-0.syr01.atlas.cogentco.com 3 <1 ms <1 ms <1 ms gi1-47.3802.ccr01.syr01.atlas.cogentco.com [38.20.65.121] 4 4 ms 4 ms 4 ms te0-0-0-16.ccr21.alb02.atlas.cogentco.com [154.54.27.165] 5 7 ms 7 ms 7 ms be2109.mpd22.jfk02.atlas.cogentco.com [154.54.3.137] 6 14 ms 14 ms 13 ms be2151.mpd22.dca01.atlas.cogentco.com [154.54.40.73] 7 14 ms 15 ms 15 ms be2112.ccr41.iad02.atlas.cogentco.com [154.54.5.233] 8 14 ms 14 ms 14 ms 38.88.214.50 9 * 15 ms 15 ms 209.85.252.80 10 15 ms 15 ms 15 ms 72.14.238.175 11 15 ms 14 ms 14 ms iad23s06-in-f14.1e100.net [74.125.228.46] -Dann From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Kyle Farmer Sent: Friday, May 9, 2014 1:12 PM To: Outages@outages.org Subject: [outages] Cogent Problem? Cogent has had a issue for a few days now, causing extreme latency across the network; be2437.ccr21.alb02.atlas.cogentco.com <http://be2437.ccr21.alb02.atlas.cogentco.com> (66.28.4.197) 38.219 ms 10 te0-0-2-0.agr11.alb02.atlas.cogentco.com <http://te0-0-2-0.agr11.alb02.atlas.cogentco.com> (154.54.5.161) 37.838 ms te0-0-2-2.agr11.alb02.atlas.cogentco.com <http://te0-0-2-2.agr11.alb02.atlas.cogentco.com> (154.54.28.82) 37.968 ms te0-0-2-0.agr11.alb02.atlas.cogentco.com <http://te0-0-2-0.agr11.alb02.atlas.cogentco.com> (154.54.5.161) 38.100 ms 11 te0-0-2-0.agr11.alb02.atlas.cogentco.com <http://te0-0-2-0.agr11.alb02.atlas.cogentco.com> (154.54.5.161) 4645.684 ms !H 4503.251 ms !H te0-0-2-2.agr11.alb02.atlas.cogentco.com <http://te0-0-2-2.agr11.alb02.atlas.cogentco.com> (154.54.28.82) 4581.944 ms !H Can anyone verify what is going on? I called them a few weeks ago so I'm hoping this might hit some admins who work there. --Kyle
Looks good coming out of Denver on our 100mb Cogent connection: 2. fa0-2.na01.b009854-0.den01.atlas.cogentco.com 0.0% 10 1.2 1.1 0.8 1.7 0.3 3. vl3509.mag02.den01.atlas.cogentco.com 0.0% 10 1.2 7.6 0.8 50.5 15.8 4. te0-7-0-5.ccr21.den01.atlas.cogentco.com 0.0% 10 1.7 1.2 1.0 1.7 0.3 5. be2129.mpd21.mci01.atlas.cogentco.com 0.0% 10 13.4 13.5 12.8 14.7 0.6 6. be2158.ccr41.ord01.atlas.cogentco.com 0.0% 10 25.7 25.7 25.2 25.9 0.2 7. be2005.ccr21.ord03.atlas.cogentco.com 0.0% 10 25.9 25.7 25.2 26.4 0.4 8. 38.88.204.78 0.0% 10 25.5 25.2 24.8 26.1 0.4 9. 209.85.254.120 0.0% 10 40.7 29.9 25.1 44.8 7.6 10. 209.85.254.238 0.0% 10 25.6 25.4 25.1 25.7 0.2 11. 72.14.232.72 0.0% 10 67.0 45.9 43.1 67.0 7.4 12. 72.14.236.147 0.0% 10 43.4 43.3 43.1 43.6 0.2 13. 72.14.238.175 0.0% 10 44.0 43.3 42.8 44.0 0.4 14. iad23s06-in-f14.1e100.net 0.0% 10 42.8 42.7 42.2 43.2 0.4 Chris On 05/09/2014 11:23 AM, Dann Schuler wrote:
I have a 100Mb Cogent fiber line out of downtown Syracuse, NY and are not experiencing any issues.
But their tech support has always been pretty good, you should reach out to them again.
2    2 ms    2 ms    1 ms fa0-3.na11.b017044-0.syr01.atlas.cogentco.com
 3   <1 ms   <1 ms   <1 ms gi1-47.3802.ccr01.syr01.atlas.cogentco.com [38.20.65.121]
4    4 ms    4 ms    4 ms te0-0-0-16.ccr21.alb02.atlas.cogentco.com [154.54.27.165]
5    7 ms    7 ms    7 ms be2109.mpd22.jfk02.atlas.cogentco.com [154.54.3.137]
6   14 ms   14 ms   13 ms be2151.mpd22.dca01.atlas.cogentco.com [154.54.40.73]
7   14 ms   15 ms   15 ms be2112.ccr41.iad02.atlas.cogentco.com [154.54.5.233]
8   14 ms   14 ms   14 ms 38.88.214.50
9    *      15 ms   15 ms 209.85.252.80
10   15 ms   15 ms   15 ms 72.14.238.175
11   15 ms   14 ms   14 ms iad23s06-in-f14.1e100.net [74.125.228.46]
-Dann
*From:*Outages [mailto:outages-bounces@outages.org] *On Behalf Of *Kyle Farmer *Sent:* Friday, May 9, 2014 1:12 PM *To:* Outages@outages.org *Subject:* [outages] Cogent Problem?
Cogent has had a issue for a few days now, causing extreme latency across the network;
be2437.ccr21.alb02.atlas.cogentco.com <http://be2437.ccr21.alb02.atlas.cogentco.com> (66.28.4.197) 38.219 ms
10 te0-0-2-0.agr11.alb02.atlas.cogentco.com <http://te0-0-2-0.agr11.alb02.atlas.cogentco.com> (154.54.5.161) 37.838 ms
te0-0-2-2.agr11.alb02.atlas.cogentco.com <http://te0-0-2-2.agr11.alb02.atlas.cogentco.com> (154.54.28.82) 37.968 ms
te0-0-2-0.agr11.alb02.atlas.cogentco.com <http://te0-0-2-0.agr11.alb02.atlas.cogentco.com> (154.54.5.161) 38.100 ms
11 te0-0-2-0.agr11.alb02.atlas.cogentco.com <http://te0-0-2-0.agr11.alb02.atlas.cogentco.com> (154.54.5.161) 4645.684 ms !H 4503.251 ms !H
te0-0-2-2.agr11.alb02.atlas.cogentco.com <http://te0-0-2-2.agr11.alb02.atlas.cogentco.com> (154.54.28.82) 4581.944 ms !H
Can anyone verify what is going on? I called them a few weeks ago so I'm hoping this might hit some admins who work there.
--Kyle
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Can you post the full trace route? James Milko Architect, Network Engineering 900 Main Campus Drive Raleigh, NC 27606 Bandwidth <http://www.bandwidth.com/business/> o 919.439.1935 On Fri, May 9, 2014 at 1:12 PM, Kyle Farmer <bannereddivpool@gmail.com>wrote:
Cogent has had a issue for a few days now, causing extreme latency across the network;
be2437.ccr21.alb02.atlas.cogentco.com (66.28.4.197) 38.219 ms 10 te0-0-2-0.agr11.alb02.atlas.cogentco.com (154.54.5.161) 37.838 ms te0-0-2-2.agr11.alb02.atlas.cogentco.com (154.54.28.82) 37.968 ms te0-0-2-0.agr11.alb02.atlas.cogentco.com (154.54.5.161) 38.100 ms 11 te0-0-2-0.agr11.alb02.atlas.cogentco.com (154.54.5.161) 4645.684 ms !H 4503.251 ms !H te0-0-2-2.agr11.alb02.atlas.cogentco.com (154.54.28.82) 4581.944 ms !H
Can anyone verify what is going on? I called them a few weeks ago so I'm hoping this might hit some admins who work there.
--Kyle
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
The !H indicates host unreachable. I'm guessing that some router near the host has a 4.5 second ARP timeout. It's not a latency issue, but probably an end host issue. On Fri, May 9, 2014 at 11:12 AM, Kyle Farmer <bannereddivpool@gmail.com>wrote:
Cogent has had a issue for a few days now, causing extreme latency across the network;
be2437.ccr21.alb02.atlas.cogentco.com (66.28.4.197) 38.219 ms 10 te0-0-2-0.agr11.alb02.atlas.cogentco.com (154.54.5.161) 37.838 ms te0-0-2-2.agr11.alb02.atlas.cogentco.com (154.54.28.82) 37.968 ms te0-0-2-0.agr11.alb02.atlas.cogentco.com (154.54.5.161) 38.100 ms 11 te0-0-2-0.agr11.alb02.atlas.cogentco.com (154.54.5.161) 4645.684 ms !H 4503.251 ms !H te0-0-2-2.agr11.alb02.atlas.cogentco.com (154.54.28.82) 4581.944 ms !H
Can anyone verify what is going on? I called them a few weeks ago so I'm hoping this might hit some admins who work there.
--Kyle
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
$ traceroute video.primelink1.com traceroute to video.primelink1.com (38.101.32.14), 64 hops max, 40 byte packets 1 199.48.129.177 (199.48.129.177) 0.451 ms 0.619 ms 0.361 ms 2 208.79.82.101 (208.79.82.101) 0.428 ms 0.376 ms 0.468 ms 3 ge-6-8.car2.Raleigh1.Level3.net (4.71.162.13) 3.732 ms 1.847 ms 2.320 ms 4 ae-9-9.ebr1.Washington1.Level3.net (4.69.132.178) 7.817 ms 7.624 ms 7.572 ms 5 ae-91-91.csw4.Washington1.Level3.net (4.69.134.142) 7.578 ms ae-61-61.csw1.Washington1.Level3.net (4.69.134.130) 7.565 ms ae-81-81.csw3.Washington1.Level3.net (4.69.134.138) 7.814 ms 6 ae-2-70.edge3.Washington4.Level3.net (4.69.149.82) 7.635 ms ae-4-90.edge3.Washington4.Level3.net (4.69.149.210) 7.400 ms 7.593 ms 7 COGENT-COMM.edge3.Washington4.Level3.net (4.68.63.174) 8.157 ms 8.163 ms 8.661 ms 8 be2177.ccr22.dca01.atlas.cogentco.com (154.54.41.206) 9.385 ms be2113.mpd21.dca01.atlas.cogentco.com (154.54.6.170) 9.258 ms be2177.ccr22.dca01.atlas.cogentco.com (154.54.41.206) 9.237 ms 9 be2148.ccr21.jfk02.atlas.cogentco.com (154.54.31.118) 15.374 ms 15.926 ms be2149.ccr22.jfk02.atlas.cogentco.com (154.54.31.126) 15.705 ms 10 be2109.ccr21.alb02.atlas.cogentco.com (154.54.3.138) 27.944 ms be2107.ccr21.alb02.atlas.cogentco.com (154.54.3.94) 28.124 ms be2108.ccr21.alb02.atlas.cogentco.com (154.54.3.134) 27.568 ms 11 te0-0-2-2.agr11.alb02.atlas.cogentco.com (154.54.28.82) 28.007 ms 28.353 ms te0-0-2-0.agr11.alb02.atlas.cogentco.com (154.54.5.161) 27.332 ms 12 te0-0-2-2.agr11.alb02.atlas.cogentco.com (154.54.28.82) 4653.993 ms !H te0-0-2-0.agr11.alb02.atlas.cogentco.com (154.54.5.161) 4608.391 ms !H 4553.602 ms !H $ Above is the full traceroute. What I find is pinging the end route you'll see it jump up to 10000MS and down to 9000MS. Almost like a bad BGP upstream. On Fri, May 9, 2014 at 2:07 PM, Joel Maslak <jmaslak@antelope.net> wrote:
The !H indicates host unreachable. I'm guessing that some router near the host has a 4.5 second ARP timeout. It's not a latency issue, but probably an end host issue.
On Fri, May 9, 2014 at 11:12 AM, Kyle Farmer <bannereddivpool@gmail.com>wrote:
Cogent has had a issue for a few days now, causing extreme latency across the network;
be2437.ccr21.alb02.atlas.cogentco.com (66.28.4.197) 38.219 ms 10 te0-0-2-0.agr11.alb02.atlas.cogentco.com (154.54.5.161) 37.838 ms te0-0-2-2.agr11.alb02.atlas.cogentco.com (154.54.28.82) 37.968 ms te0-0-2-0.agr11.alb02.atlas.cogentco.com (154.54.5.161) 38.100 ms 11 te0-0-2-0.agr11.alb02.atlas.cogentco.com (154.54.5.161) 4645.684 ms !H 4503.251 ms !H te0-0-2-2.agr11.alb02.atlas.cogentco.com (154.54.28.82) 4581.944 ms !H
Can anyone verify what is going on? I called them a few weeks ago so I'm hoping this might hit some admins who work there.
--Kyle
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Here's a trace to that same location over Cogent out of Denver and it all is fine here - except for the last hop and that's most likely them blocking me: 2. fa0-2.na01.b009854-0.den01.atlas.cogentco.com 0.0% 10 1.1 1.2 0.9 2.7 0.5 3. vl3509.mag02.den01.atlas.cogentco.com 0.0% 10 1.6 11.8 0.8 96.1 29.9 4. te0-7-0-5.ccr21.den01.atlas.cogentco.com 0.0% 10 1.1 1.5 1.1 3.5 0.7 5. be2129.mpd21.mci01.atlas.cogentco.com 0.0% 10 12.8 13.2 12.8 13.7 0.3 6. be2156.ccr41.ord01.atlas.cogentco.com 0.0% 10 25.8 28.8 24.9 45.6 7.5 7. be2079.ccr21.yyz02.atlas.cogentco.com 0.0% 10 40.3 41.1 39.7 47.0 2.2 8. be2436.ccr21.alb02.atlas.cogentco.com 0.0% 10 49.2 49.4 48.2 53.3 1.5 9. te0-0-2-2.agr11.alb02.atlas.cogentco.com 0.0% 10 48.6 48.4 47.9 50.8 0.9 10. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 Chris On 05/09/2014 12:09 PM, Kyle Farmer wrote:
$ traceroute video.primelink1.com <http://video.primelink1.com> traceroute to video.primelink1.com <http://video.primelink1.com> (38.101.32.14), 64 hops max, 40 byte packets  1  199.48.129.177 (199.48.129.177)  0.451 ms  0.619 ms  0.361 ms  2  208.79.82.101 (208.79.82.101)  0.428 ms  0.376 ms  0.468 ms  3  ge-6-8.car2.Raleigh1.Level3.net <http://ge-6-8.car2.Raleigh1.Level3.net> (4.71.162.13)  3.732 ms  1.847 ms  2.320 ms  4  ae-9-9.ebr1.Washington1.Level3.net <http://ae-9-9.ebr1.Washington1.Level3.net> (4.69.132.178)  7.817 ms  7.624 ms  7.572 ms  5  ae-91-91.csw4.Washington1.Level3.net <http://ae-91-91.csw4.Washington1.Level3.net> (4.69.134.142)  7.578 ms   ae-61-61.csw1.Washington1.Level3.net <http://ae-61-61.csw1.Washington1.Level3.net> (4.69.134.130)  7.565 ms   ae-81-81.csw3.Washington1.Level3.net <http://ae-81-81.csw3.Washington1.Level3.net> (4.69.134.138)  7.814 ms  6  ae-2-70.edge3.Washington4.Level3.net <http://ae-2-70.edge3.Washington4.Level3.net> (4.69.149.82)  7.635 ms   ae-4-90.edge3.Washington4.Level3.net <http://ae-4-90.edge3.Washington4.Level3.net> (4.69.149.210)  7.400 ms  7.593 ms  7  COGENT-COMM.edge3.Washington4.Level3.net <http://COGENT-COMM.edge3.Washington4.Level3.net> (4.68.63.174)  8.157 ms  8.163 ms  8.661 ms  8  be2177.ccr22.dca01.atlas.cogentco.com <http://be2177.ccr22.dca01.atlas.cogentco.com> (154.54.41.206)  9.385 ms   be2113.mpd21.dca01.atlas.cogentco.com <http://be2113.mpd21.dca01.atlas.cogentco.com> (154.54.6.170)  9.258 ms   be2177.ccr22.dca01.atlas.cogentco.com <http://be2177.ccr22.dca01.atlas.cogentco.com> (154.54.41.206)  9.237 ms  9  be2148.ccr21.jfk02.atlas.cogentco.com <http://be2148.ccr21.jfk02.atlas.cogentco.com> (154.54.31.118)  15.374 ms  15.926 ms   be2149.ccr22.jfk02.atlas.cogentco.com <http://be2149.ccr22.jfk02.atlas.cogentco.com> (154.54.31.126)  15.705 ms 10  be2109.ccr21.alb02.atlas.cogentco.com <http://be2109.ccr21.alb02.atlas.cogentco.com> (154.54.3.138)  27.944 ms   be2107.ccr21.alb02.atlas.cogentco.com <http://be2107.ccr21.alb02.atlas.cogentco.com> (154.54.3.94)  28.124 ms   be2108.ccr21.alb02.atlas.cogentco.com <http://be2108.ccr21.alb02.atlas.cogentco.com> (154.54.3.134)  27.568 ms 11  te0-0-2-2.agr11.alb02.atlas.cogentco.com <http://te0-0-2-2.agr11.alb02.atlas.cogentco.com> (154.54.28.82)  28.007 ms  28.353 ms   te0-0-2-0.agr11.alb02.atlas.cogentco.com <http://te0-0-2-0.agr11.alb02.atlas.cogentco.com> (154.54.5.161)  27.332 ms 12  te0-0-2-2.agr11.alb02.atlas.cogentco.com <http://te0-0-2-2.agr11.alb02.atlas.cogentco.com> (154.54.28.82)  4653.993 ms !H   te0-0-2-0.agr11.alb02.atlas.cogentco.com <http://te0-0-2-0.agr11.alb02.atlas.cogentco.com> (154.54.5.161)  4608.391 ms !H  4553.602 ms !H $Â
Above is the full traceroute. Â What I find is pinging the end route you'll see it jump up to 10000MS and down to 9000MS. Â Almost like a bad BGP upstream.
On Fri, May 9, 2014 at 2:07 PM, Joel Maslak <jmaslak@antelope.net <mailto:jmaslak@antelope.net>> wrote:
The !H indicates host unreachable. Â I'm guessing that some router near the host has a 4.5 second ARP timeout. Â It's not a latency issue, but probably an end host issue.
On Fri, May 9, 2014 at 11:12 AM, Kyle Farmer <bannereddivpool@gmail.com <mailto:bannereddivpool@gmail.com>> wrote:
Cogent has had a issue for a few days now, causing extreme latency across the network;
  be2437.ccr21.alb02.atlas.cogentco.com <http://be2437.ccr21.alb02.atlas.cogentco.com> (66.28.4.197)  38.219 ms 10  te0-0-2-0.agr11.alb02.atlas.cogentco.com <http://te0-0-2-0.agr11.alb02.atlas.cogentco.com> (154.54.5.161)  37.838 ms   te0-0-2-2.agr11.alb02.atlas.cogentco.com <http://te0-0-2-2.agr11.alb02.atlas.cogentco.com> (154.54.28.82)  37.968 ms   te0-0-2-0.agr11.alb02.atlas.cogentco.com <http://te0-0-2-0.agr11.alb02.atlas.cogentco.com> (154.54.5.161)  38.100 ms 11  te0-0-2-0.agr11.alb02.atlas.cogentco.com <http://te0-0-2-0.agr11.alb02.atlas.cogentco.com> (154.54.5.161)  4645.684 ms !H  4503.251 ms !H   te0-0-2-2.agr11.alb02.atlas.cogentco.com <http://te0-0-2-2.agr11.alb02.atlas.cogentco.com> (154.54.28.82)  4581.944 ms !H
Can anyone verify what is going on? Â I called them a few weeks ago so I'm hoping this might hit some admins who work there.
--Kyle
_______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
I read this traceroute to indicate two things (return-path would be nice but gotta work with what I got): The routers at hop #11 (I see it varies due to load balancing per packet) claim that the destination, 38.101.32.14, is unreachable (i.e. you are getting back ICMP host-unreach from those routers). That could mean either they don't have a route for whatever 38.101.32.14 falls under (network-wise), or that the routers are aware that 38.101.32.14 isn't reachable/alive (god forbid they have a /32 for it) You might wonder "what's up with hop #11 then 'doing it again' at hop #12?", and the answer is probably that the routers at hop #11 are supposed to have knowledge/reachability of/to 38.101.32.14, but don't (for whatever reason), and are configured by default to punt packets back to another router to try and find a different path (i.e. bouncing between 154.54.28.82 and 154.54.5.161, hoping one can find the thing the other cannot). TL;DR -- You should be talking to both Cogent, as well as whoever maintains this video.primelink1.com service/server/network, to inform them of what's going on. It's obvious something somewhere is either broken or administratively set to behave this way. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB | On Fri, May 09, 2014 at 02:09:22PM -0400, Kyle Farmer wrote:
$ traceroute video.primelink1.com traceroute to video.primelink1.com (38.101.32.14), 64 hops max, 40 byte packets 1 199.48.129.177 (199.48.129.177) 0.451 ms 0.619 ms 0.361 ms 2 208.79.82.101 (208.79.82.101) 0.428 ms 0.376 ms 0.468 ms 3 ge-6-8.car2.Raleigh1.Level3.net (4.71.162.13) 3.732 ms 1.847 ms 2.320 ms 4 ae-9-9.ebr1.Washington1.Level3.net (4.69.132.178) 7.817 ms 7.624 ms 7.572 ms 5 ae-91-91.csw4.Washington1.Level3.net (4.69.134.142) 7.578 ms ae-61-61.csw1.Washington1.Level3.net (4.69.134.130) 7.565 ms ae-81-81.csw3.Washington1.Level3.net (4.69.134.138) 7.814 ms 6 ae-2-70.edge3.Washington4.Level3.net (4.69.149.82) 7.635 ms ae-4-90.edge3.Washington4.Level3.net (4.69.149.210) 7.400 ms 7.593 ms 7 COGENT-COMM.edge3.Washington4.Level3.net (4.68.63.174) 8.157 ms 8.163 ms 8.661 ms 8 be2177.ccr22.dca01.atlas.cogentco.com (154.54.41.206) 9.385 ms be2113.mpd21.dca01.atlas.cogentco.com (154.54.6.170) 9.258 ms be2177.ccr22.dca01.atlas.cogentco.com (154.54.41.206) 9.237 ms 9 be2148.ccr21.jfk02.atlas.cogentco.com (154.54.31.118) 15.374 ms 15.926 ms be2149.ccr22.jfk02.atlas.cogentco.com (154.54.31.126) 15.705 ms 10 be2109.ccr21.alb02.atlas.cogentco.com (154.54.3.138) 27.944 ms be2107.ccr21.alb02.atlas.cogentco.com (154.54.3.94) 28.124 ms be2108.ccr21.alb02.atlas.cogentco.com (154.54.3.134) 27.568 ms 11 te0-0-2-2.agr11.alb02.atlas.cogentco.com (154.54.28.82) 28.007 ms 28.353 ms te0-0-2-0.agr11.alb02.atlas.cogentco.com (154.54.5.161) 27.332 ms 12 te0-0-2-2.agr11.alb02.atlas.cogentco.com (154.54.28.82) 4653.993 ms !H te0-0-2-0.agr11.alb02.atlas.cogentco.com (154.54.5.161) 4608.391 ms !H 4553.602 ms !H $
Above is the full traceroute. What I find is pinging the end route you'll see it jump up to 10000MS and down to 9000MS. Almost like a bad BGP upstream.
On Fri, May 9, 2014 at 2:07 PM, Joel Maslak <jmaslak@antelope.net> wrote:
The !H indicates host unreachable. I'm guessing that some router near the host has a 4.5 second ARP timeout. It's not a latency issue, but probably an end host issue.
On Fri, May 9, 2014 at 11:12 AM, Kyle Farmer <bannereddivpool@gmail.com>wrote:
Cogent has had a issue for a few days now, causing extreme latency across the network;
be2437.ccr21.alb02.atlas.cogentco.com (66.28.4.197) 38.219 ms 10 te0-0-2-0.agr11.alb02.atlas.cogentco.com (154.54.5.161) 37.838 ms te0-0-2-2.agr11.alb02.atlas.cogentco.com (154.54.28.82) 37.968 ms te0-0-2-0.agr11.alb02.atlas.cogentco.com (154.54.5.161) 38.100 ms 11 te0-0-2-0.agr11.alb02.atlas.cogentco.com (154.54.5.161) 4645.684 ms !H 4503.251 ms !H te0-0-2-2.agr11.alb02.atlas.cogentco.com (154.54.28.82) 4581.944 ms !H
Can anyone verify what is going on? I called them a few weeks ago so I'm hoping this might hit some admins who work there.
--Kyle
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
participants (6)
-
Chris Stone -
Dann Schuler -
James Milko -
Jeremy Chadwick -
Joel Maslak -
Kyle Farmer