What is Marqeta's uptime?

Over the last 90 days, Marqeta reported 96.28% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.marqeta.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Marqeta's uptime history rolling forward in real time.

Has Marqeta had outages in 2026?

Yes — Marqeta has had 10 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.

When was the last Marqeta outage?

The most recent Marqeta incident was "Delay in Diva reports and MQD endpoints", which started on May 5, 2026 and was resolved on May 8, 2026. Pingoru captured this directly from https://status.marqeta.com. See the full incident card above for affected components and the update timeline.

How often does Marqeta have outages?

Based on the last 90 days, Marqeta averages 3.3 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.

Where is Marqeta's status page?

Marqeta's official status page is https://status.marqeta.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.

Is Marqeta down right now?

Marqeta has degraded performance. Pingoru checks the official status page every 5 minutes and flips this headline the moment Marqeta reports a change. Current status is based on 13 tracked services.

How does Pingoru know if Marqeta is down?

We read https://status.marqeta.com directly, using Marqeta's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.

Where can I get notified when Marqeta has an outage?

Create a free Pingoru account and add Marqeta as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.

Marqeta's status page says the service is up, but I'm having issues — what's wrong?

Three common reasons: • A real Marqeta incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Marqeta issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.

Where does Pingoru get the official Marqeta status?

We use Marqeta's own status page at https://status.marqeta.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.

What does "Degraded" mean?

Marqeta is reporting degraded performance — services are up but slower than usual, or a subset of requests is failing.

Is Marqeta down?

Last checked 1m ago

Current status

Marqeta has degraded performance

Active incident: AWS Outage Impacting Marqeta Services

Get alerts when Marqeta breaks → View Marqeta outage history →

Free · no credit card

Official status page: https://status.marqeta.com · Polled every 5 minutes · 13 components tracked

Marqeta is reporting degraded performance right now (last checked 1m ago). Services are up but slower or partially failing.

Real-time Marqeta status, recent outages, and incident history — pulled directly from Marqeta's official status page at https://status.marqeta.com every 5 minutes. Pingoru tracks 13 Marqeta services and has captured 11 incidents in the last 90 days (96.28% uptime). Get email, Slack, Discord, or webhook alerts the moment Marqeta reports a new incident — free for 5 monitors, no credit card.

Users who monitor Marqeta also follow these Payments services:

Breadcrumb View all 6,000+ providers

Marqeta uptime 96.28% uptime · past 90 days

Mon Wed Fri

FebMarAprMay

Less More

Active incident 1

AWS Outage Impacting Marqeta Services

Ongoing ● 3d 13h

Started May 08, 2026, 12:46 AM UTC

Payment ProcessingReporting & AnalyticsDigital Wallets & TokenizationRisk & DisputesWebhooksSandbox3DS
Timeline · 14 updates
- investigating · May 08, 2026, 12:46 AM UTC
  
  Marqeta engineers are detecting an elevated number of STIPs starting from about 4:30PM PST. Teams are monitoring an AWS us-east-1 outage as the likely cause. We will provide updates every 30 minutes or upon discovery of new information.
- identified · May 08, 2026, 01:14 AM UTC
  
  We are continuing to monitor the AWS problem in us-east-1, and we are seeing impact across many Marqeta services due to this. We are actively removing traffic from this region to limit the impact to our customers. Next update will be in 30 minutes or when AWS provides any additional context.
- identified · May 08, 2026, 01:45 AM UTC
  
  All Marqeta services remain impacted by the ongoing AWS us-east-1 outage with no ETA for resolution from AWS. The next update will be in 30 minutes or sooner if conditions change.
- identified · May 08, 2026, 02:14 AM UTC
  
  Marqeta services remain impacted by the ongoing AWS us-east-1 outage. AWS continues working to resolve increased temperatures in the affected availability zone with no current ETA for full resolution. Some services are beginning to see improvement. Next update in 30 minutes or sooner if conditions change.
- identified · May 08, 2026, 02:44 AM UTC
  
  Marqeta services remain impacted by the ongoing AWS us-east-1 outage. AWS continues working to resolve the thermal issue in the affected availability zone. We are closely monitoring their progress and our service recovery. Next update in 30 minutes or sooner if conditions change.
- identified · May 08, 2026, 03:14 AM UTC
  
  Marqeta services remain impacted by the ongoing AWS us-east-1 outage. AWS is shifting traffic away from the impacted zone for additional services. Our teams continue monitoring the situation closely and will provide the next update in 30 minutes or when new information is available.
- identified · May 08, 2026, 03:44 AM UTC
  
  Marqeta services remain impacted by the ongoing AWS us-east-1 outage. AWS is shifting traffic away from the impacted zone for additional services. Our teams continue monitoring the situation closely and will provide the next update in 30 minutes or when new information is available.
