On this page
Is Customer.io Down? How to Tell and What to Do
Customer.io is a marketing automation and messaging platform that sends behavioral emails, SMS, and push notifications based on user events. When it goes down, campaigns don't fire, event-triggered messages miss their delivery window, and transactional messages that users expect — like password resets and signup confirmations — can fail silently.
Statusfield brings reported Customer.io incidents into the same workspace as your other monitors. Select supported components and route relevant changes to your team. Vendor reports can lag an incident, so check your own application as well.
Follow Customer.io incidents with your team
Statusfield brings reported status for Customer.io together with your other critical tools. Choose the changes that should alert your team. Eligible new accounts can start a free trial — no credit card required.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.
Common Signs of a Customer.io Outage
| Symptom | What's likely happening |
|---|---|
| Triggered emails not sending | Message delivery pipeline is degraded |
| Events not appearing in Customer.io | Event ingestion API is failing |
| Campaigns not firing on schedule | Campaign scheduler or delivery layer is degraded |
| Customer.io dashboard won't load | Web application layer is unavailable |
| Broadcasts not delivering | Bulk sending infrastructure is degraded |
| SMS messages delayed or undelivered | SMS delivery connector is failing |
| Transactional messages (password reset, etc.) not arriving | Transactional delivery path is degraded |
How to Confirm It's Customer.io, Not You
1. Test event ingestion with a manual API call
Send a test event via the Customer.io API directly (or via curl). If the API returns a 5xx error or times out, the ingestion layer is down — not your application's integration.
2. Check the activity log in Customer.io
Navigate to the Customers section and check the activity log for a recent customer. If events that your application is sending aren't appearing, the ingestion pipeline has a backlog or is failing.
3. Send a test message manually
Use the "Send test" button on a campaign or broadcast. If a test message fails to deliver to your own address within 5 minutes, the delivery layer is degraded.
4. Check for event backlog warnings
Customer.io displays warnings when event queues are backing up. If you see "processing delay" alerts in the dashboard, the pipeline is degraded even if events appear to be accepting.
Use vendor reports as investigation context
Statusfield brings reported Customer.io incidents into the same workspace as your other monitors. Select supported components and route relevant changes to your team. Vendor reports can lag an incident, so check your own application as well.
A reported incident can help you decide where to investigate and what to tell your team. An operational status does not prove that your account, region or complete workflow is working. Review the affected components and timestamps alongside your own logs and checks.
What to Do During a Customer.io Outage
Immediate (first 5 minutes)
- Identify which path is affected — is it event ingestion, triggered messages, scheduled campaigns, or all of them? Each has different urgency.
- Pause time-sensitive broadcasts — if a broadcast is scheduled to fire during the outage window, delay it. A broadcast that fires against a degraded delivery layer will show high soft-bounce rates.
- Check transactional message delivery — if password resets or verification emails are in the affected path, users will be blocked from your product. Escalate to Customer.io support immediately if transactional is down.
- Do not retry failed sends manually — queued messages will typically process once the service recovers. Manual retries during a delivery degradation can cause duplicate sends.
Communication (first 15 minutes)
- Alert your product and growth teams — triggered onboarding flows and lifecycle campaigns may be silently failing.
- If transactional messages (auth, verification) are affected, notify your support team to expect elevated "didn't receive email" tickets.
- For campaign teams with active A/B tests, pause the test — skewed delivery during an outage will contaminate results.
Recovery
- After Customer.io recovers, check the event backlog — events queued during the outage may trigger messages in a burst.
- Review campaign send counts for the outage window to identify gaps in delivery.
- For transactional messages, check whether users who failed to receive emails require a manual resend or support follow-up.
- Verify A/B test sample sizes are balanced before resuming any paused tests.
Customer.io Components and What Each Outage Looks Like
| Component | Impact when degraded |
|---|---|
| Event ingestion API | User events not being received; triggers won't fire |
| Triggered message delivery | Behavioral emails/SMS not sending on event receipt |
| Campaign scheduler | Scheduled campaigns not firing at their set time |
| Broadcast delivery | Bulk sends delayed or partially delivered |
| SMS / push connector | SMS or push messages not delivering |
| Transactional delivery path | Password resets, confirmations, and alerts not sending |
| Web application | Dashboard inaccessible; no campaign visibility |
Transactional message failure is highest-severity — it breaks core product flows for users. Event ingestion failures are high-severity for behavioral campaigns but lower for scheduled ones.
Bring Customer.io updates to your team
Follow reported Customer.io status in Statusfield and choose which changes reach your configured alert destinations. Delivery depends on source updates, polling and successful processing. Check the catalog for supported components and the pricing page for channel availability.
Eligible first-time customers can start a free trial, no credit card required.
Follow Customer.io incidents with your team
Follow Customer.io and your other vendors in one Statusfield workspace. Select supported components and route the updates your team needs. Eligible new accounts can start a free trial — no credit card required.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.
FAQ
Is Customer.io down right now?
This article is a troubleshooting guide, not a live outage verdict. Check the Statusfield catalog and the official vendor status page for the latest reported status, affected components and observation times. Compare those reports with what your own application is experiencing.
How can I get alerts about Customer.io incidents?
Follow reported Customer.io status in Statusfield and choose which changes reach your configured alert destinations. Delivery depends on source updates, polling and successful processing. Check the catalog for supported components and the pricing page for channel availability.
Does an operational Customer.io status mean my application is working?
No. A vendor status page describes reported service conditions. Your account, integration, network or application can still fail. Check your own public HTTPS endpoint and use logs or workflow tests to investigate the customer experience.
Browse the service catalog and plans and alert destinations.
Keep your vendors in view.
Choose from 7,000+ services, follow the components you use, and configure alerts for your team.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.