All Systems Operational
IronWorker Operational
IronMQ v2 (AWS US-East) Operational
IronMQ v2 (AWS EU-West) Operational
IronMQ v2 (Rackspace ORD) Operational
IronMQ v2 (Rackspace LON) Operational
IronMQ v2 (PRO-4) ? Operational
IronMQ v3 (AWS US-East) Operational
IronMQ v3 (AWS EU-West) Operational
IronCache Operational
HUD Operational
HUD-E ? Operational
IronMQ v3 (mq-rackspace-ord-2.iron.io) Operational
IronWorker Dedicated Operational
IronWorker Public Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Past Incidents
Jul 30, 2016

No incidents reported today.

Jul 29, 2016
Resolved - We have resolved the issue and all systems are operational. We will continue to monitor status.
Jul 29, 13:09 PDT
Investigating - We have identified a system issue. This is a high priority issue, and our Operations team is actively investigating. We will post an update as soon as information becomes available.
Jul 29, 02:46 PDT
Jul 28, 2016

No incidents reported.

Jul 27, 2016

No incidents reported.

Jul 26, 2016
Resolved - Service has been restored to functional status. Due to an issue with connections not closing properly on the hosts in the original public v3 cluster, this required a necessary failover to a new v3 cluster. During this timeframe, some customer queues and messages were lost due to the deteriorated health of the original cluster. Upon failing over to the new MQv3 cluster, most customers were able to see their queues and messages. In the days following service restoration, we have been able to migrate customer messages off of the failed cluster. Unfortunately, some messages have not been retrievable. Development Operations will continue all efforts to migrate all available messages to the new v3 cluster, and expect this laborious procedure will continue over the next few days. All customers whose queues and messages were recoverable have now been moved onto the new cluster. Development Operations is identifying the list of customers whose messages were not recoverable, in order to confirm message status.
Jul 26, 14:48 PDT
Monitoring - We have identified the issue and implemented a solution. We expect to post our return to normal status momentarily.
Jul 26, 08:11 PDT
Jul 25, 2016
Resolved - We have resolved the issue and all systems are operational. We will continue to monitor status.
Jul 25, 16:22 PDT
Investigating - We have identified a system issue. This is a high priority issue, and our Operations team is actively investigating. We will post an update as soon as information becomes available.
Jul 25, 16:05 PDT
Jul 24, 2016

No incidents reported.

Jul 23, 2016
Resolved - We have resolved the issue and all systems are operational. We will continue to monitor status.
Jul 23, 07:33 PDT
Identified - There is no ETA at the moment, but we have identified a solution and are in the process of implementing a fix.
Jul 22, 21:14 PDT
Investigating - We have identified a system issue. This is a high priority issue, and our Operations team is actively investigating. We will post an update as soon as information becomes available.
Jul 22, 20:36 PDT
Jul 21, 2016

No incidents reported.

Jul 20, 2016

No incidents reported.

Jul 19, 2016

No incidents reported.

Jul 18, 2016

No incidents reported.

Jul 17, 2016

No incidents reported.

Jul 16, 2016
Resolved - We have resolved the issue and all systems are operational. We will continue to monitor status.
Jul 16, 19:02 PDT
Investigating - We have identified a system issue. This is a high priority issue, and our Operations team is actively investigating. We will post an update as soon as information becomes available.
Jul 16, 16:24 PDT