[nsp-sec] Big packet loss to Google.com

Mike Tancsa mike at sentex.net
Thu May 14 12:22:21 EDT 2009 

At 11:31 AM 5/14/2009, Joel Rosenblatt wrote:
>----------- nsp-security Confidential --------
>
>Hi,
>
>We are seeing big packet loss trying to get to google.com
>
>
>Anyone else seeing problems?

A specific peer issue perhaps ? Here are traceroutes via TORIX, 
Cogent and TATA to the google IP you were going to.

% traceroute -q1 209.85.171.100
traceroute to 209.85.171.100 (209.85.171.100), 64 hops max, 40 byte packets
  1  quartz-fxp3 (199.212.134.17)  0.301 ms
  2  iolite4-vl21 (64.7.153.4)  0.658 ms
  3  torix-vl38-tor-hespler-v38 (205.211.165.118)  5.053 ms
  4  gw-google.torontointernetxchange.net (198.32.245.6)  6.335 ms
  5  216.239.47.114 (216.239.47.114)  7.997 ms
  6  209.85.250.111 (209.85.250.111)  23.416 ms
  7  72.14.233.116 (72.14.233.116)  81.553 ms
  8  209.85.248.129 (209.85.248.129)  76.325 ms
  9  216.239.46.208 (216.239.46.208)  88.006 ms
10  64.233.174.127 (64.233.174.127)  80.755 ms
11  209.85.251.153 (209.85.251.153)  90.364 ms
12  74.125.30.130 (74.125.30.130)  90.672 ms
13  cg-in-f100.google.com (209.85.171.100)  81.308 ms

% traceroute -s 38.104.158.78 -q1 209.85.171.100
traceroute to 209.85.171.100 (209.85.171.100) from 38.104.158.78, 64 
hops max, 40 byte packets
  1  te3-5.1068.mpd01.yyz02.atlas.cogentco.com (38.104.158.77)  0.587 ms
  2  te7-8.mpd01.ord01.atlas.cogentco.com (154.54.2.161)  15.601 ms
  3  te3-4.mpd01.ord03.atlas.cogentco.com (154.54.6.206)  46.251 ms
  4  google.ord03.atlas.cogentco.com (154.54.12.130)  15.663 ms
  5  209.85.254.120 (209.85.254.120)  15.650 ms
  6  72.14.233.116 (72.14.233.116)  74.864 ms
  7  72.14.239.12 (72.14.239.12)  75.352 ms
  8  64.233.174.127 (64.233.174.127)  79.341 ms
  9  209.85.251.129 (209.85.251.129)  79.854 ms
10  74.125.31.134 (74.125.31.134)  80.600 ms
11  cg-in-f100.google.com (209.85.171.100)  79.343 ms

% traceroute -q1 -s 209.58.16.22  209.85.171.100
traceroute to 209.85.171.100 (209.85.171.100) from 209.58.16.22, 64 
hops max, 40 byte packets
  1  209.58.16.21 (209.58.16.21)  6.813 ms
  2  if-14-0.core1.TNK-Toronto.as6453.net (216.6.122.49)  0.657 ms
  3  209.58.94.45 (209.58.94.45)  0.785 ms
  4  209.58.94.6 (209.58.94.6)  1.444 ms
  5  if-5-0.core1.CT8-Chicago.as6453.net (216.6.98.18)  12.274 ms
  6  sl-st20-chi-14-0-1.sprintlink.net (144.223.241.61)  11.934 ms
  7  sl-st30-chi-0-0-0-0.sprintlink.net (144.232.1.15)  12.949 ms
  8  sl-googl9-221388-0.sprintlink.net (144.223.35.94)  79.759 ms
  9  209.85.254.120 (209.85.254.120)  14.927 ms
10  72.14.233.116 (72.14.233.116)  73.631 ms
11  72.14.239.12 (72.14.239.12)  77.486 ms
12  209.85.250.146 (209.85.250.146)  79.756 ms
13  64.233.174.97 (64.233.174.97)  80.246 ms
14  74.125.30.6 (74.125.30.6)  94.240 ms
15  cg-in-f100.google.com (209.85.171.100)  81.869 ms


Going to one of the IPs inside google's network, looks ok as well via 
my torix link

% traceroute -q1 -Picmp 72.14.238.232
traceroute to 72.14.238.232 (72.14.238.232), 64 hops max, 60 byte packets
  1  quartz-fxp3 (199.212.134.17)  0.319 ms
  2  iolite4-vl21 (64.7.153.4)  0.459 ms
  3  torix-vl38-tor-hespler-v38 (205.211.165.118)  6.834 ms
  4  gw-google.torontointernetxchange.net (198.32.245.6)  8.018 ms
  5  216.239.47.114 (216.239.47.114)  6.768 ms
  6  72.14.238.232 (72.14.238.232)  25.102 ms


         ---Mike






>Thanks,
>Joel
>
>Tracing route to google.com [209.85.171.100]
>over a maximum of 30 hops:
>
>  1    <1 ms    <1 ms    <1 ms  wat-edge-1-vlan39-2.net.columbia.edu 
> [128.59.39.
>1]
>  2    <1 ms    <1 ms    <1 
> ms  cc-core-1-x-wat-edge-1.net.columbia.edu [128.59.
>255.109]
>  3    <1 ms    <1 ms    <1 
> ms  nyser32-gw-1-x-cc-core-1.net.columbia.edu [128.5
>9.255.6]
>  4    <1 ms    <1 ms    <1 ms  te3-4.mpd01.jfk01.atlas.cogentco.com 
> [38.104.188
>.249]
>  5    <1 ms    <1 ms    <1 ms  te2-1.ccr01.jfk02.atlas.cogentco.com 
> [154.54.1.2
>09]
>  6    <1 ms    <1 ms    <1 ms  te4-2.mpd01.jfk05.atlas.cogentco.com 
> [154.54.6.5
>0]
>  7    <1 ms    <1 ms    <1 ms  te2-1.ccr02.jfk05.atlas.cogentco.com 
> [154.54.3.1
>05]
>  8     *        *        *     Request timed out.
>  9     *      293 ms     *     72.14.238.232
>10   290 ms     *        *     72.14.239.93
>11     *      277 ms     *     209.85.242.208
>12     *        *        *     Request timed out.
>13     *        *      282 ms  64.233.174.127
>14     *        *      281 ms  64.233.174.127
>15   284 ms     *      287 ms  209.85.251.125
>16     *        *        *     Request timed out.
>17     *      293 ms     *     cg-in-f100.google.com [209.85.171.100]
>18   280 ms     *      285 ms  cg-in-f100.google.com [209.85.171.100]
>
>Trace complete.
>
>Joel Rosenblatt, Manager Network & Computer Security
>Columbia Information Security Office (CISO)
>Columbia University, 612 W 115th Street, NY, NY 10025 / 212 854 3033
>http://www.columbia.edu/~joel
>
>
>
>_______________________________________________
>nsp-security mailing list
>nsp-security at puck.nether.net
>https://puck.nether.net/mailman/listinfo/nsp-security
>
>Please do not Forward, CC, or BCC this E-mail outside of the nsp-security
>community. Confidentiality is essential for effective Internet 
>security counter-measures.
>_______________________________________________

More information about the nsp-security mailing list