Subscribe Pro Status

Background job processing went down on 10/1 or us-east-1 region and 10/4 for eu-west-1 region. Both incidents were due to the same root cause: * A key scheduling service failed. * This was triggered by our core transactional database recycling after a minor version upgrade. * This happened around 3am eastern time on 10/4 in us-east-1 region. * Happened around 3am eastern time on 10/1 in eu-west-1 region. * We should have noticed this, however there was an error in some of our alerting / notification scripts. * We have since updated and thoroughly tested the notification scripts.

This incident was caused because we missed updating a key credential during deployment to our production platform. We will be reviewing our process around how we track such credentials during updates.

We have identified the core issue and a fix is in place. We will follow up with a postmortem.

This incident has been reported resolved by our upstream provider, and we are also no longer seeing any issues, so we are also considering it resolved.

Full service has been restored.

This incident has been resolved.

The issue causing a partial outage of our Merchant App and API is resolved.

This incident has been resolved.

We identified an issue during our most recent deployment that resulted in traffic to our API and web UI not being processed. The relevant change was reverted and the issue has been resolved.

A fix has been deployed by Spreedly and the core issue has been resolved. Transactions are processing successfully.

The scheduled maintenance has been completed.

Maintenance is completed. No downtime was required.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The migration is complete and all services are fully operational.

Deployment completed.

Completed successfully.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.