Carlos, How about a return-path traceroute? The ingress interface may be (and probably is) different than the egress. It would also help if you could provide source *and* destination IPs of the traceroutes. Details: http://www.nanog.org/meetings/nanog47/presentations/Sunday/RAS_Traceroute_N4... -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | On Wed, Oct 10, 2012 at 06:30:04PM -0700, Carlos Alvarez wrote:
On Wed, Oct 10, 2012 at 6:23 PM, Brent Jones <brent@brentrjones.com> wrote:
(even to other Cogent on-net POPs)
This right here is frustrating, since they are in the same city and same network:
5 vl3810.mag02.phx02.atlas.cogentco.com (66.28.64.209) 12.983 ms 12.979 ms 12.964 ms 6 * te7-4.ccr01.phx02.atlas.cogentco.com (154.54.85.85) 195.832 ms *
As you might imagine, we have a lot of complaints.
-- Carlos Alvarez TelEvolve 602-889-3003
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages