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.

Functional endpoints verified

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

our independent probeslive · checked Sep 5, 2026, 2:06 AM UTC
US-East687 msOperational
US-West585 msOperational
Europe825 msOperational
Asia-Pacific684 msOperational
US-Central595 msOperational
Canada425 msOperational
UK768 msOperational
Southeast Asia1423 msOperational
Australia892 msOperational
South America859 msOperational
their status pagetheir claim, not our reading

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

from SparkPost's own status page, checked Sep 5, 2026, 1:46 AM 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
  • Sending Domains API - USAOperational
  • SMTP API - USAOperational
  • SMTP Delivery - 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
  • Sending Domains API - EUROPEOperational
  • SMTP API - EUROPEOperational
  • SMTP Delivery - 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
664msp95 · 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-08-22 UTC: p95 1.6s2026-08-23 UTC: p95 1.4s2026-08-24 UTC: p95 1.8s2026-08-25 UTC: p95 1.8s2026-08-26 UTC: p95 1.4s2026-08-27 UTC: p95 1.2s2026-08-28 UTC: p95 854ms2026-08-29 UTC: p95 1.1s2026-08-30 UTC: p95 1.1s2026-08-31 UTC: p95 1.2s2026-09-01 UTC: p95 1.3s2026-09-02 UTC: p95 1.1s2026-09-03 UTC: p95 987ms2026-09-04 UTC: p95 946ms2026-09-05 UTC: p95 664ms
Aug 7Aug 21Sep 5
US-West
582msp95 · 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-08-22 UTC: p95 854ms2026-08-23 UTC: p95 678ms2026-08-24 UTC: p95 630ms2026-08-25 UTC: p95 540ms2026-08-26 UTC: p95 534ms2026-08-27 UTC: p95 654ms2026-08-28 UTC: p95 690ms2026-08-29 UTC: p95 791ms2026-08-30 UTC: p95 872ms2026-08-31 UTC: p95 681ms2026-09-01 UTC: p95 409ms2026-09-02 UTC: p95 528ms2026-09-03 UTC: p95 587ms2026-09-04 UTC: p95 578ms2026-09-05 UTC: p95 582ms
Aug 7Aug 21Sep 5
Europe
814msp95 · 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-08-22 UTC: p95 695ms2026-08-23 UTC: p95 884ms2026-08-24 UTC: p95 1.1s2026-08-25 UTC: p95 1.1s2026-08-26 UTC: p95 984ms2026-08-27 UTC: p95 894ms2026-08-28 UTC: p95 932ms2026-08-29 UTC: p95 945ms2026-08-30 UTC: p95 860ms2026-08-31 UTC: p95 889ms2026-09-01 UTC: p95 877ms2026-09-02 UTC: p95 937ms2026-09-03 UTC: p95 973ms2026-09-04 UTC: p95 923ms2026-09-05 UTC: p95 814ms
Aug 7Aug 21Sep 5
Asia-Pacific
966msp95 · 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-08-22 UTC: p95 793ms2026-08-23 UTC: p95 1.1s2026-08-24 UTC: p95 1.0s2026-08-25 UTC: p95 983ms2026-08-26 UTC: p95 1.2s2026-08-27 UTC: p95 1.1s2026-08-28 UTC: p95 1.2s2026-08-29 UTC: p95 1.6s2026-08-30 UTC: p95 1.2s2026-08-31 UTC: p95 1.3s2026-09-01 UTC: p95 1.2s2026-09-02 UTC: p95 1.3s2026-09-03 UTC: p95 2.5s2026-09-04 UTC: p95 996ms2026-09-05 UTC: p95 966ms
Aug 7Aug 21Sep 5
US-Central
626msp95 · 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-03 UTC: p95 708ms2026-09-04 UTC: p95 871ms2026-09-05 UTC: p95 626ms
Aug 7Aug 21Sep 5
Canada
417msp95 · 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-03 UTC: p95 699ms2026-09-04 UTC: p95 467ms2026-09-05 UTC: p95 417ms
Aug 7Aug 21Sep 5
UK
764msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 893ms2026-09-04 UTC: p95 733ms2026-09-05 UTC: p95 764ms
Aug 7Aug 21Sep 5
Southeast Asia
1.6sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 2.1s2026-09-04 UTC: p95 1.8s2026-09-05 UTC: p95 1.6s
Aug 7Aug 21Sep 5
Australia
887msp95 · 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-03 UTC: p95 1.3s2026-09-04 UTC: p95 1.2s2026-09-05 UTC: p95 887ms
Aug 7Aug 21Sep 5
South America
902msp95 · 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-03 UTC: p95 1.4s2026-09-04 UTC: p95 1.2s2026-09-05 UTC: p95 902ms
Aug 7Aug 21Sep 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
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: 687msstatus code: 401checked: Sep 5, 2026, 2:05 AM 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: 585msstatus code: 401checked: Sep 5, 2026, 2:04 AM 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: 595msstatus code: 401checked: Sep 5, 2026, 2:03 AM 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: 425msstatus code: 401checked: Sep 5, 2026, 2:06 AM 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: 859msstatus code: 401checked: Sep 5, 2026, 1:40 AM 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: 825msstatus code: 401checked: Sep 5, 2026, 2:06 AM 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: 768msstatus code: 401checked: Sep 5, 2026, 1:42 AM 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: 684msstatus code: 401checked: Sep 5, 2026, 1:54 AM 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: 1423msstatus code: 401checked: Sep 5, 2026, 1:47 AM 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: 892msstatus code: 401checked: Sep 5, 2026, 1:13 AM 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

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
Elevated 5xx Suppression List API error rates and latency for some SparkPost customers (US hosted only), 1h 7mdeclared on their status page2026-05-11
Delayed delivery for some messages in EU, 38mdeclared on their status page2026-05-09
Intermittent email injection failures affecting a small subset of customers in Europe, 26hdeclared on their status page2026-05-07

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

Tell me when this goes down

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.

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 338h 7m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 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.