Resend: API logs are delayed
Is it fixed? Not yet.
Ongoing since Nov 19, 11:04 UTC. First reported Nov 19, 11:04 UTC. The vendor posted it on its status page first.
What happened
Resend is investigating increased latency in persisting API request logs, resulting in delays of up to 15 minutes. All API endpoints remain fully responsive and no data loss has been reported.
What caused it?
Under active investigation. No report has identified a root cause yet.
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Official fixTimeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
Evidence
1 report · 1 StatusShow
- [1]Status First reportAPI logs are delayed(opens official status page in a new tab)
Status: Investigating We are currently investigating increased latency in persisting API request logs. They can appear up to 15 minutes late. No data has been lost, and all API endpoints are responding normally. Affected components General API (Degraded performance)
by resend status
FAQ
What happened in the Resend outage?
Resend is investigating increased latency in persisting API request logs, resulting in delays of up to 15 minutes. All API endpoints remain fully responsive and no data loss has been reported.
What is affected by the Resend outage?
Resend.
When did the Resend outage start and end?
It started Nov 19, 11:04 UTC and is still ongoing (44 min so far). This page updates as it develops.
How do I get alerts for Resend?
Subscribe to the Resend RSS feed for every new Resend incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Resend is down. Resend feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source, including the vendor’s own status page.