Skip to content

Outage tracker / SparkPost

Is SparkPost down?

I'm having a problem

Operationalchecked 1 minute ago

We reached SparkPost from all 10 regions we check.

As of Oct 5, 2026, 8:16 PM UTC, SparkPost answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 44 days we have measured SparkPost (since Aug 22, 2026).

our independent probeslive · checked Oct 5, 2026, 8:16 PM UTC
US-East751 msOperational
US-West196 msOperational
Europe687 msOperational
Asia-Pacific732 msOperational
US-Central492 msOperational
Canada370 msOperational
UK766 msOperational
Southeast Asia933 msOperational
Australia1172 msOperational
South America1260 msOperational
their status pagetheir claim, not our reading

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

from SparkPost's own status page, checked Oct 5, 2026, 8:13 PM UTC
Our probes and SparkPost's own status page agree: both show SparkPost as reachable right now.

SparkPost's own component breakdown, as they publish it

  • Alerts API - USAOperational
  • Blocklist API - USAOperational
  • Engagement Tracking Service (redirecting clicks and serving opens) - USAOperational
  • Event Webhooks - USAOperational
  • Events API - USAOperational
  • Metrics API - USAOperational
  • Relay Webhooks - USAOperational
  • SMTP API - USAOperational
  • SMTP Delivery - USAOperational
  • Sending Domains API - USAOperational
  • SparkPost Application - USAOperational
  • Suppression List API - USAOperational
  • Transmissions API - USAOperational
  • Alerts API - EUROPEOperational
  • Blocklist API - EUROPEOperational
  • Engagement Tracking Service (redirecting clicks and serving opens) - EUROPEOperational
  • Event Webhooks - EUROPEOperational
  • Events API - EUROPEOperational
  • Metrics API - EUROPEOperational
  • Relay Webhooks - EUROPEOperational
  • SMTP API - EUROPEOperational
  • SMTP Delivery - EUROPEOperational
  • Sending Domains API - EUROPEOperational
  • SparkPost Application - EUROPEOperational
  • Suppression List API - EUROPEOperational
  • Transmissions API - EUROPEOperational
  • Mailbox Provider Service InterruptionOperational

These are SparkPost's components, named and scored by SparkPost. 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 SparkPost'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.

SparkPost response time, by region

