Customer.io Outage History

Customer.io is up right now

Pingoru has recorded 67 incidents for Customer.io: 56 in the last 12 months and 6 in the last 90 days.

Source: status.customerio.com

67incidents recorded
56last 12 months
6last 90 days
69 minutestypical duration
Incidents per month
0510AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Customer.io 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 202675 of 720 (1%)
May 202632 of 744 (0%)
June 2026910 of 720 (1%)
July 2026810 of 744 (1%)
August 202621 of 744 (0%)
September 202632 of 720 (0%)
October 202600 of 590 (0%)

Incidents, newest first

Major April 20, 2026 Delay in Salesforce & Hubspot data-in integrations 14m Data Processing

Started Apr 20, 2026, 07:52 PM UTC· resolved Apr 20, 2026, 08:06 PM UTC

  1. investigating Apr 20, 2026, 07:52 PM UTC

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

  2. monitoring Apr 20, 2026, 08:04 PM UTC

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

  3. resolved Apr 20, 2026, 08:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 20, 2026 Customer.io UI is currently unavailable for some customers 10m Management Interface

Started Apr 20, 2026, 04:45 PM UTC· resolved Apr 20, 2026, 04:55 PM UTC

  1. investigating Apr 20, 2026, 04:55 PM 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 Apr 20, 2026, 05:03 PM 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 Apr 20, 2026, 05:35 PM UTC

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

Read the full incident report →

Notice April 16, 2026 Customer.io UI currently experiencing issues 12m

Started Apr 16, 2026, 09:17 PM UTC· resolved Apr 16, 2026, 09:30 PM UTC

  1. resolved Apr 16, 2026, 09:17 PM 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!

Read the full incident report →

Notice April 15, 2026 Unable to create event-driven campaigns –

Started Apr 15, 2026, 08:30 PM UTC· resolved Apr 15, 2026, 08:30 PM UTC

  1. resolved Apr 15, 2026, 09:06 PM 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.

Read the full incident report →

Major April 13, 2026 Integration Destinations UI Disruption 5m Management Interface

Started Apr 13, 2026, 06:26 PM UTC· resolved Apr 13, 2026, 06:31 PM UTC

  1. investigating Apr 13, 2026, 06:26 PM 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 Apr 13, 2026, 06:28 PM UTC

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

  3. resolved Apr 13, 2026, 06:31 PM UTC

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

Read the full incident report →

Minor April 7, 2026 EU Region API Processing Delays 4h 7m Data Processing

Started Apr 07, 2026, 04:46 PM UTC· resolved Apr 07, 2026, 08:53 PM UTC

  1. investigating Apr 07, 2026, 04:46 PM 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 Apr 07, 2026, 05:26 PM 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 Apr 07, 2026, 08:53 PM UTC

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

Read the full incident report →

Notice March 18, 2026 UI Errors Identified – Management Interface

Started Mar 18, 2026, 07:09 PM UTC· resolved Mar 18, 2026, 07:09 PM UTC

  1. resolved Mar 18, 2026, 07:09 PM UTC

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

Read the full incident report →

Minor March 16, 2026 Domain Verification Currently Unavailable 25m Management Interface

Started Mar 16, 2026, 09:30 AM UTC· resolved Mar 16, 2026, 09:55 AM UTC

  1. investigating Mar 16, 2026, 09:30 AM UTC

    Customers are unable to add or edit unverified sending domains.

  2. identified Mar 16, 2026, 09:38 AM UTC

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

  3. monitoring Mar 16, 2026, 09:48 AM UTC

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

  4. resolved Mar 16, 2026, 09:55 AM UTC

    The issue has been resolved.

Read the full incident report →

Minor February 23, 2026 Some customers in our US region may experience errors and delays 31m Data Processing, Message Sending

Started Feb 23, 2026, 08:11 PM UTC· resolved Feb 23, 2026, 08:42 PM UTC

  1. identified Feb 23, 2026, 08:11 PM 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 Feb 23, 2026, 08:28 PM UTC

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

  3. resolved Feb 23, 2026, 08:42 PM UTC

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

Read the full incident report →

Notice February 13, 2026 Reverse ETL syncs may experience delays in US 20m

