Re: delays to google

[Randy Bush]

> going to Frankfurt to get to Mountain view:

do not eat the wurst in the senator lounge

randy

Re: delays to google

[Matthew Petach]

On 5/14/09, Peter Beckman  wrote:
> On Thu, 14 May 2009, Graeme Fowler wrote:
> > On Thu, 2009-05-14 at 12:34 -0400, Justin M. Streiner wrote:
> > > I'm guessing whatever the issue is has been resolved, or the storm has
> > > passed?
> > >
> http://www.google.com/appsstatus#rm:1/di:1/do:1/ddo:0
> > Not that it would have been much use to you at the time.
>
>   It's clear the problem was not affecting a small subset of users:
>
> "We're aware of a problem with Google Mail affecting a small subset of
>  users."
>
>   If ISC has an issue open on it, and there is chatter on Nanog about it,
>   unless they consider their userbase to be 6 billion potential users, the
>   issue affected more than a "small subset."

Actually, only a small subset of users only know how to search on Google;
everyone else realized they could use Yahoo search in the meantime.  ;P

*ducks and runs*

Re: delays to google

[Seth Mattinen]

Andy Ringsmuth wrote:
> It's starting to show up in the news media as well:
> 
> http://apnews.myway.com/article/20090514/D9864P900.html
> 
> 
> Google glitch disrupts search engine, e-mail
> 


Because we let google control our fate far too much.

Personally, I think this thread is more off topic than the ones that
were moderated and should live on the outages mailing list. This is not
operational, it's just google being broken, again.

~Seth

Re: delays to google

[Andy Ringsmuth]

It's starting to show up in the news media as well:

http://apnews.myway.com/article/20090514/D9864P900.html


Google glitch disrupts search engine, e-mail
<>
 Email this Story

May 14, 12:54 PM (ET)

MOUNTAIN VIEW, Calif. (AP) - Technical problems at Google are  
preventing an unknown number of people from using its Internet search  
engine, e-mail and other services.


In a Thursday post on its Web site, the Mountain View-based company  
reports that a "small subset of users" hasn't been able to get into  
their e-mail accounts. Without elaborating, Google says the e-mail  
trouble might be affecting other services as well.


Multiple messages posted on Twitter, a popular information-sharing  
forum, indicate that people all over the world are having trouble with  
the Google search engine and e-mail. But other Twitter users say their  
Google services have been running smoothly.


Google says the company is working to fix the problems.

Re: delays to google

[Peter Beckman]

On Thu, 14 May 2009, Graeme Fowler wrote:


On Thu, 2009-05-14 at 12:34 -0400, Justin M. Streiner wrote:

I'm guessing whatever the issue is has been resolved, or the storm has
passed?


http://www.google.com/appsstatus#rm:1/di:1/do:1/ddo:0

Not that it would have been much use to you at the time.


 It's clear the problem was not affecting a small subset of users:

"We're aware of a problem with Google Mail affecting a small subset of
 users."

 If ISC has an issue open on it, and there is chatter on Nanog about it,
 unless they consider their userbase to be 6 billion potential users, the
 issue affected more than a "small subset."

---
Peter Beckman  Internet Guy
beck...@angryox.com http://www.angryox.com/
---

Re: RE: delays to google

[Joel Esler]

[Citation Needed]

On Thu, May 14, 2009 at 1:21 PM,  wrote:

> Google ack'da maintenance on their core network did not go as
> planned-Forced traffic to one peer link that was unable to handle all the
> traffic. Maintenance has been rolled back. Issue has been restored,
>
> -Adam
>
>
> On May 14, 2009 12:44pm, "Mullins, Douglas"  wrote:
>
>> conficker?
>>
>
>
>
>
>
>  Doug
>>
>
>
>
>
>
>
>
>
>  -Original Message-
>>
>
>
>  From: Patrick Darden [mailto:dar...@armc.org]
>>
>
>
>  Sent: Thursday, May 14, 2009 12:13 PM
>>
>
>
>  To: na...@merit.edu
>>
>
>
>  Subject: Re: delays to google
>>
>
>
>
>
>
>
>
>
>  Fixed?
>>
>
>
>
>
>
>  5 mins ago:
>>
>
>
>  1 gw1.armc.org (68.153.29.1) 0.571 ms 0.705 ms 0.732 ms
>>
>
>
>  2 65.14.131.185 (65.14.131.185) 2.330 ms 2.318 ms 2.308 ms
>>
>
>
>  3 axr00mia-7-0-0-0.bellsouth.net (65.83.237.92) 3.009 ms 3.001 ms 3.080
>>
>
>
>  ms
>>
>
>
>  4 AXR00AEP-0-1-0.bellsouth.net (65.83.236.50) 2.384 ms 2.370 ms 2.499 ms
>>
>
>
>  5 65.83.238.202 (65.83.238.202) 3.148 ms 3.136 ms *
>>
>
>
>  6 cr1.attga.ip.att.net (12.122.141.22) 4.011 ms 3.769 ms 4.106 ms
>>
>
>
>  7 12.123.22.5 (12.123.22.5) 3.735 ms 3.042 ms 3.033 ms
>>
>
>
>  8 * * *
>>
>
>
>  9 72.14.233.56 (72.14.233.56) 159.416 ms * *
>>
>
>
>  10 72.14.232.213 (72.14.232.213) 163.622 ms 209.85.254.241
>>
>
>
>  (209.85.254.241) 165.287 ms 209.85.254.243 (209.85.254.243) 219.136 ms
>>
>
>
>  11 209.85.254.6 (209.85.254.6) 170.937 ms 171.154 ms 209.85.254.10
>>
>
>
>  (209.85.254.10) 169.944 ms
>>
>
>
>  12 * * *
>>
>
>
>  13 * * *
>>
>
>
>  14 * * *
>>
>
>
>  15 * * *
>>
>
>
>  16 * * *
>>
>
>
>  17 * * *
>>
>
>
>  18 * * *
>>
>
>
>  19 * * *
>>
>
>
>  20 * * *
>>
>
>
>  21 * * *
>>
>
>
>  22 * * *
>>
>
>
>  23 * * *
>>
>
>
>  24 * * *
>>
>
>
>  25 * * *
>>
>
>
>  26 * * *
>>
>
>
>  27 * * *
>>
>
>
>  28 * * *
>>
>
>
>  29 * * *
>>
>
>
>  30 * * *
>>
>
>
>
>
>
>
>
>
>  Now (12:11 eastern)
>>
>
>
>  [r...@inetsec ~]# traceroute www.google.com
>>
>
>
>  traceroute to www.google.com (74.125.65.99), 30 hops max, 60 byte
>>
>
>
>  packets
>>
>
>
>  1 gw1.armc.org (68.153.29.1) 0.760 ms 0.884 ms 0.908 ms
>>
>
>
>  2 65.14.131.185 (65.14.131.185) 2.345 ms 2.342 ms 3.132 ms
>>
>
>
>  3 axr01asm-7-1-0-1.bellsouth.net (65.83.237.90) 3.338 ms 3.331 ms 3.322
>>
>
>
>  ms
>>
>
>
>  4 axr00msy-0-3-1.bellsouth.net (65.83.236.46) 3.112 ms 3.105 ms 3.095 ms
>>
>
>
>  5 65.83.238.202 (65.83.238.202) 3.503 ms 3.654 ms *
>>
>
>
>  6 cr2.attga.ip.att.net (12.122.140.22) 4.489 ms 3.823 ms 3.795 ms
>>
>
>
>  7 12.123.22.129 (12.123.22.129) 3.591 ms 3.094 ms 3.079 ms
>>
>
>
>  8 12.88.97.6 (12.88.97.6) 3.197 ms 3.172 ms 3.160 ms
>>
>
>
>  9 72.14.233.56 (72.14.233.56) 3.322 ms 3.490 ms 72.14.233.54
>>
>
>
>  (72.14.233.54) 3.510 ms
>>
>
>
>  10 209.85.254.249 (209.85.254.249) 16.887 ms 3.501 ms 72.14.239.127
>>
>
>
>  (72.14.239.127) 4.261 ms
>>
>
>
>  11 209.85.253.214 (209.85.253.214) 12.987 ms 12.979 ms 209.85.253.218
>>
>
>
>  (209.85.253.218) 3.882 ms
>>
>
>
>  12 gx-in-f99.google.com (74.125.65.99) 4.357 ms 4.740 ms 4.481 ms
>>
>
>
>
>
>
>
>
>
>  --Patrick Darden
>>
>
>
>
>
>
>
>
>
>
>
>
>
>


-- 
joel esler | Sourcefire | gtalk: jes...@sourcefire.com | 302-223-5974 |
http://twitter.com/joelesler

Re: RE: delays to google

[A2thaH]

Google ack'da maintenance on their core network did not go as  
planned-Forced traffic to one peer link that was unable to handle all the  
traffic. Maintenance has been rolled back. Issue has been restored,


-Adam

On May 14, 2009 12:44pm, "Mullins, Douglas"  wrote:

conficker?







Doug










-Original Message-




From: Patrick Darden [mailto:dar...@armc.org]




Sent: Thursday, May 14, 2009 12:13 PM




To: na...@merit.edu




Subject: Re: delays to google










Fixed?







5 mins ago:




1 gw1.armc.org (68.153.29.1) 0.571 ms 0.705 ms 0.732 ms




2 65.14.131.185 (65.14.131.185) 2.330 ms 2.318 ms 2.308 ms




3 axr00mia-7-0-0-0.bellsouth.net (65.83.237.92) 3.009 ms 3.001 ms 3.080




ms




4 AXR00AEP-0-1-0.bellsouth.net (65.83.236.50) 2.384 ms 2.370 ms 2.499 ms




5 65.83.238.202 (65.83.238.202) 3.148 ms 3.136 ms *




6 cr1.attga.ip.att.net (12.122.141.22) 4.011 ms 3.769 ms 4.106 ms




7 12.123.22.5 (12.123.22.5) 3.735 ms 3.042 ms 3.033 ms




8 * * *




9 72.14.233.56 (72.14.233.56) 159.416 ms * *




10 72.14.232.213 (72.14.232.213) 163.622 ms 209.85.254.241




(209.85.254.241) 165.287 ms 209.85.254.243 (209.85.254.243) 219.136 ms




11 209.85.254.6 (209.85.254.6) 170.937 ms 171.154 ms 209.85.254.10




(209.85.254.10) 169.944 ms




12 * * *




13 * * *




14 * * *




15 * * *




16 * * *




17 * * *




18 * * *




19 * * *




20 * * *




21 * * *




22 * * *




23 * * *




24 * * *




25 * * *




26 * * *




27 * * *




28 * * *




29 * * *




30 * * *










Now (12:11 eastern)




[r...@inetsec ~]# traceroute www.google.com




traceroute to www.google.com (74.125.65.99), 30 hops max, 60 byte




packets




