[Outages-discussion] Verizon slowdown between 1130 and 1330 each day this week

[Scott Weeks]

I don't see anything wrong with the traceroute.  There is no router output showing drops or other errors, so who knows about that.  Is he just concerned with the number of hops?  That's not impacting his service.  Boston to NYC is 7msec.  Then 22-23msec from NYC to Chicago.  ???

scott

--- amon at vnl.com wrote:

From: Dale Amon <amon at vnl.com>
To: outages-discussion at outages.org
Cc: Jim Caggy <jim.caggy at mapdigital.com>
Subject: [Outages-discussion] Verizon slowdown between 1130 and 1330 each	day this week
Date: Wed, 20 May 2009 12:22:18 -0400

Has anyone else seen anything like this? Here's a report from
our network engineer on site:

> Hey Dale for the last couple days we've had either a major slowdown, lost
> packets or completely lost TCP connections somewhere between the hotel's
> endpoint and the Internet.  Verizon Tech support is being stupid and just
> showing us the stats between the Hotels border router to their gateway
> router, which is just a single hop, but there are multiple hops within the
> Verizon backbone before our packets get to the Internet.

> The problem starts between 1130 and 1330.  It's a major slowdown that I
> would imagine other customers of Verizon are experiencing.   Is there any
> resources you can tap to find out why we are getting this slowdown in the
> backbone or on the way to the Internet.  Its definitely causing major packet
> loss because its terminated our windows media streams several times in the
> last few days during that time period. 

> Here is a traceroute from us to the streaming provider so you can see the
> hops.  There has to be others who have experienced problems along this route
> during the timeframe mentioned above in the last few days.

  1    <1 ms    <1 ms    <1 ms  10.5.4.2 
  2     2 ms     1 ms     1 ms  65.206.112.1 
  3     3 ms     3 ms     3 ms  Serial5-1.GW1.BOS4.ALTER.NET [157.130.11.161] 
  4     4 ms     4 ms     3 ms  167.at-6-0-0.XR2.BOS4.ALTER.NET [152.63.16.242] 
  5     3 ms     3 ms     3 ms  0.so-3-0-2.XL4.BOS4.ALTER.NET [152.63.16.133] 
  6    11 ms    11 ms    11 ms  0.so-6-3-0.XL4.NYC4.ALTER.NET [152.63.0.73] 
  7    11 ms    11 ms    11 ms  204.255.173.54 
  8    16 ms    11 ms    11 ms  vlan52.ebr2.NewYork2.Level3.net [4.69.138.254] 
  9    35 ms    36 ms    53 ms  ae-2-2.ebr1.Chicago1.Level3.net [4.69.132.65] 
 10    33 ms    33 ms    34 ms  ae-13-51.car3.Chicago1.Level3.net [4.68.101.7] 
 11    97 ms    33 ms    33 ms  xe-0-3-0.cr2.ord1.us.nlayer.net [4.71.101.14] 
 12    33 ms    35 ms    33 ms  po6.ar2.ord1.us.scnet.net [69.31.111.6] 
 13    35 ms    34 ms    35 ms  ge0-50.aggr4302.ord2.us.scnet.net [75.102.0.114] 
 14    33 ms    32 ms    33 ms  gimli.audiovideoweb.com [216.246.4.18]

Thanks for any help. It's got us at the
hair pulling stage. Given what we're using it for
your own C-level management might be there ;-) 
(it's the JPMorgan Tech09 Investor conference).




_______________________________________________
Outages-discussion mailing list
Outages-discussion at outages.org
https://puck.nether.net/mailman/listinfo/outages-discussion