Skip to content

Outage tracker / Marqeta

Is Marqeta down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Marqeta from all 10 regions we check.

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

Functional endpoints verified

Last outage: 1h on Sep 23, 2026 (web surface, from Canada).

our independent probeslive · checked Oct 5, 2026, 8:17 PM UTC
US-East93 msOperational
US-West450 msOperational
Europe409 msOperational
Asia-Pacific743 msOperational
US-Central155 msOperational
Canada260 msOperational
UK356 msOperational
Southeast Asia771 msOperational
Australia845 msOperational
South America1006 msOperational
their status pagetheir claim, not our reading

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

from Marqeta's own status page, checked Oct 5, 2026, 7:58 PM UTC
Our probes and Marqeta's own status page agree: both show Marqeta as reachable 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
238msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 529ms2026-09-07 UTC: p95 286ms2026-09-08 UTC: p95 358ms2026-09-09 UTC: p95 406ms2026-09-10 UTC: p95 360ms2026-09-11 UTC: p95 337ms2026-09-12 UTC: p95 283ms2026-09-13 UTC: p95 294ms2026-09-14 UTC: p95 521ms2026-09-15 UTC: p95 399ms2026-09-16 UTC: p95 359ms2026-09-17 UTC: p95 515ms2026-09-18 UTC: p95 664ms2026-09-19 UTC: p95 829ms2026-09-20 UTC: p95 903ms2026-09-21 UTC: p95 433ms2026-09-22 UTC: p95 693ms2026-09-23 UTC: p95 672ms2026-09-24 UTC: p95 547ms2026-09-25 UTC: p95 280ms2026-09-26 UTC: p95 543ms2026-09-27 UTC: p95 714ms2026-09-28 UTC: p95 661ms2026-09-29 UTC: p95 392ms2026-09-30 UTC: p95 607ms2026-10-01 UTC: p95 413ms2026-10-02 UTC: p95 295ms2026-10-03 UTC: p95 224ms2026-10-04 UTC: p95 220ms2026-10-05 UTC: p95 238ms
Sep 6Sep 20Oct 5
US-West
519msp95 · 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-06 UTC: p95 630ms2026-09-07 UTC: p95 350ms2026-09-08 UTC: p95 611ms2026-09-09 UTC: p95 608ms2026-09-10 UTC: p95 397ms2026-09-11 UTC: p95 324ms2026-09-12 UTC: p95 348ms2026-09-13 UTC: p95 379ms2026-09-14 UTC: p95 708ms2026-09-15 UTC: p95 559ms2026-09-16 UTC: p95 625ms2026-09-17 UTC: p95 938ms2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.3s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 427ms2026-09-22 UTC: p95 691ms2026-09-23 UTC: p95 524ms2026-09-24 UTC: p95 619ms2026-09-25 UTC: p95 583ms2026-09-26 UTC: p95 802ms2026-09-27 UTC: p95 653ms2026-09-28 UTC: p95 919ms2026-09-29 UTC: p95 321ms2026-09-30 UTC: p95 703ms2026-10-01 UTC: p95 440ms2026-10-02 UTC: p95 406ms2026-10-03 UTC: p95 527ms2026-10-04 UTC: p95 435ms2026-10-05 UTC: p95 519ms
Sep 6Sep 20Oct 5
Europe
453msp95 · 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 807ms2026-09-07 UTC: p95 500ms2026-09-08 UTC: p95 967ms2026-09-09 UTC: p95 689ms2026-09-10 UTC: p95 595ms2026-09-11 UTC: p95 520ms2026-09-12 UTC: p95 520ms2026-09-13 UTC: p95 407ms2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 637ms2026-09-16 UTC: p95 653ms2026-09-17 UTC: p95 907ms2026-09-18 UTC: p95 807ms2026-09-19 UTC: p95 857ms2026-09-20 UTC: p95 857ms2026-09-21 UTC: p95 564ms2026-09-22 UTC: p95 951ms2026-09-23 UTC: p95 678ms2026-09-24 UTC: p95 655ms2026-09-25 UTC: p95 619ms2026-09-26 UTC: p95 936ms2026-09-27 UTC: p95 858ms2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 527ms2026-09-30 UTC: p95 784ms2026-10-01 UTC: p95 549ms2026-10-02 UTC: p95 445ms2026-10-03 UTC: p95 443ms2026-10-04 UTC: p95 445ms2026-10-05 UTC: p95 453ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.1sp95 · 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-06 UTC: p95 1.6s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 1.7s2026-09-15 UTC: p95 1.6s2026-09-16 UTC: p95 1.6s2026-09-17 UTC: p95 1.4s2026-09-18 UTC: p95 1.7s2026-09-19 UTC: p95 1.9s2026-09-20 UTC: p95 1.9s2026-09-21 UTC: p95 1.8s2026-09-22 UTC: p95 1.7s2026-09-23 UTC: p95 1.7s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.8s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 2.4s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.7s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
US-Central
289msp95 · 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 687ms2026-09-07 UTC: p95 251ms2026-09-08 UTC: p95 288ms2026-09-09 UTC: p95 696ms2026-09-10 UTC: p95 607ms2026-09-11 UTC: p95 603ms2026-09-12 UTC: p95 437ms2026-09-13 UTC: p95 523ms2026-09-14 UTC: p95 944ms2026-09-15 UTC: p95 578ms2026-09-16 UTC: p95 610ms2026-09-17 UTC: p95 786ms2026-09-18 UTC: p95 959ms2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1s2026-09-21 UTC: p95 636ms2026-09-22 UTC: p95 744ms2026-09-23 UTC: p95 749ms2026-09-24 UTC: p95 571ms2026-09-25 UTC: p95 463ms2026-09-26 UTC: p95 821ms2026-09-27 UTC: p95 844ms2026-09-28 UTC: p95 881ms2026-09-29 UTC: p95 341ms2026-09-30 UTC: p95 712ms2026-10-01 UTC: p95 684ms2026-10-02 UTC: p95 806ms2026-10-03 UTC: p95 321ms2026-10-04 UTC: p95 304ms2026-10-05 UTC: p95 289ms
Sep 6Sep 20Oct 5
Canada
305msp95 · 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 552ms2026-09-07 UTC: p95 324ms2026-09-08 UTC: p95 295ms2026-09-09 UTC: p95 454ms2026-09-10 UTC: p95 461ms2026-09-11 UTC: p95 363ms2026-09-12 UTC: p95 369ms2026-09-13 UTC: p95 293ms2026-09-14 UTC: p95 642ms2026-09-15 UTC: p95 495ms2026-09-16 UTC: p95 559ms2026-09-17 UTC: p95 544ms2026-09-18 UTC: p95 881ms2026-09-19 UTC: p95 829ms2026-09-20 UTC: p95 757ms2026-09-21 UTC: p95 852ms2026-09-22 UTC: p95 630ms2026-09-23 UTC: p95 519ms2026-09-24 UTC: p95 726ms2026-09-25 UTC: p95 331ms2026-09-26 UTC: p95 701ms2026-09-27 UTC: p95 657ms2026-09-28 UTC: p95 940ms2026-09-29 UTC: p95 568ms2026-09-30 UTC: p95 749ms2026-10-01 UTC: p95 519ms2026-10-02 UTC: p95 545ms2026-10-03 UTC: p95 343ms2026-10-04 UTC: p95 329ms2026-10-05 UTC: p95 305ms
Sep 6Sep 20Oct 5
UK
535msp95 · 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 846ms2026-09-07 UTC: p95 437ms2026-09-08 UTC: p95 578ms2026-09-09 UTC: p95 503ms2026-09-10 UTC: p95 612ms2026-09-11 UTC: p95 666ms2026-09-12 UTC: p95 247ms2026-09-13 UTC: p95 298ms2026-09-14 UTC: p95 967ms2026-09-15 UTC: p95 700ms2026-09-16 UTC: p95 497ms2026-09-17 UTC: p95 756ms2026-09-18 UTC: p95 836ms2026-09-19 UTC: p95 1.0s2026-09-20 UTC: p95 841ms2026-09-21 UTC: p95 908ms2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 735ms2026-09-24 UTC: p95 668ms2026-09-25 UTC: p95 367ms2026-09-26 UTC: p95 901ms2026-09-27 UTC: p95 998ms2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 664ms2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 493ms2026-10-02 UTC: p95 420ms2026-10-03 UTC: p95 420ms2026-10-04 UTC: p95 491ms2026-10-05 UTC: p95 535ms
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.7s2026-09-07 UTC: p95 1.5s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.7s2026-09-18 UTC: p95 1.8s2026-09-19 UTC: p95 1.9s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.6s2026-09-23 UTC: p95 1.9s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 900ms2026-09-30 UTC: p95 1.7s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.3s
Sep 6Sep 20Oct 5
Australia
1.5sp95 · 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-06 UTC: p95 1.7s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.4s2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 1.6s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.0s2026-09-14 UTC: p95 1.4s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.7s2026-09-19 UTC: p95 1.7s2026-09-20 UTC: p95 2.4s2026-09-21 UTC: p95 1.8s2026-09-22 UTC: p95 2.0s2026-09-23 UTC: p95 1.6s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.8s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 1.9s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 2.0s2026-10-01 UTC: p95 1.9s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.5s
Sep 6Sep 20Oct 5
South America
1.0sp95 · 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-06 UTC: p95 1.4s2026-09-07 UTC: p95 1.0s2026-09-08 UTC: p95 992ms2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 796ms2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.4s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 962ms2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 935ms2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 866ms2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.9s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 1.0s
Sep 6Sep 20Oct 5

