Skip to content

Outage tracker / Resend

Is Resend down?

I'm having a problem

Vendor reports no incidentWhat Resend reports

Resend reports no incident on its status page.

As of the last successful poll, 2026-10-23 08:47 UTC.

Resend's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 1 minute ago

Our checks of Resend pass from all 10 regions we check.

As of Oct 23, 2026, 8:49 AM UTC, RealUptime's checks of Resend passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 23, 2026, 8:49 AM UTC
US-East956 msChecks passing
US-West1530 msChecks passing
Europe934 msChecks passing
Asia-Pacific1500 msChecks passing
US-Central613 msChecks passing
Canada676 msChecks passing
UK1675 msChecks passing
Southeast Asia1757 msChecks passing
Australia1554 msChecks passing
South America1117 msChecks passing
their status pagetheir claim, not our reading

Resend reports: All systems operational (“All Systems Operational”)

from Resend's own status page, checked Oct 23, 2026, 8:41 AM UTC
Resend's own status page shows no incident, and our checks of Resend pass right now.

Resend's own component breakdown, as they publish it

  • Single EmailOperational
  • Batch EmailsOperational
  • Broadcast EmailsOperational
  • Scheduled EmailsOperational
  • SMTPOperational
  • General APIOperational
  • Email EventsOperational
  • AutomationsOperational
  • WebhooksOperational
  • DashboardOperational
  • WebsiteOperational
  • MCP ServerOperational

These are Resend's components, named and scored by Resend. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Resend's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Resend response time, by region

