Perhaps the network is "oldish" and there are BW bottlenecks that lead
to queues on the switches/routers that results in higher latency.
This would depend alot on the internal QoS strategy used by AT&T, the
type of equipment used and the load in different parts of the network.
The only way to know what happens inside their MPLS cloud is to get past
support and ask someone from the technical staff.
On 11/16/2012 12:06 AM, Randy wrote:
--- On Thu, 11/15/12, William Herrin <b...@herrin.us> wrote:
From: William Herrin <b...@herrin.us>
Subject: Re: MPLS acceptable latency?
To: "Mikeal Clark" <mikeal.cl...@gmail.com>
Cc: "NANOG [nanog@nanog.org]" <nanog@nanog.org>
Date: Thursday, November 15, 2012, 1:23 PM
On Thu, Nov 15, 2012 at 1:54 PM,
Mikeal Clark <mikeal.cl...@gmail.com>
wrote:
I have some AT&T MPLS sites under a managed
contract with latency
averaging 75-85 ms without any load. These sites
are only 45 minutes
away.
I've noticed this with AT&T's MPLS product when dealing
with the
internal corporate network here. I don't know what they're
doing wrong
but it is so very wrong.
circa 2007, noticed same thing: never below 90ms coast-to-coast across as13979.
atm ds3 handoffs on both ends.
What is considered normal/acceptable?
Less than 10ms unless you're using a sub-T1 interface or
going a very
long distance.
Regards,
Bill Herrin
--
William D. Herrin ................ her...@dirtside.com
b...@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
