Skip to content

Outage tracker / Marqeta

Is Marqeta down?

I'm having a problem

Vendor reports no incidentWhat Marqeta reports

Marqeta reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:01 UTC.

Marqeta'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 11 minutes ago

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

As of Nov 5, 2026, 3:11 PM UTC, RealUptime's checks of Marqeta passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:11 PM UTC
US-East440 msChecks passing
US-West1388 msChecks passing
Europe1118 msChecks passing
Asia-Pacific2092 msChecks passing
US-Central252 msChecks passing
Canada501 msChecks passing
UK748 msChecks passing
Southeast Asia1493 msChecks passing
Australia821 msChecks passing
South America1403 msChecks passing
their status pagetheir claim, not our reading

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

from Marqeta's own status page, checked Nov 5, 2026, 2:27 PM UTC
Marqeta's own status page shows no incident, and our checks of Marqeta pass right now.

Marqeta's own component breakdown, as they publish it

  • Core APIOperational
  • ACH ProcessingOperational
  • Payment ProcessingOperational
  • Card IssuingOperational
  • Card FulfillmentOperational
  • ApplicationsOperational
  • CreditOperational
  • Reporting & AnalyticsOperational
  • Digital Wallets & TokenizationOperational
  • Risk & DisputesOperational
  • WebhooksOperational
  • SandboxOperational
  • 3DSOperational

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

Marqeta response time, by region

