Customer.io

Affected: Message Sending

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-19 22:50 UTC

   We are currently investigating this issue.

2. identified 2026-09-19 22:52 UTC

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

3. monitoring 2026-09-19 23:10 UTC

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

4. resolved 2026-09-19 23:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Message Sending

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-04 12:16 UTC

   We are currently investigating reports of reduced deliverability affecting messages sent to Microsoft-hosted email addresses. Our team is actively looking into this and we will provide an update as soon as we have more information. Thank you for your patience!

2. monitoring 2026-09-04 12:30 UTC

   Starting around 08:00 UTC, Microsoft began experiencing an incident causing an increased volume of deferred/bounced emails. We are actively monitoring the situation. No other email providers are currently affected.

3. resolved 2026-09-04 13:35 UTC

   Microsoft has resolved the underlying issue, we are seeing deliveries to their services resume as normal. Earlier bounces will be retried accordingly. We appreciate your understanding and please do reach out to support if you need any further assistance.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-09-03 17:29 UTC

   Our team has found an issue causing degraded experiences for interactions with the Agent within customer.io. We are working on a fix now.

2. monitoring 2026-09-03 17:32 UTC

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

3. resolved 2026-09-03 17:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Management Interface

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-05 17:36 UTC

   We are currently investigating this issue.

2. monitoring 2026-08-05 17:44 UTC

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

3. monitoring 2026-08-05 17:44 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-08-05 18:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Data Processing, Management Interface

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-03 07:08 UTC

   Our team is currently investigating an issue that is causing some delays in data processing. This impacts a small subset of customers in the US datacentre.

2. investigating 2026-08-03 07:20 UTC

   We are continuing to investigate this issue.

3. resolved 2026-08-03 07:42 UTC

   This incident has been resolved. Thanks for your patience.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Management Interface

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-31 14:24 UTC

   We are currently investigating an issue impacting access to EU accounts and API access. There is no impact with data processing or data loss.

2. identified 2026-07-31 14:29 UTC

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

3. monitoring 2026-07-31 14:33 UTC

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

4. resolved 2026-07-31 14:39 UTC

   This incident is resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Data Processing, Management Interface

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-23 08:27 UTC

   Our team is looking into a problem affecting UI slowness and processing delays for some EU customers.

2. identified 2026-07-23 09:16 UTC

   A fix has been implemented and we are monitoring the results. Thanks for your patience and we'll continue to update as we make progress

3. monitoring 2026-07-23 09:29 UTC

   A fix has been deployed, and we are recovering any delayed backlogs. We are continuing to monitor the results.

4. resolved 2026-07-23 10:04 UTC

   This incident has been resolved. Thanks a lot for your patience while we worked on a fix here.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Data Processing, Message Sending

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-20 21:35 UTC

   Our engineers are currently looking into an issue that is causing data processing and message-sending delays for a small subset of customers in the US region. We apologise for any inconvenience caused.

2. identified 2026-07-20 22:29 UTC

   The issue has been identified and we're working on a fix. Thank you for your patience.

3. monitoring 2026-07-20 22:38 UTC

   A fix has been deployed, and we are processing any delayed backlogs. We are continuing to monitor the results.

4. resolved 2026-07-20 22:58 UTC

   This incident has been resolved and all backlogs have been processed.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Message Sending

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-20 17:07 UTC

   Our team is currently investigating an issue delaying message sending in the US and EU regions

2. monitoring 2026-07-20 17:41 UTC

   A fix has been implemented and we're monitoring the results.

3. resolved 2026-07-20 17:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Data Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-15 17:19 UTC

   Our engineers are currently looking into an issue that is causing data processing delays for some customers in our EU region. Thank you for patience and we apologize for the inconvenience.

2. identified 2026-07-15 17:35 UTC

   We've identified the cause of the event processing delays and our team is working on a fix. Thank you for your patience and we'll update again as we make progress.

3. monitoring 2026-07-15 17:51 UTC

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

