Skip to content

Outage tracker

Marqeta: the full evidence record

The last 24 hours in detail, 15 days of measured availability, a 12-month summary, our own incident log, Marqeta's declared record, and how the two compare.

← Back to Marqeta's live status

We started measuring Marqeta on August 22, 2026, which is 15 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Marqeta's own status page declared. Below it, any public chatter we saw about Marqeta and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Marqeta's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Unverified user reportsNo reports about Marqeta in the last 24 hours, which is not evidence that nothing is wrong.
Marqeta's status pageNo incident declared in the last 24 hours.

Each probe cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused probe is not an outage. Report bars count unverified reports, not people we verified; they never change our reading. The status-page lane is Marqeta's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Marqeta next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Availability by region

Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionAvailabilityProbes recorded
US-East100.00%620
US-West100.00%620
Europe100.00%615
Asia-Pacific100.00%598
US-Central100.00%61
Canada100.00%61
UK100.00%61
Southeast Asia100.00%58
Australia100.00%57
South America100.00%59

Monthly summary

Tracking Marqeta since Aug 22, 2026. In that time our probes detected no outage. Months before that date are not tracked and carry no figure.

MonthUptimeOutagesDowntime
Oct 2025not tracked
Nov 2025not tracked
Dec 2025not tracked
Jan 2026not tracked
Feb 2026not tracked
Mar 2026not tracked
Apr 2026not tracked
May 2026not tracked
Jun 2026not tracked
Jul 2026not tracked
Aug 2026 from Aug 22, 2026100%00 min
Sep 2026100%00 min

Uptime here is the share of each month in which our probes had no outage open for Marqeta: two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and Marqeta's own status page contribute nothing to these figures.

Our incident log

Every outage our own probes detected for Marqeta in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: Marqeta's own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.

No outages detected for Marqeta since we started measuring it on August 22, 2026. We show nothing from before that date.

Their declared record

Marqeta's own incident history, taken from their public status feed. This is their account of what happened, not our measurement, and it never changes the incident log above or the other way around.

Integration Service Degradation on Master CardPartial outage
Sep 3, 2026, 2:33 PM UTC to Sep 3, 2026, 9:57 PM UTC (7h 24m)resolved
their latest update (Sep 3, 2026, 9:57 PM UTC): MasterCard has identified the root cause of the issue and stabilized their systems. Performance across all impacted endpoints—including Token Lifecycle Management, Click to Pay enrolment, API-based dispute submissions, and Card Activations—has fully recovered, and Marqeta custome…
Visa Clearing File Processing DelayMinor incident
Aug 28, 2026, 6:51 AM UTC to Aug 28, 2026, 8:07 AM UTC (1h 16m)resolved
their latest update (Aug 28, 2026, 8:07 AM UTC): As of 00:52 PT (07:52 UTC), Marqeta engineers have resolved the issue affecting Visa clearing file processing following a recent infrastructure upgrade. The impact is a 4-6h delay to clearing and settlement file processing and reconciliation for affected programs. We will continu…
STIPs on the Visa NetworkMinor incident
Aug 26, 2026, 5:53 PM UTC to Aug 26, 2026, 6:48 PM UTC (54 min)resolved
their latest update (Aug 26, 2026, 6:48 PM UTC): On Wednesday, August 26, 2026, at approximately 10:41 PT (17:41 UTC), Marqeta engineers detected an issue affecting transaction authorizations processed by network stand-in across Visa. Marqeta raised a high priority incident with Visa to provide the root cause of the suspected e…
STIPs on the Visa NetworkAll systems operational
Aug 22, 2026, 5:03 AM UTC to Aug 22, 2026, 6:10 AM UTC (1h 7m)resolved
their latest update (Aug 22, 2026, 6:10 AM UTC): On Friday, August 21, 2026, Marqeta resolved a brief service disruption affecting Stand-In Processing (STIP) on the Visa network between 09:42 and 09:45 PDT. Our engineering team immediately conducted a thorough review, verified that all internal networking infrastructure was ful…
Issue affecting a subset of credit accountsMinor incident
Aug 20, 2026, 10:53 PM UTC to Aug 21, 2026, 3:05 PM UTC (16h 12m)resolved
their latest update (Aug 21, 2026, 3:05 PM UTC): On August 20, 2026, Marqeta identified an issue affecting available credit and account balance calculations on a subset of accounts. Our engineering team has since isolated the cause, validated a corrective fix, and completed a structured remediation to restore accurate balances …
Intermittent STIPs on the Mastercard networkMinor incident
Aug 18, 2026, 7:51 PM UTC to Aug 18, 2026, 9:46 PM UTC (1h 56m)resolved
their latest update (Aug 18, 2026, 9:46 PM UTC): Marqeta and our network partner confirmed the underlying networking issue causing delayed delivery of standing advice was fixed as of 12:38 PST, and no further abnormalities have been observed during the monitoring period. All Mastercard transaction authorization processing has r…
STIPs across all networksMinor incident
Aug 17, 2026, 3:20 PM UTC to Aug 17, 2026, 5:51 PM UTC (2h 31m)resolved
their latest update (Aug 17, 2026, 5:51 PM UTC): Marqeta engineers have confirmed that the AWS emergency maintenance has fully concluded, and we have restored standard traffic routing across all card networks. Our monitoring shows stable, normal transaction processing with no further abnormalities detected. Thank you for your p…
Intermittent Service disruptions affecting Visa "Click to Pay" API endpoints.Minor incident
Aug 13, 2026, 6:07 PM UTC to Aug 14, 2026, 1:18 PM UTC (19h 11m)resolved
their latest update (Aug 14, 2026, 1:18 PM UTC): There have been no reoccurrences detected. We will continue to follow up with Visa to ensure an RCA is conducted
STIPs on Visa - Aug 10thAll systems operational
Aug 10, 2026, 8:59 PM UTC to Aug 10, 2026, 11:09 PM UTC (2h 10m)resolved
their latest update (Aug 10, 2026, 11:09 PM UTC): Following a period of continued monitoring with no further impact observed, the issue affecting Visa transactions processed via network stand-in between 15:34 PT (18:34 EST / 22:34 UTC) and 13:45 PT (16:45 EST / 20:45 UTC) is resolved.
MQD and Diva Access issueMajor outage
Jul 31, 2026, 5:19 PM UTC to Jul 31, 2026, 6:38 PM UTC (1h 19m)resolved
their latest update (Jul 31, 2026, 6:38 PM UTC): Marqeta engineering teams have resolved the service disruption affecting the Marqeta Dashboard, Diva, and 3DS at 11:00 PDT. The root cause was an infrastructure configuration change that inadvertently restricted network connectivity for our production database environment, which …

Showing the 10 most recent of 53 incidents Marqeta has declared in the history we hold.

These entries are Marqeta's own declarations, taken from their public status feed, shown separately from the outages we detected ourselves. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

The scorecard

How Marqeta's status page compared with what we measured, for every outage above that falls inside the window we have been capturing their claims.

We started recording Marqeta's own status page on August 22, 2026, 13 days ago. This comparison covers that period only, we do not reconstruct what they said before it, and we compare only inside outages we measured ourselves.

We have not measured an outage for Marqeta since we started recording their status page, so there is nothing to compare. That is a short measurement window, not a track record.

Marqeta decides what their status page covers, and it may report per component while our check reaches one surface from ten regions. We state what each side measured and leave the conclusion to you. If Marqeta believes a figure here is wrong, we publish corrections as prominently as the original.

Full detail on what a probe does and does not prove is in the methodology page.