I get 12ms from Sacramento to Reno and 18ms from Sacramento to Fresno. Sac
to Fresno is about 175 miles.

Are you just concerned about the latency number or are your users reporting
issues?

On Thu, May 5, 2011 at 11:13 AM, Stringham, Steven <[email protected]>wrote:

>  We have a few sites on our MPLS network with Twtelecom.  Some of the have
> pretty good latency (<10ms for Phoenix to Las Vegas - all fiber to the
> building) to not so good latency (40ms Phoenix ->Reno Nevada - Dual T1s in
> Reno). I am seeing similar latency (38ms) from Phoenix to San Jose (another
> dual T1 on the San Jose side, but a fiber connection to my Phoenix side. My
> Phoenix to Albuquerue (all fiber again) is about 15ms. This is about the
> same distance as to the San Jose - but over double the latency.
>
> Strict math (best case - line of site 2/3 speed of light calculations) say
> that my Reno line should be about 10ms. So, I double it for equipment and I
> still get 20ms. Less than half.
>
> My question is what do you folks see out there? Do you see a higher latency
> on a T1 line than a fiber to the building line by that much of a
> difference?  Or, is there a routing issue that is creating delays?
>
> Any feed back you can give would be helpful.
> Thanks
>  Steven Stringham
>
>
>
>
>
>
>
> ------------------------------
>
> For more information about *Lewis and Roca LLP*, please go to *
> www.lewisandroca.com* <http://www.lewisandroca.com/>.
>
>   Phoenix (602)262-5311      Minden (775)586-9500  Tucson (520)622-2090
>      Albuquerque (505)764-5400  Las Vegas (702)949-8200      Silicon
> Valley (650)391-1380  Reno (775)823-2900
>
>   This message is intended only for the use of the individual or entity to
> which it is addressed. If the reader of this message is not the intended
> recipient, or the employee or agent responsible for delivering the message
> to the intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this message is strictly prohibited. If you have
> received this communication in error, please notify us immediately by
> replying to the sender of this E-Mail by return E-Mail or by telephone.
>
>   In accordance with Internal Revenue Service Circular 230, we advise you
> that if this email contains any tax advice, such tax advice was not intended
> or written to be used, and it cannot be used, by any taxpayer for the
> purpose of avoiding penalties that may be imposed on the taxpayer.
>
>     ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to [email protected]
> with the body: unsubscribe ntsysadmin
>



-- 
Thank you,
Mike Sullivan

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin

Reply via email to