1 gw1.armc.org (68.153.29.1) 0.760 ms 0.884 ms 0.908 ms




2 65.14.131.185 (65.14.131.185) 2.345 ms 2.342 ms 3.132 ms




3 axr01asm-7-1-0-1.bellsouth.net (65.83.237.90) 3.338 ms 3.331 ms 3.322




ms




4 axr00msy-0-3-1.bellsouth.net (65.83.236.46) 3.112 ms 3.105 ms 3.095 ms




5 65.83.238.202 (65.83.238.202) 3.503 ms 3.654 ms *




6 cr2.attga.ip.att.net (12.122.140.22) 4.489 ms 3.823 ms 3.795 ms




7 12.123.22.129 (12.123.22.129) 3.591 ms 3.094 ms 3.079 ms




8 12.88.97.6 (12.88.97.6) 3.197 ms 3.172 ms 3.160 ms




9 72.14.233.56 (72.14.233.56) 3.322 ms 3.490 ms 72.14.233.54




(72.14.233.54) 3.510 ms




10 209.85.254.249 (209.85.254.249) 16.887 ms 3.501 ms 72.14.239.127




(72.14.239.127) 4.261 ms




11 209.85.253.214 (209.85.253.214) 12.987 ms 12.979 ms 209.85.253.218




(209.85.253.218) 3.882 ms




12 gx-in-f99.google.com (74.125.65.99) 4.357 ms 4.740 ms 4.481 ms










--Patrick Darden

Re: delays to google

[Nuno Vieira - nfsi telecom]

maybe is a good time to enable IPv6 :-)

We noticed issues on IPv4, but IPv6 was working perfectly (we are on Google 
IPv6 program)...

I was able to access google all the times, as i was using IPv6 as preferred 
transport

IPv4: 

traceroute to www.google.com (209.85.227.104), 30 hops max, 40 byte packets
 1  ge130-1000m.cr2.lisboa.nfsi.pt (81.92.200.126)  0.159 ms  0.154 ms  0.148 ms
 2  xe12-10GE.xmr1.Lisbon.as25137.net (81.92.201.10)  0.330 ms  0.408 ms  0.450 
ms
 3  if-3-1.core1.PV9-Lisbon.as6453.net (195.219.187.49)  0.238 ms  0.279 ms 
if-3-2.core1.PV9-Lisbon.as6453.net (195.219.186.9)  0.275 ms
 4  if-12-0-0.mcore3.L78-London.as6453.net (195.219.144.5)  27.960 ms  27.993 
ms  28.083 ms
 5  if-1-0-0.mse1.LRT-London.as6453.net (195.219.144.2)  27.483 ms  27.225 ms  
27.224 ms
 6  if-13-0-0-3.mcore3.LDN-London.as6453.net (195.219.195.21)  34.298 ms  
33.299 ms  33.242 ms
 7  Vlan1254.icore1.LDN-London.as6453.net (195.219.195.90)  27.223 ms  27.219 
ms  27.302 ms
 8  xe-10-2-0-edge3.london1.level3.net (4.68.63.105)  27.444 ms  27.444 ms  
27.437 ms
 9  ae-11-51.car1.London1.Level3.net (4.69.139.66)  27.566 ms  27.673 ms 
ae-21-52.car1.London1.Level3.net (4.69.139.98)  27.656 ms
10  * * *
11  * * *
12  * 66.249.95.170 (66.249.95.170)  373.764 ms 72.14.232.134 (72.14.232.134)  
387.434 ms
13  * * *
14  *  (209.85.243.93)  403.618 ms *
15  wy-in-f104.google.com (209.85.227.104)  376.948 ms * *

IPv6:

traceroute to www.google.com (2001:4860:a004::68), 30 hops max, 40 byte packets
 1  ge-1.Edge1.ip6.Lisbon.NFSi.pt (2001:b18::)  8.656 ms  8.692 ms  8.736 ms
 2  2001:5a0:1500::1 (2001:5a0:1500::1)  0.585 ms^C
r...@matrix:/var/log# traceroute6 www.google.com
traceroute to www.google.com (2001:4860:a004::68), 30 hops max, 40 byte packets
 1  ge-1.Edge1.ip6.Lisbon.NFSi.pt (2001:b18::)  0.133 ms  0.212 ms  0.209 ms
 2  2001:5a0:1500::1 (2001:5a0:1500::1)  0.198 ms 2001:5a0:1500::11 
(2001:5a0:1500::11)  0.192 ms *
 3  2001:5a0:1500::1a (2001:5a0:1500::1a)  26.925 ms * *
 4  2001:5a0:c00:100::e (2001:5a0:c00:100::e)  36.672 ms * *
 5  2001:5a0:200::5 (2001:5a0:200::5)  130.695 ms  130.838 ms  130.826 ms
 6  pr61.ams04.net.google.com (2001:7f8:1::a501:5169:1)  42.306 ms  41.953 ms  
42.176 ms
 7  * * *
 8  * * *
 9  ww-in-x68.google.com (2001:4860:a004::68)  42.858 ms  45.349 ms  44.190 ms

Those traceroutes have been taken 1 hour ago, orso, but now everything looks ok 
in both protocols.

cheers,
---
Nuno Vieira
nfsi telecom, lda.

nuno.vie...@nfsi.pt
Tel. (+351) 21 949 2300 - Fax (+351) 21 949 2301
http://www.nfsi.pt/

Re: delays to google

[Graeme Fowler]

On Thu, 2009-05-14 at 12:34 -0400, Justin M. Streiner wrote:
> I'm guessing whatever the issue is has been resolved, or the storm has 
> passed?

http://www.google.com/appsstatus#rm:1/di:1/do:1/ddo:0

Not that it would have been much use to you at the time.

Graeme

RE: delays to google

[Mullins, Douglas]

conficker?

Doug


-Original Message-
From: Patrick Darden [mailto:dar...@armc.org] 
Sent: Thursday, May 14, 2009 12:13 PM
To: na...@merit.edu
Subject: Re: delays to google


Fixed?

5 mins ago:
1 gw1.armc.org (68.153.29.1) 0.571 ms 0.705 ms 0.732 ms
2 65.14.131.185 (65.14.131.185) 2.330 ms 2.318 ms 2.308 ms
3 axr00mia-7-0-0-0.bellsouth.net (65.83.237.92) 3.009 ms 3.001 ms 3.080
ms
4 AXR00AEP-0-1-0.bellsouth.net (65.83.236.50) 2.384 ms 2.370 ms 2.499 ms
5 65.83.238.202 (65.83.238.202) 3.148 ms 3.136 ms *
6 cr1.attga.ip.att.net (12.122.141.22) 4.011 ms 3.769 ms 4.106 ms
7 12.123.22.5 (12.123.22.5) 3.735 ms 3.042 ms 3.033 ms
8 * * *
9 72.14.233.56 (72.14.233.56) 159.416 ms * *
10 72.14.232.213 (72.14.232.213) 163.622 ms 209.85.254.241 
(209.85.254.241) 165.287 ms 209.85.254.243 (209.85.254.243) 219.136 ms
11 209.85.254.6 (209.85.254.6) 170.937 ms 171.154 ms 209.85.254.10 
(209.85.254.10) 169.944 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *


Now (12:11 eastern)
[r...@inetsec ~]# traceroute www.google.com
traceroute to www.google.com (74.125.65.99), 30 hops max, 60 byte
packets
1 gw1.armc.org (68.153.29.1) 0.760 ms 0.884 ms 0.908 ms
2 65.14.131.185 (65.14.131.185) 2.345 ms 2.342 ms 3.132 ms
3 axr01asm-7-1-0-1.bellsouth.net (65.83.237.90) 3.338 ms 3.331 ms 3.322
ms
4 axr00msy-0-3-1.bellsouth.net (65.83.236.46) 3.112 ms 3.105 ms 3.095 ms
5 65.83.238.202 (65.83.238.202) 3.503 ms 3.654 ms *
6 cr2.attga.ip.att.net (12.122.140.22) 4.489 ms 3.823 ms 3.795 ms
7 12.123.22.129 (12.123.22.129) 3.591 ms 3.094 ms 3.079 ms
8 12.88.97.6 (12.88.97.6) 3.197 ms 3.172 ms 3.160 ms
9 72.14.233.56 (72.14.233.56) 3.322 ms 3.490 ms 72.14.233.54 
(72.14.233.54) 3.510 ms
10 209.85.254.249 (209.85.254.249) 16.887 ms 3.501 ms 72.14.239.127 
(72.14.239.127) 4.261 ms
11 209.85.253.214 (209.85.253.214) 12.987 ms 12.979 ms 209.85.253.218 
(209.85.253.218) 3.882 ms
12 gx-in-f99.google.com (74.125.65.99) 4.357 ms 4.740 ms 4.481 ms


--Patrick Darden

Re: delays to google

[mikael krantz]

Works gr8 in europe from direct peers with Google:
 6  72.14.198.177 (72.14.198.177)  45.648 ms  1.259 ms  1.069 ms
 7  209.85.252.186 (209.85.252.186)  1.455 ms  1.350 ms  1.400 ms
 8  209.85.254.153 (209.85.254.153)  20.040 ms  20.494 ms  20.226 ms
 9  216.239.48.10 (216.239.48.10)  59.618 ms  35.241 ms  34.844 ms
10  72.14.232.165 (72.14.232.165)  35.193 ms  35.256 ms 72.14.232.167
(72.14.232.167)  35.508 ms
11  72.14.233.210 (72.14.233.210)  35.158 ms  39.258 ms  36.284 ms
12  fk-in-f147.google.com (209.85.129.147)  35.704 ms  35.817 ms  35.601 ms



On Thu, May 14, 2009 at 6:04 PM,   wrote:
> Sessions time out or fail from AT&T Commercial, Verizon commercial,
> Verizon FiOS, and AT&T 3G GSM, all from the East Coast.
>
> However, routing from a shell at pair.com:
>
> %traceroute mail.google.com
> traceroute: Warning: mail.google.com has multiple addresses; using
> 74.125.53.17
> traceroute to googlemail.l.google.com (74.125.53.17), 64 hops max, 40 byte
> packets
>  2  192.168.1.41 (192.168.1.41)  3.963 ms  1.456 ms  1.477 ms
>  3  TenGigabitEthernet7-2.ar5.CHI1.gblx.net (207.138.112.145)  15.972 ms
> 14.336 ms  14.268 ms
>  4  po1-20G.ar3.CHI2.gblx.net (67.16.132.241)  14.563 ms  13.708 ms
> 14.454 ms
>  5  72.14.197.69 (72.14.197.69)  53.439 ms  13.862 ms  13.986 ms
>  6  209.85.254.122 (209.85.254.122)  14.283 ms  14.322 ms  13.999 ms
>  7  72.14.233.116 (72.14.233.116)  65.376 ms  65.557 ms  65.849 ms
>  8  216.239.46.208 (216.239.46.208)  72.424 ms  72.163 ms  71.921 ms
>  9  64.233.174.131 (64.233.174.131)  72.007 ms  71.711 ms
>    64.233.174.129 (64.233.174.129)  71.916 ms
> 10  72.14.232.6 (72.14.232.6)  82.512 ms  82.767 ms  71.942 ms
> 11  pw-in-f17.google.com (74.125.53.17)  71.432 ms  71.686 ms  71.938 ms
>
> If I tunnel through, my connection behaves with reasonable crispness.
>
> Cheers,
>
> -Andrew
>
>