Is it Marqeta, 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 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: 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 Marqeta go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Marqeta, and again when they can reach it again. That is our own measurement from ten regions, not Marqeta'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: 93msstatus code: 200checked: Oct 5, 2026, 7:55 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
      Operationallatency: 450msstatus code: 200checked: Oct 5, 2026, 8:17 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
      Operationallatency: 155msstatus code: 200checked: Oct 5, 2026, 8:04 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
      Operationallatency: 260msstatus code: 200checked: Oct 5, 2026, 8:04 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
    Operationallatency: 1006msstatus code: 200checked: Oct 5, 2026, 8:03 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 409msstatus code: 200checked: Oct 5, 2026, 8:05 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
      Operationallatency: 356msstatus code: 200checked: Oct 5, 2026, 8:03 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 743msstatus code: 200checked: Oct 5, 2026, 7:56 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
      Operationallatency: 771msstatus code: 200checked: Oct 5, 2026, 8:06 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
      Operationallatency: 845msstatus code: 200checked: Oct 5, 2026, 8:08 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 outages

STIPs and transaction declines, 37h 4mdeclared on their status page2026-09-27
STIPs on Visa, 1h 48mdeclared on their status page2026-09-25
STIPs on Mastercard, 28h 32mdeclared on their status page2026-09-24
Partial outage, 1hmeasured by our probes · Canada2026-09-23
Visa Duplicate Clearing Files, 32h 28mdeclared on their status page2026-09-21
Google Pay Outage, 37mdeclared on their status page2026-09-16
Salesforce.com down, customer support impacted, 10h 43mdeclared on their status page2026-09-16
Intermittent Service disruptions affecting Visa "Click to Pay" API endpoints., 32h 12mdeclared on their status page2026-09-15

measured 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 measurements and Marqeta's own claim at the time, side by side.

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

Marqeta uptime measured by RealUptimeLive, from this page's own readings.
[![Marqeta uptime measured by RealUptime](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 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 Marqeta's SLA implies, from our measurement

At or above your target

We measured none of downtime for Marqeta 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.

Separately, we measured 59 minutes where only one of our regions was affected. It is excluded above because most SLAs would not credit it, and it is the kind of outage a single-vantage monitor never sees at all.

This is computed from our own probe measurements, not from Marqeta'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://sandbox-api.marqeta.com/v3/ping
secondary
https://www.marqeta.com/
secondary
https://status.marqeta.com/api/v2/status.json
RealUptime is not affiliated with Marqeta; the name identifies what we measured, 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 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.