top | item 5052515

Mit.edu is down

87 points| simonster | 13 years ago |mit.edu | reply

45 comments

order
[+] lwf|13 years ago|reply
Hi there! We know MITnet is down, and we're pretty sure its an issue with BGP. We've been having issues periodically over the past few weeks, and this is almost certainly not the result of an attack, just network misconfiguration.

-- Luke from MIT SIPB

[+] saifelse|13 years ago|reply
Is there a particular reason why Google servers are still accessible from within MIT despite MITnet being down?
[+] mitstudent|13 years ago|reply
How long do you estimate until the Internet will be back up? Thank you.
[+] lwf|13 years ago|reply
To be clear, MIT SIPB maintains services at MIT, but does not maintain MIT's network. Further details as to the root cause are forthcoming.

It is not clear whether this was an attack or not.

[+] lvs|13 years ago|reply
3down needs an update. it is borderline useless in situations like these.
[+] edwardunknown|13 years ago|reply
Not to worry, they'll probably begin the actual attack as soon as you get everything fixed :)
[+] agwa|13 years ago|reply
MIT's name servers are all on their own network? Seriously?

  ;; AUTHORITY SECTION:
  mit.edu.              172800  IN      NS      bitsy.mit.edu.
  mit.edu.              172800  IN      NS      strawb.mit.edu.
  mit.edu.              172800  IN      NS      w20ns.mit.edu.
  
  ;; ADDITIONAL SECTION:
  bitsy.mit.edu.                172800  IN      A       18.72.0.3
  strawb.mit.edu.               172800  IN      A       18.71.0.151
  w20ns.mit.edu.                172800  IN      A       18.70.0.160
[+] yskchu|13 years ago|reply
It's not that uncommon if they're multi-homed. Of course, I'm not saying that an additional external DNS won't be nice.
[+] jessaustin|13 years ago|reply
From here in the Midwest USA, here's the last few lines of "mtr mit.edu --report":

  16.|-- ae-1-8.bar2.Boston1.Level 90.0%  10  83.3  83.3  83.3  83.3  0.0
  17.|-- ae-0-11.bar1.Boston1.Leve  0.0%  10  84.5  84.0  82.5  85.0  0.7
  18.|-- ae-7-7.car1.Boston1.Level  0.0%  10  83.1  83.9  81.8  92.9  3.2
  19.|-- MASSACHUSET.car1.Boston1.  0.0%  10  85.1  83.7  82.3  85.1  0.9
  20.|-- DMZ-RTR-2-EXTERNAL-RTR-1.  0.0%  10  89.9  88.8  86.1  94.2  2.9
  21.|-- ???                       100.0  10   0.0   0.0   0.0   0.0  0.0
(the full name for the last listed host is "DMZ-RTR-2-EXTERNAL-RTR-1.MIT.EDU")
[+] kylemaxwell|13 years ago|reply
Traceroute to web.mit.edu (previously 18.9.22.69) dies after a Level 3 router in Boston. This isn't just DNS, although both MIT.edu and DoJ.gov are returning NXDOMAIN right now.

Justice.gov and USDoJ.gov are functioning normally, though.

[+] danielweber|13 years ago|reply
I can't even ping them. MIT has huge pipes to the Internet. Someone has to be throwing a lot of bandwidth at them from very very close to choke them off, or has specifically attacked their routers.
[+] emereld|13 years ago|reply
Very disappointed if it's DDoS. This doesn't feel like the time for it.
[+] david_shaw|13 years ago|reply
Is this the result of some kind of organized DDoS (Anonymous or some other hacktivist group), or merely a coincidence given their recent exposure re: aaronsw?
[+] unknown|13 years ago|reply

[deleted]

[+] haldean|13 years ago|reply
It's back up now, so if it was a DDoS it was a pretty ineffectual one (time between post and this comment is 20 minutes).
[+] geofft|13 years ago|reply
MIT's been having serious intermittent network problems over the past two weeks, although usually not a complete outage from all parts of the Internet (there were several points last week where it was reachable from Internet2 but not from a handful of residential ISPs). I have no knowledge here, but at this point I'd be more likely to credit some router somewhere sucking than Anonymous with doing anything.
[+] rexreed|13 years ago|reply
Looks like a DNS attack? Lack of name resolution vs. server response?
[+] rst|13 years ago|reply
Lack of both --- the nameservers are unreachable, but so is everything else. (MIT apparently hosts its own DNS, but attempting to ping internal servers by IP address, bypassing DNS, also fails.)
[+] seleniumhi|13 years ago|reply
I was very surprised to see that when mit.edu went away, we also lost emergency.mit.net.