4. resolved 2026-07-15 19:46 UTC

   This incident is resolved. Thank you for your patience!

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Message Sending

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-10 17:28 UTC

   We're monitoring increased load on our backend that is causing a delay in processing sends. We are actively monitoring the issue and will share updates accordingly.

2. monitoring 2026-07-10 17:45 UTC

   A fix has been deployed and we are processing through any delay backlogs. We are continuing to monitor but expect delays to reduce shortly.

3. resolved 2026-07-10 18:08 UTC

   This incident has been resolved and any delays have been fully mitigated.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Data Processing, Management Interface

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-03 09:07 UTC

   Our team is currently investigating an issue where the Customer.io dashboard (fly.customer.io) is unavailable for some users in EU. We're also looking into potential data processing delays.

2. identified 2026-07-03 09:44 UTC

   The Customer.io UI is back online. We're continuing to work on system stability to confirm the issue is fully resolved. Processing is recovering but still delayed

3. monitoring 2026-07-03 10:25 UTC

   Processing is actively recovering. We apologize for the disruption this caused and will continue monitoring until it's fully caught up.

4. resolved 2026-07-03 11:09 UTC

   This incident has been resolved. The Customer.io UI is available, and data processing has recovered to normal operating levels. We will continue internal follow-up and remediation work. Thank you for your patience.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Data Processing, Management Interface

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-02 13:51 UTC

   Our team is currently investigating an issue where the Customer.io dashboard (fly.customer.io) is unavailable. We're also looking into potential data processing delays.

2. monitoring 2026-07-02 13:59 UTC

   The UI is back up and delays are actively recovering. We sincerely apologize for the inconvenience and appreciate your patience.

3. resolved 2026-07-02 14:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Management Interface

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-18 20:06 UTC

   We're looking into an issue where https://fly.customer.io/settings/billing/ isn't loading for some customers. We apologize for the inconvenience.

2. monitoring 2026-06-18 20:29 UTC

   We've identified the issue and access to the Billing page has been restored. We thank you for your patience!

3. resolved 2026-06-18 20:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-13 21:18 UTC

   We are aware of an issue affecting access to our web application. Customers may encounter ERR_CONNECTION_REFUSED when attempting to access the UI. At this time, we are not aware of any impact beyond UI accessibility. Message processing and delivery continue to operate normally....

2. identified 2026-06-13 22:21 UTC

   The team has identified the issue and is actively working on a fix

3. monitoring 2026-06-13 23:46 UTC

   A fix has been implemented and the systems are recovering. We are monitoring UI for any other issue.

4. resolved 2026-06-14 00:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Data Processing, Message Sending

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-10 04:45 UTC

   Our team is aware of an issue affecting Customer IO EU and US systems . We are looking into this and gathering more details.

2. investigating 2026-06-10 04:56 UTC

   Identified the issue, still processing backlog

3. monitoring 2026-06-10 05:15 UTC

   5% of our customers could have experience delays up to 40minutes, but going forward everything is working correctly

4. resolved 2026-06-10 05:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-09 15:49 UTC

   We are currently investigating an issue affecting our AI Agent and LLM actions within campaigns. Some customers may be experiencing disruption or delays with these features. We will provide an update as soon as we have more information. Thank you for your patience!

2. identified 2026-06-09 16:33 UTC

   Our engineers have identified the issue that is causing disruption. We are working on a resolution and will provide an update shortly. Thank you for your patience.

3. monitoring 2026-06-09 16:47 UTC

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

4. resolved 2026-06-09 16:56 UTC

   This incident has been resolved. Thank you for your patience!

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Management Interface

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-05 12:30 UTC

   We are currently investigating a delay affecting the setup of Pipelines in newly created workspaces in our EU region. Customers creating new workspaces may experience longer than expected wait times before Pipelines become available. Our team is actively working on this and we...

2. monitoring 2026-06-05 13:12 UTC

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

3. resolved 2026-06-05 13:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Data Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-04 23:50 UTC

   We've identified an issue affecting some EU customers' Salesforce and Hubspot syncs. Our team is working on a fix.

