Skip to main content
Customer.io logo

Is Customer.io Down?

No — Customer.io is up

Reachable from all 8 checked regions

Average response time: 201ms

Last checked · checks run every 6 hours

Official status page: https://status.customerio.com

Customer.io uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
237ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 8 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

8-day clean streak
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: no data
Sep 18: no data
Sep 19: no data
Sep 20: no data
Sep 21: no data
Sep 22: no data
Sep 23: no data
Sep 24: no data
Sep 25: no data
Sep 26: no data
Sep 27: no data
Sep 28: no data
Sep 29: no data
Sep 30: no data
Oct 1: no data
Oct 2: no data
Oct 3: no data
Oct 4: no data
Oct 5: no data
Oct 6: 100.00% uptime, 16 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
334ms
DNS 132ms TCP 8ms TLS 27ms TTFB 243ms
arn
220ms
DNS 38ms TCP 4ms TLS 13ms TTFB 111ms
cdg
205ms
DNS 39ms TCP 8ms TLS 15ms TTFB 160ms
dfw
219ms
DNS 47ms TCP 1ms TLS 52ms TTFB 170ms
ewr
132ms
DNS 43ms TCP 1ms TLS 19ms TTFB 116ms
fra
88ms
DNS 13ms TCP 1ms TLS 9ms TTFB 70ms
syd
229ms
DNS 166ms TCP 1ms TLS 7ms TTFB 221ms
yyz
181ms
DNS 17ms TCP 12ms TLS 35ms TTFB 131ms

What Customer.io does

Customer.io is a messaging automation platform. Companies send it customer data and events through its Track API, Data Pipelines and JavaScript or mobile libraries, then use that data to send targeted email, push notifications, SMS, in-app messages and webhooks. Each account's data lives in either the US or the EU region, chosen at sign-up, and both are managed through the same web app at fly.customer.io.

What an outage looks like

The web app at fly.customer.io fails to load or shows errors, campaign and broadcast messages sit as queued or go out late, and new events and attribute changes take longer to appear on people's profiles. Integrations such as Salesforce and HubSpot syncs or Reverse ETL can fall behind, and API requests can fail. Incidents often hit only one region, so EU accounts can be affected while US accounts are fine.

What to do about it

Check status.customerio.com, which has separate rows for Data Collection (the Track API), Data Processing, Message Sending and the Management Interface, and see whether the incident names the US or EU region. The in-app Workspace performance dashboard shows delays for your own workspace. Customer.io's incident updates describe delayed backlogs being processed once a fix is out, so check a message's delivery status before re-sending it by hand.

Is it down for everyone, or just you?

If this page says Customer.io is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Braze
Braze
Klaviyo
Klaviyo
SendGrid (Twilio)
SendGrid (Twilio)
Twilio
Twilio

Customer.io outage FAQ

Is Customer.io down for everyone or just my region?
Check which region the incident names, because many Customer.io incidents affect only US or only EU accounts. Your region was set when the account was created, and EU accounts call API hosts with an -eu suffix, such as track-eu.customer.io. The checks on this page probe customer.io, the company website, so the app at fly.customer.io or the tracking APIs can have problems while they stay green.
Will delayed Customer.io messages still be sent?
Usually yes. During delivery incidents Customer.io's updates describe processing delayed backlogs once a fix is deployed, and a postmortem for a 41-minute processing delay stated that no data was lost. A message marked Attempted after a transient error is retried automatically with exponential backoff, up to 11 times over about an hour. Messages marked Failed never left Customer.io and can be retried from the delivery page.
Do events sent to Customer.io during an outage get lost?
Not from the JavaScript client, which retries network and server errors automatically and stores events in the browser's localStorage, or in memory, while it cannot reach Customer.io. Events then go out when the connection returns. Customer.io also redirects US-endpoint Track API calls for EU accounts so they do not fail. Server-side code that calls the API directly should retry failed requests itself.
Will Customer.io retry reporting webhooks to my server?
Yes, for up to 7 days. Customer.io waits 4 seconds for a 2xx response and, if it does not get one, retries the webhook with exponential backoff over a period of 7 days. Responses such as 429, 500 or 502, refused connections and certificate errors put the call in a batch that is retried after an hour, so a short outage on your side does not drop delivery events.
How long do Customer.io outages usually last?
Most are short. Of the 50 most recent incidents on Customer.io's status page, 44 were marked resolved within two hours of being opened and 49 within four, with a typical incident lasting about half an hour. You can subscribe to updates on status.customerio.com by email, text message or RSS instead of refreshing the page.

How we measure this

  • We request Customer.io's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Customer.io publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Customer.io goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required