This issue should now be resolved. If you are still seeing any problems reaching api.rollbar.com or rollbar.com, please reach us via email@example.com
Our primary DNS provider (that had the outage starting this morning) has reported that the issue is resolved on their side. This should mean that all clients are able to resolve rollbar.com and api.rollbar.com, regardless of whether the nameserver change has propagated.
We'll be doing a full postmortem on this event early next week and will share more details about the issue, impact, and future steps then.
Oct 21, 15:24 PDT
Nameserver propagation update: Google's DNS servers (220.127.116.11 and 18.104.22.168) now see our new DNS provider. If you are still having trouble accessing Rollbar, try setting your DNS servers to 22.214.171.124 and 126.96.36.199 .
Oct 21, 13:49 PDT
We've started migration to another DNS provider (currently waiting for the nameserver change to propogate). In the meantime, you can reach Rollbar by adding the following to your /etc/hosts :
We'll provide further updates here, on Twitter when possible (Twitter is affected by the same issue), and on our Facebook page: https://www.facebook.com/rollbarinc/
Oct 21, 11:07 PDT
A DDoS attack on an upstream DNS provider is causing intermittent name resolution errors for both our web UI and API tier. We're monitoring the situation and attempting to mitigate the issue.
Oct 21, 09:23 PDT