APIs: messaging, media, analytics
Degraded / minor incident Customer.io status
customer.io · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
Customer.io's status page shows “Degraded / minor incident” in Message Sending and Data Collection; the vendor is resolved. User reports haven't spiked, so wide impact isn't visible yet.
confidence: low Vendor: minor issue · users: normal · routing: no data.
- Vendor status page Degraded / minor incident · 10 open incidents
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Message Sending, Data Collection, Data Processing
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 121 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | 2 h 19 min |
Evidence
- Official page: Degraded / minor incident (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “Reduced Deliverability to Microsoft-Hosted Email Addresses”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside Customer.io's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: minor issue · users: normal · routing: no data. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).
Who depends on whom
We don't map other services that depend on Customer.io. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Customer.io, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Customer.io. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Reduced Deliverability to Microsoft-Hosted Email Addresses
none resolved · started · resolved
3 updates
- investigating
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!
- monitoring
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.
- resolved
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.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.