US-East
1.0sp95 · 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-10-07 UTC: p95 273ms2026-10-08 UTC: p95 209ms2026-10-09 UTC: p95 319ms2026-10-10 UTC: p95 161ms2026-10-11 UTC: p95 196ms2026-10-12 UTC: p95 153ms2026-10-13 UTC: p95 267ms2026-10-14 UTC: p95 221ms2026-10-15 UTC: p95 239ms2026-10-16 UTC: p95 206ms2026-10-17 UTC: p95 451ms2026-10-18 UTC: p95 479ms2026-10-19 UTC: p95 524ms2026-10-20 UTC: p95 347ms2026-10-21 UTC: p95 394ms2026-10-22 UTC: p95 707ms2026-10-23 UTC: p95 755ms2026-10-24 UTC: p95 740ms2026-10-25 UTC: p95 211ms2026-10-26 UTC: p95 459ms2026-10-27 UTC: p95 798ms2026-10-28 UTC: p95 701ms2026-10-29 UTC: p95 780ms2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 763ms2026-11-04 UTC: p95 935ms2026-11-05 UTC: p95 1.0s
Oct 7Oct 21Nov 5
US-West
1.8sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 431ms2026-10-08 UTC: p95 337ms2026-10-09 UTC: p95 456ms2026-10-10 UTC: p95 417ms2026-10-11 UTC: p95 410ms2026-10-12 UTC: p95 479ms2026-10-13 UTC: p95 396ms2026-10-14 UTC: p95 481ms2026-10-15 UTC: p95 394ms2026-10-16 UTC: p95 448ms2026-10-17 UTC: p95 706ms2026-10-18 UTC: p95 754ms2026-10-19 UTC: p95 833ms2026-10-20 UTC: p95 829ms2026-10-21 UTC: p95 709ms2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 566ms2026-10-26 UTC: p95 626ms2026-10-27 UTC: p95 811ms2026-10-28 UTC: p95 1.0s2026-10-29 UTC: p95 854ms2026-10-30 UTC: p95 409ms2026-10-31 UTC: p95 527ms2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5
Europe
1.5sp95 · latest
5s2.5s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 3.9s2026-10-08 UTC: p95 510ms2026-10-09 UTC: p95 442ms2026-10-10 UTC: p95 594ms2026-10-11 UTC: p95 634ms2026-10-12 UTC: p95 627ms2026-10-13 UTC: p95 464ms2026-10-14 UTC: p95 413ms2026-10-15 UTC: p95 435ms2026-10-16 UTC: p95 360ms2026-10-17 UTC: p95 724ms2026-10-18 UTC: p95 799ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 788ms2026-10-21 UTC: p95 909ms2026-10-22 UTC: p95 821ms2026-10-23 UTC: p95 888ms2026-10-24 UTC: p95 697ms2026-10-25 UTC: p95 570ms2026-10-26 UTC: p95 611ms2026-10-27 UTC: p95 823ms2026-10-28 UTC: p95 915ms2026-10-29 UTC: p95 933ms2026-10-30 UTC: p95 439ms2026-10-31 UTC: p95 460ms2026-11-01 UTC: p95 506ms2026-11-02 UTC: p95 808ms2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.5s
Oct 7Oct 21Nov 5
Asia-Pacific
2.8sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 935ms2026-10-08 UTC: p95 935ms2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 929ms2026-10-11 UTC: p95 897ms2026-10-12 UTC: p95 858ms2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 886ms2026-10-15 UTC: p95 790ms2026-10-16 UTC: p95 904ms2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 2.1s2026-10-24 UTC: p95 2.0s2026-10-25 UTC: p95 881ms2026-10-26 UTC: p95 2.2s2026-10-27 UTC: p95 2.3s2026-10-28 UTC: p95 2.4s2026-10-29 UTC: p95 2.5s2026-10-30 UTC: p95 1.8s2026-10-31 UTC: p95 1.8s2026-11-01 UTC: p95 1.8s2026-11-02 UTC: p95 3.4s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 2.9s2026-11-05 UTC: p95 2.8s
Oct 7Oct 21Nov 5
US-Central
1.1sp95 · 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-10-07 UTC: p95 447ms2026-10-08 UTC: p95 588ms2026-10-09 UTC: p95 383ms2026-10-10 UTC: p95 254ms2026-10-11 UTC: p95 212ms2026-10-12 UTC: p95 426ms2026-10-13 UTC: p95 300ms2026-10-14 UTC: p95 390ms2026-10-15 UTC: p95 213ms2026-10-16 UTC: p95 468ms2026-10-17 UTC: p95 960ms2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 468ms2026-10-26 UTC: p95 470ms2026-10-27 UTC: p95 428ms2026-10-28 UTC: p95 926ms2026-10-29 UTC: p95 339ms2026-10-30 UTC: p95 803ms2026-10-31 UTC: p95 868ms2026-11-01 UTC: p95 880ms2026-11-02 UTC: p95 395ms2026-11-03 UTC: p95 740ms2026-11-04 UTC: p95 713ms2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
Canada
767msp95 · 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-10-07 UTC: p95 402ms2026-10-08 UTC: p95 440ms2026-10-09 UTC: p95 248ms2026-10-10 UTC: p95 518ms2026-10-11 UTC: p95 410ms2026-10-12 UTC: p95 354ms2026-10-13 UTC: p95 295ms2026-10-14 UTC: p95 251ms2026-10-15 UTC: p95 234ms2026-10-16 UTC: p95 209ms2026-10-17 UTC: p95 230ms2026-10-18 UTC: p95 202ms2026-10-19 UTC: p95 696ms2026-10-20 UTC: p95 170ms2026-10-21 UTC: p95 593ms2026-10-22 UTC: p95 318ms2026-10-23 UTC: p95 925ms2026-10-24 UTC: p95 155ms2026-10-25 UTC: p95 473ms2026-10-26 UTC: p95 476ms2026-10-27 UTC: p95 449ms2026-10-28 UTC: p95 745ms2026-10-29 UTC: p95 780ms2026-10-30 UTC: p95 907ms2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 818ms2026-11-03 UTC: p95 858ms2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 767ms
Oct 7Oct 21Nov 5
UK
863msp95 · 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-10-07 UTC: p95 513ms2026-10-08 UTC: p95 448ms2026-10-09 UTC: p95 443ms2026-10-10 UTC: p95 453ms2026-10-11 UTC: p95 470ms2026-10-12 UTC: p95 426ms2026-10-13 UTC: p95 380ms2026-10-14 UTC: p95 446ms2026-10-15 UTC: p95 364ms2026-10-16 UTC: p95 451ms2026-10-17 UTC: p95 392ms2026-10-18 UTC: p95 522ms2026-10-19 UTC: p95 386ms2026-10-20 UTC: p95 500ms2026-10-21 UTC: p95 446ms2026-10-22 UTC: p95 387ms2026-10-23 UTC: p95 416ms2026-10-24 UTC: p95 377ms2026-10-25 UTC: p95 364ms2026-10-26 UTC: p95 390ms2026-10-27 UTC: p95 541ms2026-10-28 UTC: p95 580ms2026-10-29 UTC: p95 423ms2026-10-30 UTC: p95 690ms2026-10-31 UTC: p95 498ms2026-11-01 UTC: p95 808ms2026-11-02 UTC: p95 578ms2026-11-03 UTC: p95 705ms2026-11-04 UTC: p95 514ms2026-11-05 UTC: p95 863ms
Oct 7Oct 21Nov 5
Southeast Asia
2.1sp95 · 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-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 2.0s2026-10-12 UTC: p95 1.8s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.1s2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 2.4s2026-10-28 UTC: p95 2.4s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 2.3s2026-11-01 UTC: p95 2.9s2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 2.5s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
Australia
3.6sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.9s2026-10-09 UTC: p95 1.9s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.7s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.5s2026-10-24 UTC: p95 2.1s2026-10-25 UTC: p95 2.2s2026-10-26 UTC: p95 2.2s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 2.3s2026-10-29 UTC: p95 2.2s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 1.9s2026-11-01 UTC: p95 2.2s2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 2.5s2026-11-04 UTC: p95 3.3s2026-11-05 UTC: p95 3.6s
Oct 7Oct 21Nov 5
South America
2.3sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 847ms2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 874ms2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 985ms2026-10-12 UTC: p95 782ms2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 943ms2026-10-15 UTC: p95 692ms2026-10-16 UTC: p95 708ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 987ms2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 2.3s2026-10-22 UTC: p95 2.8s2026-10-23 UTC: p95 5.7s2026-10-24 UTC: p95 2.6s2026-10-25 UTC: p95 828ms2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 2.0s2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.0s2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 2.4s2026-11-05 UTC: p95 2.3s
Oct 7Oct 21Nov 5

