All Systems Operational
Core Transactional API ? Operational
90 days ago
99.91 % uptime
Today
Supporting Services Operational
90 days ago
99.99 % uptime
Today
Core Secondary API ? Operational
90 days ago
100.0 % uptime
Today
Dashboard Operational
90 days ago
99.98 % uptime
Today
Marketing & Education Operational
Documentation ? Operational
Marketing Site ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
had a major outage
had a partial outage
Past Incidents
Apr 9, 2020

No incidents reported today.

Apr 8, 2020

No incidents reported.

Apr 7, 2020
Resolved - Dashboard results are now fully caught up and reporting in real time.
Apr 7, 16:51 EDT
Identified - Real-time reporting has returned to normal. All new transaction activity is being represented correctly in Dashboard, although transactions which occurred between 2:30pm UTC and 4:00pm UTC are currently being repopulated.
Apr 7, 12:27 EDT
Investigating - We are currently seeing degraded performance on the Spreedly Insights Dashboard. Our capacity has now returned to normal, and we expect to see an improvement in real-time reporting shortly.

We are actively monitoring to ensure that everything is working as expected.
Apr 7, 10:48 EDT
Apr 6, 2020

No incidents reported.

Apr 5, 2020

No incidents reported.

Apr 4, 2020

No incidents reported.

Apr 3, 2020

No incidents reported.

Apr 2, 2020

No incidents reported.

Apr 1, 2020

No incidents reported.

Mar 31, 2020

No incidents reported.

Mar 30, 2020

No incidents reported.

Mar 29, 2020

No incidents reported.

Mar 28, 2020
Postmortem - Read details
Apr 2, 18:02 EDT
Resolved - Transactions are succeeding as expected on the Clearhaus gateway. Details to follow.
Mar 28, 16:32 EDT
Monitoring - A fix has been put into production and we are currently monitoring it.
Mar 28, 16:32 EDT
Identified - The issue has been identified and we are working on a fix.
Mar 28, 15:29 EDT
Investigating - We are currently investigating this issue
Mar 28, 14:32 EDT
Mar 27, 2020

No incidents reported.

Mar 26, 2020
Postmortem - Read details
Apr 7, 09:39 EDT
Resolved - We have seen no further instances of 404 errors. This issue is being marked as resolved.

We apologize for any disruption this incident may have caused and are taking steps to ensure that our systems continue to be resilient for our customers. We will post more details as they become available.
Mar 26, 14:35 EDT
Monitoring - At 16:18PM UTC, Spreedly deployed a configuration change to asset caching. We became aware of 404 errors being returned to many applications using Spreedly iFrame and/or Express.

The change was reverted at 16:40PM UTC.

All systems appear to be functional, but we will continue to monitor.

We apologize for the disruption in service.
Mar 26, 13:00 EDT
Postmortem - Read details
Apr 7, 09:38 EDT
Resolved - At 12:29PM UTC, Spreedly deployed a change to receiver functionality. This change introduced an error which caused all `deliver` transactions to fail with a 422 response code and an empty response body.

Spreedly reverted the change at 12:33PM UTC and confirmed that the errors ceased.

We apologize for any disruption this incident may have caused and are taking steps to ensure that our systems continue to be resilient for our customers.
Mar 26, 08:30 EDT