CHYP.ai · ORBIT // Cloudy_Day Security Suite

APIs: messaging, media, analytics

Operational Resend status

resend.com · Official status page (Statuspage-compatible JSON)

FROM ALL SOURCES

Resend looks fine itself, but Amazon Web Services, a provider it may run on (inferred), reports major outage. Watch for knock-on effects.

confidence: low Vendor: operational · users: normal · routing: no data · upstream providers: major.

Vendor status vs. reality: Vendor status and outside signals roughly agree
The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started8 days
Crowd clock when user reports began rising above normalnot seenn/a
Network clock when routing anomaly data first flagged itnot seenn/a
ORBIT clock when our checker first recorded the changenot seenn/a

Evidence

  • Official page: Operational (“All Systems Operational”). evidence confidence: high
  • Vendor stage: resolved on “Microsoft 365 Incident”. evidence confidence: high
  • User reports are within normal range (0 in 15 min). evidence confidence: low
  • Amazon Web Services reports an issue. Resend may depend on it (inferred from public sources). Coincidence, not causation. evidence confidence: low

What we don't know: what is happening inside Resend's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.

Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.

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: operational · users: normal · routing: no data · upstream providers: major. Vendor status and outside signals roughly agree.

Who depends on whom

Resend may run on Amazon Web Services (inferred). We don't map other services that depend on Resend. 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 Resend or its upstream providers, 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 Resend. No blame or attack claims without an official source. Generated .

INCIDENT REPLAY

Microsoft 365 Incident

minor resolved · started · resolved

9 updates

  1. monitoring

    [Microsoft 365 is currently experiencing an incident](https://status.cloud.microsoft/), which is degrading its ability to accept email. While this is not a Resend incident, it is possible to see an elevated amount of “Delivery Delay” events if Microsoft is unable to accept the email. With our Delivery Delayed events, we will retry delivery. Once Microsoft resolves its incident, sending to these addresses will return to normal.

  2. monitoring

    We’re continuing to monitor delivery to Microsoft-hosted inboxes as they work to resolve the incident. Emails in a “Delivery Delayed” status will continue to be retried and delivered once Microsoft resolves the incident.

  3. monitoring

    Microsoft continues to work on restoring its services. We are monitoring delivery attempts there. Emails in “Delivery Delayed” status will continue to be retried.

  4. monitoring

    Microsoft is still working to resolve the incident affecting email delivery to Microsoft 365. Emails to Microsoft-hosted addresses may continue to show a “Delivery Delayed” status. There’s no need to retry them: we’re retrying automatically, and they’ll be delivered once Microsoft is accepting mail again. We’ll post another update as Microsoft’s status changes.

  5. monitoring

    Microsoft’s incident is ongoing, and they haven’t yet given an estimate for full recovery. We’re continuing to retry emails to Microsoft-hosted addresses that show a “Delivery Delayed” status. There’s no need to retry these. If Microsoft’s outage continues past our retry window, some of these emails may bounce. You’ll receive a bounce event for each one, and you can retry those emails once Microsoft recovers.

  6. monitoring

    Microsoft’s incident is still ongoing, and their team continues to work toward recovery. We’re beginning to see a small number of new emails being accepted by Microsoft. We’ll continue to automatically retry affected emails. If the incident extends beyond our retry window, some emails may bounce. You’ll receive a bounce event for each affected email, and you can safely retry sending those messages once Microsoft has fully recovered.

  7. monitoring

    We’re seeing an increasing number of emails being accepted by Microsoft. We’ll continue to monitor the situation closely and provide further updates as progress continues.

  8. monitoring

    Microsoft’s ability to accept email has improved, and we’re now seeing successful deliveries to Microsoft-hosted addresses. Emails in a “Delivery Delayed” status are being delivered as we retry them. We’ll keep monitoring delivery to Microsoft until it’s fully back to normal.

  9. resolved

    Email delivery to Microsoft-hosted addresses has returned to normal, and we’ve delivered emails that were in a “Delivery Delayed” status after retrying them. Microsoft is still recovering, so a small number of messages may take a little longer to arrive. As always, we’ll continue monitoring delivery to Microsoft.

Official incident page ↗

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.

Where to next