← Back to Marqeta's check readings
We started checking Marqeta on August 22, 2026, which is 64 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Marqeta reports an incident on its status page, and again when it reports it resolved.
01
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.
24h ago18h ago12h ago6h agonow
Each check 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 check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and 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.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Their declared record
Marqeta's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Intermittent API timeoutsAll systems operational
Oct 22, 2026, 5:40 PM UTC to Oct 23, 2026, 1:28 AM UTC (7h 48m)resolved
their latest update (Oct 23, 2026, 1:28 AM UTC): Marqeta engineers have completed a monitoring period following the intermittent API timeouts that affected some requests originating from the us-west-2 region on October 22, 2026. Services have remained stable throughout this period and long-term stability has been confirmed. We …
STIPs on Visa EUAll systems operational
Oct 15, 2026, 4:00 PM UTC to Oct 15, 2026, 4:00 PM UTC (0 min)resolved
their latest update (Oct 15, 2026, 4:00 PM UTC): On Thursday, October 15, 2026, at 08:51 PT (15:51 UTC), Visa experienced a service disruption affecting transaction processing. Marqeta engineers detected downstream impact affecting Visa stand-in processing (STIP) on EU card programs. During this period, some transactions may ha…
3DS Authentication FailurePartial outage
Oct 14, 2026, 9:20 AM UTC to Oct 14, 2026, 10:24 AM UTC (1h 4m)resolved
their latest update (Oct 14, 2026, 10:24 AM UTC): Marqeta engineers identified the root cause as a recent change, which has since been reverted. All 3DS authentication flows are operating normally with no further impact.
Visa Outbound API DegradedMinor incident
Oct 13, 2026, 9:01 AM UTC to Oct 13, 2026, 10:19 AM UTC (1h 17m)resolved
their latest update (Oct 13, 2026, 10:19 AM UTC): On Tuesday, October 13, 2026, at approximately 01:43 PT (08:43 UTC), Marqeta engineers detected an issue affecting outbound Visa API calls in the EU region. This affects:
Visa Token Lifecycle API, Visa PAN Lifecycle API, Visa Card Art API, Visa Click to Pay API
There is current…
Mastercard Processing DelayAll systems operational
Oct 11, 2026, 7:30 AM UTC to Oct 11, 2026, 7:30 AM UTC (0 min)resolved
their latest update (Oct 11, 2026, 7:30 AM UTC): On Sunday, October 11, 2026, at approximately 7:30 UTC, Marqeta engineers detected an issue affecting Mastercard card transaction processing. Mastercard processing was delayed between 2 - 4 hours. All processing has resumed.
STIPs On All Card NetworksMinor incident
Oct 9, 2026, 10:43 PM UTC to Oct 10, 2026, 12:49 AM UTC (2h 6m)resolved
their latest update (Oct 10, 2026, 12:49 AM UTC): The upstream cloud vendor has confirmed us-east-1 is restored, and Marqeta engineers have observed that services remain stable.
API Timeouts on Card Issuance and Spend ControlMinor incident
Oct 8, 2026, 1:45 PM UTC to Oct 8, 2026, 10:55 PM UTC (9h 9m)resolved
their latest update (Oct 8, 2026, 10:55 PM UTC): There has been no further impact observed.
Marqeta Dashboard Dispute Detail Page OutageMinor incident
Oct 7, 2026, 2:08 PM UTC to Oct 7, 2026, 5:54 PM UTC (3h 47m)resolved
their latest update (Oct 7, 2026, 5:54 PM UTC): Dashboard functionality is restored.
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…
Showing the 10 most recent of 69 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 our own check readings. 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.
Marqeta's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.