Hey Gang -
I'm unable to get to cisco.com from multiple places on the 'net
(including downforeveryoneorjustme.com); any ideas on the cause and ETR?
Thanks,
Ben
Facebook seems to also be affected.
Both work from Austin, TX.
- d.
Not sure the ETA but the network that the address for cisco.com resolves to (198.133.219.0/24) is no longer in BGP.
I'm unable to get to cisco.com from multiple places on the 'net
(including downforeveryoneorjustme.com); any ideas on the cause and ETR?
Here too
------ snip ------
core-01.fra1#sh ip bgp 198.133.219.25
BGP4 : None of the BGP4 routes match the display condition
------ snap ------
See: https://puck.nether.net/pipermail/outages/2009-August/001386.html
I do not have a route to that IP (198.133.219.25) in BGP either..
Seeing same issue from Chicago via Qwest and HE.
We have seen the route for cisco withdrawn from 208 and 2828. Facebook
seems fine
Dominic J. Eidson wrote:
Facebook seems to also be affected.
facebook works fine from germany
I'm unable to get to cisco.com from multiple places on the 'net
(including downforeveryoneorjustme.com); any ideas on the cause and ETR?
An error occurred while processing your request.
Reference #97.520dd58.1249393745.3bb006
is #down
Marc
Route is not longer in the routing table since (CET)
08/04 13:55:57 Withdraw 198.133.219.0/24>
German
can't get to cisco.com from here atm either, but can get to facebook. looks like
facebook is now coming from ashburn, va.
cisco dies within level3 for us, and for route-views.oregon-ix.net:
5 eugn-core1-gw.nero.net (207.98.64.161) [AS 3701] !H * !H
don't see that address (198.133.219.25) in the global routing table either.
show ip bgp 198.133.219.0
% Network not in table
R. Benjamin Kessler wrote:
Same here in Prague (various upstreams in Central Europe)
MK
Jon Auer napsal(a):
Same here via Verizon, Level3 and Comcast.
Btw... all 3 resolve to the same 198.133.219.25 addr.
No route for 198.133.219.0/24 in 22820 from our upstream (3356 and 174).
-Scott W
Just watched the rviews via bgplay for the aforementioned /24, shows them converging from AT&T internet, to AT&T Worldnet, to Sprint + Globix, to AAAaaaaaaaaaah!
Instead of the hoot-n-holler line, maybe check bgp?
route-views.oregon-ix.net>sho ip bgp 198.133.219.25
BGP routing table entry for 198.133.219.0/24, version 8654975
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
4826 7018 109
114.31.199.1 from 114.31.199.1 (114.31.199.1)
Origin IGP, localpref 100, valid, external, best
route-views.oregon-ix.net>
route-server>sho ip bgp 198.133.219.0/24
BGP routing table entry for 198.133.219.0/24, version 11641505
Paths: (15 available, best #2, table Default-IP-Routing-Table)
Flag: 0x24A0
Not advertised to any peer
7018 109, (received & used)
12.123.134.124 from 12.123.134.124 (12.123.134.124)
Origin IGP, localpref 100, valid, external
Community: 7018:2000 7018:32112
7018 109, (received & used)
12.123.1.236 from 12.123.1.236 (12.123.1.236)
Origin IGP, localpref 100, valid, external, best
Community: 7018:2000 7018:32112
7018 109, (received & used)
12.123.21.243 from 12.123.21.243 (12.123.21.243)
Origin IGP, localpref 100, valid, external
Community: 7018:2000 7018:32112
7018 109, (received & used)
12.123.13.241 from 12.123.13.241 (12.123.13.241)
Origin IGP, localpref 100, valid, external
Community: 7018:2000 7018:32112
7018 109, (received & used)
12.123.9.241 from 12.123.9.241 (12.123.9.241)
Origin IGP, localpref 100, valid, external
Community: 7018:2000 7018:32112
7018 109, (received & used)
12.123.145.124 from 12.123.145.124 (12.123.145.124)
Origin IGP, localpref 100, valid, external
Community: 7018:2000 7018:32112
7018 109, (received & used)
12.123.139.124 from 12.123.139.124 (12.123.139.124)
Origin IGP, localpref 100, valid, external
Community: 7018:2000 7018:32112
7018 109, (received & used)
12.123.142.124 from 12.123.142.124 (12.123.142.124)
Origin IGP, localpref 100, valid, external
Community: 7018:2000 7018:32112
7018 109, (received & used)
12.123.17.244 from 12.123.17.244 (12.123.17.244)
Origin IGP, localpref 100, valid, external
Community: 7018:2000 7018:32112
7018 109, (received & used)
12.123.5.240 from 12.123.5.240 (12.123.5.240)
Origin IGP, localpref 100, valid, external
Community: 7018:2000 7018:32112
7018 109, (received & used)
12.123.137.124 from 12.123.137.124 (12.123.137.124)
Origin IGP, localpref 100, valid, external
Community: 7018:2000 7018:32112
7018 109, (received & used)
12.123.33.249 from 12.123.33.249 (12.123.33.249)
Origin IGP, localpref 100, valid, external
Community: 7018:2000 7018:32112
7018 109, (received & used)
12.123.25.245 from 12.123.25.245 (12.123.25.245)
Origin IGP, localpref 100, valid, external
Community: 7018:2000 7018:32112
7018 109, (received & used)
12.123.45.252 from 12.123.45.252 (12.123.45.252)
Origin IGP, localpref 100, valid, external
Community: 7018:2000 7018:32112
7018 109, (received & used)
12.122.125.4 from 12.122.125.4 (12.122.125.4)
Origin IGP, metric 411, localpref 100, valid, external
route-server>
http://onestepconsulting.org/communities/as7018/ doesn't indicate
anything meaningful for those communities, so presumably they
are internal. 109 appears to be properly originating, so ...
The IP is back in BGP and the website is working for me now.
Looks like it's back.
rtr-inet1#show ip bgp 198.133.219.0/24
BGP routing table entry for 198.133.219.0/24, version 4296794
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Advertised to update-groups:
1
6128 7132 109, (received & used)
69.74.151.237 from 69.74.151.237 (65.19.127.20)
Origin IGP, localpref 100, valid, external, best
rtr-inet2#show ip bgp 198.133.219.0/24
BGP routing table entry for 198.133.219.0/24, version 11588586
Paths: (2 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
6128 7132 109, (received & used)
129.77.19.1 from 129.77.19.1 (129.77.9.252)
Origin IGP, metric 0, localpref 100, valid, internal, best
6395 3356 7018 109, (received & used)
67.96.160.189 from 67.96.160.189 (216.140.10.58)
Origin IGP, metric 6, localpref 100, valid, external
Community: 6395:1 6395:1006
Matthew Huff.vcf (1.57 KB)
Can get to facebook but not to cisco from Denver (level 3).
Traces reach SJC and die in ATT net. Possibly a local data center outage /
black-holing event.
- Gaurav