2. monitoring 2026-06-05 00:44 UTC

   We have rolled out a fix and we're monitoring closely.

3. resolved 2026-06-05 01:15 UTC

   We confirm the incident is resolved. Thank you for your patience!

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Management Interface

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-04 13:34 UTC

   Our team is aware of this issue and are digging into it right now. We apologize for the inconvenience and will be back with an update as soon as possible.

2. monitoring 2026-06-04 13:39 UTC

   We've got a fix in place, and the UI is available once again. Thank you for your patience!

3. resolved 2026-06-04 13:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Management Interface

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-02 21:18 UTC

   Our team is aware of an issue affecting access to the Customer.io UI and we are working to identify the cause.

2. monitoring 2026-06-02 21:33 UTC

   A fix has been deployed for the issue affecting access to the UI. We are monitoring performance and customer feedback.

3. identified 2026-06-02 22:25 UTC

   Our team has identified additional UI-related issues affecting some customers. We are working on a fix now.

4. monitoring 2026-06-02 22:43 UTC

   We have rolled out a fix for the remaining UI-related issues and are watching system behavior closely.

5. resolved 2026-06-02 22:57 UTC

   The issues affecting the UI have been resolved, and the system is functioning normally.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Data Processing

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-01 11:40 UTC

   We are currently investigating an issue affecting Reverse ETL syncs for some EU customers.

2. monitoring 2026-06-01 11:44 UTC

   A fix has been deployed for the issue affecting Reverse ETL syncs in EU workspaces. We are continuing to monitor this.

3. resolved 2026-06-01 12:11 UTC

   We have confirmed that the incident has been resolved and all Reverse ETL syncs are running as expected. Thanks for your patience!

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Message Sending

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-29 16:26 UTC

   Our engineers are aware of an issue where messages may be showing as "queued". We're investigating this now. Thank you for your patience!

2. identified 2026-05-29 16:40 UTC

   We've identified the issue and are working towards a resolution now.

3. monitoring 2026-05-29 16:51 UTC

   We have a resolution in place and are monitoring message throughput recovery now. Thank you for your patience!

4. resolved 2026-05-29 17:08 UTC

   We have confirmed that this incident is now resolved. Thank you very much for your patience!

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Message Sending

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-25 15:27 UTC

   We are currently investigating this issue.

2. monitoring 2026-05-25 15:58 UTC

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

3. resolved 2026-05-25 16:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Data Collection, Data Processing, Management Interface

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-05-06 16:00 UTC

   Our engineers are looking into an issue where some workspaces aren't loading as expected. Processing and deliveries may be delayed. We're working to get this resolved and will post an update soon. Thank you for your patience!

2. monitoring 2026-05-06 16:14 UTC

   The UI is available as expected, and we are monitoring before marking this as fully resolved. Thank you again for your patience!

3. resolved 2026-05-06 16:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Data Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-20 19:52 UTC

   We are currently investigating an issue impacting Salesforce and Hubspot data-in integrations in the US region.

2. monitoring 2026-04-20 20:04 UTC

   We have identified the issue, released a fix, and are currently monitoring integrations.

3. resolved 2026-04-20 20:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Management Interface

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-20 16:45 UTC

   Our engineers are looking into an issue where some workspaces aren't loading as expected. We're working to get this resolved and will post an update soon. Thank you for your patience!

2. monitoring 2026-04-20 16:50 UTC

   The UI is available as expected, and we are monitoring before marking this as fully resolved. Thank you again for your patience!

3. resolved 2026-04-20 16:55 UTC

   This incident is now resolved. Thank you for your patience and understanding!

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Data Collection, Data Processing, Management Interface

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-17 20:07 UTC

   We are currently investigating this issue.

2. identified 2026-04-17 20:08 UTC

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

3. monitoring 2026-04-17 20:13 UTC

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

4. resolved 2026-04-17 20:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-04-16 21:30 UTC

   Customers who are currently working in our UI are likely to have seen elevated errors or loading. Our engineers are aware, investigated, and have resolved this issue. Thank you for your patience and understanding!