- identified · May 08, 2026, 04:14 AM UTC
  
  Marqeta services remain impacted by the ongoing AWS us-east-1 outage. AWS is shifting traffic away from the impacted zone for additional services. Our teams continue monitoring the situation closely and will provide the next update in 30 minutes or when new information is available.
- identified · May 08, 2026, 04:42 AM UTC
  
  Marqeta services remain impacted by the ongoing AWS us-east-1 outage. Our engineers are diligently monitoring the situation and implementing measures to reduce impact where possible. We will provide our next update when we receive additional information from AWS.
- identified · May 08, 2026, 05:29 AM UTC
  
  AWS is observing some early signs of recovery. Some of Marqeta services remain impacted by the ongoing AWS us-east-1 outage. Our engineers are diligently monitoring the situation and implementing measures to reduce impact where possible. We will provide our next update when we receive additional information from AWS.
- monitoring · May 08, 2026, 06:53 AM UTC
  
  We are continuing to observe improvements to Marqeta's services. Engineers are continuing to put mitigations in place, such as moving traffic away from the affected region and availability zone. We will also continue monitoring the situation overnight for any changes in status. Our next update will be at 10:00 EST.
- monitoring · May 08, 2026, 02:00 PM UTC
  
  We are continuing to observe improvements to Marqeta's services. Engineers are continuing to put mitigations in place, such as moving traffic away from the affected region and availability zone. We will continue monitoring the situation throughout the day for any changes in status. We will provide our next update when we receive additional information from AWS.
- monitoring · May 08, 2026, 09:46 PM UTC
  
  Nearly all Marqeta services are now fully operational. Engineers are continuing to mitigate some data discrepancies in certain services. We will continue monitoring the situation throughout the weekend. We will provide our next update Monday the 11th at 10:00 am EST, or if we become aware of a substantial change in condition.
- monitoring · May 11, 2026, 02:09 PM UTC
  
  Nearly all Marqeta services are now fully operational. Engineers are continuing to mitigate some data discrepancies in certain services. We will provide our next update when the data has been fully remediated, or if we become aware of a substantial change in condition.
Latest: Nearly all Marqeta services are now fully operational. Engineers are continuing to mitigate some data discrepancies in certain services. We will provide our next update when the da…

Recent outages & incidents

Past 90 days

Delay in Diva reports and MQD endpoints

Resolved 2d 12h

Started May 05, 2026, 12:29 PM UTC · Resolved May 08, 2026, 12:40 AM UTC

Reporting & Analytics
Timeline · 11 updates
- investigating · May 05, 2026, 12:29 PM UTC
  
  An external vendor's unexpected cluster maintenance starting from about 4:00 PM on May 4th is causing a severe lag in data replication for transactional data in Diva reports and MQD endpoints. Marqeta teams are engaging with the external vendor to resolve the upstream cluster issue, running checks to quantify the data lag load times, and ensuring internal pipelines are ready to automatically process all delayed data once restored. We will have more information about an ETA to restoration once the external vendor provides their own ETA. Our next update will be in 60 minutes.
- investigating · May 05, 2026, 01:29 PM UTC
  
  An external vendor's unexpected cluster maintenance starting from about 4:00 PM PST on May 4th is causing lag in data replication for transactional data in Diva reports and MQD endpoints. Marqeta teams have escalated our engagement with the external vendor to resolve quicker. We will have more information about an ETA to restoration once the external vendor provides their own ETA. Our next update will be in 60 minutes.
- investigating · May 05, 2026, 02:29 PM UTC
  
  An external vendor's unexpected cluster maintenance starting from about 4:00 PM PST on May 4th is causing lag in data replication for transactional data in Diva reports and MQD endpoints. Marqeta teams have escalated our engagement with the external vendor to resolve quicker. We will have more information about an ETA to restoration once the external vendor provides their own ETA. Our next update will be in 60 minutes.
- investigating · May 05, 2026, 03:29 PM UTC
  
  An external vendor's unexpected cluster maintenance starting from about 4:00 PM PST on May 4th is causing lag in data replication for transactional data in Diva reports and MQD endpoints. Marqeta teams have escalated our engagement with the external vendor to resolve quicker. We will have more information about an ETA to restoration once the external vendor provides their own ETA. Our next update will be in 60 minutes.
- investigating · May 05, 2026, 04:32 PM UTC
  
  An external vendor's unexpected cluster maintenance starting from about 4:00 PM PST on May 4th is causing lag in data replication for transactional data in Diva reports and MQD endpoints. Marqeta teams have escalated our engagement with the external vendor to resolve quicker. We will have more information about an ETA to restoration once the external vendor provides their own ETA. Our next update will be in 60 minutes.
