Skip to content

Outage tracker / SparkPost

Is SparkPost down?

I'm having a problem

Vendor reports no incidentWhat SparkPost reports

SparkPost reports no incident on its status page.

As of the last successful poll, 2026-10-22 21:48 UTC.

SparkPost'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 SparkPost pass from all 10 regions we check.

As of Oct 22, 2026, 9:51 PM UTC, RealUptime's checks of SparkPost passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 22, 2026, 9:51 PM UTC
US-East1106 msChecks passing
US-West886 msChecks passing
Europe1243 msChecks passing
Asia-Pacific1505 msChecks passing
US-Central268 msChecks passing
Canada525 msChecks passing
UK600 msChecks passing
Southeast Asia933 msChecks passing
Australia836 msChecks passing
South America1308 msChecks passing
their status pagetheir claim, not our reading

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

from SparkPost's own status page, checked Oct 22, 2026, 9:22 PM UTC
SparkPost's own status page shows no incident, and our checks of SparkPost pass 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
1.4sp95 · 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-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 1.0s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 876ms2026-10-11 UTC: p95 994ms2026-10-12 UTC: p95 560ms2026-10-13 UTC: p95 686ms2026-10-14 UTC: p95 656ms2026-10-15 UTC: p95 633ms2026-10-16 UTC: p95 551ms2026-10-17 UTC: p95 565ms2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.4s
Sep 23Oct 7Oct 22
US-West
1.3sp95 · 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-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 362ms2026-10-06 UTC: p95 359ms2026-10-07 UTC: p95 330ms2026-10-08 UTC: p95 387ms2026-10-09 UTC: p95 347ms2026-10-10 UTC: p95 347ms2026-10-11 UTC: p95 329ms2026-10-12 UTC: p95 391ms2026-10-13 UTC: p95 511ms2026-10-14 UTC: p95 467ms2026-10-15 UTC: p95 404ms2026-10-16 UTC: p95 493ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.3s
Sep 23Oct 7Oct 22
Europe
1.4sp95 · 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-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.1s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 984ms2026-10-12 UTC: p95 813ms2026-10-13 UTC: p95 934ms2026-10-14 UTC: p95 883ms2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 856ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.4s
Sep 23Oct 7Oct 22
Asia-Pacific
1.8sp95 · 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-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.2s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.7s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.8s
Sep 23Oct 7Oct 22
US-Central
410msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-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 465ms2026-10-06 UTC: p95 433ms2026-10-07 UTC: p95 436ms2026-10-08 UTC: p95 434ms2026-10-09 UTC: p95 485ms2026-10-10 UTC: p95 489ms2026-10-11 UTC: p95 473ms2026-10-12 UTC: p95 538ms2026-10-13 UTC: p95 494ms2026-10-14 UTC: p95 458ms2026-10-15 UTC: p95 492ms2026-10-16 UTC: p95 487ms2026-10-17 UTC: p95 402ms2026-10-18 UTC: p95 470ms2026-10-19 UTC: p95 467ms2026-10-20 UTC: p95 455ms2026-10-21 UTC: p95 475ms2026-10-22 UTC: p95 410ms
Sep 23Oct 7Oct 22
Canada
807msp95 · 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-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 472ms2026-10-06 UTC: p95 589ms2026-10-07 UTC: p95 593ms2026-10-08 UTC: p95 711ms2026-10-09 UTC: p95 706ms2026-10-10 UTC: p95 663ms2026-10-11 UTC: p95 766ms2026-10-12 UTC: p95 428ms2026-10-13 UTC: p95 413ms2026-10-14 UTC: p95 536ms2026-10-15 UTC: p95 517ms2026-10-16 UTC: p95 470ms2026-10-17 UTC: p95 659ms2026-10-18 UTC: p95 693ms2026-10-19 UTC: p95 736ms2026-10-20 UTC: p95 501ms2026-10-21 UTC: p95 730ms2026-10-22 UTC: p95 807ms
Sep 23Oct 7Oct 22
UK
824msp95 · 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-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 797ms2026-10-06 UTC: p95 784ms2026-10-07 UTC: p95 756ms2026-10-08 UTC: p95 756ms2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 960ms2026-10-12 UTC: p95 746ms2026-10-13 UTC: p95 722ms2026-10-14 UTC: p95 603ms2026-10-15 UTC: p95 613ms2026-10-16 UTC: p95 623ms2026-10-17 UTC: p95 765ms2026-10-18 UTC: p95 881ms2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 824ms
Sep 23Oct 7Oct 22
Southeast Asia
1.7sp95 · 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-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.3s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.7s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.7s
Sep 23Oct 7Oct 22
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-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.1s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 976ms2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 924ms2026-10-12 UTC: p95 896ms2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.1s
Sep 23Oct 7Oct 22
South America
1.7sp95 · 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-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.7s2026-10-06 UTC: p95 1.6s2026-10-07 UTC: p95 1.7s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 1.6s2026-10-10 UTC: p95 1.8s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.7s
Sep 23Oct 7Oct 22

Check your own site while you wait on SparkPost

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: 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 SparkPost reports an incident on its status page, and again when it reports it resolved.

Get an email when SparkPost reports an incident

Email me when SparkPost 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 SparkPost'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: 1106msstatus code: 401checked: Oct 22, 2026, 9:51 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
      Checks passinglatency: 886msstatus code: 401checked: Oct 22, 2026, 9:28 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
      Checks passinglatency: 268msstatus code: 401checked: Oct 22, 2026, 9:00 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
      Checks passinglatency: 525msstatus code: 401checked: Oct 22, 2026, 9:15 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
    Checks passinglatency: 1308msstatus code: 401checked: Oct 22, 2026, 9:06 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 1243msstatus code: 401checked: Oct 22, 2026, 9:50 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
      Checks passinglatency: 600msstatus code: 401checked: Oct 22, 2026, 9:21 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1505msstatus code: 401checked: Oct 22, 2026, 9:41 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
      Checks passinglatency: 933msstatus code: 401checked: Oct 22, 2026, 9:07 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
      Checks passinglatency: 836msstatus code: 401checked: Oct 22, 2026, 9:10 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 probe events

Increased message delays in US and EU due to DNS resolution errors, 3h 6mdeclared on their status page2026-10-11
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

check 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 check readings and SparkPost's own claim at the time, side by side.

Full check history for SparkPost: 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

SparkPost uptime by RealUptime's checksLive, from this page's own readings.
[![SparkPost uptime by RealUptime's checks](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 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 SparkPost down?", https://realuptime.io/outages/sparkpost. 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.sparkpost.com/api/v1/account
secondary
https://www.sparkpost.com/
secondary
https://status.sparkpost.com/api/v2/status.json

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.sparkpost.com

RealUptime is not affiliated with SparkPost; the name identifies what we checked, 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 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.