Why is my Resend API returning errors?

First check resend.statuspage.io for a reported API incident. If the status page shows all-clear, verify: (1) Your API key is valid and not expired — check the Resend dashboard. (2) Your sending domain has DKIM/SPF DNS records correctly configured in Resend Settings > Domains. (3) You're not hitting rate limits — Resend has per-account sending limits. (4) The 'from' address uses a verified domain. API 401 errors indicate an authentication issue, 422 indicates a validation problem, and 429 indicates rate limiting.

Is Resend reliable for production email sending?

Resend is designed for developer-focused transactional email and has grown rapidly since launch. It's used in production by many startups and scale-ups. For high-reliability production workloads, implement retry logic with exponential backoff, monitor your delivery rates independently, and consider a fallback email provider for critical transactional sends (password resets, payment confirmations).

How do I check Resend API status programmatically?

Resend's status page runs on Statuspage.io and provides a public API at https://resend.statuspage.io/api/v2/status.json. You can poll this endpoint to check current status. Response includes indicator (none/minor/major/critical) and a description. For production monitoring, set up an independent health check on the Resend API endpoint itself.

What should I do if Resend is down and I need to send critical emails?

For critical transactional emails during a Resend outage, you need a pre-configured fallback provider. Many teams keep a secondary Postmark, SendGrid, or AWS SES account ready. Resend's SDK-based architecture makes it relatively easy to swap providers programmatically. At minimum, queue failed sends locally and retry when Resend recovers — avoid dropping critical emails (password resets, 2FA codes) on the floor during outages.

Resend / Developer Email API

Resend Status: How to Check If Resend Is Down Right Now (2026)

Updated June 2026 · 6 min read · API Status Check

Quick Answer

Check Resend status at resend.statuspage.io (official) for real-time API and email delivery status. If the API is returning errors and the status page shows green, check your API key, sending domain DKIM setup, and rate limit usage in the Resend dashboard.

Staff Pick

📡 Monitor your APIs — know when they go down before your users do

Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.

Start Free →

Affiliate link — we may earn a commission at no extra cost to you

The Official Resend Status Page

Resend maintains an official status page at resend.statuspage.io, built on Statuspage.io. It tracks all critical Resend services:

Resend API: The core REST API at api.resend.com — used for all email sends, including the /emails endpoint, batch sends, and email management operations

Email Delivery: The downstream email delivery infrastructure — whether emails sent via the API are actually reaching recipient inboxes or queuing

Resend Dashboard: The resend.com web dashboard — email logs, delivery analytics, domain management, API key management, and team settings

Webhooks: Outbound webhooks for email events — delivered, bounced, complained, clicked, opened. If webhooks are down, your app won't receive real-time delivery callbacks

SMTP Gateway: Resend's SMTP interface for applications using SMTP-based email sending (for teams not using the REST API directly)

What Each Resend Status Means

All Systems Operational: The Resend API, email delivery, and dashboard are all working normally. API calls return 200/2xx, emails are delivered, and webhook callbacks fire. If you're seeing errors, they're specific to your account setup — check API keys, domain auth, and rate limits.

Degraded Performance: Resend is functional but experiencing elevated API latency, slower delivery times, or delayed webhook callbacks. Emails will still be delivered but API calls may take longer and delivery confirmations may lag.

Partial Outage: A specific Resend service is impacted. For example, webhooks may be delayed while the API works fine, or the dashboard may be unavailable while email sending continues. Check which specific component is affected.

Major Outage: The Resend API is broadly unavailable or email delivery has stopped. API requests return 5xx errors or time out. Critical transactional emails (password resets, 2FA codes, payment confirmations) are failing. Activate your fallback email provider immediately.

Under Maintenance: Planned maintenance window. Resend announces scheduled maintenance in advance. API calls during maintenance may fail or experience higher latency. Schedule maintenance-sensitive deployments around these windows.

📡

Recommended

Monitor your Resend API health independently

Better Stack monitors Resend API availability and can alert you the moment email sending breaks — essential for apps where transactional email is mission-critical. Free tier included.

Try Better Stack Free →

Resend API Errors: Platform Outage vs. Account Configuration

When the Resend API returns errors, it's often not a platform outage — it's a configuration issue. Here's how to tell:

API Authentication Errors (401 Unauthorized)

If you're getting 401 errors, your API key is invalid, expired, or was recently rotated. Check your API keys in the Resend dashboard Settings > API Keys. Resend API keys start with 're_'. If you recently rotated your key, ensure the new key is deployed to all services using it.

Domain Verification / DKIM Issues (422 Unprocessable Entity)

Sending from an unverified domain returns a 422 error. In Resend, you must add and verify your sending domain via DNS (DKIM records). Check Resend Settings > Domains for domain status. New DKIM DNS records can take up to 72 hours to propagate, though it's usually under 1 hour.

Rate Limiting (429 Too Many Requests)

Resend applies per-account sending limits depending on your plan. If you're triggering bulk sends in rapid succession, you'll hit rate limits. The response will include retry-after headers. Implement rate-limit-aware sending with queuing (e.g., BullMQ, Redis-backed queues) for high-volume applications.

Emails Accepted but Not Delivered

If the Resend API returns 200 but emails don't arrive, check: (1) Recipient spam/junk folder. (2) Your domain's SPF record includes Resend's mail servers. (3) Whether the recipient domain is rejecting your emails (check Resend delivery logs for bounce reasons). (4) Email reputation: if your domain or IP has been flagged, delivery rates will be low even without API errors.