Excerpts are shortened. Read the full incident on Customer.io's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-04-15 20:30 UTC

   We've identified an issue that was preventing the workflow builder from adding Event campaign triggers. This did not affect processing or deliveries for existing campaigns, only the workflow UI experience was impacted. This incident has already been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Management Interface

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-13 18:26 UTC

   Our team is aware of an issue affecting Integrations with destinations in EU/US. We are looking into this and gathering more details. Data import and export is still working, only the UI is effected.

2. identified 2026-04-13 18:28 UTC

   The issue has been identified in the UI and a fix is being deployed.

3. resolved 2026-04-13 18:31 UTC

   A fix has been deployed and the system's functionality is fully restored.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Data Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-07 16:46 UTC

   Some customers in our EU region may be experiencing delays with processing data sent in through our API. Our team is investigating the cause and will provide an update soon. Thank you for your patience!

2. investigating 2026-04-07 17:26 UTC

   We are continuing to investigate this and will be back again as soon as we have an update. Thank you for your continued patience!

3. resolved 2026-04-07 20:53 UTC

   Our engineers have identified the issue and have deployed a resolution. Processing delays are clearing up. Thank you very much for your patience!

Excerpts are shortened. Read the full incident on Customer.io's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-03-26 18:30 UTC

   Some customers in the EU region may have seen errors in the UI and delays of up to 10 minutes in deliveries and data processing.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Management Interface

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-03-18 19:09 UTC

   Our team identified and resolved errors impacting creating and saving campaigns, newsletters, segments in the user interface.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Management Interface

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-16 09:30 UTC

   Customers are unable to add or edit unverified sending domains.

2. identified 2026-03-16 09:38 UTC

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

3. monitoring 2026-03-16 09:48 UTC

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

4. resolved 2026-03-16 09:55 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Data Processing, Message Sending

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-02-23 20:11 UTC

   We're currently investigating an issue that may be impacting some US-based customers, potentially causing UI errors along with delays in processing and message delivery. We appreciate your patience as our team works to get this resolved.

2. monitoring 2026-02-23 20:28 UTC

   A fix has been implemented and we're continuing to monitor for stability. Thank you for your patience!

3. resolved 2026-02-23 20:42 UTC

   This incident has been resolved. We greatly appreciate your patience!

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Data Processing, Message Sending

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-02-19 14:35 UTC

   Our engineers are looking into an issue that may be causing some customers in the EU to experience errors in the UI, as well as delays with processing and message delivery. We greatly appreciate your patience while we work to resolve this.

2. monitoring 2026-02-19 14:38 UTC

   We have a resolution in place now and are continuing to monitor.

3. resolved 2026-02-19 14:44 UTC

   Our engineers have resolved this issue. Thank you very much for your patience!

Excerpts are shortened. Read the full incident on Customer.io's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-13 22:42 UTC

   A subset of customers in US may experience delays on completing reverse ETL syncs.

2. monitoring 2026-02-13 22:51 UTC

   A fix has been implemented and we are monitoring.

3. resolved 2026-02-13 23:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Message Sending

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-28 18:56 UTC

   Our engineers are currently investigating an issue where message sending is delayed. We thank you for your patience and will be back with another update as soon as possible.

2. monitoring 2026-01-28 19:22 UTC

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

3. resolved 2026-01-28 19:26 UTC

   This issue is now resolved. We greatly appreciate your patience while we investigated.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-01-21 20:45 UTC

   Our team is aware of and has identified an issue that is causing our App API to return a 500 error when attempting to download custom exports. We're working on getting a resolution in place, and appreciate your patience.

2. resolved 2026-01-21 20:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Data Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-01-14 16:34 UTC

   Between 16:00 UTC January 13th and 08:00 UTC January 14th our team was alerted to an issue causing long delays completing Salesforce syncs. The issue has now been resolved and we are continuing to monitor.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Data Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-13 12:06 UTC

   We identified a recent change that might cause data delays for some customers in the US. We are currently investigating.

