Skip to content

Outage tracker

Marqeta: the full evidence record

The last 24 hours in detail, 46 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 46 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me the next time we see Marqeta go down

Measured by our own probes from ten regions, not Marqeta's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

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
Our probes, api (primary)
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%2105
US-West100.00%2105
Europe100.00%2100
Asia-Pacific100.00%2073
US-Central100.00%807
Canada99.75%808
UK100.00%807
Southeast Asia99.88%803
Australia100.00%803
South America99.75%805

Monthly summary

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

MonthUptimeOutagesDowntime
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 202699.86%11h
Oct 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.

Sep 23, 2026, 11:16 PM UTC to Sep 24, 2026, 12:16 AM UTC1h
single region
Canada: failing from Sep 23, 2026, 11:16 PM UTC, recovered Sep 24, 2026, 12:16 AM UTC

Permanent incident records

Every closed Marqeta incident RealUptime has ever detected gets its own permanent, citable page: the region-by-region timeline, exactly as measured, that stays up even after the incident log above ages out of this 90-day window.

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.

STIPs and transaction declinesMinor incident
Sep 27, 2026, 1:43 AM UTC to Sep 28, 2026, 2:47 PM UTC (1d 13h)resolved
their latest update (Sep 28, 2026, 2:47 PM UTC): On Saturday, September 26, 2026. Marqeta detected an issue affecting stand-in transaction processing (STIPs) and transaction declines with impact start time at approximately 5:31 PM PT. We immediately engaged our upstream infrastructure provider, who identified the root cause and…
STIPs on VisaPartial outage
Sep 25, 2026, 7:07 PM UTC to Sep 25, 2026, 8:55 PM UTC (1h 48m)resolved
their latest update (Sep 25, 2026, 8:55 PM UTC): On Friday, September 25, 2026, at approximately 11:33 PT (18:33 UTC), Marqeta engineers detected an issue affecting transaction authorizations processed via network Stand-In on Visa. There is no impact at this time. Engineers have put mitigations into place and will continue to m…
STIPs on MastercardPartial outage
Sep 24, 2026, 8:56 PM UTC to Sep 26, 2026, 1:28 AM UTC (1d 4h)resolved
their latest update (Sep 26, 2026, 1:28 AM UTC): On Thursday, September 24, 2026, at approximately 13:07 PT (20:07 UTC) Marqeta identified an issue affecting card transactions processed through Mastercard, in which a number of transactions across several Mastercard programs were declined or handled through the network's stand-…
Visa Duplicate Clearing FilesMinor incident
Sep 21, 2026, 12:57 PM UTC to Sep 22, 2026, 9:25 PM UTC (1d 8h)resolved
their latest update (Sep 22, 2026, 9:25 PM UTC): Marqeta engineers, in coordination with Visa, have completed remediation of the duplicate clearing transaction issue affecting September 18th transactions. All impacted transaction exceptions have been processed, with the final set of transactions confirmed posted at approximatel…
Google Pay OutagePartial outage
Sep 16, 2026, 4:06 PM UTC to Sep 16, 2026, 4:43 PM UTC (37 min)resolved
their latest update (Sep 16, 2026, 4:43 PM UTC): Google has confirmed their outage is resolved, and Marqeta engineers have observed Google Pay token provisioning has returned to normal operation.
Salesforce.com down, customer support impactedAll systems operational
Sep 16, 2026, 11:08 AM UTC to Sep 16, 2026, 9:50 PM UTC (10h 43m)resolved
their latest update (Sep 16, 2026, 9:50 PM UTC): Support systems are restored.
Intermittent Service disruptions affecting Visa "Click to Pay" API endpoints.All systems operational
Sep 15, 2026, 6:06 PM UTC to Sep 17, 2026, 2:18 AM UTC (1d 8h)resolved
their latest update (Sep 17, 2026, 2:18 AM UTC): Following an extended monitoring period, our engineering team has confirmed continued long-term stability of the Visa "Click to Pay" service with no further abnormalities detected since the last observed disruption at 2:46 PM PT on September 15, 2026. The investigation lead an is…
STIPs on Pulse NetworkMinor incident
Sep 12, 2026, 9:12 PM UTC to Sep 14, 2026, 9:25 PM UTC (2d 0h)resolved
their latest update (Sep 14, 2026, 9:25 PM UTC): There have been no new occurrences of STIPs on the Pulse network.
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…

Showing the 10 most recent of 61 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, 44 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.

outages compared: 1their status page reported a problem during 0 of 1reported operational while we measured down: 1 hour in total1 of those affected a single region
Sep 23, 2026, 11:16 PM UTC to Sep 24, 2026, 12:16 AM UTCTheir status page did not report a problem
single region

Marqeta's status page reported all systems operational for 1 hour while we measured Marqeta down in one of our regions (Canada).

Canada: measured down 1 hour; Marqeta reported operational for 1 hour of it.

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.