Check your own site while you wait on Marqeta

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 Marqeta. It cannot diagnose Marqeta's own systems.

What we measured, function by function

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

Get an email when Marqeta reports an incident

Email me when Marqeta 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 Marqeta'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: 440msstatus code: 200checked: Nov 5, 2026, 2:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Marqeta normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1388msstatus code: 200checked: Nov 5, 2026, 3:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Marqeta normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 252msstatus code: 200checked: Nov 5, 2026, 2:23 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Marqeta normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 501msstatus code: 200checked: Nov 5, 2026, 2:23 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Marqeta normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1403msstatus code: 200checked: Nov 5, 2026, 2:27 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Marqeta 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: 1118msstatus code: 200checked: Nov 5, 2026, 2:47 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Marqeta normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 748msstatus code: 200checked: Nov 5, 2026, 2:22 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Marqeta 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: 2092msstatus code: 200checked: Nov 5, 2026, 3:11 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Marqeta normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1493msstatus code: 200checked: Nov 5, 2026, 2:36 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Marqeta normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 821msstatus code: 200checked: Nov 5, 2026, 2:41 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Marqeta 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 Marqeta, 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 Marqeta yet, which is not evidence that nothing is wrong.

Recent probe events

STIPs on Visa, 3h 47mdeclared on their status page2026-10-30
DataVisor Portal Access Issue, 1h 45mdeclared on their status page2026-10-29
Internal Metrics Query is Disrupted, 1h 22mdeclared on their status page2026-10-28
Mastercard Message Handling Issue, 1mdeclared on their status page2026-10-27
Widgets are Degraded, 1h 59mdeclared on their status page2026-10-26
Visa Disputes Service Disruption, 2h 34mdeclared on their status page2026-10-24
Intermittent API timeouts, 7h 48mdeclared on their status page2026-10-22
STIPs on Visa EU, 1mdeclared on their status page2026-10-15

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

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

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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

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

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

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

What we check

primaryfunctional: live API
https://sandbox-api.marqeta.com/v3/ping
secondary
https://www.marqeta.com/
secondary
https://status.marqeta.com/api/v2/status.json

What our check can and cannot see

A pass means the service's own health route reported that it is up. It does not show that pages, sign-in or the features people use work; a health route can stay green while they fail.

Host checked: sandbox-api.marqeta.com

RealUptime is not affiliated with Marqeta; the name identifies what we checked, and nothing here speaks for Marqeta's own team. We send a single web request to Marqeta from 10 regions on our own schedule and time the response. We do not see inside Marqeta's systems, do not use an account or real transaction, and are not the same signal Marqeta's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Marqeta 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.