Doh - I meant to paste the destination IP in there, apologies. Boss from a remote office in Houston was seeing our Datacenter in NJ "just fine." While Our Florida folks weren't. Seems resolved now. Thanks for the feedback.
On Thu, Jun 18, 2009 at 11:44 AM, david raistrick <drais@icantclick.org> wrote:
Heh. It's sorted itself out, but I was seeing very similar problems with ebr1/car1 in atlanta (bellsouth dsl in orlando to rr in orlando).
I'd sent my findings to an internal L3 contact though. ;)
On Thu, 18 Jun 2009, L.T. Easterly wrote:
1 192.168.1.1 (192.168.1.1) 1.679 ms 2.101 ms 2.526 ms 2 10.104.240.1 (10.104.240.1) 13.304 ms 13.315 ms 13.819 ms 3 250.230.95.24.cfl.res.rr.com (24.95.230.250) 15.974 ms 16.474 ms 16.464 ms 4 gig4-0-0.orldflaabv-rtr4.cfl.rr.com (24.95.228.193) 24.250 ms 24.791 ms 27.754 ms 5 76.228.95.24.cfl.res.rr.com (24.95.228.76) 24.190 ms 36.178 ms 23.636 ms 6 xe-11-0-0.bar1.Orlando1.Level3.net (4.79.118.41) 24.710 ms 19.505 ms xe-11-3-0.bar1.Orlando1.Level3.net (4.79.116.137) 18.320 ms 7 ae-8-8.ebr1.Atlanta2.Level3.net (4.69.137.150) 32.201 ms 32.442 ms 32.645 ms 8 * ae-28-52.car2.Atlanta4.Level3.net (4.68.103.45) 30.475 ms * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * *
--- david raistrick http://www.netmeister.org/news/learn2quote.html drais@icantclick.org http://www.expita.com/nomime.html