cancel
Showing results for 
Search instead for 
Did you mean: 

level3 jump in latency if routing through SanFrancisco

Gus
Aspiring Pro
Posts: 3,236
Thanks: 26
Fixes: 3
Registered: ‎31-07-2007

level3 jump in latency if routing through SanFrancisco

Weather hitting US internet hard or is it just level3?  Normally digitalextremes.zendesk.com pings in at around 110-130, currently 200+ and is taking a good 50-60 seconds to load
FTTP 500 regrade from Tues 28th November
1 REPLY 1
npr
Pro
Posts: 1,898
Thanks: 119
Fixes: 9
Registered: ‎21-01-2013

Re: level3 jump in latency if routing through SanFrancisco

The login screen loaded here in about 1 second.
Quote
Pinging 192.161.148.134 with 32 bytes of data:
Reply from 192.161.148.134: bytes=32 time=167ms TTL=243
Reply from 192.161.148.134: bytes=32 time=167ms TTL=243
Reply from 192.161.148.134: bytes=32 time=167ms TTL=243
Reply from 192.161.148.134: bytes=32 time=168ms TTL=243
Ping statistics for 192.161.148.134:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 167ms, Maximum = 168ms, Average = 167ms

Quote
Tracing route to proxy-new.vip.pod2.sac1.zdsys.com [192.161.148.134]
over a maximum of 30 hops:
  1    2 ms    1 ms    1 ms  192.168.1.1
  2    24 ms    24 ms    24 ms  lo0.11.Central11.ptw-bng02.plus.net [195.166.130.204]
  3    24 ms    23 ms    24 ms  irb.11.PTW-CR01.plus.net [84.93.249.17]
  4    24 ms    24 ms    24 ms  te-3-4.car5.London1.Level3.net [217.163.45.181]
  5  162 ms  162 ms  163 ms  ae-1-5.bar1.SanFrancisco1.Level3.net [4.69.140.149]
  6  165 ms  167 ms  165 ms  ZENDESK-INC.bar1.SanFrancisco1.Level3.net [4.35.161.206]
  7  166 ms  166 ms  165 ms  tr01-sac1-ge-0-0-0.sac1.zdsys.com [192.161.144.3]
  8    *        *        *    Request timed out.
  9    *        *        *    Request timed out.
10    *        *        *    Request timed out.
11  167 ms  166 ms  166 ms  proxy-new.vip.pod2.sac1.zdsys.com [192.161.148.134]