-- 
Mikael Krantz
MTS Konsult AB
Mobil: 0735-245880

Re: delays to google

[Justin M. Streiner]

Google and gmail look fine from here (University of Pittsburgh)... no 
loss, ~30ms RTT, reachable through TransitRail.


I'm guessing whatever the issue is has been resolved, or the storm has 
passed?


jms

On Thu, 14 May 2009, and...@arsenaleartisans.com wrote:


Sessions time out or fail from AT&T Commercial, Verizon commercial,
Verizon FiOS, and AT&T 3G GSM, all from the East Coast.

However, routing from a shell at pair.com:

%traceroute mail.google.com
traceroute: Warning: mail.google.com has multiple addresses; using
74.125.53.17
traceroute to googlemail.l.google.com (74.125.53.17), 64 hops max, 40 byte
packets
2  192.168.1.41 (192.168.1.41)  3.963 ms  1.456 ms  1.477 ms
3  TenGigabitEthernet7-2.ar5.CHI1.gblx.net (207.138.112.145)  15.972 ms
14.336 ms  14.268 ms
4  po1-20G.ar3.CHI2.gblx.net (67.16.132.241)  14.563 ms  13.708 ms
14.454 ms
5  72.14.197.69 (72.14.197.69)  53.439 ms  13.862 ms  13.986 ms
6  209.85.254.122 (209.85.254.122)  14.283 ms  14.322 ms  13.999 ms
7  72.14.233.116 (72.14.233.116)  65.376 ms  65.557 ms  65.849 ms
8  216.239.46.208 (216.239.46.208)  72.424 ms  72.163 ms  71.921 ms
9  64.233.174.131 (64.233.174.131)  72.007 ms  71.711 ms
   64.233.174.129 (64.233.174.129)  71.916 ms
10  72.14.232.6 (72.14.232.6)  82.512 ms  82.767 ms  71.942 ms
11  pw-in-f17.google.com (74.125.53.17)  71.432 ms  71.686 ms  71.938 ms

If I tunnel through, my connection behaves with reasonable crispness.

Cheers,

-Andrew

Re: delays to google

[Stephane Tsacas]

NO problem from Iliad/Free French provider :

traceroute to www.google.com (209.85.229.147), 30 hops max, 40 byte packets
 1  ge-vl71.bzn-swr5.dedibox.fr (88.191.71.1)  0.426 ms  0.476 ms  0.526 ms
 2  * * *
 3  th2-crs16-1-be1503-p.intf.routers.proxad.net (212.27.58.45)  0.783 ms
 0.774 ms  0.785 ms
 4  cbv-6k-1-po21.intf.routers.proxad.net (212.27.58.2)  0.646 ms * *
 5  74.125.50.117 (74.125.50.117)  0.629 ms  0.636 ms  0.654 ms
 6  209.85.250.142 (209.85.250.142)  0.954 ms  0.842 ms  0.895 ms
 7  216.239.43.233 (216.239.43.233)  5.950 ms  5.832 ms  5.845 ms
 8  209.85.252.83 (209.85.252.83)  5.900 ms  5.915 ms  5.820 ms
 9  209.85.243.73 (209.85.243.73)  13.795 ms 209.85.243.77 (209.85.243.77)
 13.741 ms 209.85.243.85 (209.85.243.85)  6.123 ms
10  ww-in-f147.google.com (209.85.229.147)  6.106 ms  5.985 ms  5.982 ms

Stéphane

Re: delays to google

[Lucy Lynch]

pac-nw

going to Frankfurt to get to Mountain view:

traceroute to 74.125.87.101 (74.125.87.101), 30 hops max, 60 byte packets
 1  ext-gw.lan (192.168.11.1)  0.983 ms  1.550 ms  1.795 ms
 2  73.90.28.1 (73.90.28.1)  21.859 ms  21.945 ms  22.126 ms
 3  68.85.148.113 (68.85.148.113)  22.312 ms  22.767 ms  22.879 ms
 4  te-9-1-ur02.eugene.or.bverton.comcast.net (68.87.216.66)  22.085 ms 
22.219 ms  22.484 ms
 5  te-7-3-ar01.troutdale.or.bverton.comcast.net (68.87.216.126)  23.039 
ms  23.174 ms  23.435 ms
 6  te-0-4-0-5-cr01.seattle.wa.ibone.comcast.net (68.86.90.237)  25.493 ms 
15.267 ms  15.897 ms
 7  te-3-3.car1.Seattle1.Level3.net (4.79.104.109)  25.407 ms  25.858 ms 
26.565 ms
 8  ae-31-51.ebr1.Seattle1.Level3.net (4.68.105.30)  29.238 ms  29.498 ms 
29.620 ms
 9  ae-1-100.ebr2.Seattle1.Level3.net (4.69.132.18)  27.449 ms  26.683 ms 
26.826 ms
10  ae-2.ebr2.Denver1.Level3.net (4.69.132.54)  59.113 ms  58.653 ms 
48.738 ms
11  ae-3.ebr1.Chicago2.Level3.net (4.69.132.62)  74.530 ms  75.094 ms 
74.101 ms
12  ae-1-100.ebr2.Chicago2.Level3.net (4.69.132.114)  69.747 ms  66.950 ms 
66.559 ms
13  ae-2-2.ebr2.Washington1.Level3.net (4.69.132.70)  99.648 ms  99.452 ms 
98.975 ms
14  ae-44-44.ebr2.Frankfurt1.Level3.net (4.69.137.61)  190.130 ms 
ae-41-41.ebr2.Frankfurt1.Level3.net (4.69.137.49)  188.716 ms 
ae-42-42.ebr2.Frankfurt1.Level3.net (4.69.137.53)  187.548 ms
15  ae-62-62.csw1.Frankfurt1.Level3.net (4.69.140.18)  201.445 ms 
ae-92-92.csw4.Frankfurt1.Level3.net (4.69.140.30)  189.768 ms 
ae-82-82.csw3.Frankfurt1.Level3.net (4.69.140.26)  189.457 ms
16  ae-2-79.edge3.Frankfurt1.Level3.net (4.68.23.75)  189.786 ms 
ae-3-89.edge3.Frankfurt1.Level3.net (4.68.23.139)  188.161 ms  193.637 ms
17  212.162.24.18 (212.162.24.18)  201.646 ms 62.67.33.114 (62.67.33.114) 
190.165 ms 212.162.24.14 (212.162.24.14)  188.573 ms
18  209.85.248.12 (209.85.248.12)  185.611 ms 209.85.254.108 
(209.85.254.108)  189.279 ms  191.738 ms
19  72.14.236.250 (72.14.236.250)  202.201 ms 72.14.232.103 
(72.14.232.103)  202.911 ms 72.14.236.250 (72.14.236.250)  202.550 ms
20  209.85.248.41 (209.85.248.41)  203.061 ms 209.85.248.39 
(209.85.248.39)  200.960 ms 209.85.248.47 (209.85.248.47)  205.403 ms
21  72.14.238.105 (72.14.238.105)  207.646 ms 72.14.232.217 
(72.14.232.217)  212.893 ms 72.14.238.105 (72.14.238.105)  216.114 ms
22  hb-in-f101.google.com (74.125.87.101)  207.553 ms  207.009 ms  207.673 
ms



- Lucy

On Thu, 14 May 2009, William McCall wrote:

Re: delays to google

[Robert Glover]

We are not experiencing any issues seeing google:

[r...@hermes ~]# traceroute www.google.com
traceroute: Warning: www.google.com has multiple addresses; using 
66.102.7.104

traceroute to www.l.google.com (66.102.7.104), 30 hops max, 38 byte packets
1  router (216.139.0.65)  0.271 ms  0.746 ms  0.986 ms
2  vl1192.na21.b003122-0.sfo01.atlas.cogentco.com (38.99.42.233)  3.142 ms 
3.424 ms  4.115 ms
3  gi1-11.3503.mpd01.sfo01.atlas.cogentco.com (66.28.64.161)  4.051 ms 
3.193 ms  3.374 ms
4  te9-4.mpd01.sjc01.atlas.cogentco.com (66.28.4.182)  5.106 ms  22.628 ms 
4.882 ms
5  te7-2.mpd01.sjc03.atlas.cogentco.com (66.28.4.74)  5.026 ms  21.801 ms 
10.957 ms
6  google.sjc03.atlas.cogentco.com (154.54.10.146)  5.204 ms  4.281 ms 
4.724 ms
7  216.239.46.194 (216.239.46.194)  5.557 ms  5.157 ms 72.14.239.250 
(72.14.239.250)  9.921 ms
8  72.14.238.131 (72.14.238.131)  16.955 ms  17.620 ms 216.239.43.145 
(216.239.43.145)  17.566 ms

9  72.14.239.246 (72.14.239.246)  29.737 ms  29.334 ms  18.046 ms
10  mc-in-f104.google.com (66.102.7.104)  16.538 ms  17.477 ms  17.061 ms

Sincerely,
Bobby Glover
Director of Information Services
South Valley Internet (AS4307)
- Original Message - 
From: "Steve Williams" 

To: 
Sent: Thursday, May 14, 2009 8:48 AM
Subject: delays to google


am seeing significant delays in getting to google.  anyone else seeing 
this?


$ traceroute www.google.com
traceroute: Warning: www.google.com has multiple addresses; using 
74.125.53.147
traceroute to www.l.google.com (74.125.53.147), 30 hops max, 40 byte 
packets

1  cisco-190 (129.116.190.250)  0.430 ms  0.350 ms  0.353 ms
2  ser10-v758.gw.utexas.edu (128.83.10.29)  1.138 ms  1.099 ms  1.057 ms
3  ser2-gi1-9.gw.utexas.edu (128.83.10.2)  10.475 ms  1.174 ms  1.584 ms
4  aust-utnoc-core-ge-6-0-0-0.tx-bb.net (192.12.10.1)  1.215 ms  1.209 ms 
1.134 ms
5  te2-1--570.tr01-lsanca01.transitrail.net (137.164.131.221)  40.649 ms 
40.699 ms  40.678 ms

6  * * *
7  * * *
8  * * *
9  * * *
10  * * *
11  72.14.232.10 (72.14.232.10)  261.262 ms * *
12  * * pw-in-f147.google.com (74.125.53.147)  251.867 ms

--


