Ayende @ Rahien

My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:


+972 52-548-6969

, @ Q c

Posts: 6,026 | Comments: 44,842

filter by tags archive

RavenHQ & Amazon EC2 Outage

time to read 1 min | 178 words

Update: The issue has been resolved, I’ll update on Sunday with full details about this.

Some RavenHQ customers may have noticed that they are currently unable to access their RavenHQ databases.

The underlying reason is an outage in Amazon US-EAST-1 region, which is where the ravenhq.com server and some of the data base servers are located.

Customers with replicated plans should see no disturbance of service, since this should trigger an automatic failover to the secondary node.

If you have any questions / require support, please contact us via our support forum: http://support.ravenhq.com/

You can see the status report from Amazon below. We managed to restore some service, but then lost it again (because of EBS timeouts, I suspect).

We are currently hard at work at bringing up new servers in additional availability zones, and we hope to restore full functionality as soon as possible.



James Manning

Needs more chaos monkey!


Fail early, fail often! :)

Edward Spelt

Netflix, Pinterest en Instagram are/where offline too.

Christopher Wright

Have you considered hosting RavenHQ servers in multiple availability zones and regions, and randomizing your non-replicated customers between zones?

It sucks to have a large portion of your customer base experience an outage because of you. By hosting in multiple zones, you can reduce the portion of your customer base that any single incident affects.

Also, when you say "the secondary node", I immediately get worried. Is there a tertiary node? Are all the secondary nodes in the same zone as each other?

Ayende Rahien

Christopher, We are running in multiple availability zones, and we are putting non replicated clients in multiple zones. I'll post a full discussion of this tomorrow, but the reason you saw a lot of activity about that is that most of our free plans resided on that region.

"The secondary node" is actually a RavenDB term, which refers to the secondary node that you fail to. The question if you have tertiary or more actually depend on your plan. And N node in a replicated plan are on a different availability zone.

Colin Bull

Hummm, wondering whether this was the pesky leap second introduced on 30 June at midnight..

Christopher Wright

@Ayende: Ah, okay, that's a lot better than I initially thought. I should have remembered that you're smart.

I personally would never trust anything important to just two zones, but I understand that a lot of companies are budget-conscious and can take a short outage, especially if they can point at someone else to blame.

Comment preview

Comments have been closed on this topic.


No future posts left, oh my!


  1. Technical observations from my wife (3):
    13 Nov 2015 - Production issues
  2. Production postmortem (13):
    13 Nov 2015 - The case of the “it is slow on that machine (only)”
  3. Speaking (5):
    09 Nov 2015 - Community talk in Kiev, Ukraine–What does it take to be a good developer
  4. Find the bug (5):
    11 Sep 2015 - The concurrent memory buster
  5. Buffer allocation strategies (3):
    09 Sep 2015 - Bad usage patterns
View all series


Main feed Feed Stats
Comments feed   Comments Feed Stats