I have been unable to reach http://www.wunderground.com/ from Mpls, Mn as well as from my colos in the Washington, Dallas and Seattle locations. (http://www.downforeveryoneorjustme.com/www.wunderground.com also reports it down) Saw one mention on Twitter of Level3 in SF dropping packets: * yeah, my route to @wunderground<http://twitter.com/#!/wunderground> is dropped by level3 in SF… great jorb* Anyone else having issues? Thanks in advance, -- *Colleen Velo email: cmvelo@gmail.com*
Down for me too: ... 8 ae-72-72.ebr2.SanJose1.Level3.net (4.69.153.21) 28.957 ms 32.084 ms 32.032 ms 9 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 32.950 ms 32.503 ms 32.449 ms 10 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 36.082 ms 33.274 ms 33.222 ms 11 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 14.432 ms 13.460 ms 13.413 ms 12 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 13.712 ms 18.466 ms 18.388 ms 13 * * * 14 * * * On Fri, Dec 30, 2011 at 11:04 PM, Colleen Velo <cmvelo@gmail.com> wrote:
I have been unable to reach http://www.wunderground.com/ from Mpls, Mn as well as from my colos in the Washington, Dallas and Seattle locations. (http://www.downforeveryoneorjustme.com/www.wunderground.com also reports it down)
Saw one mention on Twitter of Level3 in SF dropping packets: yeah, my route to @wunderground is dropped by level3 in SF… great jorb
Anyone else having issues?
Thanks in advance,
-- Colleen Velo email: cmvelo@gmail.com
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
On 12/30/11 11:04 PM, Colleen Velo wrote:
I have been unable to reach http://www.wunderground.com/ from Mpls, Mn as well as from my colos in the Washington, Dallas and Seattle locations. (http://www.downforeveryoneorjustme.com/www.wunderground.com also reports it down)
Works for me from Comcast - Petaluma CA $ traceroute www.wunderground.com traceroute to www.wunderground.com (38.102.136.104), 64 hops max, 40 byte packets 1 192.168.1.1 (192.168.1.1) 3.496 ms 1.013 ms 1.062 ms 2 24.5.160.1 (24.5.160.1) 37.398 ms 23.717 ms 30.258 ms 3 te-9-2-ur02.petaluma.ca.sfba.comcast.net (68.85.100.241) 10.996 ms 12.263 ms 15.252 ms 4 te-8-1-ur05.rohnertpr.ca.sfba.comcast.net (68.87.192.158) 13.671 ms 11.710 ms 12.359 ms 5 te-1-4-0-4-ar01.sfsutro.ca.sfba.comcast.net (68.87.226.234) 15.114 ms 16.949 ms 13.598 ms 6 pos-3-4-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.90.225) 16.594 ms 15.180 ms 14.296 ms 7 xe-11-1-0.edge1.SanJose1.Level3.net (4.79.43.133) 29.305 ms 46.102 ms 26.652 ms 8 vlan60.csw1.SanJose1.Level3.net (4.69.152.62) 15.159 ms 14.470 ms vlan80.csw3.SanJose1.Level3.net (4.69.152.190) 28.342 ms 9 ae-72-72.ebr2.SanJose1.Level3.net (4.69.153.21) 15.691 ms ae-92-92.ebr2.SanJose1.Level3.net (4.69.153.29) 15.805 ms 32.937 ms 10 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 21.573 ms 19.630 ms 18.488 ms 11 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 18.506 ms 16.519 ms 16.931 ms 12 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 57.588 ms 150.381 ms 204.704 ms 13 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 15.647 ms 17.682 ms 19.319 ms 14 38.102.136.100 (38.102.136.100) 18.395 ms 19.069 ms 18.835 ms 15 38.102.136.100 (38.102.136.100) 15.848 ms 17.318 ms 16.602 ms pepe-3:~ jay$ -- Jay Hennigan - CCIE #7880 - Network Engineering - jay@impulse.net Impulse Internet Service - http://www.impulse.net/ Your local telephone and internet company - 805 884-6323 - WB6RDV
Comcast SJC: Choking at that GLOBAL-INT router on CAR-3 in Comcast SFO. Must be the weather... -mike Sent from my iPhone On Dec 30, 2011, at 23:23, Jay Hennigan <jay@west.net> wrote:
On 12/30/11 11:04 PM, Colleen Velo wrote:
I have been unable to reach http://www.wunderground.com/ from Mpls, Mn as well as from my colos in the Washington, Dallas and Seattle locations. (http://www.downforeveryoneorjustme.com/www.wunderground.com also reports it down)
Works for me from Comcast - Petaluma CA
$ traceroute www.wunderground.com traceroute to www.wunderground.com (38.102.136.104), 64 hops max, 40 byte packets 1 192.168.1.1 (192.168.1.1) 3.496 ms 1.013 ms 1.062 ms 2 24.5.160.1 (24.5.160.1) 37.398 ms 23.717 ms 30.258 ms 3 te-9-2-ur02.petaluma.ca.sfba.comcast.net (68.85.100.241) 10.996 ms 12.263 ms 15.252 ms 4 te-8-1-ur05.rohnertpr.ca.sfba.comcast.net (68.87.192.158) 13.671 ms 11.710 ms 12.359 ms 5 te-1-4-0-4-ar01.sfsutro.ca.sfba.comcast.net (68.87.226.234) 15.114 ms 16.949 ms 13.598 ms 6 pos-3-4-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.90.225) 16.594 ms 15.180 ms 14.296 ms 7 xe-11-1-0.edge1.SanJose1.Level3.net (4.79.43.133) 29.305 ms 46.102 ms 26.652 ms 8 vlan60.csw1.SanJose1.Level3.net (4.69.152.62) 15.159 ms 14.470 ms vlan80.csw3.SanJose1.Level3.net (4.69.152.190) 28.342 ms 9 ae-72-72.ebr2.SanJose1.Level3.net (4.69.153.21) 15.691 ms ae-92-92.ebr2.SanJose1.Level3.net (4.69.153.29) 15.805 ms 32.937 ms 10 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 21.573 ms 19.630 ms 18.488 ms 11 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 18.506 ms 16.519 ms 16.931 ms 12 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 57.588 ms 150.381 ms 204.704 ms 13 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 15.647 ms 17.682 ms 19.319 ms 14 38.102.136.100 (38.102.136.100) 18.395 ms 19.069 ms 18.835 ms 15 38.102.136.100 (38.102.136.100) 15.848 ms 17.318 ms 16.602 ms pepe-3:~ jay$
-- Jay Hennigan - CCIE #7880 - Network Engineering - jay@impulse.net Impulse Internet Service - http://www.impulse.net/ Your local telephone and internet company - 805 884-6323 - WB6RDV _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
I am seeing dropped packets at GLOBAL-INTE.car1.SanFrancisco1.Level3.netwhen I try to do traceroutes from my colos in Washington, Seattle and Dallas: $: ~$ traceroute www.wunderground.com traceroute to www.wunderground.com (38.102.136.104), 30 hops max, 60 byte packets 1 184.173.141.49-static.reverse.softlayer.com (184.173.141.49) 0.994 ms 1.693 ms 2.014 ms 2 ae13.dar01.sr01.wdc01.networklayer.com (208.43.118.156) 0.285 ms 0.275 ms 0.252 ms 3 ae8.bbr02.eq01.wdc02.networklayer.com (173.192.18.192) 0.587 ms 0.595 ms 0.571 ms 4 xe-8-2-0.edge1.Washington4.Level3.net (4.53.112.25) 0.636 ms 0.660 ms 0.639 ms 5 vlan60.csw1.Washington1.Level3.net (4.69.149.62) 1.090 ms vlan70.csw2.Washington1.Level3.net (4.69.149.126) 1.125 ms vlan60.csw1.Washington1.Level3.net (4.69.149.62) 1.093 ms 6 ae-72-72.ebr2.Washington1.Level3.net (4.69.134.149) 1.124 ms ae-62-62.ebr2.Washington1.Level3.net (4.69.134.145) 1.463 ms 1.165 ms 7 ae-3-3.ebr1.NewYork2.Level3.net (4.69.132.90) 6.353 ms 6.486 ms 6.441 ms 8 ae-1-100.ebr2.NewYork2.Level3.net (4.69.135.254) 6.441 ms 6.508 ms 6.430 ms 9 ae-6-6.ebr2.NewYork1.Level3.net (4.69.141.21) 6.530 ms 6.331 ms 6.590 ms 10 ae-2-2.ebr4.SanJose1.Level3.net (4.69.135.185) 72.180 ms 73.800 ms 72.517 ms 11 ae-81-81.csw3.SanJose1.Level3.net (4.69.153.10) 72.535 ms ae-61-61.csw1.SanJose1.Level3.net (4.69.153.2) 72.903 ms 72.817 ms 12 ae-82-82.ebr2.SanJose1.Level3.net (4.69.153.25) 72.492 ms ae-92-92.ebr2.SanJose1.Level3.net (4.69.153.29) 72.544 ms ae-62-62.ebr2.SanJose1.Level3.net (4.69.153.17) 72.257 ms 13 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 73.282 ms 73.325 ms 104.650 ms 14 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 73.410 ms 72.917 ms 73.415 ms 15 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 73.523 ms 73.627 ms 73.638 ms 16 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 73.643 ms 73.868 ms 74.068 ms 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * $: /var/lib/tomcat6/logs/IB$ traceroute www.wunderground.com traceroute to www.wunderground.com (38.102.136.104), 30 hops max, 60 byte packets 1 173.192.157.225-static.reverse.softlayer.com (173.192.157.225) 0.442 ms 0.555 ms 0.629 ms 2 ae12.dar02.sr01.sea01.networklayer.com (67.228.118.226) 0.207 ms 0.225 ms 0.204 ms 3 ae9.bbr02.wb01.sea02.networklayer.com (173.192.18.184) 0.470 ms 0.452 ms 0.429 ms 4 te-3-2.car4.Seattle1.Level3.net (4.71.152.137) 0.646 ms 0.695 ms 0.695 ms 5 ae-31-51.ebr1.Seattle1.Level3.net (4.69.147.150) 5.545 ms 5.320 ms 5.483 ms 6 ae-7-7.ebr2.SanJose1.Level3.net (4.69.132.49) 17.946 ms 17.972 ms 18.171 ms 7 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 19.043 ms 19.064 ms 74.083 ms 8 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 19.066 ms 18.908 ms 19.118 ms 9 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 19.347 ms 19.200 ms 19.122 ms 10 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 19.678 ms 19.747 ms 19.537 ms 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * $ ~$ traceroute www.wunderground.com traceroute to www.wunderground.com (38.102.136.104), 30 hops max, 60 byte packets 1 sl-dal05-70-0-gw.sl.ibsys.com (173.192.70.1) 0.580 ms 0.653 ms 0.696 ms 2 ae0.dar02.sr01.dal05.networklayer.com (173.192.118.132) 0.241 ms 0.232 ms 0.213 ms 3 ae5.bbr02.eq01.dal03.networklayer.com (173.192.18.216) 0.791 ms 0.774 ms ae21.bbr01.eq01.dal03.networklayer.com (50.97.18.192) 0.779 ms 4 xe-11-0-3.edge2.Dallas3.Level3.net (4.59.36.93) 0.799 ms 0.827 ms xe-11-1-1.edge4.Dallas3.Level3.net (4.59.32.37) 0.806 ms 5 vlan60.csw1.Dallas1.Level3.net (4.69.145.62) 11.503 ms vlan70.csw2.Dallas1.Level3.net (4.69.145.126) 1.325 ms vlan80.csw3.Dallas1.Level3.net (4.69.145.190) 1.244 ms 6 ae-93-93.ebr3.Dallas1.Level3.net (4.69.151.170) 1.151 ms ae-63-63.ebr3.Dallas1.Level3.net (4.69.151.134) 1.374 ms ae-93-93.ebr3.Dallas1.Level3.net (4.69.151.170) 1.324 ms 7 ae-3-3.ebr2.LosAngeles1.Level3.net (4.69.132.77) 33.607 ms 33.633 ms 33.521 ms 8 ae-6-6.ebr2.SanJose5.Level3.net (4.69.148.202) 39.871 ms 39.849 ms 39.802 ms 9 ae-5-5.ebr4.SanJose1.Level3.net (4.69.148.142) 42.162 ms 42.090 ms 42.157 ms 10 ae-34-34.ebr2.SanJose1.Level3.net (4.69.153.33) 39.725 ms 39.908 ms 40.862 ms 11 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 43.597 ms 43.616 ms 43.848 ms 12 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 43.256 ms 43.369 ms 43.183 ms 13 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 40.229 ms 40.628 ms 40.404 ms 14 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 41.232 ms 41.401 ms 40.793 ms 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * On Sat, Dec 31, 2011 at 1:21 AM, Jay Hennigan <jay@west.net> wrote:
On 12/30/11 11:04 PM, Colleen Velo wrote:
I have been unable to reach http://www.wunderground.com/ from Mpls, Mn as well as from my colos in the Washington, Dallas and Seattle locations. (http://www.downforeveryoneorjustme.com/www.wunderground.com also reports it down)
Works for me from Comcast - Petaluma CA
$ traceroute www.wunderground.com traceroute to www.wunderground.com (38.102.136.104), 64 hops max, 40 byte packets 1 192.168.1.1 (192.168.1.1) 3.496 ms 1.013 ms 1.062 ms 2 24.5.160.1 (24.5.160.1) 37.398 ms 23.717 ms 30.258 ms 3 te-9-2-ur02.petaluma.ca.sfba.comcast.net (68.85.100.241) 10.996 ms 12.263 ms 15.252 ms 4 te-8-1-ur05.rohnertpr.ca.sfba.comcast.net (68.87.192.158) 13.671 ms 11.710 ms 12.359 ms 5 te-1-4-0-4-ar01.sfsutro.ca.sfba.comcast.net (68.87.226.234) 15.114 ms 16.949 ms 13.598 ms 6 pos-3-4-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.90.225) 16.594 ms 15.180 ms 14.296 ms 7 xe-11-1-0.edge1.SanJose1.Level3.net (4.79.43.133) 29.305 ms 46.102 ms 26.652 ms 8 vlan60.csw1.SanJose1.Level3.net (4.69.152.62) 15.159 ms 14.470 ms vlan80.csw3.SanJose1.Level3.net (4.69.152.190) 28.342 ms 9 ae-72-72.ebr2.SanJose1.Level3.net (4.69.153.21) 15.691 ms ae-92-92.ebr2.SanJose1.Level3.net (4.69.153.29) 15.805 ms 32.937 ms 10 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 21.573 ms 19.630 ms 18.488 ms 11 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 18.506 ms 16.519 ms 16.931 ms 12 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 57.588 ms 150.381 ms 204.704 ms 13 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 15.647 ms 17.682 ms 19.319 ms 14 38.102.136.100 (38.102.136.100) 18.395 ms 19.069 ms 18.835 ms 15 38.102.136.100 (38.102.136.100) 15.848 ms 17.318 ms 16.602 ms pepe-3:~ jay$
-- Jay Hennigan - CCIE #7880 - Network Engineering - jay@impulse.net Impulse Internet Service - http://www.impulse.net/ Your local telephone and internet company - 805 884-6323 - WB6RDV _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- *Colleen Velo email: cmvelo@gmail.com*
Interesting. Note that we are going through the same router before I stop getting responses. 4.53.128.234 - GLOBAL-INTE.car1.SanFrancisco1.Level3.net 9 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 23.765 ms 28.404 ms 28.320 ms 10 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 25.725 ms 23.918 ms 23.803 ms 11 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 16.766 ms 16.664 ms 14.278 ms 12 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 187.296 ms 187.268 ms 125.660 ms 13 * * * 14 * * * On Fri, Dec 30, 2011 at 11:21 PM, Jay Hennigan <jay@west.net> wrote:
On 12/30/11 11:04 PM, Colleen Velo wrote:
I have been unable to reach http://www.wunderground.com/ from Mpls, Mn as well as from my colos in the Washington, Dallas and Seattle locations. (http://www.downforeveryoneorjustme.com/www.wunderground.com also reports it down)
Works for me from Comcast - Petaluma CA
$ traceroute www.wunderground.com traceroute to www.wunderground.com (38.102.136.104), 64 hops max, 40 byte packets 1 192.168.1.1 (192.168.1.1) 3.496 ms 1.013 ms 1.062 ms 2 24.5.160.1 (24.5.160.1) 37.398 ms 23.717 ms 30.258 ms 3 te-9-2-ur02.petaluma.ca.sfba.comcast.net (68.85.100.241) 10.996 ms 12.263 ms 15.252 ms 4 te-8-1-ur05.rohnertpr.ca.sfba.comcast.net (68.87.192.158) 13.671 ms 11.710 ms 12.359 ms 5 te-1-4-0-4-ar01.sfsutro.ca.sfba.comcast.net (68.87.226.234) 15.114 ms 16.949 ms 13.598 ms 6 pos-3-4-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.90.225) 16.594 ms 15.180 ms 14.296 ms 7 xe-11-1-0.edge1.SanJose1.Level3.net (4.79.43.133) 29.305 ms 46.102 ms 26.652 ms 8 vlan60.csw1.SanJose1.Level3.net (4.69.152.62) 15.159 ms 14.470 ms vlan80.csw3.SanJose1.Level3.net (4.69.152.190) 28.342 ms 9 ae-72-72.ebr2.SanJose1.Level3.net (4.69.153.21) 15.691 ms ae-92-92.ebr2.SanJose1.Level3.net (4.69.153.29) 15.805 ms 32.937 ms 10 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 21.573 ms 19.630 ms 18.488 ms 11 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 18.506 ms 16.519 ms 16.931 ms 12 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 57.588 ms 150.381 ms 204.704 ms 13 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 15.647 ms 17.682 ms 19.319 ms 14 38.102.136.100 (38.102.136.100) 18.395 ms 19.069 ms 18.835 ms 15 38.102.136.100 (38.102.136.100) 15.848 ms 17.318 ms 16.602 ms pepe-3:~ jay$
-- Jay Hennigan - CCIE #7880 - Network Engineering - jay@impulse.net Impulse Internet Service - http://www.impulse.net/ Your local telephone and internet company - 805 884-6323 - WB6RDV _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
fyi: Official word from Wunderground's Twitter feed (50 mins ago): wunderground <http://twitter.com/#!/wunderground> Weather Underground As some of you have noticed, we are experiencing a network problem and are working to resolve the issue. Apologies for any inconvenience. On Sat, Dec 31, 2011 at 1:29 AM, Krassimir Tzvetanov <maillists@krassi.biz>wrote:
Interesting. Note that we are going through the same router before I stop getting responses. 4.53.128.234 - GLOBAL-INTE.car1.SanFrancisco1.Level3.net
9 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 23.765 ms 28.404 ms 28.320 ms 10 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 25.725 ms 23.918 ms 23.803 ms 11 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 16.766 ms 16.664 ms 14.278 ms 12 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 187.296 ms 187.268 ms 125.660 ms 13 * * * 14 * * *
On Fri, Dec 30, 2011 at 11:21 PM, Jay Hennigan <jay@west.net> wrote:
On 12/30/11 11:04 PM, Colleen Velo wrote:
I have been unable to reach http://www.wunderground.com/ from Mpls, Mn as well as from my colos in the Washington, Dallas and Seattle locations. (http://www.downforeveryoneorjustme.com/www.wunderground.com also reports it down)
Works for me from Comcast - Petaluma CA
$ traceroute www.wunderground.com traceroute to www.wunderground.com (38.102.136.104), 64 hops max, 40 byte packets 1 192.168.1.1 (192.168.1.1) 3.496 ms 1.013 ms 1.062 ms 2 24.5.160.1 (24.5.160.1) 37.398 ms 23.717 ms 30.258 ms 3 te-9-2-ur02.petaluma.ca.sfba.comcast.net (68.85.100.241) 10.996 ms 12.263 ms 15.252 ms 4 te-8-1-ur05.rohnertpr.ca.sfba.comcast.net (68.87.192.158) 13.671 ms 11.710 ms 12.359 ms 5 te-1-4-0-4-ar01.sfsutro.ca.sfba.comcast.net (68.87.226.234) 15.114 ms 16.949 ms 13.598 ms 6 pos-3-4-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.90.225) 16.594 ms 15.180 ms 14.296 ms 7 xe-11-1-0.edge1.SanJose1.Level3.net (4.79.43.133) 29.305 ms 46.102 ms 26.652 ms 8 vlan60.csw1.SanJose1.Level3.net (4.69.152.62) 15.159 ms 14.470 ms vlan80.csw3.SanJose1.Level3.net (4.69.152.190) 28.342 ms 9 ae-72-72.ebr2.SanJose1.Level3.net (4.69.153.21) 15.691 ms ae-92-92.ebr2.SanJose1.Level3.net (4.69.153.29) 15.805 ms 32.937 ms 10 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 21.573 ms 19.630 ms 18.488 ms 11 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 18.506 ms 16.519 ms 16.931 ms 12 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 57.588 ms 150.381 ms 204.704 ms 13 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 15.647 ms 17.682 ms 19.319 ms 14 38.102.136.100 (38.102.136.100) 18.395 ms 19.069 ms 18.835 ms 15 38.102.136.100 (38.102.136.100) 15.848 ms 17.318 ms 16.602 ms pepe-3:~ jay$
-- Jay Hennigan - CCIE #7880 - Network Engineering - jay@impulse.net Impulse Internet Service - http://www.impulse.net/ Your local telephone and internet company - 805 884-6323 - WB6RDV _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- *Colleen Velo email: cmvelo@gmail.com*
Same here: nagios:/home/fbulk# tcptraceroute www.wunderground.com Selected device eth0.3, address 96.31.0.5, port 49309 for outgoing packets Tracing the path to www.wunderground.com (38.102.136.104) on TCP port 80 (www), 30 hops max 1 router-core-inside.mtcnet.net (96.31.0.254) 0.220 ms 0.189 ms 0.193 ms 2 sxct.movl.mtcnet.net (167.142.156.194) 0.184 ms 0.137 ms 0.129 ms 3 siouxcenter.movl.153.netins.net (167.142.180.153) 2.032 ms 1.921 ms 1.932 ms 4 ins-kb1-te-13-2-220.kmrr.netins.net (167.142.64.253) 6.595 ms 6.929 ms 6.573 ms 5 ins-kc2-et-8-3.kmrr.netins.net (167.142.67.37) 8.077 ms 8.091 ms 8.062 ms 6 ins-dc1-et-8-1.desm.netins.net (167.142.67.29) 8.201 ms 8.152 ms 8.111 ms 7 te-3-3.car2.KansasCity1.Level3.net (4.53.34.113) 14.309 ms 14.305 ms 14.299 ms 8 ae-4-4.ebr2.Denver1.Level3.net (4.69.135.238) 26.934 ms 26.901 ms 26.881 ms 9 ae-1-100.ebr1.Denver1.Level3.net (4.69.151.181) 26.888 ms 26.962 ms 26.947 ms 10 ae-3-3.ebr2.SanJose1.Level3.net (4.69.132.57) 52.187 ms 52.168 ms 52.208 ms 11 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 61.726 ms 53.280 ms 53.301 ms 12 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 72.035 ms 53.173 ms 53.175 ms 13 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 53.598 ms 53.583 ms 53.595 ms 14 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 54.026 ms 54.121 ms 54.008 ms 15 * * From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Colleen Velo Sent: Saturday, December 31, 2011 1:04 AM To: outages@outages.org Subject: [outages] Wunderground down for anyone else? I have been unable to reach http://www.wunderground.com/ from Mpls, Mn as well as from my colos in the Washington, Dallas and Seattle locations. (http://www.downforeveryoneorjustme.com/www.wunderground.com also reports it down) Saw one mention on Twitter of Level3 in SF dropping packets: yeah, my route to <http://twitter.com/#!/wunderground> @wunderground is dropped by level3 in SF. great jorb Anyone else having issues? Thanks in advance, -- Colleen Velo email: cmvelo@gmail.com
fyi: Wunderground appears to be back online: $: /var/lib/tomcat6/logs/IB$ traceroute www.wunderground.com traceroute to www.wunderground.com (38.102.136.104), 30 hops max, 60 byte packets 1 173.192.157.225-static.reverse.softlayer.com (173.192.157.225) 0.400 ms 0.461 ms 0.511 ms 2 ae12.dar02.sr01.sea01.networklayer.com (67.228.118.226) 7.270 ms 7.245 ms 7.251 ms 3 ae9.bbr02.wb01.sea02.networklayer.com (173.192.18.184) 0.453 ms 0.433 ms 0.451 ms 4 te-3-2.car4.Seattle1.Level3.net (4.71.152.137) 0.622 ms 0.675 ms 0.712 ms 5 ae-31-51.ebr1.Seattle1.Level3.net (4.69.147.150) 3.827 ms 3.812 ms 3.923 ms 6 ae-7-7.ebr2.SanJose1.Level3.net (4.69.132.49) 17.959 ms 18.077 ms 18.068 ms 7 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 18.864 ms 19.038 ms 18.770 ms 8 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 18.995 ms 18.907 ms 18.778 ms 9 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 19.151 ms 19.201 ms 18.863 ms 10 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 19.775 ms 19.827 ms 19.906 ms 11 38.102.136.100 (38.102.136.100) 19.440 ms 19.447 ms 19.352 ms 12 38.102.136.100 (38.102.136.100) 19.479 ms 19.557 ms 19.503 ms On Sat, Dec 31, 2011 at 7:50 AM, Frank Bulk <frnkblk@iname.com> wrote:
Same here:****
** **
nagios:/home/fbulk# tcptraceroute www.wunderground.com****
Selected device eth0.3, address 96.31.0.5, port 49309 for outgoing packets ****
Tracing the path to www.wunderground.com (38.102.136.104) on TCP port 80 (www), 30 hops max****
1 router-core-inside.mtcnet.net (96.31.0.254) 0.220 ms 0.189 ms 0.193 ms****
2 sxct.movl.mtcnet.net (167.142.156.194) 0.184 ms 0.137 ms 0.129 ms*** *
3 siouxcenter.movl.153.netins.net (167.142.180.153) 2.032 ms 1.921 ms 1.932 ms****
4 ins-kb1-te-13-2-220.kmrr.netins.net (167.142.64.253) 6.595 ms 6.929 ms 6.573 ms****
5 ins-kc2-et-8-3.kmrr.netins.net (167.142.67.37) 8.077 ms 8.091 ms 8.062 ms****
6 ins-dc1-et-8-1.desm.netins.net (167.142.67.29) 8.201 ms 8.152 ms 8.111 ms****
7 te-3-3.car2.KansasCity1.Level3.net (4.53.34.113) 14.309 ms 14.305 ms 14.299 ms****
8 ae-4-4.ebr2.Denver1.Level3.net (4.69.135.238) 26.934 ms 26.901 ms 26.881 ms****
9 ae-1-100.ebr1.Denver1.Level3.net (4.69.151.181) 26.888 ms 26.962 ms 26.947 ms****
10 ae-3-3.ebr2.SanJose1.Level3.net (4.69.132.57) 52.187 ms 52.168 ms 52.208 ms****
11 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 61.726 ms 53.280 ms 53.301 ms****
12 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 72.035 ms 53.173 ms 53.175 ms****
13 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 53.598 ms 53.583 ms 53.595 ms****
14 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 54.026 ms 54.121 ms 54.008 ms****
15 * *****
** **
*From:* outages-bounces@outages.org [mailto:outages-bounces@outages.org] *On Behalf Of *Colleen Velo *Sent:* Saturday, December 31, 2011 1:04 AM *To:* outages@outages.org *Subject:* [outages] Wunderground down for anyone else?****
** **
I have been unable to reach http://www.wunderground.com/ from Mpls, Mn as well as from my colos in the Washington, Dallas and Seattle locations.****
(http://www.downforeveryoneorjustme.com/www.wunderground.com also reports it down) ****
** **
Saw one mention on Twitter of Level3 in SF dropping packets:****
* yeah, my route to @wunderground<http://twitter.com/#!/wunderground> is dropped by level3 in SF… great jorb*****
** **
Anyone else having issues?****
** **
Thanks in advance,****
** **
-- *Colleen Velo email: cmvelo@gmail.com*****
-- *Colleen Velo email: cmvelo@gmail.com*
yes, fine for UK as well, raining in manchester by the way :) mx5:~ colinj$ traceroute wunderground.com traceroute to wunderground.com (38.102.136.104), 64 hops max, 40 byte packets 1 192.168.1.2 (192.168.1.2) 1.445 ms 0.926 ms 0.928 ms 2 par8.the1.hso.uk.com (217.196.224.63) 15.916 ms 15.763 ms 15.887 ms 3 89.248.31.242 (89.248.31.242) 24.045 ms 22.486 ms 24.827 ms 4 eth-1-2-pcr2.the1.hso.uk.com (89.248.31.66) 16.292 ms 26.165 ms 24.314 ms 5 ge-0-0-0.643.pgr1.the1.hso.uk.com (89.248.31.90) 15.240 ms 17.064 ms 17.926 ms 6 10.0.10.253 (10.0.10.253) 15.573 ms 16.778 ms 15.256 ms 7 vl443.mpd01.lon01.atlas.cogentco.com (149.6.184.93) 16.264 ms 15.476 ms 16.397 ms 8 te3-2.ccr01.lon01.atlas.cogentco.com (130.117.1.73) 17.043 ms te1-8.ccr01.lon01.atlas.cogentco.com (130.117.3.226) 16.863 ms te3-2.ccr01.lon01.atlas.cogentco.com (130.117.1.73) 16.671 ms 9 te0-1-0-4.ccr21.lon13.atlas.cogentco.com (154.54.57.106) 114.251 ms 113.770 ms 113.818 ms 10 te0-1-0-4.ccr21.bos01.atlas.cogentco.com (154.54.1.93) 113.213 ms te0-0-0-4.ccr21.bos01.atlas.cogentco.com (154.54.5.161) 113.084 ms te0-1-0-4.ccr21.bos01.atlas.cogentco.com (154.54.1.93) 114.004 ms 11 te0-5-0-5.mpd22.ord01.atlas.cogentco.com (154.54.42.249) 113.367 ms te0-1-0-7.mpd21.ord01.atlas.cogentco.com (154.54.43.177) 113.050 ms te0-4-0-7.mpd22.ord01.atlas.cogentco.com (154.54.43.189) 114.308 ms 12 te0-4-0-0.mpd21.mci01.atlas.cogentco.com (154.54.30.170) 125.348 ms te0-3-0-1.mpd21.mci01.atlas.cogentco.com (154.54.7.138) 126.565 ms te0-1-0-2.mpd22.mci01.atlas.cogentco.com (154.54.3.202) 125.450 ms 13 te0-0-0-2.mpd22.sfo01.atlas.cogentco.com (154.54.6.34) 161.894 ms te0-1-0-3.mpd21.sfo01.atlas.cogentco.com (154.54.2.210) 163.074 ms te0-0-0-2.mpd21.sfo01.atlas.cogentco.com (154.54.6.38) 162.378 ms 14 te4-4.mpd01.sfo02.atlas.cogentco.com (154.54.3.130) 163.198 ms 162.411 ms te4-2.mpd01.sfo02.atlas.cogentco.com (154.54.3.122) 163.134 ms 15 38.104.130.34 (38.104.130.34) 163.917 ms 162.637 ms 163.118 ms 16 38.102.136.100 (38.102.136.100) 162.169 ms 162.446 ms 163.073 ms 17 38.102.136.100 (38.102.136.100) 162.348 ms 165.737 ms 162.418 ms Colin On 31 Dec 2011, at 14:15, Colleen Velo wrote:
fyi: Wunderground appears to be back online:
$: /var/lib/tomcat6/logs/IB$ traceroute www.wunderground.com traceroute to www.wunderground.com (38.102.136.104), 30 hops max, 60 byte packets 1 173.192.157.225-static.reverse.softlayer.com (173.192.157.225) 0.400 ms 0.461 ms 0.511 ms 2 ae12.dar02.sr01.sea01.networklayer.com (67.228.118.226) 7.270 ms 7.245 ms 7.251 ms 3 ae9.bbr02.wb01.sea02.networklayer.com (173.192.18.184) 0.453 ms 0.433 ms 0.451 ms 4 te-3-2.car4.Seattle1.Level3.net (4.71.152.137) 0.622 ms 0.675 ms 0.712 ms 5 ae-31-51.ebr1.Seattle1.Level3.net (4.69.147.150) 3.827 ms 3.812 ms 3.923 ms 6 ae-7-7.ebr2.SanJose1.Level3.net (4.69.132.49) 17.959 ms 18.077 ms 18.068 ms 7 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 18.864 ms 19.038 ms 18.770 ms 8 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 18.995 ms 18.907 ms 18.778 ms 9 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 19.151 ms 19.201 ms 18.863 ms 10 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 19.775 ms 19.827 ms 19.906 ms 11 38.102.136.100 (38.102.136.100) 19.440 ms 19.447 ms 19.352 ms 12 38.102.136.100 (38.102.136.100) 19.479 ms 19.557 ms 19.503 ms
On Sat, Dec 31, 2011 at 7:50 AM, Frank Bulk <frnkblk@iname.com> wrote: Same here:
nagios:/home/fbulk# tcptraceroute www.wunderground.com
Selected device eth0.3, address 96.31.0.5, port 49309 for outgoing packets
Tracing the path to www.wunderground.com (38.102.136.104) on TCP port 80 (www), 30 hops max
1 router-core-inside.mtcnet.net (96.31.0.254) 0.220 ms 0.189 ms 0.193 ms
2 sxct.movl.mtcnet.net (167.142.156.194) 0.184 ms 0.137 ms 0.129 ms
3 siouxcenter.movl.153.netins.net (167.142.180.153) 2.032 ms 1.921 ms 1.932 ms
4 ins-kb1-te-13-2-220.kmrr.netins.net (167.142.64.253) 6.595 ms 6.929 ms 6.573 ms
5 ins-kc2-et-8-3.kmrr.netins.net (167.142.67.37) 8.077 ms 8.091 ms 8.062 ms
6 ins-dc1-et-8-1.desm.netins.net (167.142.67.29) 8.201 ms 8.152 ms 8.111 ms
7 te-3-3.car2.KansasCity1.Level3.net (4.53.34.113) 14.309 ms 14.305 ms 14.299 ms
8 ae-4-4.ebr2.Denver1.Level3.net (4.69.135.238) 26.934 ms 26.901 ms 26.881 ms
9 ae-1-100.ebr1.Denver1.Level3.net (4.69.151.181) 26.888 ms 26.962 ms 26.947 ms
10 ae-3-3.ebr2.SanJose1.Level3.net (4.69.132.57) 52.187 ms 52.168 ms 52.208 ms
11 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 61.726 ms 53.280 ms 53.301 ms
12 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 72.035 ms 53.173 ms 53.175 ms
13 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 53.598 ms 53.583 ms 53.595 ms
14 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 54.026 ms 54.121 ms 54.008 ms
15 * *
From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Colleen Velo Sent: Saturday, December 31, 2011 1:04 AM To: outages@outages.org Subject: [outages] Wunderground down for anyone else?
I have been unable to reach http://www.wunderground.com/ from Mpls, Mn as well as from my colos in the Washington, Dallas and Seattle locations.
(http://www.downforeveryoneorjustme.com/www.wunderground.com also reports it down)
Saw one mention on Twitter of Level3 in SF dropping packets:
yeah, my route to @wunderground is dropped by level3 in SF… great jorb
Anyone else having issues?
Thanks in advance,
-- Colleen Velo email: cmvelo@gmail.com
-- Colleen Velo email: cmvelo@gmail.com _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Confirmed from here in the Midwest, too. nagios:/home/fbulk# tcptraceroute www.wunderground.com Selected device eth0.3, address 96.31.0.5, port 44816 for outgoing packets Tracing the path to www.wunderground.com (38.102.136.104) on TCP port 80 (www), 30 hops max 1 router-core-inside.mtcnet.net (96.31.0.254) 0.216 ms 0.181 ms 0.191 ms 2 sxct.movl.mtcnet.net (167.142.156.194) 0.184 ms 0.134 ms 0.125 ms 3 siouxcenter.movl.153.netins.net (167.142.180.153) 2.012 ms 1.926 ms 1.921 ms 4 ins-kb1-te-13-2-220.kmrr.netins.net (167.142.64.253) 6.533 ms 6.434 ms 6.456 ms 5 ins-kc2-et-8-3.kmrr.netins.net (167.142.67.37) 8.162 ms 8.098 ms 8.075 ms 6 ins-dc1-et-8-1.desm.netins.net (167.142.67.29) 8.142 ms 8.161 ms 8.075 ms 7 te-3-3.car2.KansasCity1.Level3.net (4.53.34.113) 14.285 ms 15.358 ms 14.361 ms 8 ae-4-4.ebr2.Denver1.Level3.net (4.69.135.238) 26.991 ms 26.923 ms 26.917 ms 9 ae-1-100.ebr1.Denver1.Level3.net (4.69.151.181) 27.013 ms 26.995 ms 26.902 ms 10 ae-3-3.ebr2.SanJose1.Level3.net (4.69.132.57) 52.141 ms 52.084 ms 52.083 ms 11 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 53.251 ms 53.376 ms 53.244 ms 12 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 53.143 ms 53.129 ms 53.079 ms 13 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 115.776 ms 88.438 ms 68.525 ms 14 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 54.070 ms 53.940 ms 53.996 ms 15 38.102.136.104 [open] 53.630 ms 53.629 ms 53.741 ms nagios:/home/fbulk# Frank From: Colleen Velo [mailto:cmvelo@gmail.com] Sent: Saturday, December 31, 2011 8:15 AM To: Frank Bulk Cc: outages@outages.org Subject: Re: [outages] Wunderground down for anyone else? fyi: Wunderground appears to be back online: $: /var/lib/tomcat6/logs/IB$ traceroute www.wunderground.com traceroute to www.wunderground.com (38.102.136.104), 30 hops max, 60 byte packets 1 173.192.157.225-static.reverse.softlayer.com (173.192.157.225) 0.400 ms 0.461 ms 0.511 ms 2 ae12.dar02.sr01.sea01.networklayer.com (67.228.118.226) 7.270 ms 7.245 ms 7.251 ms 3 ae9.bbr02.wb01.sea02.networklayer.com (173.192.18.184) 0.453 ms 0.433 ms 0.451 ms 4 te-3-2.car4.Seattle1.Level3.net (4.71.152.137) 0.622 ms 0.675 ms 0.712 ms 5 ae-31-51.ebr1.Seattle1.Level3.net (4.69.147.150) 3.827 ms 3.812 ms 3.923 ms 6 ae-7-7.ebr2.SanJose1.Level3.net (4.69.132.49) 17.959 ms 18.077 ms 18.068 ms 7 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 18.864 ms 19.038 ms 18.770 ms 8 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 18.995 ms 18.907 ms 18.778 ms 9 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 19.151 ms 19.201 ms 18.863 ms 10 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 19.775 ms 19.827 ms 19.906 ms 11 38.102.136.100 (38.102.136.100) 19.440 ms 19.447 ms 19.352 ms 12 38.102.136.100 (38.102.136.100) 19.479 ms 19.557 ms 19.503 ms On Sat, Dec 31, 2011 at 7:50 AM, Frank Bulk <frnkblk@iname.com> wrote: Same here: nagios:/home/fbulk# tcptraceroute www.wunderground.com Selected device eth0.3, address 96.31.0.5, port 49309 for outgoing packets Tracing the path to www.wunderground.com (38.102.136.104) on TCP port 80 (www), 30 hops max 1 router-core-inside.mtcnet.net (96.31.0.254) 0.220 ms 0.189 ms 0.193 ms 2 sxct.movl.mtcnet.net (167.142.156.194) 0.184 ms 0.137 ms 0.129 ms 3 siouxcenter.movl.153.netins.net (167.142.180.153) 2.032 ms 1.921 ms 1.932 ms 4 ins-kb1-te-13-2-220.kmrr.netins.net (167.142.64.253) 6.595 ms 6.929 ms 6.573 ms 5 ins-kc2-et-8-3.kmrr.netins.net (167.142.67.37) 8.077 ms 8.091 ms 8.062 ms 6 ins-dc1-et-8-1.desm.netins.net (167.142.67.29) 8.201 ms 8.152 ms 8.111 ms 7 te-3-3.car2.KansasCity1.Level3.net (4.53.34.113) 14.309 ms 14.305 ms 14.299 ms 8 ae-4-4.ebr2.Denver1.Level3.net (4.69.135.238) 26.934 ms 26.901 ms 26.881 ms 9 ae-1-100.ebr1.Denver1.Level3.net (4.69.151.181) 26.888 ms 26.962 ms 26.947 ms 10 ae-3-3.ebr2.SanJose1.Level3.net (4.69.132.57) 52.187 ms 52.168 ms 52.208 ms 11 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 61.726 ms 53.280 ms 53.301 ms 12 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 72.035 ms 53.173 ms 53.175 ms 13 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 53.598 ms 53.583 ms 53.595 ms 14 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 54.026 ms 54.121 ms 54.008 ms 15 * * From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Colleen Velo Sent: Saturday, December 31, 2011 1:04 AM To: outages@outages.org Subject: [outages] Wunderground down for anyone else? I have been unable to reach http://www.wunderground.com/ from Mpls, Mn as well as from my colos in the Washington, Dallas and Seattle locations. (http://www.downforeveryoneorjustme.com/www.wunderground.com also reports it down) Saw one mention on Twitter of Level3 in SF dropping packets: yeah, my route to <http://twitter.com/#!/wunderground> @wunderground is dropped by level3 in SF. great jorb Anyone else having issues? Thanks in advance, -- Colleen Velo email: cmvelo@gmail.com -- Colleen Velo email: cmvelo@gmail.com
participants (6)
-
Colin Johnston -
Colleen Velo -
Frank Bulk -
Jay Hennigan -
Krassimir Tzvetanov -
Mike Lyon