Incident report for February 15, 2026

On February 15, 2026, Resend experienced a significant incident that led to email sending delays and dashboard loading errors due to database connection exhaustion, lasting 3 hours and 31 minutes before full recovery was achieved. Although no emails were lost, most were delayed by about 2 hours on average, with the dashboard becoming inaccessible. The issue was caused by a spike in database connections due to a lack of configuration, leading to idle connections not being released quickly enough under load. Resend resolved the issue by reducing connection pool sizes, limiting idle connection times, and setting stricter connection limits per database role. They also scaled up compute resources and addressed the number of connections for the affected application, enabling the platform to recover and reprocess delayed emails. Moving forward, Resend plans to enhance database connection resilience and improve their incident response processes to prevent similar occurrences.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.