Depending on whether TTL is propagated into MPLS, this could be true. Though it should also be pointed out that ICMP responses aren't exactly a precise scientific tool... The responding router could just be busy, and the response time could be reflective of load more than link latency etc. Similarly, failure to get any response at all from a router isn't necessarily indicative of packet loss...
Cheers, -Benson Sent via BlackBerry from T-Mobile -----Original Message----- From: "Frank Bulk - iNAME" <[EMAIL PROTECTED]> Date: Thu, 26 Jun 2008 19:54:42 To:"'John T. Yocum'" <[EMAIL PROTECTED]> Cc:nanog list <[EMAIL PROTECTED]> Subject: RE: Possible explanations for a large hop in latency Did that satisfy you? I guess with MPLS they could tag the traffic and send it around the country twice and I wouldn't see it at L3. Frank -----Original Message----- From: John T. Yocum [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2008 7:04 PM To: [EMAIL PROTECTED] Cc: nanog list Subject: Re: Possible explanations for a large hop in latency When I asked ATT about the sudden latency jump I see in traceroutes, they told me it was due to how their MPLS network is setup. --John Frank Bulk wrote: > Our upstream provider has a connection to AT&T (12.88.71.13) where I > relatively consistently measure with a RTT of 15 msec, but the next hop > (12.122.112.22) comes in with a RTT of 85 msec. Unless AT&T is sending that > traffic over a cable modem or to Europe and back, I can't see a reason why > there is a consistent ~70 msec jump in RTT. Hops farther along the route > are just a few msec more each hop, so it doesn't appear that 12.122.112.22 > has some kind of ICMP rate-limiting. > > Is this a real performance issue, or is there some logical explanation? > > Frank > >