'''
   (O O)
,-- oOO-(_)-OOo -,
|Stephen Williams|
|  Manager of Computer Services  |
|   Center for Space Research|
| University of Texas at Austin  |
| 3925 W. Braker Ln., Suite 200  |
|  Austin, TX 78759-5321 |
|512.471.7235  512.471.3570 (fax)|
|   willi...@csr.utexas.edu  |
| Oooo __|
   oooO   (   )
  (   )) /
   \ ((_/
\_)

Re: delays to google

[Joe Greco]

> We are tracking it here:  http://isc.sans.org/diary.html?storyid=6388

Received some complaints about being unable to reach HP's download web
site.  Seems reachable but alternately nonresponsive, "Service unavailable,"
HP fail page, fail to resolve, etc. (h2.www2.hp.com)  Maybe related,
maybe not.

... JG
-- 
Joe Greco - sol.net Network Services - Milwaukee, WI - http://www.sol.net
"We call it the 'one bite at the apple' rule. Give me one chance [and] then I
won't contact you again." - Direct Marketing Ass'n position on e-mail spam(CNN)
With 24 million small businesses in the US alone, that's way too many apples.

RE: delays to google

[Ben Matthew]

Yes me!!

No other bugger seems to have noticed until now though.  Getting similar traces 
to you; then it just sorts itself out after 5-10 minutes.

I did think it was an issue with my LINX peering.  Clearly not (from your 
trace).

Queue the irritated: why don't you just email n...@google emails.

Love & kisses,

Ben
Absolute Radio (AS34763)


-Original Message-
From: Steve Williams [mailto:willi...@csr.utexas.edu] 
Sent: 14 May 2009 16:49
To: na...@merit.edu
Subject: delays to google

am seeing significant delays in getting to google.  anyone else seeing this?

$ traceroute www.google.com
traceroute: Warning: www.google.com has multiple addresses; using 
74.125.53.147
traceroute to www.l.google.com (74.125.53.147), 30 hops max, 40 byte packets
 1  cisco-190 (129.116.190.250)  0.430 ms  0.350 ms  0.353 ms
 2  ser10-v758.gw.utexas.edu (128.83.10.29)  1.138 ms  1.099 ms  1.057 ms
 3  ser2-gi1-9.gw.utexas.edu (128.83.10.2)  10.475 ms  1.174 ms  1.584 ms
 4  aust-utnoc-core-ge-6-0-0-0.tx-bb.net (192.12.10.1)  1.215 ms  1.209 
ms  1.134 ms
 5  te2-1--570.tr01-lsanca01.transitrail.net (137.164.131.221)  40.649 
ms  40.699 ms  40.678 ms
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  72.14.232.10 (72.14.232.10)  261.262 ms * *
12  * * pw-in-f147.google.com (74.125.53.147)  251.867 ms

-- 


 '''
(O O)
 ,-- oOO-(_)-OOo -,
 |Stephen Williams|
 |  Manager of Computer Services  |
 |   Center for Space Research|
 | University of Texas at Austin  |
 | 3925 W. Braker Ln., Suite 200  |
 |  Austin, TX 78759-5321 |
 |512.471.7235  512.471.3570 (fax)|
 |   willi...@csr.utexas.edu  |
 | Oooo __|
oooO   (   )
   (   )) /