2. investigating 2025-12-13 12:33 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-12-13 13:03 UTC

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

4. resolved 2025-12-13 13:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Management Interface

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-12 17:07 UTC

   Our engineers are looking into this issue now. We sincerely apologize for the inconvenience.

2. identified 2025-12-12 17:20 UTC

   The issue has been identified and we're working towards a resolution now. Thank you for your patience!

3. resolved 2025-12-12 17:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Management Interface

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-09 14:20 UTC

   We are currently investigating an issue preventing the in-app message editor from loading in some accounts.

2. investigating 2025-12-09 14:21 UTC

   We are continuing to investigate this issue.

3. resolved 2025-12-09 15:01 UTC

   The team has identified the issue and released a fix.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Data Processing, Message Sending

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-08 18:12 UTC

   We identified a recent change that might cause data delays. We are investigating.

2. identified 2025-12-08 18:24 UTC

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

3. monitoring 2025-12-08 18:28 UTC

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

4. resolved 2025-12-08 20:19 UTC

   This incident has been resolved.

5. postmortem 2025-12-11 15:45 UTC

   `Incident Summary ` `On December 8th, 2025, beginning at 17:38 UTC, some customers experienced delays in data processing and message delivery. Normal functionality was fully restored at 18:19 UTC, for a total duration of 41 minutes. No data was lost. ` `A failure during the...

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Management Interface

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-24 17:20 UTC

   We are currently investigating reports loading the User Interface (UI) in some workspaces.

2. identified 2025-11-24 17:45 UTC

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

3. resolved 2025-11-24 18:15 UTC

   The team has released a fix and this incident is now resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Message Sending

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-11-24 08:15 UTC

   Our team is aware of an issue with Campaign and Transactional deliveries going out. We are currently looking into this.

2. identified 2025-11-24 08:38 UTC

   We identified the issue, backlog is processing now

3. identified 2025-11-24 08:45 UTC

   Transactional queue backlog is process, priority queue is still ongoing

4. resolved 2025-11-24 08:51 UTC

   We confirm the incident has been resolved. The system is fully operational.

5. postmortem 2025-12-11 16:12 UTC

   **Duration:** 2h 14m, Nov 24 8:08 AM UTC - 10:22 AM UTC\] **Severity:** P2 **Impact:** Reduced message processing rates across US infrastructure ### What Happened On November 24th, our message rendering service experienced degraded performance during a period of high traffic....

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Data Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-21 11:46 UTC

   We are investigating reports of some Form submissions being delayed in the US and EU Data centers. Forms continue to function as expected.

2. investigating 2025-11-21 12:37 UTC

   We are continuing to investigate the issue.

3. monitoring 2025-11-21 12:55 UTC

   The issue has been identified and our team is currently monitoring the service.

4. resolved 2025-11-21 13:09 UTC

   The issue has now been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Management Interface

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. identified 2025-11-18 12:28 UTC

   Customers using the legacy in-app message editor may encounter issues when trying to edit messages. Sending and viewing of existing messages are not affected. The team has identified the root cause and is actively working to restore the functionality.

2. identified 2025-11-18 12:46 UTC

   During the investigation, it was discovered that some customers are experiencing delays in receiving in-app messages.

3. identified 2025-11-18 13:18 UTC

   The team is continuing to work towards a resolution.

4. identified 2025-11-18 13:46 UTC

   Customers may experience issues when verifying new domains associated to Cloudflare. The team is continuing to work towards a resoltuion.

5. identified 2025-11-18 14:16 UTC

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

6. monitoring 2025-11-18 14:43 UTC

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

7. resolved 2025-11-18 14:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.

Affected: Management Interface

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-05 10:09 UTC

   We have received reports of Code Editor emails crashing. Our team is currently investigating

2. monitoring 2025-11-05 10:25 UTC

   Our team has rolled out a fix, and the Code Editor is operational.

3. resolved 2025-11-05 10:29 UTC

   The issue has now been resolved.

Excerpts are shortened. Read the full incident on Customer.io's status page.