outage

Fri Mar 23 21:44:03 UTC 2007

 I peer with google at a bunch of spots so I can't see anything, and
everything looks ok..

Looks like global crossing issue

route-server.phx1>trace 64.233.175.98

Type escape sequence to abort.
Tracing the route to 64.233.175.98

  1 ge4-1-0-226-1000M.ar4.PHX1.gblx.net (67.17.64.89) 0 msec 0 msec 0
msec
  2 so3-0-0-2488M.ar3.PAO2.gblx.net (67.17.94.97) 20 msec 16 msec 20
msec
  3  *  *  *
  4  *  *  *
  5  *  *  *
  6  *  *  *

|-----Original Message-----
|From: Baart, Jeff [mailto:JBaart at talk.com] 
|Sent: Friday, March 23, 2007 5:38 PM
|To: Koch, Christian; Jeff Baart; nanog at nanog.org
|Subject: RE: outage
|
|
|Out of the 3 IP's that have A records for google.com 
|
|The only one that fails for me is (although no domain names 
|will work in a browser - only IP's) 
|
|64.233.187.99 
|
|And only from our south east pops where we use Itc Deltacom 
|who uses Global Xing. 
|
|batman# traceroute 64.233.167.99
|traceroute to 64.233.167.99 (64.233.167.99), 64 hops max, 40 
|byte packets
| 1  216-83-236-225.wan.networktel.net (216.83.236.225)  0.621 
|ms  0.409 ms  0.610 ms
| 2  216-83-239-210.wan.networktel.net (216.83.239.210)  1.352 
|ms  0.664 ms  0.608 ms
| 3  66.0.120.241 (66.0.120.241)  13.981 ms  12.001 ms  14.121 ms
| 4  5-0-0-66.deltacom.net (66.0.0.5)  12.562 ms  12.167 ms  12.940 ms
| 5  so-0-0-0.ar3.DAL1.gblx.net (64.208.169.141)  31.458 ms  
|30.561 ms  30.846 ms
| 6  te2-1-10G.ar1.ATL2.gblx.net (67.17.108.5)  101.644 ms  
|218.952 ms  236.461 ms
| 7  te2-1-10G.ar1.ATL2.gblx.net (67.17.108.5)  115.021 ms  
|216.940 ms  228.338 ms
| 8  * * *
| 9  * * *
|10  64.233.175.98 (64.233.175.98)  63.708 ms  63.302 ms  62.690 ms
|11  72.14.232.53 (72.14.232.53)  64.534 ms  64.168 ms  65.736 ms
|12  64.233.175.42 (64.233.175.42)  64.796 ms 72.14.232.74 
|(72.14.232.74)  64.210 ms 64.233.175.42 (64.233.175.42)  69.647 ms
|
|13  py-in-f99.google.com (64.233.167.99)  65.109 ms  64.547 ms 
| 64.551 ms batman# traceroute 64.233.187.99 traceroute to 
|64.233.187.99 (64.233.187.99), 64 hops max, 40 byte packets
|
| 1  216-83-236-225.wan.networktel.net (216.83.236.225)  0.922 
|ms  3.517 ms  0.469 ms
| 2  216-83-239-210.wan.networktel.net (216.83.239.210)  0.461 
|ms  0.466 ms  0.984 ms
| 3  66.0.120.241 (66.0.120.241)  12.279 ms  12.472 ms  12.538 ms
| 4  5-0-0-66.deltacom.net (66.0.0.5)  11.984 ms  11.943 ms  14.339 ms
| 5  so-0-0-0.ar3.DAL1.gblx.net (64.208.169.141)  31.577 ms  
|31.821 ms  31.826 ms
| 6  te2-1-10G.ar1.ATL2.gblx.net (67.17.108.5)  69.674 ms  
|236.217 ms  247.271 ms
| 7  te2-1-10G.ar1.ATL2.gblx.net (67.17.108.5)  178.381 ms  
|217.020 ms  351.692 ms
| 8  * * * 
|
|
|
|
|From our Michigan POP's (where we use Level 3 and XO) - we 
|don't have the issues 
|
|
|--- JUNOS 6.4R1.6 built 2004-07-28 04:31:42 UTC 
|
|{master}
|jbaart at CR01-MELROSE01-M20> traceroute 64.233.187.99 traceroute 
|to 64.233.187.99 (64.233.187.99), 30 hops max, 40 byte packets
|
| 1  reverse.118.255.114.209.static.ldmi.com (209.114.255.118)  
|10.872 ms  201.010 ms  2.240 ms 
|     MPLS Label=21 CoS=0 TTL=1 S=1
| 2  core01-s8-1-1.cmh.oh.ldmi.net (209.114.255.242)  18.802 ms 
| 18.884 ms  18.563 ms
| 3  clevoh1wce1-atm4-0-0-1.wcg.net (65.77.88.73)  22.313 ms  
|24.840 ms  22.224 ms
| 4  clevoh1wce2-gige6-0.wcg.net (65.77.88.18)  22.529 ms  
|22.376 ms  22.541 ms
| 5  nycmny2wcx2-slot3-0.wcg.net (64.200.240.74)  35.196 ms  
|36.181 ms  35.552 ms
| 6  hrndva1wcx2-pos1-0-oc192.wcg.net (64.200.210.178)  87.901 
|ms  44.301 ms  230.123 ms
| 7  hrndva1wcx3-pos4-0-oc192.wcg.net (64.200.89.122)  41.598 
|ms  41.160 ms  41.119 ms
| 8  drvlga1wct1-atm12-0-0-4.wcg.net (64.200.123.49)  191.327 
|ms  53.669 ms  53.248 ms
| 9  atlnga6lce1-pos5-0.wcg.net (64.200.127.62)  53.045 ms  
|53.122 ms  52.845 ms 10  72.14.197.173 (72.14.197.173)  53.760 
|ms  54.118 ms  54.246 ms
|
|11  64.233.174.86 (64.233.174.86)  53.048 ms  53.701 ms  53.233 ms
|12  209.85.248.59 (209.85.248.59)  55.167 ms  63.872 ms 
|72.14.236.175 (72.14.236.175)  59.177 ms
|13  216.239.49.226 (216.239.49.226)  57.620 ms  57.030 ms  57.495 ms
|14  jc-in-f99.google.com (64.233.187.99)  54.470 ms  55.172 ms 
| 54.742 ms 
|
|
|
|And 
|
|
|Type escape sequence to abort. 
|Tracing the route to py-in-f99.google.com (64.233.167.99) 
|
|  1 core03-vlan100.dtw.mi.ldmi.net (209.114.255.34) 124 msec 
|184 msec 4 msec
|  2 t3-3-2-0.ar2.DET1.gblx.net (64.208.170.145) 8 msec 4 msec 8 msec
|  3 pos7-0-0-10G.ar2.CHI2.gblx.net (67.17.105.110) 8 msec 8 msec 8 msec
|  4 google-1.ar2.CHI2.gblx.net (64.215.195.178) 8 msec 4 msec 8 msec
|  5 216.239.46.1 8 msec 8 msec 8 msec
|  6 72.14.232.53 8 msec 
|    66.249.94.133 8 msec 20 msec
|  7 64.233.175.26 8 msec 
|    64.233.175.42 8 msec 8 msec
|  8 py-in-f99.google.com (64.233.167.99) 8 msec 8 msec 8 msec 
|
|
|
|
|-----Original Message-----
|From: Koch, Christian [mailto:ckoch at qualitytech.com]
|Sent: Friday, March 23, 2007 3:47 PM
|To: Jeff Baart; nanog at nanog.org
|Subject: RE: outage 
|
|Can you be more specific? 
|
|  
|
||-----Original Message-----
||From: owner-nanog at merit.edu [mailto:owner-nanog at merit.edu] On 
|Behalf Of 
||Jeff Baart
||Sent: Friday, March 23, 2007 4:41 PM
||To: nanog at nanog.org
||Subject: outage
|| 
||Anyone know if there is just some sort of Google hosting 
|outage ... or 
||if there is a larger Tier 1 issue going on this afternoon
|? 
|| 
|| 
|| 
||Thanks. 
|| 
|| 
|
|