5 Ways to Check Resend Status Right Now

Official Resend Status Page

Visit resend.statuspage.io for real-time component status and incident history. Subscribe to email notifications for instant outage alerts.

resend.statuspage.io →

Check Resend API Directly

Test the Resend API endpoint directly with a health check. A 200 response confirms the API is reachable.

# Check Resend status via Statuspage.io API
curl -s https://resend.statuspage.io/api/v2/status.json

# Test Resend API health (requires your API key)
curl -s -o /dev/null -w "%{http_code}\n" \
  -H "Authorization: Bearer re_YOUR_API_KEY" \
  https://api.resend.com/emails

# 200 = API healthy, 5xx = platform issue, 401 = auth issue

Check Your Resend Email Logs

In the Resend dashboard, navigate to Emails to see real-time delivery logs. Look for patterns of bounced, failed, or undelivered emails that indicate either a platform issue or a domain/reputation problem specific to your account.

X/Twitter Search

Search 'Resend email down' or 'Resend API outage' on X. Developer communities post immediately when transactional email breaks — it blocks signups and authentication flows.

Search X for 'Resend email down' →

Resend Discord Community

Resend has an active developer Discord where outages and issues are discussed quickly. The Resend team is often responsive in Discord for urgent issues.

Resend Discord →

Common Resend Errors and What They Mean

These are the errors you'll encounter when Resend has issues or your configuration is wrong:

"HTTP 401 — Invalid API Key"Your API key is missing, incorrect, or has been revoked. Verify your API key starts with 're_' and matches an active key in Resend Settings > API Keys. Never hardcode API keys — use environment variables.

"HTTP 422 — You can only send emails from a verified domain"Your 'from' address uses a domain not yet verified in Resend. Add your domain in Resend Settings > Domains, add the required DNS records (DKIM, MX, SPF), and wait for verification.

"HTTP 429 — Too Many Requests"You've exceeded Resend's rate limits for your plan tier. Check your current plan limits in the Resend dashboard. Implement a sending queue (e.g., Redis + BullMQ) to throttle your sending rate.

"HTTP 500 / Connection timeout from api.resend.com"Resend's API infrastructure is experiencing issues. Check resend.statuspage.io for a reported incident. Implement retry logic with exponential backoff — don't drop emails on a 5xx error.

"Email accepted (200 OK) but never delivered"Check your Resend dashboard email logs for bounce reasons. Common causes: recipient address doesn't exist (hard bounce), recipient's mail server rejected your domain (check SPF/DMARC), or email landed in spam (check email content and sending reputation).

"Webhooks not firing for email events"Check the Webhooks component on resend.statuspage.io for a delivery delay. Also verify your webhook endpoint is publicly accessible and returning 200 to Resend's callback. Resend retries failed webhook deliveries.

What to Do When Resend Is Down

Immediate Response

Confirm on resend.statuspage.io before changing any code or config
Queue failed email sends locally rather than dropping them
Switch to your fallback email provider for critical sends (2FA, password reset)
Monitor resend.statuspage.io for incident updates and ETA
Check Resend's Discord for real-time communication from the team

Long-Term Resilience

Implement retry logic with exponential backoff on all Resend API calls
Use a message queue (BullMQ, SQS) for email sends rather than direct API calls
Keep a pre-configured fallback provider (Postmark, SES) for critical transactional sends
Monitor your email delivery rates independently via Resend dashboard metrics
Set up an external health check on the Resend API endpoint

Frequently Asked Questions

Where is the official Resend status page?

Resend's official status page is at resend.statuspage.io. It tracks real-time status for the API, email delivery, dashboard, webhooks, and SMTP. Subscribe to email notifications for automatic incident alerts.

How do I check if Resend is down or if it's my code?

Check resend.statuspage.io for a reported incident first. If the status page shows all-clear, debug your integration: (1) Try the Resend API with curl using your API key directly. (2) Check Resend email logs in the dashboard for specific error details. (3) Test with a minimal API call to isolate the problem. HTTP 401 = auth issue, 422 = domain/validation issue, 429 = rate limit, 5xx = platform issue.

Is Resend suitable for production use?

Resend is widely used in production for transactional email — it's popular among Next.js and React developers due to its developer-first design and React Email integration. For mission-critical transactional sends (2FA, payment confirmations), supplement Resend with retry logic, a sending queue, and optionally a pre-configured fallback provider.

What are the best Resend alternatives if it's down?

For developer-focused transactional email: Postmark (excellent deliverability, strong developer API), SendGrid (high volume, feature-rich), AWS SES (lowest cost at scale). For teams already using React Email templates, Postmark and Resend have the most similar developer experience.

Does Resend support multiple sending domains?

Yes. Resend supports multiple sending domains per account. Each domain requires separate DKIM/SPF DNS verification. You can configure different domains for different projects or environments (production vs. staging). Verified domains are managed in Resend Settings > Domains.

Alert Pro

14-day free trial

Stop checking — get alerted instantly

Next time Resend goes down, you'll know in under 60 seconds — not when your users start complaining.

Email alerts for Resend + 9 more APIs
$0 due today for trial
Cancel anytime — $9/mo after trial

Start Free Trial →Compare all plans →

Also recommended:

Better Stack — all-in-one monitoring 1Password — secure your API keys