Your provider is likely backhauling the circuits opposite directions to PE routers in a different geographic local than the sites. It's time to have a discussion with your sales engineer about the physical pathing of your circuits and PE router locations.
When I know I have latency critical circuits, I always insist on backhaul to the same geographic region and/or Pe. It's unlikely the MPLS or circuits themselves have anything to do with the latency, assuming this is T1, Ethernet, or similar. It's possible it could be a routing issue SP side, but is not as likely as a general pathing issue. On Thu, Nov 15, 2012 at 12:20 PM, Jared Mauch <[email protected]> wrote: > > On Nov 15, 2012, at 2:15 PM, Scott Weeks wrote: > > > > > > > --- [email protected] wrote: > > From: Mikeal Clark <[email protected]> > > > > 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. What is considered normal/acceptable? > > -------------------------------------------- > > > > > > Coast-to-coast latency is around 60-65msec, so that's high. > > What link speed? > > Perhaps he's using ISDN or a T1? > > Serialization delay is not to be ignored. > > - Jared > >