US-East
989msp95 · 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-06 UTC: p95 1.1s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.4s2026-09-18 UTC: p95 534ms2026-09-19 UTC: p95 637ms2026-09-20 UTC: p95 526ms2026-09-21 UTC: p95 551ms2026-09-22 UTC: p95 538ms2026-09-23 UTC: p95 550ms2026-09-24 UTC: p95 596ms2026-09-25 UTC: p95 576ms2026-09-26 UTC: p95 522ms2026-09-27 UTC: p95 564ms2026-09-28 UTC: p95 560ms2026-09-29 UTC: p95 612ms2026-09-30 UTC: p95 537ms2026-10-01 UTC: p95 872ms2026-10-02 UTC: p95 995ms2026-10-03 UTC: p95 974ms2026-10-04 UTC: p95 973ms2026-10-05 UTC: p95 989ms
Sep 6Sep 20Oct 5
US-West
368msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 481ms2026-09-07 UTC: p95 413ms2026-09-08 UTC: p95 425ms2026-09-09 UTC: p95 459ms2026-09-10 UTC: p95 403ms2026-09-11 UTC: p95 402ms2026-09-12 UTC: p95 240ms2026-09-13 UTC: p95 295ms2026-09-14 UTC: p95 358ms2026-09-15 UTC: p95 453ms2026-09-16 UTC: p95 571ms2026-09-17 UTC: p95 540ms2026-09-18 UTC: p95 335ms2026-09-19 UTC: p95 321ms2026-09-20 UTC: p95 304ms2026-09-21 UTC: p95 353ms2026-09-22 UTC: p95 313ms2026-09-23 UTC: p95 364ms2026-09-24 UTC: p95 382ms2026-09-25 UTC: p95 690ms2026-09-26 UTC: p95 803ms2026-09-27 UTC: p95 701ms2026-09-28 UTC: p95 737ms2026-09-29 UTC: p95 675ms2026-09-30 UTC: p95 669ms2026-10-01 UTC: p95 788ms2026-10-02 UTC: p95 769ms2026-10-03 UTC: p95 796ms2026-10-04 UTC: p95 442ms2026-10-05 UTC: p95 368ms
Sep 6Sep 20Oct 5
Europe
1.1sp95 · 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-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 1.3s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 954ms2026-09-18 UTC: p95 834ms2026-09-19 UTC: p95 815ms2026-09-20 UTC: p95 815ms2026-09-21 UTC: p95 784ms2026-09-22 UTC: p95 803ms2026-09-23 UTC: p95 771ms2026-09-24 UTC: p95 764ms2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 966ms2026-09-27 UTC: p95 928ms2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
Asia-Pacific
1.2sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.1s2026-09-07 UTC: p95 945ms2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 917ms2026-09-11 UTC: p95 892ms2026-09-12 UTC: p95 926ms2026-09-13 UTC: p95 998ms2026-09-14 UTC: p95 851ms2026-09-15 UTC: p95 882ms2026-09-16 UTC: p95 871ms2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 997ms2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5
US-Central
466msp95 · 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-06 UTC: p95 1.0s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 999ms2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 810ms2026-09-13 UTC: p95 735ms2026-09-14 UTC: p95 686ms2026-09-15 UTC: p95 334ms2026-09-16 UTC: p95 342ms2026-09-17 UTC: p95 367ms2026-09-18 UTC: p95 341ms2026-09-19 UTC: p95 363ms2026-09-20 UTC: p95 385ms2026-09-21 UTC: p95 479ms2026-09-22 UTC: p95 369ms2026-09-23 UTC: p95 377ms2026-09-24 UTC: p95 383ms2026-09-25 UTC: p95 357ms2026-09-26 UTC: p95 516ms2026-09-27 UTC: p95 637ms2026-09-28 UTC: p95 856ms2026-09-29 UTC: p95 712ms2026-09-30 UTC: p95 851ms2026-10-01 UTC: p95 545ms2026-10-02 UTC: p95 440ms2026-10-03 UTC: p95 420ms2026-10-04 UTC: p95 471ms2026-10-05 UTC: p95 466ms
Sep 6Sep 20Oct 5
Canada
486msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 418ms2026-09-07 UTC: p95 452ms2026-09-08 UTC: p95 451ms2026-09-09 UTC: p95 445ms2026-09-10 UTC: p95 506ms2026-09-11 UTC: p95 452ms2026-09-12 UTC: p95 834ms2026-09-13 UTC: p95 932ms2026-09-14 UTC: p95 794ms2026-09-15 UTC: p95 464ms2026-09-16 UTC: p95 428ms2026-09-17 UTC: p95 512ms2026-09-18 UTC: p95 569ms2026-09-19 UTC: p95 527ms2026-09-20 UTC: p95 577ms2026-09-21 UTC: p95 413ms2026-09-22 UTC: p95 434ms2026-09-23 UTC: p95 430ms2026-09-24 UTC: p95 555ms2026-09-25 UTC: p95 472ms2026-09-26 UTC: p95 668ms2026-09-27 UTC: p95 749ms2026-09-28 UTC: p95 706ms2026-09-29 UTC: p95 742ms2026-09-30 UTC: p95 793ms2026-10-01 UTC: p95 626ms2026-10-02 UTC: p95 493ms2026-10-03 UTC: p95 461ms2026-10-04 UTC: p95 468ms2026-10-05 UTC: p95 486ms
Sep 6Sep 20Oct 5
UK
803msp95 · 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-06 UTC: p95 754ms2026-09-07 UTC: p95 723ms2026-09-08 UTC: p95 727ms2026-09-09 UTC: p95 740ms2026-09-10 UTC: p95 684ms2026-09-11 UTC: p95 757ms2026-09-12 UTC: p95 763ms2026-09-13 UTC: p95 792ms2026-09-14 UTC: p95 836ms2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 940ms2026-09-17 UTC: p95 991ms2026-09-18 UTC: p95 806ms2026-09-19 UTC: p95 827ms2026-09-20 UTC: p95 789ms2026-09-21 UTC: p95 789ms2026-09-22 UTC: p95 766ms2026-09-23 UTC: p95 735ms2026-09-24 UTC: p95 804ms2026-09-25 UTC: p95 800ms2026-09-26 UTC: p95 837ms2026-09-27 UTC: p95 817ms2026-09-28 UTC: p95 807ms2026-09-29 UTC: p95 656ms2026-09-30 UTC: p95 768ms2026-10-01 UTC: p95 783ms2026-10-02 UTC: p95 806ms2026-10-03 UTC: p95 805ms2026-10-04 UTC: p95 734ms2026-10-05 UTC: p95 803ms
Sep 6Sep 20Oct 5
Southeast Asia
1.3sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.9s2026-09-07 UTC: p95 1.7s2026-09-08 UTC: p95 1.9s2026-09-09 UTC: p95 1.7s2026-09-10 UTC: p95 2.0s2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.4s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.6s2026-09-17 UTC: p95 1.4s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.5s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.3s
Sep 6Sep 20Oct 5
Australia
1.1sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.9s2026-09-10 UTC: p95 1.9s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.3s2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
South America
1.8sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.6s2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.8s2026-09-13 UTC: p95 1.9s2026-09-14 UTC: p95 1.6s2026-09-15 UTC: p95 1.5s2026-09-16 UTC: p95 2.0s2026-09-17 UTC: p95 2.0s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 1.6s2026-09-30 UTC: p95 1.7s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.8s2026-10-04 UTC: p95 2.2s2026-10-05 UTC: p95 1.8s
Sep 6Sep 20Oct 5