Started Feb 13, 2026, 10:42 PM UTC· resolved Feb 13, 2026, 11:02 PM UTC

  1. identified Feb 13, 2026, 10:42 PM UTC

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

  2. monitoring Feb 13, 2026, 10:51 PM UTC

    A fix has been implemented and we are monitoring.

  3. resolved Feb 13, 2026, 11:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 28, 2026 Some customers are experiencing delays with message sending 29m Message Sending

Started Jan 28, 2026, 06:56 PM UTC· resolved Jan 28, 2026, 07:26 PM UTC

  1. investigating Jan 28, 2026, 06:56 PM 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 Jan 28, 2026, 07:22 PM UTC

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

  3. resolved Jan 28, 2026, 07:26 PM UTC

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

Read the full incident report →

Notice January 21, 2026 Issue with downloading exports from our App API 10m

Started Jan 21, 2026, 08:45 PM UTC· resolved Jan 21, 2026, 08:55 PM UTC

  1. identified Jan 21, 2026, 08:45 PM 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 Jan 21, 2026, 08:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 14, 2026 Delays with Salesforce Syncs 16h Data Processing

Started Jan 14, 2026, 04:00 PM UTC· resolved Jan 15, 2026, 08:00 AM UTC

  1. resolved Jan 14, 2026, 04:34 PM 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.

Read the full incident report →

Minor December 13, 2025 Customers may be impacted by data delays 1h 30m Data Processing

Started Dec 13, 2025, 12:06 PM UTC· resolved Dec 13, 2025, 01:37 PM UTC

  1. investigating Dec 13, 2025, 12:06 PM UTC

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

  2. investigating Dec 13, 2025, 12:33 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Dec 13, 2025, 01:03 PM UTC

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

  4. resolved Dec 13, 2025, 01:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 12, 2025 Some customers are experiencing issues with saving their content 18m Management Interface

Started Dec 12, 2025, 05:07 PM UTC· resolved Dec 12, 2025, 05:25 PM UTC

  1. investigating Dec 12, 2025, 05:07 PM UTC

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

  2. identified Dec 12, 2025, 05:20 PM UTC

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

  3. resolved Dec 12, 2025, 05:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 9, 2025 Intermittent issues loading the in-app message editor. 40m Management Interface

Started Dec 09, 2025, 02:20 PM UTC· resolved Dec 09, 2025, 03:01 PM UTC

  1. investigating Dec 09, 2025, 02:20 PM UTC

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

  2. investigating Dec 09, 2025, 02:21 PM UTC

    We are continuing to investigate this issue.

  3. resolved Dec 09, 2025, 03:01 PM UTC

    The team has identified the issue and released a fix.

Read the full incident report →

Minor November 24, 2025 Trouble loading User Interface in some workspace 54m Management Interface

Started Nov 24, 2025, 05:20 PM UTC· resolved Nov 24, 2025, 06:15 PM UTC

  1. investigating Nov 24, 2025, 05:20 PM UTC

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

  2. identified Nov 24, 2025, 05:45 PM UTC

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

  3. resolved Nov 24, 2025, 06:15 PM UTC

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

Read the full incident report →

Minor November 24, 2025 US infrastructure delays with a subset of deliveries sending 36m Message Sending

