> going to Frankfurt to get to Mountain view:
do not eat the wurst in the senator lounge
randy
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
> >
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
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 p
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.
Adam
>
>
> On May 14, 2009 12:44pm, "Mullins, Douglas" wrote:
>
>> conficker?
>>
>
>
>
>
>
> Doug
>>
>
>
>
>
>
>
>
>
> -Original Message-
>>
>
>
> From: Patrick Darden [mailto:dar...@armc.or
er?
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
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
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
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
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
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
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
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.7
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
> 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
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.
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.20
e -
> 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, St
> -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 S
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
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
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 googlema
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
$ 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
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.
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
>
> S
nt: 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
>
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 s
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
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
>
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
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.14
33 matches
Mail list logo