\ ((_/
 \_) 








DISCLAIMER 
This e-mail message, including any attachments, is intended solely for the use 
of the addressee and may contain confidential information. If it is not 
intended for you, please inform the sender and delete the e-mail and any 
attachments immediately. Any review, retransmission, disclosure, copying or 
modification of it is strictly forbidden. Please be advised that the views and 
opinions expressed in this e-mail may not reflect the views and opinions of 
TIML Radio Limited or any of its parent and subsidiary companies.
Whilst we take reasonable precautions to ensure that our emails are free from 
viruses, we cannot be responsible for any viruses transmitted with this e-mail 
and recommend that you subject any incoming e-mail to your own virus checking 
procedures. Use of this or any other e-mail facility signifies consent to any 
interception we might lawfully carry out to prevent abuse of these facilities.

TIML Radio Limited (trading as Absolute Radio)
Registered office: One Golden Square, London. W1F 9DJ
Registered in England No 02674136 VAT No 927 2572 11

Re: delays to google

[Patrick Darden]

Fixed?

5 mins ago:
1 gw1.armc.org (68.153.29.1) 0.571 ms 0.705 ms 0.732 ms
2 65.14.131.185 (65.14.131.185) 2.330 ms 2.318 ms 2.308 ms
3 axr00mia-7-0-0-0.bellsouth.net (65.83.237.92) 3.009 ms 3.001 ms 3.080 ms
4 AXR00AEP-0-1-0.bellsouth.net (65.83.236.50) 2.384 ms 2.370 ms 2.499 ms
5 65.83.238.202 (65.83.238.202) 3.148 ms 3.136 ms *
6 cr1.attga.ip.att.net (12.122.141.22) 4.011 ms 3.769 ms 4.106 ms
7 12.123.22.5 (12.123.22.5) 3.735 ms 3.042 ms 3.033 ms
8 * * *
9 72.14.233.56 (72.14.233.56) 159.416 ms * *
10 72.14.232.213 (72.14.232.213) 163.622 ms 209.85.254.241 
(209.85.254.241) 165.287 ms 209.85.254.243 (209.85.254.243) 219.136 ms
11 209.85.254.6 (209.85.254.6) 170.937 ms 171.154 ms 209.85.254.10 
(209.85.254.10) 169.944 ms

12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *


Now (12:11 eastern)
[r...@inetsec ~]# traceroute www.google.com
traceroute to www.google.com (74.125.65.99), 30 hops max, 60 byte packets
1 gw1.armc.org (68.153.29.1) 0.760 ms 0.884 ms 0.908 ms
2 65.14.131.185 (65.14.131.185) 2.345 ms 2.342 ms 3.132 ms
3 axr01asm-7-1-0-1.bellsouth.net (65.83.237.90) 3.338 ms 3.331 ms 3.322 ms
4 axr00msy-0-3-1.bellsouth.net (65.83.236.46) 3.112 ms 3.105 ms 3.095 ms
5 65.83.238.202 (65.83.238.202) 3.503 ms 3.654 ms *
6 cr2.attga.ip.att.net (12.122.140.22) 4.489 ms 3.823 ms 3.795 ms
7 12.123.22.129 (12.123.22.129) 3.591 ms 3.094 ms 3.079 ms
8 12.88.97.6 (12.88.97.6) 3.197 ms 3.172 ms 3.160 ms
9 72.14.233.56 (72.14.233.56) 3.322 ms 3.490 ms 72.14.233.54 
(72.14.233.54) 3.510 ms
10 209.85.254.249 (209.85.254.249) 16.887 ms 3.501 ms 72.14.239.127 
(72.14.239.127) 4.261 ms
11 209.85.253.214 (209.85.253.214) 12.987 ms 12.979 ms 209.85.253.218 
(209.85.253.218) 3.882 ms

12 gx-in-f99.google.com (74.125.65.99) 4.357 ms 4.740 ms 4.481 ms


--Patrick Darden

Re: delays to google

[Leland E. Vandervort]

Works fine for me... all google services up and okay here (Paris).

traceroute to googlemail.l.google.com (209.85.137.83), 30 hops max, 40
byte packets
 1  fe0-0.gw1.discpro.org (217.70.182.177)  1.644 ms  1.518 ms  1.420 ms
 2  gandi-discpro.gdist1-d.gandi.net (217.70.176.82)  0.887 ms  0.701 ms
0.606 ms
 3  vl9.core3-d.gandi.net (217.70.176.101)  0.666 ms  0.632 ms  0.527 ms
 4  vl9.core4-d.gandi.net (217.70.176.102)  0.592 ms  0.556 ms  0.526 ms
 5  reserved.above.net.43.141.79.in-addr.arpa (79.141.43.5)  0.666 ms
0.827 ms  0.599 ms
 6  xe-4-0-0.mpr1.lhr3.uk.above.net (64.125.31.249)  7.963 ms  7.907 ms
8.165 ms
 7  so-1-0-0.mpr1.lhr2.uk.above.net (64.125.28.38)  7.878 ms  7.824 ms
8.161 ms
 8  213-152-230-99.google.net (213.152.230.99)  8.905 ms  8.771 ms  8.751
ms
 9  209.85.252.42 (209.85.252.42)  8.893 ms 209.85.252.40 (209.85.252.40)
8.228 ms  8.090 ms
10  72.14.233.63 (72.14.233.63)  12.992 ms  16.538 ms 209.85.248.80
(209.85.248.80)  21.237 ms
11  209.85.250.141 (209.85.250.141)  16.448 ms  19.357 ms  16.506 ms
12  72.14.238.128 (72.14.238.128)  23.823 ms  23.637 ms 209.85.248.248
(209.85.248.248)  22.558 ms
13  209.85.241.189 (209.85.241.189)  24.015 ms  23.872 ms  23.672 ms
14  216.239.43.26 (216.239.43.26)  26.986 ms  24.831 ms 216.239.43.98
(216.239.43.98)  24.033 ms
15  mg-in-f83.google.com (209.85.137.83)  24.097 ms  23.879 ms  23.818 ms


traceroute to www.l.google.com (209.85.227.147), 30 hops max, 40 byte
packets
 1  fe0-0.gw1.discpro.org (217.70.182.177)  1.703 ms  2.808 ms  1.850 ms
 2  gandi-discpro.gdist1-d.gandi.net (217.70.176.82)  2.301 ms  1.563 ms
2.236 ms
 3  vl9.core3-d.gandi.net (217.70.176.101)  6.426 ms  2.403 ms  1.240 ms
 4  vl9.core4-d.gandi.net (217.70.176.102)  1.253 ms  2.448 ms  1.267 ms
 5  reserved.above.net.43.141.79.in-addr.arpa (79.141.43.5)  1.239 ms
1.806 ms  1.270 ms
 6  xe-4-0-0.mpr1.lhr3.uk.above.net (64.125.31.249)  8.534 ms  9.148 ms
20.502 ms
 7  so-1-0-0.mpr1.lhr2.uk.above.net (64.125.28.38)  10.123 ms  8.156 ms
101.081 ms
 8  213-152-230-99.google.net (213.152.230.99)  10.094 ms  10.335 ms
8.779 ms
 9  209.85.252.40 (209.85.252.40)  9.063 ms  8.662 ms  8.336 ms
10  66.249.95.170 (66.249.95.170)  11.511 ms  11.400 ms 72.14.232.134
(72.14.232.134)  10.318 ms
11  209.85.252.83 (209.85.252.83)  10.614 ms  10.413 ms  10.455 ms
12  209.85.243.93 (209.85.243.93)  23.418 ms  17.760 ms  17.950 ms
13  wy-in-f147.google.com (209.85.227.147)  11.635 ms  10.581 ms  10.587
ms


Leland


On Thu, 14 May 2009, Eduardo Silvestre wrote:

> Hello,
>
> Same issue in portugal and spain.
>
> pt:~# traceroute www.google.com
> traceroute: Warning: www.google.com has multiple addresses; using 
> 209.85.227.147
> traceroute to www.l.google.com (209.85.227.147), 30 hops max, 40 byte packets
>  1  ge130-1000m.cr2.lisboa.nfsi.pt (81.92.200.126)  0.203 ms  0.085 ms  0.108 
> ms
>  2  xe12-10GE.xmr1.Lisbon.as25137.net (81.92.201.10)  7.358 ms  0.349 ms  
> 0.239 ms
>  3  if-3-2.core1.PV9-Lisbon.as6453.net (195.219.186.9)  0.235 ms  0.347 ms  
> 0.239 ms
>  4  if-12-0-0.mcore3.L78-London.as6453.net (195.219.144.5)  26.974 ms  27.200 
> ms  26.847 ms
>  5  if-5-0-0.mcore3.LDN-London.as6453.net (195.219.195.9)  32.343 ms  32.452 
> ms  32.345 ms
>  6  Vlan62.icore1.LDN-London.as6453.net (195.219.83.1)  39.464 ms  29.329 ms  
> 35.719 ms
>  7  xe-10-2-0-edge3.london1.level3.net (4.68.63.105)  27.469 ms  27.456 ms  
> 27.474 ms
>  8  ae-11-51.car1.London1.Level3.net (4.69.139.66)  27.596 ms 
> ae-21-52.car1.London1.Level3.net (4.69.139.98)  85.304 ms 
> ae-11-51.car1.London1.Level3.net (4.69.139.66)  36.955 ms
>  9  * * *
> 10  * * *
> 11  * * *
> 12  * 72.14.236.191 (72.14.236.191)  389.644 ms *
> 13  * * 209.85.243.93 (209.85.243.93)  387.207 ms
> 14  * * wy-in-f147.google.com (209.85.227.147)  392.378 ms
>
> es:~# traceroute www.google.com
> traceroute to www.google.com (209.85.227.103), 30 hops max, 40 byte packets
>  1  94.46.247.33 (94.46.247.33)  0.401 ms  0.448 ms  0.515 ms
>  2  194.25.210.137 (194.25.210.137)  0.287 ms  0.297 ms  0.345 ms
>  3  194.25.6.66 (194.25.6.66)  41.014 ms  33.308 ms  41.071 ms
>  4  * * *
>  5  * * 209.85.255.170 (209.85.255.170)  390.129 ms
>  6  72.14.232.208 (72.14.232.208)  387.012 ms * *
>  7  * 72.14.232.130 (72.14.232.130)  387.439 ms  386.662 ms
>  8  * * 72.14.236.191 (72.14.236.191)  380.375 ms
>  9  * * *
> 10  * * *
> 11  wy-in-f103.google.com (209.85.227.103)  382.547 ms  403.198 ms *
>
> Regards,
>
> ---
> Eduardo Silvestre
> nfsi telecom, lda.
>
> eduardo.silves...@nfsi.pt
> Tel. (+351) 21 949 2300 - Fax (+351) 21 949 2301
> http://www.nfsi.pt/
>
> - Original Message -
> From: "Athanasios Douitsis" 
> To: "Steve Williams" 
> Cc: na...@merit.edu
> Sent: Thursday, May 14, 2009 4:51:38 PM GMT +00:00 GMT Britain, Ireland, 
> Port

RE: delays to google

[John Bond]

Yes we saw the same thing here but only from certain sources; however it
seems to be back now


John Bond
Network and security Analyst

Eduserv 
innovative technology services 

john.b...@eduserv.org.uk 

tel: +44 (0)1225 474351
fax: +44 (0)1225 474301

http://www.eduserv.org.uk 



> -Original Message-
> From: Sachs, Marcus Hans (Marc) [mailto:marcus.sa...@verizon.com]
> Sent: 14 May 2009 16:57
> To: Steve Williams
> Cc: na...@merit.edu
> Subject: RE: delays to google
> 
> We are tracking it here:  http://isc.sans.org/diary.html?storyid=6388
> 
> Marc Sachs
> Director, SANS Internet Storm Center
> 
> -Original Message-
> From: Steve Williams [mailto:willi...@csr.utexas.edu]
> Sent: Thursday, May 14, 2009 11:49 AM
> To: na...@merit.edu
> Subject: delays to google
> 
> am seeing significant delays in getting to google.  anyone else seeing
> this?
> 
> $ traceroute www.google.com
> traceroute: Warning: www.google.com has multiple addresses; using
> 74.125.53.147
> traceroute to www.l.google.com (74.125.53.147), 30 hops max, 40 byte
> packets
>  1  cisco-190 (129.116.190.250)  0.430 ms  0.350 ms  0.353 ms
>  2  ser10-v758.gw.utexas.edu (128.83.10.29)  1.138 ms  1.099 ms  1.057
> ms
>  3  ser2-gi1-9.gw.utexas.edu (128.83.10.2)  10.475 ms  1.174 ms  1.584
> ms
>  4  aust-utnoc-core-ge-6-0-0-0.tx-bb.net (192.12.10.1)  1.215 ms
1.209
> ms  1.134 ms
>  5  te2-1--570.tr01-lsanca01.transitrail.net (137.164.131.221)  40.649
> ms  40.699 ms  40.678 ms
>  6  * * *
>  7  * * *
>  8  * * *
>  9  * * *
> 10  * * *
> 11  72.14.232.10 (72.14.232.10)  261.262 ms * *
> 12  * * pw-in-f147.google.com (74.125.53.147)  251.867 ms
> 
> --
> 
> 
>  '''
> (O O)
>  ,-- oOO-(_)-OOo -,
>  |Stephen Williams|
>  |  Manager of Computer Services  |
>  |   Center for Space Research|
>  | University of Texas at Austin  |
>  | 3925 W. Braker Ln., Suite 200  |
>  |  Austin, TX 78759-5321 |
>  |512.471.7235  512.471.3570 (fax)|
>  |   willi...@csr.utexas.edu  |
>  | Oooo __|
> oooO   (   )
>(   )) /
> \ ((_/
>  \_)
> 
> 
> 
> 
> 
> 

Re: delays to google

[Marshall Eubanks]

On May 14, 2009, at 11:52 AM, Mario Fernandez wrote:

Seeing the same thing from NY using NTT, we routed via Cogent which  
does not

seem to be having the problem.



Neither does Cogent in Virginia.

Regards
Marshall


On Thu, May 14, 2009 at 11:51 AM, Athanasios Douitsis >wrote:



On Thu, May 14, 2009 at 6:48 PM, Steve Williams 
wrote:


am seeing significant delays in getting to google.  anyone else  
seeing

this?

$ traceroute www.google.com
traceroute: Warning: www.google.com has multiple addresses; using
74.125.53.147
traceroute to www.l.google.com (74.125.53.147), 30 hops max, 40 byte
packets
1  cisco-190 (129.116.190.250)  0.430 ms  0.350 ms  0.353 ms
2  ser10-v758.gw.utexas.edu (128.83.10.29)  1.138 ms  1.099 ms   
1.057 ms
3  ser2-gi1-9.gw.utexas.edu (128.83.10.2)  10.475 ms  1.174 ms   
1.584 ms
4  aust-utnoc-core-ge-6-0-0-0.tx-bb.net (192.12.10.1)  1.215 ms   
1.209

ms

1.134 ms
5  te2-1--570.tr01-lsanca01.transitrail.net (137.164.131.221)   
40.649 ms

40.699 ms  40.678 ms
6  * * *
7  * * *
8  * * *
9  * * *
10  * * *
11  72.14.232.10 (72.14.232.10)  261.262 ms * *
12  * * pw-in-f147.google.com (74.125.53.147)  251.867 ms

--


  '''
 (O O)
,-- oOO-(_)-OOo -,
|Stephen Williams|
|  Manager of Computer Services  |
|   Center for Space Research|
| University of Texas at Austin  |
| 3925 W. Braker Ln., Suite 200  |
|  Austin, TX 78759-5321 |
|512.471.7235  512.471.3570 (fax)|
|   willi...@csr.utexas.edu  |
| Oooo __|
 oooO   (   )
(   )) /
 \ ((_/
  \_)

seeing this too.






--

Sent from Boston, Massachusetts, United States
Yogi Berra   -

"If you ask me anything I don't know, I'm not going to answer."

Re: delays to google

[Eduardo Silvestre]

Hello,

Same issue in portugal and spain.

pt:~# traceroute www.google.com
traceroute: Warning: www.google.com has multiple addresses; using 209.85.227.147
traceroute to www.l.google.com (209.85.227.147), 30 hops max, 40 byte packets
 1  ge130-1000m.cr2.lisboa.nfsi.pt (81.92.200.126)  0.203 ms  0.085 ms  0.108 ms
 2  xe12-10GE.xmr1.Lisbon.as25137.net (81.92.201.10)  7.358 ms  0.349 ms  0.239 
ms
 3  if-3-2.core1.PV9-Lisbon.as6453.net (195.219.186.9)  0.235 ms  0.347 ms  
0.239 ms
 4  if-12-0-0.mcore3.L78-London.as6453.net (195.219.144.5)  26.974 ms  27.200 
ms  26.847 ms
 5  if-5-0-0.mcore3.LDN-London.as6453.net (195.219.195.9)  32.343 ms  32.452 ms 
 32.345 ms
 6  Vlan62.icore1.LDN-London.as6453.net (195.219.83.1)  39.464 ms  29.329 ms  
35.719 ms
 7  xe-10-2-0-edge3.london1.level3.net (4.68.63.105)  27.469 ms  27.456 ms  
27.474 ms
 8  ae-11-51.car1.London1.Level3.net (4.69.139.66)  27.596 ms 
ae-21-52.car1.London1.Level3.net (4.69.139.98)  85.304 ms 
ae-11-51.car1.London1.Level3.net (4.69.139.66)  36.955 ms
 9  * * *
10  * * *
11  * * *
12  * 72.14.236.191 (72.14.236.191)  389.644 ms *
13  * * 209.85.243.93 (209.85.243.93)  387.207 ms
14  * * wy-in-f147.google.com (209.85.227.147)  392.378 ms

es:~# traceroute www.google.com
traceroute to www.google.com (209.85.227.103), 30 hops max, 40 byte packets
 1  94.46.247.33 (94.46.247.33)  0.401 ms  0.448 ms  0.515 ms
 2  194.25.210.137 (194.25.210.137)  0.287 ms  0.297 ms  0.345 ms
 3  194.25.6.66 (194.25.6.66)  41.014 ms  33.308 ms  41.071 ms
 4  * * *
 5  * * 209.85.255.170 (209.85.255.170)  390.129 ms
 6  72.14.232.208 (72.14.232.208)  387.012 ms * *
 7  * 72.14.232.130 (72.14.232.130)  387.439 ms  386.662 ms
 8  * * 72.14.236.191 (72.14.236.191)  380.375 ms
 9  * * *
10  * * *
11  wy-in-f103.google.com (209.85.227.103)  382.547 ms  403.198 ms *

Regards,

---
Eduardo Silvestre
nfsi telecom, lda.

eduardo.silves...@nfsi.pt
Tel. (+351) 21 949 2300 - Fax (+351) 21 949 2301
http://www.nfsi.pt/

- Original Message -
From: "Brance Amussen" 
To: na...@merit.edu
Sent: Thursday, May 14, 2009 4:56:33 PM GMT +00:00 GMT Britain, Ireland, 
Portugal
Subject: Re: delays to google

We are. As well too NYTimes, Gmail, etc...

traceroute to www.nytimes.com (199.239.136.200), 64 hops max, 40 byte
packets
 1  128.220.29.1 (128.220.29.1)  1.222 ms  0.805 ms  1.170 ms
 2  172.17.2.201 (172.17.2.201)  0.894 ms  0.666 ms  0.650 ms
 3  10.160.0.226 (10.160.0.226)  1.311 ms  1.361 ms  1.120 ms
 4  162.129.253.97 (162.129.253.97)  1.485 ms  1.303 ms  1.312 ms
 5  206.196.178.142 (206.196.178.142)  11.428 ms  2.705 ms  2.576 ms
 6  45.78.120.65.in-addr.arpa (65.120.78.45)  3.602 ms  3.796 ms  3.677 ms
 7  nyc-core-01.inet.qwest.net (67.14.7.42)  8.801 ms  8.505 ms  8.304 ms
 8  nyc-edge-03.inet.qwest.net (205.171.217.26)  8.609 ms  8.527 ms  12.914
ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *

traceroute to googlemail.l.google.com (209.85.133.19), 64 hops max, 40 byte
packets
 1  128.220.29.1 (128.220.29.1)  1.307 ms  0.855 ms  0.911 ms
 2  172.17.2.201 (172.17.2.201)  0.785 ms  0.677 ms  0.623 ms
 3  10.160.0.226 (10.160.0.226)  1.245 ms  1.181 ms  1.168 ms
 4  162.129.253.97 (162.129.253.97)  1.386 ms  1.434 ms  1.475 ms
 5  gi1-3.ccr01.bwi01.atlas.cogentco.com (38.104.12.5)  4.709 ms  4.506 ms
4.494 ms
 6  te4-2.ccr01.phl01.atlas.cogentco.com (154.54.2.174)  7.189 ms  7.394 ms
7.414 ms
 7  te8-2.mpd03.jfk02.atlas.cogentco.com (154.54.2.110)  9.701 ms  9.538 ms
9.690 ms
 8  te7-4.mpd01.jfk05.atlas.cogentco.com (154.54.3.98)  9.456 ms
te7-1.ccr04.jfk02.atlas.cogentco.com (154.54.24.134)  9.527 ms
te7-4.mpd01.jfk05.atlas.cogentco.com (154.54.3.98)  9.685 ms
 9  te8-4.ccr02.jfk05.atlas.cogentco.com (154.54.26.66)  9.731 ms
te1-1.ccr02.jfk05.atlas.cogentco.com (154.54.3.161)  9.898 ms
te2-1.ccr02.jfk05.atlas.cogentco.com (154.54.3.105)  9.844 ms
10  * * *
11  209.85.255.68 (209.85.255.68)  278.907 ms  276.794 ms *
12  209.85.251.9 (209.85.251.9)  298.127 ms *  297.635 ms
13  * * *
14  * * *
15  * 209.85.177.58 (209.85.177.58)  292.976 ms *



On 5/14/09 11:48 AM, "Steve Williams"  wrote:

> am seeing significant delays in getting to google.  anyone else seeing this?
> 
> $ traceroute www.google.com
> traceroute: Warning: www.google.com has multiple addresses; using
> 74.125.53.147
> traceroute to www.l.google.com (74.125.53.147), 30 hops max, 40 byte packets
>  1  cisco-190 (129.116.190.250)  0.430 ms  0.350 ms  0.353 ms
>  2  ser10-v758.gw.utexas.edu (128.83.10.29)  1.138 ms  1.099 ms  1.057 ms
>  3  ser2-gi1-9.gw.utexas.edu (128.83.10.2)  10.475 ms  1.174 ms  1.584 ms
>  4  aust-utnoc-core-ge-6-0-0-0.tx-bb.net (192.12.10.1)  1.215 ms  1.209
> ms  1.134 ms
>  5  te2-1--570.tr01-lsanca01.transitrail.net (137.164.131.221)  40.649
> ms  40.699 ms  40.678 ms
>  6  * * *
>  7  * * *
>  8  * * *
>  9  * * *
> 10  * * *
> 11  72.14.232.10 (72.14.232.10)  261.262 ms * *
> 12  * * pw-in-f147.google.com (74.125.53.147)  251.867 ms

Re: delays to google

[andrew]

Sessions time out or fail from AT&T Commercial, Verizon commercial,
Verizon FiOS, and AT&T 3G GSM, all from the East Coast.

However, routing from a shell at pair.com:

%traceroute mail.google.com
traceroute: Warning: mail.google.com has multiple addresses; using
74.125.53.17
traceroute to googlemail.l.google.com (74.125.53.17), 64 hops max, 40 byte
packets
 2  192.168.1.41 (192.168.1.41)  3.963 ms  1.456 ms  1.477 ms
 3  TenGigabitEthernet7-2.ar5.CHI1.gblx.net (207.138.112.145)  15.972 ms 
14.336 ms  14.268 ms
 4  po1-20G.ar3.CHI2.gblx.net (67.16.132.241)  14.563 ms  13.708 ms 
14.454 ms
 5  72.14.197.69 (72.14.197.69)  53.439 ms  13.862 ms  13.986 ms
 6  209.85.254.122 (209.85.254.122)  14.283 ms  14.322 ms  13.999 ms
 7  72.14.233.116 (72.14.233.116)  65.376 ms  65.557 ms  65.849 ms
 8  216.239.46.208 (216.239.46.208)  72.424 ms  72.163 ms  71.921 ms
 9  64.233.174.131 (64.233.174.131)  72.007 ms  71.711 ms
64.233.174.129 (64.233.174.129)  71.916 ms
10  72.14.232.6 (72.14.232.6)  82.512 ms  82.767 ms  71.942 ms
11  pw-in-f17.google.com (74.125.53.17)  71.432 ms  71.686 ms  71.938 ms

If I tunnel through, my connection behaves with reasonable crispness.

Cheers,

-Andrew

Re: delays to google

[Andrey Gordon]

Fine on Cogent in Boston

asa1-wcnt> traceroute www.google.com

Type escape sequence to abort.
Tracing the route to 64.233.161.147

 1  fa0-1.na01.b006523-1.bos01.atlas.cogentco.com (38.99.223.37) 0 msec 0
msec 10 msec
 2  gi1-36.3804.ccr02.bos01.atlas.cogentco.com (66.28.5.25) 0 msec 0 msec 0
msec
 3  te3-1.ccr04.jfk02.atlas.cogentco.com (154.54.6.10) 10 msec 10 msec 10
msec
 4  te7-4.ccr02.jfk05.atlas.cogentco.com (154.54.3.70) 0 msec 0 msec
te4-4.ccr02.jfk05.atlas.cogentco.com (154.54.7.10) 10 msec
 5  core1-0-0-8.lga.net.google.com (198.32.118.39) 10 msec 0 msec 10 msec
 6  209.85.255.68 10 msec 10 msec
72.14.238.232 10 msec
 7  209.85.249.11 20 msec
72.14.239.93 20 msec
209.85.249.11 10 msec
 8  64.233.175.219 10 msec 20 msec
64.233.175.111 10 msec
 9  216.239.49.214 30 msec 20 msec
216.239.48.190 20 msec
 10 www.l.google.com (64.233.161.147) 10 msec 10 msec 20 msec
asa1-wcnt>

-
Andrey Gordon [andrey.gor...@gmail.com]

Re: delays to google

[nevin]

$ traceroute www.google.com
traceroute to www.google.com (72.14.205.103), 30 hops max, 40 byte packets
 1  ge4-1.core.mpls.gippy.net (216.243.170.254)  1.285 ms  1.500 ms  1.451 ms
 2  209-240-78-33.static.iphouse.net (209.240.78.33)  1.418 ms  1.597 ms  1.887 
ms
 3  ge0-2-0.m20-2.mpls.iphouse.net (216.250.189.189)  0.879 ms  1.133 ms  1.125 
ms
 4  ge0-2-0.m20-1.mpls.iphouse.net (216.250.189.190)  1.076 ms  1.081 ms  1.079 
ms
 5  4.59.66.13 (4.59.66.13)  1.059 ms  1.251 ms  1.168 ms
 6  ae-11-11.car1.Minneapolis1.Level3.net (4.69.136.101)  55.587 ms  55.156 ms  
45.585 ms
 7  ae-4-4.ebr1.Chicago1.Level3.net (4.69.136.106)  9.725 ms  22.425 ms  21.340 
ms
 8  ae-2-2.ebr2.NewYork2.Level3.net (4.69.132.66)  29.637 ms  30.114 ms  30.330 
ms
 9  ae-6-6.ebr4.NewYork1.Level3.net (4.69.141.21)  43.328 ms  43.298 ms  43.226 
ms
10  ae-64-64.csw1.NewYork1.Level3.net (4.69.134.114)  30.466 ms 
ae-74-74.csw2.NewYork1.Level3.net (4.69.134.118)  32.182 ms 
ae-64-64.csw1.NewYork1.Level3.net (4.69.134.114)  30.421 ms
11  ae-3-89.edge1.NewYork1.Level3.net (4.68.16.142)  30.154 ms 
ae-2-79.edge1.NewYork1.Level3.net (4.68.16.78)  30.402 ms 
ae-3-89.edge1.NewYork1.Level3.net (4.68.16.142)  30.382 ms
12  * * *
13  * * 72.14.238.232 (72.14.238.232)  326.622 ms
14  72.14.233.113 (72.14.233.113)  329.033 ms 216.239.43.146 (216.239.43.146)  
332.014 ms  332.005 ms
15  66.249.94.90 (66.249.94.90)  331.205 ms * 66.249.94.92 (66.249.94.92)  
328.687 ms
16  * 72.14.236.138 (72.14.236.138)  333.385 ms 72.14.232.66 (72.14.232.66)  
367.110 ms
17  qb-in-f103.google.com (72.14.205.103)  329.104 ms  332.490 ms  328.249 ms

Same here.

-- Nevin Lyne
-- CTO
-- EngineHosting.com

Re: delays to google

[William McCall]

Seeing this on blackberry and Verizon business.

On 5/14/09, Steve Williams  wrote:
> am seeing significant delays in getting to google.  anyone else seeing this?
>
> $ traceroute www.google.com
> traceroute: Warning: www.google.com has multiple addresses; using
> 74.125.53.147
> traceroute to www.l.google.com (74.125.53.147), 30 hops max, 40 byte packets
>  1  cisco-190 (129.116.190.250)  0.430 ms  0.350 ms  0.353 ms
>  2  ser10-v758.gw.utexas.edu (128.83.10.29)  1.138 ms  1.099 ms  1.057 ms
>  3  ser2-gi1-9.gw.utexas.edu (128.83.10.2)  10.475 ms  1.174 ms  1.584 ms
>  4  aust-utnoc-core-ge-6-0-0-0.tx-bb.net (192.12.10.1)  1.215 ms  1.209
> ms  1.134 ms
>  5  te2-1--570.tr01-lsanca01.transitrail.net (137.164.131.221)  40.649
> ms  40.699 ms  40.678 ms
>  6  * * *
>  7  * * *
>  8  * * *
>  9  * * *
> 10  * * *
> 11  72.14.232.10 (72.14.232.10)  261.262 ms * *
> 12  * * pw-in-f147.google.com (74.125.53.147)  251.867 ms
>
> --
>
>
>  '''
> (O O)
>  ,-- oOO-(_)-OOo -,
>  |Stephen Williams|
>  |  Manager of Computer Services  |
>  |   Center for Space Research|
>  | University of Texas at Austin  |
>  | 3925 W. Braker Ln., Suite 200  |
>  |  Austin, TX 78759-5321 |
>  |512.471.7235  512.471.3570 (fax)|
>  |   willi...@csr.utexas.edu  |
>  | Oooo __|
> oooO   (   )
>(   )) /
> \ ((_/
>  \_)
>
>
>
>
>
>
>

-- 
Sent from my mobile device

RE: delays to google

[Crooks, Sam]

Also seeing this in Dallas, TX area, from AT&T and Verizon

> -Original Message-
> From: Mario Fernandez [mailto:ma...@fernandez.ca] 
> Sent: Thursday, May 14, 2009 10:53 AM
> To: Athanasios Douitsis
> Cc: na...@merit.edu
> Subject: Re: delays to google
> 
> Seeing the same thing from NY using NTT, we routed via Cogent 
> which does not seem to be having the problem.
> 
> On Thu, May 14, 2009 at 11:51 AM, Athanasios Douitsis 
> wrote:
> 
> > On Thu, May 14, 2009 at 6:48 PM, Steve Williams 
> >  > >wrote:
> >
> > > am seeing significant delays in getting to google.  anyone else 
> > > seeing this?
> > >
> > > $ traceroute www.google.com
> > > traceroute: Warning: www.google.com has multiple addresses; using
> > > 74.125.53.147
> > > traceroute to www.l.google.com (74.125.53.147), 30 hops 
> max, 40 byte 
> > > packets
> > > 1  cisco-190 (129.116.190.250)  0.430 ms  0.350 ms  0.353 ms
> > > 2  ser10-v758.gw.utexas.edu (128.83.10.29)  1.138 ms  1.099 ms  
> > > 1.057 ms
> > > 3  ser2-gi1-9.gw.utexas.edu (128.83.10.2)  10.475 ms  1.174 ms  
> > > 1.584 ms
> > > 4  aust-utnoc-core-ge-6-0-0-0.tx-bb.net (192.12.10.1)  1.215 ms  
> > > 1.209
> > ms
> > >  1.134 ms
> > > 5  te2-1--570.tr01-lsanca01.transitrail.net (137.164.131.221)  
> > > 40.649 ms
> > >  40.699 ms  40.678 ms
> > > 6  * * *
> > > 7  * * *
> > > 8  * * *
> > > 9  * * *
> > > 10  * * *
> > > 11  72.14.232.10 (72.14.232.10)  261.262 ms * *
> > > 12  * * pw-in-f147.google.com (74.125.53.147)  251.867 ms
> > >
> > > --
> > >
> > >
> > >'''
> > >   (O O)
> > > ,-- oOO-(_)-OOo -,
> > > |Stephen Williams|
> > > |  Manager of Computer Services  |
> > > |   Center for Space Research|
> > > | University of Texas at Austin  |
> > > | 3925 W. Braker Ln., Suite 200  |
> > > |  Austin, TX 78759-5321 |
> > > |512.471.7235  512.471.3570 (fax)|
> > > |   willi...@csr.utexas.edu  |
> > > | Oooo __|
> > >   oooO   (   )
> > >  (   )) /
> > >   \ ((_/
> > >\_)
> > >
> > > seeing this too.
> >
> 
> 
> 
> -- 
> 
> Sent from Boston, Massachusetts, United States Yogi Berra 
> <http://www.brainyquote.com/quotes/authors/y/yogi_berra.html> 
>  - "If you ask me anything I don't know, I'm not going to answer."
> 

Re: delays to google

[Eduardo Silvestre]

Hello,

Same issue in portugal and spain.

pt:~# traceroute www.google.com
traceroute: Warning: www.google.com has multiple addresses; using 209.85.227.147
traceroute to www.l.google.com (209.85.227.147), 30 hops max, 40 byte packets
 1  ge130-1000m.cr2.lisboa.nfsi.pt (81.92.200.126)  0.203 ms  0.085 ms  0.108 ms
 2  xe12-10GE.xmr1.Lisbon.as25137.net (81.92.201.10)  7.358 ms  0.349 ms  0.239 
ms
 3  if-3-2.core1.PV9-Lisbon.as6453.net (195.219.186.9)  0.235 ms  0.347 ms  
0.239 ms
 4  if-12-0-0.mcore3.L78-London.as6453.net (195.219.144.5)  26.974 ms  27.200 
ms  26.847 ms
 5  if-5-0-0.mcore3.LDN-London.as6453.net (195.219.195.9)  32.343 ms  32.452 ms 
 32.345 ms
 6  Vlan62.icore1.LDN-London.as6453.net (195.219.83.1)  39.464 ms  29.329 ms  
35.719 ms
 7  xe-10-2-0-edge3.london1.level3.net (4.68.63.105)  27.469 ms  27.456 ms  
27.474 ms
 8  ae-11-51.car1.London1.Level3.net (4.69.139.66)  27.596 ms 
ae-21-52.car1.London1.Level3.net (4.69.139.98)  85.304 ms 
ae-11-51.car1.London1.Level3.net (4.69.139.66)  36.955 ms
 9  * * *
10  * * *
11  * * *
12  * 72.14.236.191 (72.14.236.191)  389.644 ms *
13  * * 209.85.243.93 (209.85.243.93)  387.207 ms
14  * * wy-in-f147.google.com (209.85.227.147)  392.378 ms

es:~# traceroute www.google.com
traceroute to www.google.com (209.85.227.103), 30 hops max, 40 byte packets
 1  94.46.247.33 (94.46.247.33)  0.401 ms  0.448 ms  0.515 ms
 2  194.25.210.137 (194.25.210.137)  0.287 ms  0.297 ms  0.345 ms
 3  194.25.6.66 (194.25.6.66)  41.014 ms  33.308 ms  41.071 ms
 4  * * *
 5  * * 209.85.255.170 (209.85.255.170)  390.129 ms
 6  72.14.232.208 (72.14.232.208)  387.012 ms * *
 7  * 72.14.232.130 (72.14.232.130)  387.439 ms  386.662 ms
 8  * * 72.14.236.191 (72.14.236.191)  380.375 ms
 9  * * *
10  * * *
11  wy-in-f103.google.com (209.85.227.103)  382.547 ms  403.198 ms *

Regards,

---
Eduardo Silvestre
nfsi telecom, lda.

eduardo.silves...@nfsi.pt
Tel. (+351) 21 949 2300 - Fax (+351) 21 949 2301
http://www.nfsi.pt/

- Original Message -
From: "Athanasios Douitsis" 
To: "Steve Williams" 
Cc: na...@merit.edu
Sent: Thursday, May 14, 2009 4:51:38 PM GMT +00:00 GMT Britain, Ireland, 
Portugal
Subject: Re: delays to google

On Thu, May 14, 2009 at 6:48 PM, Steve Williams wrote:

> am seeing significant delays in getting to google.  anyone else seeing
> this?
>
> $ traceroute www.google.com
> traceroute: Warning: www.google.com has multiple addresses; using
> 74.125.53.147
> traceroute to www.l.google.com (74.125.53.147), 30 hops max, 40 byte
> packets
> 1  cisco-190 (129.116.190.250)  0.430 ms  0.350 ms  0.353 ms
> 2  ser10-v758.gw.utexas.edu (128.83.10.29)  1.138 ms  1.099 ms  1.057 ms
> 3  ser2-gi1-9.gw.utexas.edu (128.83.10.2)  10.475 ms  1.174 ms  1.584 ms
> 4  aust-utnoc-core-ge-6-0-0-0.tx-bb.net (192.12.10.1)  1.215 ms  1.209 ms
>  1.134 ms
> 5  te2-1--570.tr01-lsanca01.transitrail.net (137.164.131.221)  40.649 ms
>  40.699 ms  40.678 ms
> 6  * * *
> 7  * * *
> 8  * * *
> 9  * * *
> 10  * * *
> 11  72.14.232.10 (72.14.232.10)  261.262 ms * *
> 12  * * pw-in-f147.google.com (74.125.53.147)  251.867 ms
>
> --
>
>
>'''
>   (O O)
> ,-- oOO-(_)-OOo -,
> |Stephen Williams|
> |  Manager of Computer Services  |
> |   Center for Space Research|
> | University of Texas at Austin  |
> | 3925 W. Braker Ln., Suite 200  |
> |  Austin, TX 78759-5321 |
> |512.471.7235  512.471.3570 (fax)|
> |   willi...@csr.utexas.edu  |
> | Oooo __|
>   oooO   (   )
>  (   )) /
>   \ ((_/
>\_)
>
> seeing this too.

RE: delays to google

[Sachs, Marcus Hans (Marc)]

We are tracking it here:  http://isc.sans.org/diary.html?storyid=6388

Marc Sachs
Director, SANS Internet Storm Center 

-Original Message-
From: Steve Williams [mailto:willi...@csr.utexas.edu] 
Sent: Thursday, May 14, 2009 11:49 AM
To: na...@merit.edu
Subject: delays to google

am seeing significant delays in getting to google.  anyone else seeing this?

$ traceroute www.google.com
traceroute: Warning: www.google.com has multiple addresses; using 
74.125.53.147
traceroute to www.l.google.com (74.125.53.147), 30 hops max, 40 byte packets
 1  cisco-190 (129.116.190.250)  0.430 ms  0.350 ms  0.353 ms
 2  ser10-v758.gw.utexas.edu (128.83.10.29)  1.138 ms  1.099 ms  1.057 ms
 3  ser2-gi1-9.gw.utexas.edu (128.83.10.2)  10.475 ms  1.174 ms  1.584 ms
 4  aust-utnoc-core-ge-6-0-0-0.tx-bb.net (192.12.10.1)  1.215 ms  1.209 
ms  1.134 ms
 5  te2-1--570.tr01-lsanca01.transitrail.net (137.164.131.221)  40.649 
ms  40.699 ms  40.678 ms
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  72.14.232.10 (72.14.232.10)  261.262 ms * *
12  * * pw-in-f147.google.com (74.125.53.147)  251.867 ms

-- 


 '''
(O O)
 ,-- oOO-(_)-OOo -,
 |Stephen Williams|
 |  Manager of Computer Services  |
 |   Center for Space Research|
 | University of Texas at Austin  |
 | 3925 W. Braker Ln., Suite 200  |
 |  Austin, TX 78759-5321 |
 |512.471.7235  512.471.3570 (fax)|
 |   willi...@csr.utexas.edu  |
 | Oooo __|
oooO   (   )
   (   )) /