Is it SparkPost, or is it you?

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 SparkPost -- it cannot diagnose SparkPost's own systems.

What we measured, function by function

SparkPost 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: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see SparkPost go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching SparkPost, and again when they can reach it again. That is our own measurement from ten regions, not SparkPost's status page. No account, no card.

Delivery channel

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

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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 751msstatus code: 401checked: Oct 5, 2026, 7:50 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach SparkPost normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 196msstatus code: 401checked: Oct 5, 2026, 8:07 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach SparkPost normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 492msstatus code: 401checked: Oct 5, 2026, 7:27 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach SparkPost normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 370msstatus code: 401checked: Oct 5, 2026, 7:35 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach SparkPost normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 1260msstatus code: 401checked: Oct 5, 2026, 7:30 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach SparkPost normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 687msstatus code: 401checked: Oct 5, 2026, 7:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach SparkPost normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 766msstatus code: 401checked: Oct 5, 2026, 7:27 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach SparkPost normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 732msstatus code: 401checked: Oct 5, 2026, 8:16 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach SparkPost normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 933msstatus code: 401checked: Oct 5, 2026, 7:32 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach SparkPost normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1172msstatus code: 401checked: Oct 5, 2026, 7:54 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach SparkPost 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 SparkPost, 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 SparkPost yet, which is not evidence that nothing is wrong.

Recent outages

Mail delivery delays, 31mdeclared on their status page2026-10-01
Outbound message delivery is delayed/slow for some SparkPost customers (US hosted only), 54mdeclared on their status page2026-09-17
Health Score and Cohort data is delayed, 2h 27mdeclared on their status page2026-09-14
Elevated hard bounces for Apple private relay recipients (privaterelay.appleid.com), 4h 54mdeclared on their status page2026-08-27
Outbound message delivery is delayed/slow for some SparkPost customers (EU hosted only), 1h 6mdeclared on their status page2026-08-19
Partial Outage and Delivery Issues in US-West-2 Region, 7h 30mdeclared on their status page2026-07-24
There is a delay effecting some mail sending in EU., 48mdeclared on their status page2026-06-29
Issue with updating payment information, 50mdeclared on their status page2026-05-12

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

We have been measuring SparkPost 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 SparkPost covering any window you pick, with our measurements and SparkPost's own claim at the time, side by side.

Full availability history for SparkPost: 90-day availability by region, month-by-month uptime, and every incident 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

SparkPost uptime measured by RealUptimeLive, from this page's own readings.
[![SparkPost uptime measured by RealUptime](https://realuptime.io/outages/sparkpost/badge.svg?days=30)](https://realuptime.io/outages/sparkpost)
<a href="https://realuptime.io/outages/sparkpost"><img src="https://realuptime.io/outages/sparkpost/badge.svg?days=30" alt="SparkPost uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What SparkPost's SLA implies, from our measurement

At or above your target

We measured none of downtime for SparkPost over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from SparkPost's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.sparkpost.com/api/v1/account
secondary
https://www.sparkpost.com/
secondary
https://status.sparkpost.com/api/v2/status.json
RealUptime is not affiliated with SparkPost; the name identifies what we measured, and nothing here speaks for SparkPost's own team. We send a single web request to SparkPost from 10 regions on our own schedule and time the response. We do not see inside SparkPost's systems, do not use an account or real transaction, and are not the same signal SparkPost's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for SparkPost is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.