US-East
1.3sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 609ms2026-09-25 UTC: p95 357ms2026-09-26 UTC: p95 414ms2026-09-27 UTC: p95 323ms2026-09-28 UTC: p95 288ms2026-09-29 UTC: p95 371ms2026-09-30 UTC: p95 349ms2026-10-01 UTC: p95 333ms2026-10-02 UTC: p95 319ms2026-10-03 UTC: p95 396ms2026-10-04 UTC: p95 330ms2026-10-05 UTC: p95 335ms2026-10-06 UTC: p95 366ms2026-10-07 UTC: p95 345ms2026-10-08 UTC: p95 349ms2026-10-09 UTC: p95 577ms2026-10-10 UTC: p95 571ms2026-10-11 UTC: p95 614ms2026-10-12 UTC: p95 973ms2026-10-13 UTC: p95 550ms2026-10-14 UTC: p95 536ms2026-10-15 UTC: p95 437ms2026-10-16 UTC: p95 343ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.3s
Sep 24Oct 8Oct 23
US-West
1.8sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 729ms2026-09-25 UTC: p95 530ms2026-09-26 UTC: p95 423ms2026-09-27 UTC: p95 521ms2026-09-28 UTC: p95 515ms2026-09-29 UTC: p95 355ms2026-09-30 UTC: p95 384ms2026-10-01 UTC: p95 578ms2026-10-02 UTC: p95 541ms2026-10-03 UTC: p95 360ms2026-10-04 UTC: p95 331ms2026-10-05 UTC: p95 482ms2026-10-06 UTC: p95 486ms2026-10-07 UTC: p95 400ms2026-10-08 UTC: p95 430ms2026-10-09 UTC: p95 481ms2026-10-10 UTC: p95 548ms2026-10-11 UTC: p95 619ms2026-10-12 UTC: p95 487ms2026-10-13 UTC: p95 495ms2026-10-14 UTC: p95 653ms2026-10-15 UTC: p95 635ms2026-10-16 UTC: p95 499ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.8s
Sep 24Oct 8Oct 23
Europe
953msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 477ms2026-09-25 UTC: p95 365ms2026-09-26 UTC: p95 369ms2026-09-27 UTC: p95 281ms2026-09-28 UTC: p95 320ms2026-09-29 UTC: p95 278ms2026-09-30 UTC: p95 313ms2026-10-01 UTC: p95 375ms2026-10-02 UTC: p95 452ms2026-10-03 UTC: p95 476ms2026-10-04 UTC: p95 306ms2026-10-05 UTC: p95 275ms2026-10-06 UTC: p95 364ms2026-10-07 UTC: p95 362ms2026-10-08 UTC: p95 259ms2026-10-09 UTC: p95 586ms2026-10-10 UTC: p95 296ms2026-10-11 UTC: p95 356ms2026-10-12 UTC: p95 347ms2026-10-13 UTC: p95 328ms2026-10-14 UTC: p95 490ms2026-10-15 UTC: p95 293ms2026-10-16 UTC: p95 207ms2026-10-17 UTC: p95 619ms2026-10-18 UTC: p95 935ms2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 961ms2026-10-21 UTC: p95 943ms2026-10-22 UTC: p95 994ms2026-10-23 UTC: p95 953ms
Sep 24Oct 8Oct 23
Asia-Pacific
2.3sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 836ms2026-09-26 UTC: p95 746ms2026-09-27 UTC: p95 849ms2026-09-28 UTC: p95 779ms2026-09-29 UTC: p95 773ms2026-09-30 UTC: p95 811ms2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 854ms2026-10-03 UTC: p95 824ms2026-10-04 UTC: p95 597ms2026-10-05 UTC: p95 728ms2026-10-06 UTC: p95 664ms2026-10-07 UTC: p95 653ms2026-10-08 UTC: p95 642ms2026-10-09 UTC: p95 749ms2026-10-10 UTC: p95 833ms2026-10-11 UTC: p95 802ms2026-10-12 UTC: p95 933ms2026-10-13 UTC: p95 751ms2026-10-14 UTC: p95 812ms2026-10-15 UTC: p95 927ms2026-10-16 UTC: p95 917ms2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 2.3s2026-10-22 UTC: p95 1.9s2026-10-23 UTC: p95 2.3s
Sep 24Oct 8Oct 23
US-Central
838msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 726ms2026-09-25 UTC: p95 647ms2026-09-26 UTC: p95 470ms2026-09-27 UTC: p95 276ms2026-09-28 UTC: p95 270ms2026-09-29 UTC: p95 340ms2026-09-30 UTC: p95 330ms2026-10-01 UTC: p95 416ms2026-10-02 UTC: p95 385ms2026-10-03 UTC: p95 528ms2026-10-04 UTC: p95 468ms2026-10-05 UTC: p95 584ms2026-10-06 UTC: p95 583ms2026-10-07 UTC: p95 555ms2026-10-08 UTC: p95 611ms2026-10-09 UTC: p95 674ms2026-10-10 UTC: p95 816ms2026-10-11 UTC: p95 807ms2026-10-12 UTC: p95 773ms2026-10-13 UTC: p95 871ms2026-10-14 UTC: p95 923ms2026-10-15 UTC: p95 607ms2026-10-16 UTC: p95 768ms2026-10-17 UTC: p95 898ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 965ms2026-10-22 UTC: p95 821ms2026-10-23 UTC: p95 838ms
Sep 24Oct 8Oct 23
Canada
818msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 749ms2026-09-25 UTC: p95 699ms2026-09-26 UTC: p95 637ms2026-09-27 UTC: p95 652ms2026-09-28 UTC: p95 593ms2026-09-29 UTC: p95 614ms2026-09-30 UTC: p95 719ms2026-10-01 UTC: p95 584ms2026-10-02 UTC: p95 479ms2026-10-03 UTC: p95 511ms2026-10-04 UTC: p95 545ms2026-10-05 UTC: p95 586ms2026-10-06 UTC: p95 518ms2026-10-07 UTC: p95 686ms2026-10-08 UTC: p95 668ms2026-10-09 UTC: p95 728ms2026-10-10 UTC: p95 697ms2026-10-11 UTC: p95 476ms2026-10-12 UTC: p95 478ms2026-10-13 UTC: p95 448ms2026-10-14 UTC: p95 471ms2026-10-15 UTC: p95 602ms2026-10-16 UTC: p95 624ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.0s2026-10-23 UTC: p95 818ms
Sep 24Oct 8Oct 23
UK
1.5sp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 502ms2026-09-25 UTC: p95 571ms2026-09-26 UTC: p95 494ms2026-09-27 UTC: p95 318ms2026-09-28 UTC: p95 288ms2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 966ms2026-10-01 UTC: p95 807ms2026-10-02 UTC: p95 442ms2026-10-03 UTC: p95 421ms2026-10-04 UTC: p95 404ms2026-10-05 UTC: p95 314ms2026-10-06 UTC: p95 314ms2026-10-07 UTC: p95 287ms2026-10-08 UTC: p95 417ms2026-10-09 UTC: p95 413ms2026-10-10 UTC: p95 463ms2026-10-11 UTC: p95 270ms2026-10-12 UTC: p95 412ms2026-10-13 UTC: p95 325ms2026-10-14 UTC: p95 417ms2026-10-15 UTC: p95 644ms2026-10-16 UTC: p95 220ms2026-10-17 UTC: p95 937ms2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.5s
Sep 24Oct 8Oct 23
Southeast Asia
2.5sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.9s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 959ms2026-10-05 UTC: p95 861ms2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 2.4s2026-10-12 UTC: p95 940ms2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 999ms2026-10-15 UTC: p95 942ms2026-10-16 UTC: p95 662ms2026-10-17 UTC: p95 2.2s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 2.2s2026-10-22 UTC: p95 3.1s2026-10-23 UTC: p95 2.5s
Sep 24Oct 8Oct 23
Australia
1.9sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 845ms2026-09-26 UTC: p95 746ms2026-09-27 UTC: p95 624ms2026-09-28 UTC: p95 576ms2026-09-29 UTC: p95 777ms2026-09-30 UTC: p95 823ms2026-10-01 UTC: p95 554ms2026-10-02 UTC: p95 546ms2026-10-03 UTC: p95 826ms2026-10-04 UTC: p95 808ms2026-10-05 UTC: p95 766ms2026-10-06 UTC: p95 796ms2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 857ms2026-10-09 UTC: p95 781ms2026-10-10 UTC: p95 883ms2026-10-11 UTC: p95 502ms2026-10-12 UTC: p95 539ms2026-10-13 UTC: p95 920ms2026-10-14 UTC: p95 885ms2026-10-15 UTC: p95 856ms2026-10-16 UTC: p95 668ms2026-10-17 UTC: p95 625ms2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 2.1s2026-10-21 UTC: p95 2.4s2026-10-22 UTC: p95 2.2s2026-10-23 UTC: p95 1.9s
Sep 24Oct 8Oct 23
South America
1.3sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 868ms2026-09-25 UTC: p95 998ms2026-09-26 UTC: p95 548ms2026-09-27 UTC: p95 782ms2026-09-28 UTC: p95 909ms2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 999ms2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 909ms2026-10-11 UTC: p95 722ms2026-10-12 UTC: p95 526ms2026-10-13 UTC: p95 616ms2026-10-14 UTC: p95 749ms2026-10-15 UTC: p95 657ms2026-10-16 UTC: p95 641ms2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.3s
Sep 24Oct 8Oct 23