Started Nov 24, 2025, 08:15 AM UTC· resolved Nov 24, 2025, 08:51 AM UTC

  1. investigating Nov 24, 2025, 08:15 AM UTC

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

  2. identified Nov 24, 2025, 08:38 AM UTC

    We identified the issue, backlog is processing now

  3. identified Nov 24, 2025, 08:45 AM UTC

    Transactional queue backlog is process, priority queue is still ongoing

  4. resolved Nov 24, 2025, 08:51 AM UTC

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

  5. postmortem Dec 11, 2025, 04:12 PM 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. The service, which renders your messages for delivery, encountered memory constraints that caused intermittent service restarts and slower processing rates for priority queues across our US infrastructure. ### Customer Impact * **Affected Services:** All message types including campaigns, transactional messages, and journey workflows **Date:** November 24, 2025 * **Geographic Scope:** US-based workspaces * **Performance Impact:** Message processing slowed to approximately 50% of normal capacity during peak impact * **Duration:** 2 hours 14 mins of degraded performance * **Data Integrity:** No messages were lost; all queued messages were successfully processed ### Root Cause Our message rendering service runs on an auto-scaling infrastructure that automatically adjusts capacity based on workload. During this incident, sudden traffic spikes caused individual servers to consume memory faster than our auto-scaling could compensate. When servers reached memory limits, they restarted automatically \(as designed for resilience\), but these rolling restarts reduced our overall processing capacity during a time of peak demand, creating a compound effect. ### Resolution **Immediate fix:** We deployed updated code to our rendering service that better manages memory consumption during traffic bursts, preventing the cascade of restarts that degraded performance. **Why this works:** The update implements more efficient memory allocation patterns and adds throttling mechanisms that prevent any single traffic burst from overwhelming individual servers, regardless of auto-scaling speed. ### What We're Doing to Prevent This 1. **Smarter Resource Management** \(Completed\) * Deployed code optimizations that prevent memory exhaustion during traffic spikes * Implemented per-node workload throttling to maintain stability 2. **Improved Auto-scaling** \(In Progress - Q1 2026\) * Tuning our auto-scaling to be more predictive rather than reactive * Increasing baseline capacity to handle larger bursts without scaling delays 3. **Better Early Warning** \(In Progress\) * Adding memory pressure alerts that trigger before critical thresholds * Implementing graduated responses to traffic spikes \(pre-scaling based on queue depth trends\) ### Our Commitment While our platform maintained data integrity throughout this incident \(no messages were lost\), we understand that processing delays impact your customer engagement timing. We are actively working to ensure all customers’ messages are processed and delivered as efficiently and reliably as possible. ### Questions? Your Customer Success Manager has details specific to your workspace's impact during this incident. For technical questions or to discuss our infrastructure roadmap, please reach out to your account team.

Read the full incident report →

Minor November 21, 2025 Forms submissions experiencing intermittent delays 1h 22m Data Processing

Started Nov 21, 2025, 11:46 AM UTC· resolved Nov 21, 2025, 01:09 PM UTC

  1. investigating Nov 21, 2025, 11:46 AM 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 Nov 21, 2025, 12:37 PM UTC

    We are continuing to investigate the issue.

  3. monitoring Nov 21, 2025, 12:55 PM UTC

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

  4. resolved Nov 21, 2025, 01:09 PM UTC

    The issue has now been resolved.

Read the full incident report →

Minor November 18, 2025 Legacy in-app editing, delays receiving in-app messages and Journeys domain verification with Cloudflare 2h 22m Management Interface

Started Nov 18, 2025, 12:28 PM UTC· resolved Nov 18, 2025, 02:51 PM UTC

  1. identified Nov 18, 2025, 12:28 PM 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 Nov 18, 2025, 12:46 PM UTC

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

  3. identified Nov 18, 2025, 01:18 PM UTC

    The team is continuing to work towards a resolution.

  4. identified Nov 18, 2025, 01:46 PM UTC

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

  5. identified Nov 18, 2025, 02:16 PM UTC

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

  6. monitoring Nov 18, 2025, 02:43 PM UTC

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

  7. resolved Nov 18, 2025, 02:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 5, 2025 Code Editor is freezing unexpectedly 20m Management Interface

Started Nov 05, 2025, 10:09 AM UTC· resolved Nov 05, 2025, 10:29 AM UTC

  1. investigating Nov 05, 2025, 10:09 AM UTC

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

  2. monitoring Nov 05, 2025, 10:25 AM UTC

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

  3. resolved Nov 05, 2025, 10:29 AM UTC

    The issue has now been resolved.

Read the full incident report →

Minor November 4, 2025 Some workspaces experiencing delays in campaign journeys and deliveries in US Data Center 1h 7m Data Processing, Message Sending

Started Nov 04, 2025, 08:46 PM UTC· resolved Nov 04, 2025, 09:54 PM UTC

  1. investigating Nov 04, 2025, 08:46 PM UTC

    We are currently investigating this issue.

  2. monitoring Nov 04, 2025, 09:12 PM UTC

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

  3. resolved Nov 04, 2025, 09:54 PM UTC

    This incident has been resolved.

  4. postmortem Nov 13, 2025, 07:36 PM UTC

    # **Incident Summary** On November 4, 2025, between 20:10 UTC and 21:54 UTC, some customers with our US data center may have experienced delays in message sending. This issue did not affect data ingestion and no data was lost. A configuration change caused a failure in processing attribute updates from campaign attribute & webhook actions resulting in campaign journeys stalling. The configuration change was reverted, restoring the attribute update processing and message sending. # **Root Cause** A configuration change to the internal authentication system used for inter-service communication unexpectedly caused our services responsible for attribute processing to fail, leading to a backlog in message sending. # **Resolution and Recovery** Engineers reverted the configuration change at 21:07 UTC, allowing attribute processing to resume successfully. The team monitored the system until confirming recovery at 21:54 UTC. # **Corrective and Preventative Measures** To improve resilience, the team is enhancing monitoring to detect early signs of attribute processing faults and updating alerting to provide clearer failure context and faster remediation. These measures are being tracked and prioritized within our internal development process.