- investigating · May 05, 2026, 05:30 PM UTC
  
  An external vendor's unexpected cluster maintenance starting from about 4:00 PM PST on May 4th is causing lag in data replication for transactional data in Diva reports and MQD endpoints. Marqeta teams have escalated our engagement with the external vendor to resolve quicker. We will have more information about an ETA to restoration once the external vendor provides their own ETA. Our next update will be in 60 minutes.
- identified · May 05, 2026, 06:30 PM UTC
  
  An external vendor's unexpected cluster maintenance starting from about 4:00 PM PST on May 4th is causing lag in data replication for transactional data in Diva reports and MQD endpoints. Marqeta teams have observed assets beginning to catch up. We are continuing our engagement with the external vendor to resolve quicker and receive an ETA for full restoration. Our next update will be in 60 minutes.
- identified · May 05, 2026, 07:30 PM UTC
  
  An external vendor's unexpected cluster maintenance starting from about 4:00 PM PST on May 4th is causing lag in data replication for transactional data in Diva reports and MQD endpoints. Marqeta teams have observed assets beginning to catch up. We are continuing our engagement with the external vendor to resolve quicker and receive an ETA for full restoration. Our next update will be in 60 minutes.
- identified · May 05, 2026, 08:30 PM UTC
  
  An external vendor's unexpected cluster maintenance starting from about 4:00 PM PST on May 4th is causing lag in data replication for transactional data in Diva reports and MQD endpoints. Marqeta teams have observed assets continuing to improve. Some corrected reports will be available in the early morning of May 6th. We are continuing our engagement with the external vendor to resolve quicker and receive an ETA for full restoration. Our next update will be in 60 minutes.
- identified · May 05, 2026, 09:12 PM UTC
  
  An external vendor's unexpected cluster maintenance starting from about 4:00 PM PST on May 4th is impacting data replication for transactional data in Diva reports and MQD endpoints. All replicated assets in the system are now fully synchronized with the exception of one cluster, which currently shows approximately 8 hours behind and is progressing toward full synchronization. Marqeta teams continue to monitor the recovery process and maintain engagement with the external vendor. More detailed information will be provided tomorrow morning, or if new information becomes available.
- resolved · May 08, 2026, 12:40 AM UTC
  
  All replicated assets in the system should now be fully synchronized.
Latest: All replicated assets in the system should now be fully synchronized.
3DS Service Degradation

Resolved 1d

Started Apr 29, 2026, 05:04 PM UTC · Resolved Apr 30, 2026, 05:34 PM UTC

3DS
Timeline · 9 updates
- investigating · Apr 29, 2026, 05:04 PM UTC
  
  Starting at 13:00 EST, 3DS is experiencing degraded performance that may cause challenge timeouts. Our engineering team is investigating the root cause. We will provide another update in approximately 30 minutes.
- investigating · Apr 29, 2026, 05:32 PM UTC
  
  3DS is experiencing degraded performance that may cause challenge timeouts and STIPs. Our engineering team is investigating the root cause. Next update will be in approximately 30 minutes or when new information becomes available.
- investigating · Apr 29, 2026, 06:04 PM UTC
  
  Our engineering team is actively continuing to investigate the root cause of the 3DS performance issue. Challenge timeouts and STIPs may still be impacting customers. We remain focused on resolution and will provide another update in approximately 30 minutes.
- investigating · Apr 29, 2026, 06:35 PM UTC
  
  Multiple teams are working together to investigate and resolve the 3DS performance degradation. Challenge timeouts and STIPs may continue to impact customers. We will provide another update in approximately 30 minutes.
- identified · Apr 29, 2026, 07:04 PM UTC
  
  Engineers have identified the root cause and are now working on a resolution. We will provide another update in approximately 60 minutes or when new information becomes available.
- identified · Apr 29, 2026, 08:08 PM UTC
  
  Our engineering teams remain focused on implementing the resolution. We will provide another update in approximately 60 minutes or when new information is provided.
- identified · Apr 29, 2026, 09:15 PM UTC
  
  Work continues toward a full resolution. We will provide the next update when new information becomes available.
- identified · Apr 29, 2026, 10:20 PM UTC
  
  Engineers have confirmed that the incident is now stabilized. We will provide a final update once full resolution is confirmed
- resolved · Apr 30, 2026, 05:34 PM UTC
  
  This incident has been resolved. Service has been restored and customers should no longer experience any impact.
Latest: This incident has been resolved. Service has been restored and customers should no longer experience any impact.
Increase Rate Of Magstripe Declines

Resolved 8h 30m

Started Apr 03, 2026, 07:44 PM UTC · Resolved Apr 04, 2026, 04:15 AM UTC