\ ((_/
 \_) 

Re: delays to google

[Brance Amussen]

We are. As well too NYTimes, Gmail, etc...

traceroute to www.nytimes.com (199.239.136.200), 64 hops max, 40 byte
packets
 1  128.220.29.1 (128.220.29.1)  1.222 ms  0.805 ms  1.170 ms
 2  172.17.2.201 (172.17.2.201)  0.894 ms  0.666 ms  0.650 ms
 3  10.160.0.226 (10.160.0.226)  1.311 ms  1.361 ms  1.120 ms
 4  162.129.253.97 (162.129.253.97)  1.485 ms  1.303 ms  1.312 ms
 5  206.196.178.142 (206.196.178.142)  11.428 ms  2.705 ms  2.576 ms
 6  45.78.120.65.in-addr.arpa (65.120.78.45)  3.602 ms  3.796 ms  3.677 ms
 7  nyc-core-01.inet.qwest.net (67.14.7.42)  8.801 ms  8.505 ms  8.304 ms
 8  nyc-edge-03.inet.qwest.net (205.171.217.26)  8.609 ms  8.527 ms  12.914
ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *

traceroute to googlemail.l.google.com (209.85.133.19), 64 hops max, 40 byte
packets
 1  128.220.29.1 (128.220.29.1)  1.307 ms  0.855 ms  0.911 ms
 2  172.17.2.201 (172.17.2.201)  0.785 ms  0.677 ms  0.623 ms
 3  10.160.0.226 (10.160.0.226)  1.245 ms  1.181 ms  1.168 ms
 4  162.129.253.97 (162.129.253.97)  1.386 ms  1.434 ms  1.475 ms
 5  gi1-3.ccr01.bwi01.atlas.cogentco.com (38.104.12.5)  4.709 ms  4.506 ms
4.494 ms
 6  te4-2.ccr01.phl01.atlas.cogentco.com (154.54.2.174)  7.189 ms  7.394 ms
7.414 ms
 7  te8-2.mpd03.jfk02.atlas.cogentco.com (154.54.2.110)  9.701 ms  9.538 ms
9.690 ms
 8  te7-4.mpd01.jfk05.atlas.cogentco.com (154.54.3.98)  9.456 ms
te7-1.ccr04.jfk02.atlas.cogentco.com (154.54.24.134)  9.527 ms
te7-4.mpd01.jfk05.atlas.cogentco.com (154.54.3.98)  9.685 ms
 9  te8-4.ccr02.jfk05.atlas.cogentco.com (154.54.26.66)  9.731 ms
te1-1.ccr02.jfk05.atlas.cogentco.com (154.54.3.161)  9.898 ms
te2-1.ccr02.jfk05.atlas.cogentco.com (154.54.3.105)  9.844 ms
10  * * *
11  209.85.255.68 (209.85.255.68)  278.907 ms  276.794 ms *
12  209.85.251.9 (209.85.251.9)  298.127 ms *  297.635 ms
13  * * *
14  * * *
15  * 209.85.177.58 (209.85.177.58)  292.976 ms *



On 5/14/09 11:48 AM, "Steve Williams"  wrote:

> am seeing significant delays in getting to google.  anyone else seeing this?
> 
> $ traceroute www.google.com
> traceroute: Warning: www.google.com has multiple addresses; using
> 74.125.53.147
> traceroute to www.l.google.com (74.125.53.147), 30 hops max, 40 byte packets
>  1  cisco-190 (129.116.190.250)  0.430 ms  0.350 ms  0.353 ms
>  2  ser10-v758.gw.utexas.edu (128.83.10.29)  1.138 ms  1.099 ms  1.057 ms
>  3  ser2-gi1-9.gw.utexas.edu (128.83.10.2)  10.475 ms  1.174 ms  1.584 ms
>  4  aust-utnoc-core-ge-6-0-0-0.tx-bb.net (192.12.10.1)  1.215 ms  1.209
> ms  1.134 ms
>  5  te2-1--570.tr01-lsanca01.transitrail.net (137.164.131.221)  40.649
> ms  40.699 ms  40.678 ms
>  6  * * *
>  7  * * *
>  8  * * *
>  9  * * *
> 10  * * *
> 11  72.14.232.10 (72.14.232.10)  261.262 ms * *
> 12  * * pw-in-f147.google.com (74.125.53.147)  251.867 ms

Re: delays to google

[Adam Kennedy]

Same here through AT&T (AS7018) and Level3 (AS7911).


On 5/14/09 11:48 AM, "Steve Williams"  wrote:

> am seeing significant delays in getting to google.  anyone else seeing this?
> 
> $ traceroute www.google.com
> traceroute: Warning: www.google.com has multiple addresses; using
> 74.125.53.147
> traceroute to www.l.google.com (74.125.53.147), 30 hops max, 40 byte packets
>  1  cisco-190 (129.116.190.250)  0.430 ms  0.350 ms  0.353 ms
>  2  ser10-v758.gw.utexas.edu (128.83.10.29)  1.138 ms  1.099 ms  1.057 ms
>  3  ser2-gi1-9.gw.utexas.edu (128.83.10.2)  10.475 ms  1.174 ms  1.584 ms
>  4  aust-utnoc-core-ge-6-0-0-0.tx-bb.net (192.12.10.1)  1.215 ms  1.209
> ms  1.134 ms
>  5  te2-1--570.tr01-lsanca01.transitrail.net (137.164.131.221)  40.649
> ms  40.699 ms  40.678 ms
>  6  * * *
>  7  * * *
>  8  * * *
>  9  * * *
> 10  * * *
> 11  72.14.232.10 (72.14.232.10)  261.262 ms * *
> 12  * * pw-in-f147.google.com (74.125.53.147)  251.867 ms

-- 
Adam Kennedy
Senior Network Administrator
Cyberlink Technologies, Inc.
Phone: 888-293-3693 x4352
Fax: 574-855-5761

Re: delays to google

[Mario Fernandez]

Seeing the same thing from NY using NTT, we routed via Cogent which does not
seem to be having the problem.

On Thu, May 14, 2009 at 11:51 AM, Athanasios Douitsis wrote:

> On Thu, May 14, 2009 at 6:48 PM, Steve Williams  >wrote:
>
> > am seeing significant delays in getting to google.  anyone else seeing
> > this?
> >
> > $ traceroute www.google.com
> > traceroute: Warning: www.google.com has multiple addresses; using
> > 74.125.53.147
> > traceroute to www.l.google.com (74.125.53.147), 30 hops max, 40 byte
> > packets
> > 1  cisco-190 (129.116.190.250)  0.430 ms  0.350 ms  0.353 ms
> > 2  ser10-v758.gw.utexas.edu (128.83.10.29)  1.138 ms  1.099 ms  1.057 ms
> > 3  ser2-gi1-9.gw.utexas.edu (128.83.10.2)  10.475 ms  1.174 ms  1.584 ms
> > 4  aust-utnoc-core-ge-6-0-0-0.tx-bb.net (192.12.10.1)  1.215 ms  1.209
> ms
> >  1.134 ms
> > 5  te2-1--570.tr01-lsanca01.transitrail.net (137.164.131.221)  40.649 ms
> >  40.699 ms  40.678 ms
> > 6  * * *
> > 7  * * *
> > 8  * * *
> > 9  * * *
> > 10  * * *
> > 11  72.14.232.10 (72.14.232.10)  261.262 ms * *
> > 12  * * pw-in-f147.google.com (74.125.53.147)  251.867 ms
> >
> > --
> >
> >
> >'''
> >   (O O)
> > ,-- oOO-(_)-OOo -,
> > |Stephen Williams|
> > |  Manager of Computer Services  |
> > |   Center for Space Research|
> > | University of Texas at Austin  |
> > | 3925 W. Braker Ln., Suite 200  |
> > |  Austin, TX 78759-5321 |
> > |512.471.7235  512.471.3570 (fax)|
> > |   willi...@csr.utexas.edu  |
> > | Oooo __|
> >   oooO   (   )
> >  (   )) /
> >   \ ((_/
> >\_)
> >
> > seeing this too.
>



-- 

Sent from Boston, Massachusetts, United States
Yogi Berra   -
"If you ask me anything I don't know, I'm not going to answer."

Re: delays to google

[Athanasios Douitsis]

On Thu, May 14, 2009 at 6:48 PM, Steve Williams wrote:

> am seeing significant delays in getting to google.  anyone else seeing
> this?
>
> $ traceroute www.google.com
> traceroute: Warning: www.google.com has multiple addresses; using
> 74.125.53.147
> traceroute to www.l.google.com (74.125.53.147), 30 hops max, 40 byte
> packets
> 1  cisco-190 (129.116.190.250)  0.430 ms  0.350 ms  0.353 ms
> 2  ser10-v758.gw.utexas.edu (128.83.10.29)  1.138 ms  1.099 ms  1.057 ms
> 3  ser2-gi1-9.gw.utexas.edu (128.83.10.2)  10.475 ms  1.174 ms  1.584 ms
> 4  aust-utnoc-core-ge-6-0-0-0.tx-bb.net (192.12.10.1)  1.215 ms  1.209 ms
>  1.134 ms
> 5  te2-1--570.tr01-lsanca01.transitrail.net (137.164.131.221)  40.649 ms
>  40.699 ms  40.678 ms
> 6  * * *
> 7  * * *
> 8  * * *
> 9  * * *
> 10  * * *
> 11  72.14.232.10 (72.14.232.10)  261.262 ms * *
> 12  * * pw-in-f147.google.com (74.125.53.147)  251.867 ms
>
> --
>
>
>'''
>   (O O)
> ,-- oOO-(_)-OOo -,
> |Stephen Williams|
> |  Manager of Computer Services  |
> |   Center for Space Research|
> | University of Texas at Austin  |
> | 3925 W. Braker Ln., Suite 200  |
> |  Austin, TX 78759-5321 |
> |512.471.7235  512.471.3570 (fax)|
> |   willi...@csr.utexas.edu  |
> | Oooo __|
>   oooO   (   )
>  (   )) /
>   \ ((_/
>\_)
>
> seeing this too.