Rewindex

CompaniesResendIncidents

Resend: Delayed new team provisioning and contact webhook delivery

MinorStatus: resolvedStarted Resolved (23 min)3 updatesresend-status.com (opens in new tab)
Part of an outage event

AWS us-east-1 outage, Oct 9, 2026 · 17 vendors, 18 incidents

Resend’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted −46 min vs the first vendor naming AWS)

Swipe sideways to see the whole diagram.

same windowAWS us-east-1own incident not archivedWithin an hour5 vendors, 2 blamed AWSConvex, Temporal Cloud, JFrog, PlanetScale +1Later1 vendor, 1 blamed AWSChargebeeResend (this incident)posted −46 min
same windowAWS us-east-1own incident not archivedWithin an hour5 vendors, 2 blamed AWSConvex, Temporal Cloud,JFrog, PlanetScale +1Later1 vendor, 1 blamed AWSChargebeeResend (this incident)posted −46 min
Resend is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS us-east-1<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>5 vendors, 2 blamed AWS<br/>Convex, Temporal Cloud, JFrog, PlanetScale +1"]:::blames
  root --> h1
  later["Later<br/>1 vendor, 1 blamed AWS<br/>Chargebee"]:::blames
  root --> later
  me["Resend (this incident)<br/>posted −46 min"]:::me
  root -.->|"same window"| me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: DashboardGeneral APIWebhooks

Timeline of updates

  1. identified

    We've identified an issue on our infrastructure affecting new team provisioning and contact webhook delivery. Email sending and receiving is not affected. • Newly created teams may take longer to have their account resources fully setup. • Some webhooks related to contact activity are being delivered with a delay. Our team is working on fixing this issue.

  2. monitoring

    Our team is monitoring to ensure the issue has been fixed.

  3. resolved

    We have resolved the underlying issue and service has been resumed.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on resend-status.com (opens in new tab).

Resend profileRecent Resend incidentsMarkdownJSON