CheckUpstream does not yet run an independent probe against Marqeta, so no availability figure is published for it — only Marqeta's own disclosure record below. 42 incidents were recorded in the past 12 months; the most recent resolved 4 days ago after 1 hour. Status signals are polled from Marqeta's official Atlassian Statuspage status page, alongside independent probes and community reports.
Independent measurement how this is computed
Not measured
We run no independent probe against Marqeta yet, so we publish no availability figure for it. What follows is Marqeta's own disclosure record, which is a different thing.
Vendor disclosed: 34 incidents · 163 of 180 days with none posted · 2d 5h of declared impact
Fewer incidents in the last 30 days than 9% of 232 tracked services.
Share of each window with no impact declared by Marqeta
7d
99.547%
30d
98.209%
90d
99.176%
180d
98.764%
1y
99.390%
Downtime like this can be refundable
If you're a paying Marqeta customer, outages in these windows may count against Marqeta's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Marqeta entitlement →Does Marqeta actually matter to you?
A Marqeta outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 34 incidents Marqeta published and resolved in the last 180 days, measured between their own start and resolution times. It describes how long Marqeta takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 28, 07:00 UTC · resolved in 5m · Resolved
Aug 28, 06:51 UTC · resolved in 1h 18m · Resolved
Aug 26, 17:53 UTC · resolved in 1h 1m · Resolved
Aug 22, 05:03 UTC
Live Marqeta status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/marqeta)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Marqeta is currently Operational. CheckUpstream tracks Marqeta in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is Marqeta down" view? See the Marqeta Live status page.
Jul 31, 17:19 UTC · resolved in 15m · Resolved
Jul 29, 12:26 UTC · resolved in 2h 14m · Resolved
Jul 21, 19:41 UTC · resolved in 3h 19m · Resolved
Jul 21, 13:31 UTC · resolved in 9h 38m · Resolved
Jul 20, 20:13 UTC · resolved in 3d 23h · Resolved
Jul 15, 20:18 UTC · resolved in 1d 21h · Resolved
Jul 15, 07:57 UTC · resolved in 8h 32m · Resolved
Jul 14, 20:59 UTC · resolved in 3h 41m · Resolved
Jul 9, 21:31 UTC · resolved in 3d 17h · Resolved
Jul 2, 05:11 UTC · resolved in 20h 34m · Resolved
Jun 30, 01:45 UTC · resolved in 15h 46m · Resolved
Marqeta's last resolved incident started 4 days ago and lasted 1h 18m (degraded performance).
We don't publish one. CheckUpstream runs no independent probe against Marqeta yet, and the only other figure available would be derived from Marqeta's own incident posts — which measures how much a vendor discloses rather than how available it was. Vendors that post often score worse than vendors that stay quiet, so the number would be backwards.
Sign up to CheckUpstream and add Marqeta to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Marqeta's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.