Extole Outage History

Extole is up right now

Pingoru has recorded 20 incidents for Extole: 13 in the last 12 months and 2 in the last 90 days.

Source: status.extole.com

20incidents recorded
13last 12 months
2last 90 days
83 minutestypical duration
Incidents per month
024AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Extole in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202611 of 720 (0%)
May 202634 of 744 (1%)
June 202614 of 720 (1%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202610 of 720 (0%)
October 202610 of 744 (0%)
November 202600 of 79 (0%)

Incidents, newest first

Notice October 23, 2026 Extole Update to Service Sub-Processors – Data Processing

Started Oct 23, 2026, 09:16 PM UTC· resolved Oct 23, 2026, 09:16 PM UTC

  1. resolved Oct 23, 2026, 09:16 PM UTC

    This is a notice of a new service sub-processor Extole clients may elect to use, OpenAI. Sub-processor purpose: Extole uses OpenAI to power its in-product AI Chat offered to client organizations. Data shared with OpenAI: As part of the AI Chat functionality, a client user may share limited PII for a program. The full list of Extole sub-processors is here: https://docs.extole.com/product/product-overview/security-and-compliance/gdpr-ccpa

Read the full incident report →

Major September 14, 2026 Consumer API Performance 10m Pod 0, Pod 1, Pod 2, Pod 3 and 11 more

Started Sep 14, 2026, 04:09 PM UTC· resolved Sep 14, 2026, 04:20 PM UTC

  1. investigating Sep 14, 2026, 04:09 PM UTC

    We are currently investigating this issue.

  2. resolved Sep 14, 2026, 04:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 26, 2026 CSS Not Rendering 3h 57m

Started Jun 26, 2026, 06:38 PM UTC· resolved Jun 26, 2026, 10:35 PM UTC

  1. investigating Jun 26, 2026, 06:38 PM UTC

    We are currently investigating an issue where CSS is not applying to certain pages.

  2. identified Jun 26, 2026, 06:47 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Jun 26, 2026, 10:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 21, 2026 GitHub Security Incident Response –

Started May 21, 2026, 07:23 PM UTC· resolved May 21, 2026, 07:23 PM UTC

  1. resolved May 21, 2026, 07:23 PM UTC

    GitHub security incident (May 2026) — investigated, no Extole impact We are aware of the security incident disclosed by GitHub on May 20, 2026, involving unauthorized access to GitHub's internal repositories via a compromised third-party VS Code extension (Nx Console), itself linked to the earlier @tanstack/* npm supply-chain compromise on May 11, 2026. We have completed our investigation and confirmed that Extole is not impacted: - GitHub has stated the incident was limited to its own internal repositories, with no evidence of impact to customer repositories, organizations, or enterprises. - Extole does not use the Nx Console extension or any of the @nrwl/* packages. - The @tanstack/* packages compromised in the upstream incident (the Router/Start monorepo) are not used by Extole; the @tanstack/* package we do use (vue-query) was explicitly confirmed unaffected by TanStack. - We checked our workstations and build infrastructure for the published indicators of compromise and found none. No customer action is required. We will continue to monitor for any further disclosures from GitHub or TanStack and will update this status if anything changes.

Read the full incident report →

Minor May 5, 2026 Email Delays 3h 58m Email

Started May 05, 2026, 11:57 AM UTC· resolved May 05, 2026, 03:56 PM UTC

  1. investigating May 05, 2026, 11:57 AM UTC

    We are currently investigating an issue with our email provider Sendgrid, that is causing email delays.

  2. identified May 05, 2026, 01:50 PM UTC

    Emails being sent through Sendgrid are currently not being delivered. We are working with Sendgrid to resolve the issue.

  3. monitoring May 05, 2026, 03:28 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 05, 2026, 03:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 1, 2026 Consumer Database Failover 3m Pod 0, Pod 1, Pod 2, Pod 3 and 11 more

Started May 01, 2026, 05:08 AM UTC· resolved May 01, 2026, 05:11 AM UTC

  1. resolved May 01, 2026, 05:41 AM UTC

    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.

Read the full incident report →

Minor April 29, 2026 Incerased API Error Rate 28m Pod 0, Pod 1, Pod 2, Pod 3 and 11 more

Started Apr 29, 2026, 11:53 AM UTC· resolved Apr 29, 2026, 12:21 PM UTC

  1. investigating Apr 29, 2026, 11:53 AM UTC

    We are currently investigating this issue.

  2. identified Apr 29, 2026, 12:11 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 29, 2026, 12:17 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Apr 29, 2026, 12:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 4, 2026 Core API Errors 27m Pod 0, Pod 1, Pod 2, Pod 3 and 11 more

Started Feb 04, 2026, 03:38 PM UTC· resolved Feb 04, 2026, 04:05 PM UTC

  1. monitoring Feb 04, 2026, 03:38 PM UTC

    We have resolved an issue with our Core API and are monitoring the fix to ensure it fixes the problem.

  2. monitoring Feb 04, 2026, 04:05 PM UTC

    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.

  3. resolved Feb 04, 2026, 04:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 28, 2026 Consumer API Response Delays 1h 15m Pod 0, Pod 1, Pod 2, Pod 3 and 7 more

Started Jan 28, 2026, 10:00 PM UTC· resolved Jan 28, 2026, 11:16 PM UTC

  1. identified Jan 28, 2026, 10:00 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Jan 28, 2026, 10:43 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Jan 28, 2026, 11:16 PM UTC

    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.

  4. resolved Jan 28, 2026, 11:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 26, 2026 Data Processing Delays – Data Processing

Started Jan 26, 2026, 06:48 PM UTC· resolved Jan 26, 2026, 06:48 PM UTC

  1. monitoring Jan 26, 2026, 06:48 PM UTC

    Jan 26, 10:48 PST Resolved - 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.

  2. resolved Jan 26, 2026, 06:48 PM UTC

    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.

Read the full incident report →

Notice January 21, 2026 Data Processing Delays 2h 28m Data Processing

Started Jan 21, 2026, 03:17 PM UTC· resolved Jan 21, 2026, 05:45 PM UTC

  1. investigating Jan 21, 2026, 03:17 PM UTC

    We are investigating an issue causing delays in our data processing pipeline which is impacting updates to dashboard, no event loss or reward performance is impacted.

  2. identified Jan 21, 2026, 05:19 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jan 21, 2026, 05:41 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Jan 21, 2026, 05:45 PM UTC

    Jan 21, 09:45 PST Resolved - This incident has been resolved. Jan 21, 09:41 PST Monitoring - A fix has been implemented and we are monitoring the results. Jan 21, 09:19 PST Identified - The issue has been identified and a fix is being implemented. Jan 21, 07:17 PST Investigating - We are investigating an issue causing delays in our data processing pipeline which is impacting updates to dashboard, no event loss or reward performance is impacted.

  5. resolved Jan 21, 2026, 05:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 12, 2026 Consumer API Error Rate 6m Pod 0, Pod 1, Pod 2, Pod 3 and 6 more

Started Jan 12, 2026, 12:59 PM UTC· resolved Jan 12, 2026, 01:06 PM UTC

  1. investigating Jan 12, 2026, 12:59 PM UTC

    We are seeing increased error rates on consumer-api and are investigating the issue.

  2. investigating Jan 12, 2026, 01:00 PM UTC

    We are continuing to investigate this issue.

  3. identified Jan 12, 2026, 01:00 PM UTC

    The issue has been identified and a fix is being implemented.

  4. identified Jan 12, 2026, 01:00 PM UTC

    We are continuing to work on a fix for this issue.

  5. monitoring Jan 12, 2026, 01:06 PM UTC

    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.

  6. resolved Jan 12, 2026, 01:06 PM UTC

    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.

Read the full incident report →

Major November 22, 2025 Consumer API 404s for /zones Requests 51m Pod 0, Pod 1, Campaign Publishing, Pod 2 and 9 more

Started Nov 22, 2025, 06:44 PM UTC· resolved Nov 22, 2025, 07:35 PM UTC

  1. identified Nov 22, 2025, 06:44 PM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Nov 22, 2025, 06:44 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified Nov 22, 2025, 06:51 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Nov 22, 2025, 07:32 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. monitoring Nov 22, 2025, 07:35 PM UTC

    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.

  6. resolved Nov 22, 2025, 07:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 20, 2025 AWS Outage 4h 31m Data Processing, Pod 0, Pod 1, Campaign Publishing and 13 more

Started Oct 20, 2025, 05:18 PM UTC· resolved Oct 20, 2025, 09:49 PM UTC

  1. monitoring Oct 20, 2025, 05:18 PM UTC

    AWS Outage in US-EAST is impacting mulitple services and we are currently executing our business continuity plan.

  2. monitoring Oct 20, 2025, 07:31 PM UTC

    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.

  3. monitoring Oct 20, 2025, 09:49 PM UTC

    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.

  4. resolved Oct 20, 2025, 09:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 6, 2025 Increase in errors on client-api –

Started Oct 06, 2025, 04:40 PM UTC· resolved Oct 06, 2025, 04:40 PM UTC

  1. resolved Oct 06, 2025, 04:40 PM UTC

    Increase in error rate on API, engineers have identified the problem and deployed a resolution.

Read the full incident report →

Minor July 23, 2025 Admin API Performance Degradation 15m

Started Jul 23, 2025, 10:06 AM UTC· resolved Jul 23, 2025, 10:21 AM UTC

  1. investigating Jul 23, 2025, 10:06 AM UTC

    We are currently investigating a performance issue with the Admin API that is impacting the ability to change campaigns.

  2. identified Jul 23, 2025, 10:10 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jul 23, 2025, 10:14 AM UTC

    We have identified the root cause and applied a fix, and are monitoring the improved performance. Campaigns edits will start to be applied now.

  4. monitoring Jul 23, 2025, 10:17 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jul 23, 2025, 10:21 AM UTC

    This incident has been resolved.

  6. postmortem Jul 23, 2025, 10:22 AM UTC

    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.

Read the full incident report →

Minor July 10, 2025 Consumer API 404s for /zones Requests 4h 4m

Started Jul 10, 2025, 07:30 AM UTC· resolved Jul 10, 2025, 11:34 AM UTC

  1. resolved Jul 10, 2025, 07:30 AM UTC

    From 12:30AM to 4:34AM PDT requests sent to /zones for consumer API were returning a 404. This was related to an Extole Platform change that has been reverted.

Read the full incident report →

Minor May 11, 2025 Consumer AP 22m

Started May 11, 2025, 11:37 PM UTC· resolved May 12, 2025, 12:00 AM UTC

  1. identified May 11, 2025, 11:37 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring May 11, 2025, 11:40 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring May 11, 2025, 11:56 PM UTC

    We are continuing to monitor and investigate the root cause.

  4. resolved May 12, 2025, 12:00 AM UTC

    This incident has been resolved.

Read the full incident report →