Read the full incident report →

Minor October 31, 2025 Issue preventing some workspaces from loading in the US 23m Management Interface

Started Oct 31, 2025, 05:48 PM UTC· resolved Oct 31, 2025, 06:12 PM UTC

  1. investigating Oct 31, 2025, 05:48 PM UTC

    We are currently investigating an issue impacting loading of the user interface for some workspaces in the US

  2. identified Oct 31, 2025, 06:01 PM UTC

    The issue has been identified and we are working on a fix

  3. monitoring Oct 31, 2025, 06:06 PM UTC

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

  4. resolved Oct 31, 2025, 06:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 30, 2025 Some US customers may be impacted by data delays and UI errors 4h 32m Data Processing, Message Sending, Management Interface

Started Oct 30, 2025, 05:25 PM UTC· resolved Oct 30, 2025, 09:58 PM UTC

  1. investigating Oct 30, 2025, 05:25 PM UTC

    Some US customers will experience errors in the UI and delays in data processing and sending. We do not anticipate any data loss.

  2. investigating Oct 30, 2025, 06:05 PM UTC

    We are continuing to investigate this issue.

  3. identified Oct 30, 2025, 06:34 PM UTC

    The issue has been identified and a fix is being worked on. Some US customers will continue to experience errors in the UI and delays in data processing and sending. No data loss is anticipated.

  4. identified Oct 30, 2025, 07:03 PM UTC

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

  5. identified Oct 30, 2025, 07:34 PM UTC

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

  6. identified Oct 30, 2025, 08:03 PM UTC

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

  7. identified Oct 30, 2025, 08:11 PM UTC

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

  8. identified Oct 30, 2025, 08:41 PM UTC

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

  9. identified Oct 30, 2025, 09:11 PM UTC

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

  10. monitoring Oct 30, 2025, 09:48 PM UTC

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

  11. resolved Oct 30, 2025, 09:58 PM UTC

    This incident has been resolved.

  12. postmortem Nov 06, 2025, 10:31 PM UTC

    # **Incident Summary** On October 30th, 2025, between 17:12 UTC and 22:10 UTC, some customers with our US data center may have experienced delays in data processing, message sending and user interface errors. This issue did not affect data ingestion and no data was lost. A kernel-level issue caused file system corruption for a database in our cluster which resulted in a database crash. Using internal recovery procedures, we restored service and confirmed full data integrity. # **Root Cause** A filesystem related fault occurred on one of the production databases that stores customer journey information caused the service to fail when reading certain data. Under normal conditions, a replica database would maintain continuity of service. However, in this instance, the database experienced replication lag which prevented an immediate failover. This resulted in a longer recovery period. # **Resolution and Recovery** Engineers repaired and validated the affected database, ensuring data integrity throughout the recovery process. Using recent copies of the data, the team restored the impacted areas, verified system health, and restarted dependent services to confirm normal operation. Following the restoration, a replica database was rebuilt. # **Corrective and Preventative Measures** To ensure greater resilience, the team is enhancing database monitoring to detect early signs of filesystem related faults, updating database recovery strategies based on learnings from this incident, and increasing the frequency of recovery drills to validate new procedures. These measures are being tracked and prioritized within our internal development process.

Read the full incident report →

Minor October 29, 2025 Delayed Workspace Performance 9m Data Processing, Message Sending, Management Interface

Started Oct 29, 2025, 08:02 PM UTC· resolved Oct 29, 2025, 08:12 PM UTC

  1. investigating Oct 29, 2025, 08:02 PM UTC

    We are currently investigating an issue where some customer may see delays in data processing and message sending in the US.

  2. monitoring Oct 29, 2025, 08:02 PM UTC

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

  3. resolved Oct 29, 2025, 08:12 PM UTC

    This incident has been resolved.

Read the full incident report →