Check your own site while you wait on Resend

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Resend. It cannot diagnose Resend's own systems.

What we measured, function by function

Resend answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Resend reports an incident on its status page, and again when it reports it resolved.

Get an email when Resend reports an incident

Email me when Resend reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Resend's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 956msstatus code: 401checked: Oct 23, 2026, 8:44 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Resend normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1530msstatus code: 401checked: Oct 23, 2026, 8:47 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Resend normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 613msstatus code: 401checked: Oct 23, 2026, 8:49 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Resend normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 676msstatus code: 401checked: Oct 23, 2026, 8:37 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Resend normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1117msstatus code: 401checked: Oct 23, 2026, 8:34 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Resend normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 934msstatus code: 401checked: Oct 23, 2026, 8:40 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Resend normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 1675msstatus code: 401checked: Oct 23, 2026, 8:47 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Resend normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1500msstatus code: 401checked: Oct 23, 2026, 8:44 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Resend normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1757msstatus code: 401checked: Oct 23, 2026, 8:41 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Resend normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1554msstatus code: 401checked: Oct 23, 2026, 8:43 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Resend normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Resend, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Resend yet, which is not evidence that nothing is wrong.

Recent probe events

Delayed new team provisioning and contact webhook delivery, 34mdeclared on their status page2026-10-10
Delayed new team provisioning and contact webhook delivery, 23mdeclared on their status page2026-10-09
Resend API with elevated error rate, 52mdeclared on their status page2026-10-01
Delayed function processing , 2h 46mdeclared on their status page2026-09-26
Intermittent errors on some dashboard and API requests, 51mdeclared on their status page2026-09-24
Failing to verify new domains, 19mdeclared on their status page2026-09-22
Degraded performance, 48h 1mdeclared on their status page2026-09-18
Degraded performance, 1mdeclared on their status page2026-09-18

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Resend since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Resend covering any window you pick, with our check readings and Resend's own claim at the time, side by side.

Full check history for Resend: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Resend uptime by RealUptime's checksLive, from this page's own readings.
[![Resend uptime by RealUptime's checks](https://realuptime.io/outages/resend/badge.svg?days=30)](https://realuptime.io/outages/resend)
<a href="https://realuptime.io/outages/resend"><img src="https://realuptime.io/outages/resend/badge.svg?days=30" alt="Resend uptime by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Resend down?", https://realuptime.io/outages/resend. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional: live API
https://api.resend.com/domains
secondary
https://resend.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.resend.com

RealUptime is not affiliated with Resend; the name identifies what we checked, and nothing here speaks for Resend's own team. We send a single web request to Resend from 10 regions on our own schedule and time the response. We do not see inside Resend's systems, do not use an account or real transaction, and are not the same signal Resend's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Resend is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.