Resolved
{:closed=>"Closed", :complete=>"Complete", :false_alarm=>"False Alarm", :identified=>"Identified", :investigating=>"Investigating", :open=>"Open", :recovering=>"Recovering", :resolved=>"Resolved", :scheduled=>"Scheduled", :underway=>"Underway"}
After 1 hour and 1 minute

Dyn Managed DNS has given green lights: https://www.dynstatus.com/incidents/nlr4yrr162t8. The DDoS is officially over or mitigated.

{:closed=>"Closed", :complete=>"Complete", :false_alarm=>"False Alarm", :identified=>"Identified", :investigating=>"Investigating", :open=>"Open", :recovering=>"Recovering", :resolved=>"Resolved", :scheduled=>"Scheduled", :underway=>"Underway"}
After 55 minutes

Our support desk Intercom is back up again, as far as we can tell. If it's available from your location, you can safely use it again.

{:closed=>"Closed", :complete=>"Complete", :false_alarm=>"False Alarm", :identified=>"Identified", :investigating=>"Investigating", :open=>"Open", :recovering=>"Recovering", :resolved=>"Resolved", :scheduled=>"Scheduled", :underway=>"Underway"}
After 7 minutes

Correction: Please use info@fortrabbit.com instead of support@fortrabbit.com for urgent support cases while Intercom is not available.

{:closed=>"Closed", :complete=>"Complete", :false_alarm=>"False Alarm", :identified=>"Identified", :investigating=>"Investigating", :open=>"Open", :recovering=>"Recovering", :resolved=>"Resolved", :scheduled=>"Scheduled", :underway=>"Underway"}

A massive DDoS against Dyn Managed DNS is causing trouble for various services, such as partial AWS (US East), Intercom, Twitter and more. Fortrabbit Apps, mostly in US1 but potentially in EU2 as well, might be partially affected - it depends on whether the Apps are using external 3rd party services, whose DNS records cannot be resolved.

We keep monitoring the issue and let you know when it is resolved or if other new information become available. If you need to contact us, but cannot use our support service Intercom due to the DNS issues, please send us an email to support@fortrabbit.com instead.

Further reading: * https://www.dynstatus.com/incidents/nlr4yrr162t8 * https://news.ycombinator.com/item?id=12759520

Began at: