Extole had 15 outages in the last 2 years totaling 9h 13m of downtime — averaging 0.6 incidents per month.
There were 15 Extole outages since May 11, 2025 totaling 9h 13m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating an issue where CSS is not applying to certain pages.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating an issue with our email provider Sendgrid, that is causing email delays.
Emails being sent through Sendgrid are currently not being delivered. We are working with Sendgrid to resolve the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
One of the databases in US-EAST-1 experienced a failover and one of the backup database has been promoted. Requests were delayed from 05:08:09 UTC to 05:11:19 UTC.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Feb 4, 08:05 PST Resolved - This incident has been resolved. Feb 4, 07:38 PST Monitoring - We have resolved an issue with our Core API and are monitoring the fix to ensure it fixes the problem.
Jan 28, 15:16 PST Resolved - This incident has been resolved. Jan 28, 14:43 PST Monitoring - A fix has been implemented and we are monitoring the results. Jan 28, 14:00 PST Identified - The issue has been identified and a fix is being implemented.
There is a delay in data processing causing reports to run slower than usual. The root cause has been identified and fixed and reports should run shortly.
Jan 12, 05:06 PST Resolved - This incident has been resolved. We have deployed a fix and are not seeing more errors. Our team is investigating the root cause to mitigate future problems. Jan 12, 05:00 PST Update - We are continuing to work on a fix for this issue. Jan 12, 05:00 PST Identified - The issue has been identified and a fix is being implemented. Jan 12, 05:00 PST Update - We are continuing to investigate this issue. Jan 12, 04:59 PST Investigating - We are seeing increased error rates on consumer-api and are investigating the issue.
Nov 22, 11:35 PST Resolved - This incident has been resolved. Nov 22, 11:32 PST Monitoring - A fix has been implemented and we are monitoring the results. Nov 22, 10:51 PST Update - We are continuing to work on a fix for this issue. Nov 22, 10:44 PST Update - We are continuing to work on a fix for this issue. Nov 22, 10:44 PST Identified - The issue has been identified and a fix is being implemented.
Oct 20, 14:49 PDT Resolved - This incident has been resolved. Oct 20, 12:31 PDT Update - Due to outages with Amazon Web Services, our platform has experienced intermittent latency and other issues with delivering experiences, rewarding, and reporting. We are working to ensure that we do not lose any information during these outages. Oct 20, 10:18 PDT Monitoring - AWS Outage in US-EAST is impacting mulitple services and we are currently executing our business continuity plan.
Increase in error rate on API, engineers have identified the problem and deployed a resolution.
We are currently investigating a performance issue with the Admin API that is impacting the ability to change campaigns.
The issue has been identified and a fix is being implemented.
We have identified the root cause and applied a fix, and are monitoring the improved performance. Campaigns edits will start to be applied now.
We are continuing to monitor for any further issues.
This incident has been resolved.
A migration of multiple campaigns caused a performance problem on the campaign API creating a backlog of events. We are investigating long term fixes to prevent this in the future.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor and investigate the root cause.
This incident has been resolved.