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
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, andrew@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
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
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 beckman@angryox.com http://www.angryox.com/ ---------------------------------------------------------------------------
On 5/14/09, Peter Beckman <beckman@angryox.com> 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*
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, <andrew@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
-- Mikael Krantz MTS Konsult AB Mobil: 0735-245880
participants (6)
-
andrew＠arsenaleartisans.com -
Graeme Fowler -
Justin M. Streiner -
Matthew Petach -
mikael krantz -
Peter Beckman