Feb 7, 11:20 PST
Completed - The scheduled maintenance has been completed.
Feb 7, 06:00 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 7, 05:50 PST
Scheduled - We will be undergoing scheduled maintenance during this time.
May 14, 16:50 PDT
Resolved - The migration has completed and service has returned to normal.
May 14, 15:20 PDT
Update - Migration is still in progress. This is taking more time than expected but we're monitoring it closely.
May 14, 14:12 PDT
Update - We are continuing to work on a fix for this issue.
May 14, 14:10 PDT
Identified - Due to a database upgrade issue, a portion of our IronWorker customers are experiencing issues with certain API commands. We've identified the issue and are in the process of resolving.
Jul 2, 16:41 PDT
Completed - The scheduled maintenance has been completed.
May 21, 10:47 PDT
Scheduled - We'll be performing a planned upgrade of IronWorker on May 23rd at midnight.
During this time, one API call will be unavailable: GET /projects/{Project ID}/tasks/{Task ID}
All other API requests will be available, so tasks will continue to be queued and run.
Jul 9, 15:51 PDT
Resolved - This incident has been resolved.
Jul 9, 15:49 PDT
Identified - The issue has been identified and a fix is being implemented.
Jul 9, 14:17 PDT
Investigating - We are currently investigating this issue.
Jul 17, 00:34 PDT
Completed - The scheduled maintenance has been completed.
Jul 17, 00:01 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 18, 12:45 PDT
Scheduled - This maintenance should not generate any downtime, but services may be taken down for up to an hour in an emergency situation. In the case of necessary downtime, another notification will be sent out.
We're migrating the rest of our third-party hosted MongoDB services to Amazon's DocumentDB. We've been working closely with the AWS team to make this happen.
The internal benefits are heightened security by moving yet another service under the AWS Cloud Security umbrella. Externally, there will be a small performance benefit for our customers as we'll be dealing with a lower latency network configuration and an optimized query engine.
We appreciate your support as we make moves to improve the Iron platform!
Jul 29, 02:16 PDT
Completed - The scheduled maintenance has been completed.
Jul 29, 00:00 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 24, 15:19 PDT
Scheduled - This maintenance should not generate any downtime, but services may be taken down for up to an hour in an emergency situation. In the case of necessary downtime, another notification will be sent out.
We're migrating IronCache service to Amazon's DocumentDB. We've been working closely with the AWS team to make this happen.
The internal benefits are heightened security by moving yet another service under the AWS Cloud Security umbrella. Externally, there will be a small performance benefit for our customers as we'll be dealing with a lower latency network configuration and an optimized query engine.
Oct 25, 04:53 PDT
Resolved - This incident has been resolved.
Oct 25, 04:53 PDT
Identified - The issue has been identified and a fix is being implemented.
Oct 25, 04:00 PDT
Investigating - We are currently investigating this issue.
Apr 30, 16:00 PDT
Resolved - On May 1, at 11 am UTC we identified the issue with our autoscale functionality: there were errors while starting our IronWorker service on new instances but it was working fine on existing ones. After investigating into the errors thrown, we found the issue was happening while pulling our docker images from DockerHub. The root cause was problems on dockerhub side information about which you can find on their status page: https://status.docker.com/
In order to resolve the issue, we have manually launched our service on new instances and temporarily disabled the autoscale functionality.
Dec 10, 07:01 PST
Completed - The scheduled maintenance has been completed.
Dec 10, 03:21 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 10, 03:20 PST
Scheduled - During the maintenance, none of the messages will be lost and there will be no downtime.
Mar 3, 01:30 PST
Resolved - Amazon performed an upgrade of our PostgreSQL DB version. This DB stores logins, passwords, tokens and other information about our customers. While upgrading they shutted down the database instance, performed the upgrade, and restarted the database instance. As a result, you could see HTTP 401 errors in your logs between 09:28 am UTC and 09:45 am UTC.
Here is more information: https://forums.aws.amazon.com/ann.jspa?annID=8176