dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
21

woodchuckchu
@comcast.net

1 recommendation

woodchuckchu to Dexter0

Anon

to Dexter0

Re: [DNS] why can't I access nationalgridus.com?

There seems to be an outage through a major provider. Slashdot is also inaccessible.

graysonf
MVM
join:1999-07-16
Fort Lauderdale, FL

graysonf

MVM

I can get to /.

camper
just visiting this planet
Premium Member
join:2010-03-21
Bethel, CT

camper

Premium Member

 
/. has been unavailable for me since 9am (EDT) when I first tried today. It looks like /. is located in a savvis datacenter.


$ dig slashdot.org

slashdot.org. 300 IN A 216.34.181.45

 

$ whois 216.34.181.45

Savvis SAVVIS (NET-216-32-0-0-1) 216.32.0.0 - 216.35.255.255

SourceForge, Inc. SAVV-S234813-8 (NET-216-34-181-0-1) 216.34.181.0 - 216.34.181.255


graysonf
MVM
join:1999-07-16
Fort Lauderdale, FL

graysonf

MVM

Must be a routing problem for you. I canget to /. fine from SE Florida.

Streetlight
join:2005-11-07
Colorado Springs, CO

Streetlight to camper

Member

to camper
Can't get /. since 7:00 AM MST 4/22/14. Tried to ping and no joy - 100% lost packets.

camper
just visiting this planet
Premium Member
join:2010-03-21
Bethel, CT

camper to graysonf

Premium Member

to graysonf
said by graysonf:

Must be a routing problem for you.

 
More than likely, you are using one of the transit providers who can still get into their datacenter. It looks like many (most?) transit providers are having difficulty getting into the savvis datacenter.

graysonf
MVM
join:1999-07-16
Fort Lauderdale, FL

graysonf

MVM

Looks like it gets into savvis to me:

Tracing route to slashdot.org [216.34.181.45]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 33 ms 19 ms 10 ms 66.229.224.1
3 8 ms 8 ms 8 ms xe-10-0-0-32767-sur01.plantwest.fl.pompano.comcast.net [68.85.124.2
]
4 10 ms 10 ms 9 ms 69.139.181.137
5 11 ms 12 ms 9 ms he-2-9-0-0-cr01.miami.fl.ibone.comcast.net [68.86.94.253]
6 30 ms 28 ms 27 ms he-0-13-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.89.25]
7 41 ms 39 ms 39 ms he-0-10-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.89.177]
8 42 ms 43 ms 44 ms pos-0-3-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.86.142]
9 60 ms 48 ms 38 ms er2-tengig3-2.virginiaequinix.savvis.net [208.173.52.125]
10 42 ms 40 ms 39 ms cr2-tengig0-8-5-0.washington.savvis.net [204.70.206.241]
11 55 ms 55 ms 54 ms 206.28.96.218
12 55 ms 56 ms 56 ms hr1-te-12-0-1.elkgrovech3.savvis.net [204.70.198.73]
13 181 ms 203 ms 212 ms das5-v3030.ch3.savvis.net [64.37.207.150]
14 62 ms 56 ms 69 ms 64.27.160.194
15 55 ms 56 ms 58 ms slashdot.org [216.34.181.45]

camper
just visiting this planet
Premium Member
join:2010-03-21
Bethel, CT

camper

Premium Member

 
You are one of the lucky ones.

Here's more info about the savvis issue, from the outages mailing list.

»puck.nether.net/pipermai ··· 884.html

Follow the thread there. It looks like savvis had a major problem.