MemCachier Status

 

All systems go!

 
Azure Asia East Cluster 1 UP
Azure Asia South Cluster 1 UP
Azure EU North Cluster 1 UP
Azure EU West Cluster 1 UP
Azure Japan East Cluster 1 UP
Azure Japan West Cluster 1 UP
Azure US East Cluster 1 UP
Azure US West Cluster 1 UP
EC2 EU [Amazon, Heroku] Cluster 1 UP
EC2 EU [Amazon, Heroku] Cluster 2 UP
EC2 EU [Amazon, Heroku] Development UP
EC2 US-East [Amazon, Heroku] Cluster 1 UP
EC2 US-East [Amazon, Heroku] Cluster 2 UP
EC2 US-East [Amazon, Heroku] Cluster 3 UP
EC2 US-East [Amazon, Heroku] Cluster 4 UP
EC2 US-East [Amazon, Heroku] Cluster 5 UP
EC2 US-East [Amazon, Heroku] Development UP
Google US Central [Google, CloudControl] Cluster 1 UP
Google US Central [Google, CloudControl] Development UP
Rackspace Dallas Cluster 1 UP
analytics.memcachier.com UP
New Relic Integration UP
Provisioning of Caches UP
www.memcachier.com UP
Current time: May 5, 2016 23:45 UTC

[Resolved] Issue with US-East C3 cluster

We have resolved an issue with the US-East C3 cluster. One machine's network experienced intermittent packet drops, causing performance issues from 11:10am - 11:16am PST until it was resolved.

We are doing a deeper investigation of the C3 cluster due to the number of recent issues it has experienced to ensure no further issues occur going forward.

April 28, 2016 18:34 UTC · 7 days ago

Issue with US-East C3 cluster at 7:42am PST

We experienced an issue accepting new connections on the US-East C3 cluster this morning from 7:41am - 7:44am PST. We are currently investigating the cause but believe it to have been triggered by a network failure.

April 26, 2016 17:20 UTC · 9 days ago