Payment Processing
Timeline · 3 updates
- identified · Apr 03, 2026, 07:44 PM UTC
  
  From March 24th, we are experiencing an increase in the rate of declines for card-present transactions using magnetic stripe swipe (magstripe). This may cause cardholder's physical cards to be declined even though the cards and accounts are in good standing. Engineers are working to resolve this issue today. We will update here once this work is complete.
- identified · Apr 04, 2026, 02:55 AM UTC
  
  Engineers are continuing to work to resolve the last few instances of this issue. We will update here once this work is complete.
- resolved · Apr 04, 2026, 04:15 AM UTC
  
  Engineers have resolved the last known instances of this issue.
Latest: Engineers have resolved the last known instances of this issue.
Intermittent STIPs across multiple networks

Resolved 3d 22h

Started Apr 02, 2026, 08:31 PM UTC · Resolved Apr 06, 2026, 06:32 PM UTC

Core APIPayment ProcessingDigital Wallets & Tokenization
Timeline · 3 updates
- identified · Apr 02, 2026, 08:31 PM UTC
  
  We have observed a database connectivity issue that intermittently impacted Marqeta services on April 1st between 16:04 and 17:56 PST. During this window, some customers may have experienced an elevated amount of STIPs as well as partial disruptions to tokenization and API traffic. Our engineering team has traced the instability to an intermittent database connection failure and has escalated the matter to our third-party vendor for support. We are currently engaged in an active troubleshooting with the vendor's support to isolate the root cause and prevent recurrence by applying a tactical solution. We apologize for any inconvenience this incident may caused, and will periodically provide updates once available.
- monitoring · Apr 03, 2026, 03:10 AM UTC
  
  Following our investigation with the database vendor, a tactical fix was successfully applied at 16:26 PST. Since the implementation of this fix, we have observed a significant improvement in database connection stability and a return to normal service levels. Our engineering team is continuously monitoring the environment to verify the long-term effectiveness of the resolution and ensure overall system stability. We will provide a final update once we have confirmed the issue is fully resolved and appreciate your continued patience.
- resolved · Apr 06, 2026, 06:32 PM UTC
  
  Following an extended period of stability, we have verified that the tactical fix applied to our database environment has fully resolved the connectivity issues and all affected services are performing at baseline levels. We appreciate your patience throughout this event.
Latest: Following an extended period of stability, we have verified that the tactical fix applied to our database environment has fully resolved the connectivity issues and all affected se…
Delay in bank file delivery

Resolved 3h 18m

Started Mar 17, 2026, 04:09 PM UTC · Resolved Mar 17, 2026, 07:27 PM UTC

ACH Processing
Timeline · 2 updates
- identified · Mar 17, 2026, 04:09 PM UTC
  
  We are currently experiencing delays in bank file delivery for some customers. Engineers have identified the issue and restarted the delivery process. All bank files are expected to be delivered within the next 3 hours.
- resolved · Mar 17, 2026, 07:27 PM UTC
  
  All bank files have been successfully delivered as of 12:17 PM PT. No further delays are expected.
Latest: All bank files have been successfully delivered as of 12:17 PM PT. No further delays are expected.

See the full Marqeta outage history

6 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Marqeta outage history →

Or sign up free to get alerts when Marqeta breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 11 incidents View full outage history →

AWS Outage Impacting Marqeta Services Ongoing

Started May 08, 2026, 12:46 AM UTC · ● 3d 13h
Delay in Diva reports and MQD endpoints Resolved

Started May 05, 2026, 12:29 PM UTC · Resolved May 08, 2026, 12:40 AM UTC · 2d 12h
3DS Service Degradation Resolved

Started Apr 29, 2026, 05:04 PM UTC · Resolved Apr 30, 2026, 05:34 PM UTC · 1d
Increase Rate Of Magstripe Declines Resolved

Started Apr 03, 2026, 07:44 PM UTC · Resolved Apr 04, 2026, 04:15 AM UTC · 8h 30m
Intermittent STIPs across multiple networks Resolved

Started Apr 02, 2026, 08:31 PM UTC · Resolved Apr 06, 2026, 06:32 PM UTC · 3d 22h
Delay in bank file delivery Resolved

Started Mar 17, 2026, 04:09 PM UTC · Resolved Mar 17, 2026, 07:27 PM UTC · 3h 18m
STIPS on Master Card network Resolved

Started Mar 12, 2026, 08:29 PM UTC · Resolved Mar 13, 2026, 12:50 AM UTC · 4h 20m
FEDACH Processing Delay Resolved

Started Mar 03, 2026, 04:16 PM UTC · Resolved Mar 04, 2026, 05:05 PM UTC · 1d