Marqeta Outage History
Uptime record, past incidents, and downtime history for Marqeta.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| May 2026 | 32% | 25 | 17 |
| April 2026 | 80% | 30 | 6 |
| March 2026 | 90.3% | 31 | 3 |
| February 2026 | 100% | 5 | 0 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Feb 24
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
May 2026
Visa clearing delayed for some customers.
Started: May 15, 9:12 AM
identified
Our teams have been actively monitoring file receipt and processing throughout the day, and we have confirmed that overall clearing volume today exceeds our previous day's totals, with most recent file processed at 14:35 PDT, We are also working to formally reconcile received data against the Visa network summary to provide full confirmation that all expected clearing activity has been recovered, and will provide a further update once reconciliation is complete. We sincerely apologize for a...
May 15, 11:58 PM
identified
Our technical teams have confirmed after engaging Visa that we have processed from our side all files sent so far from Visa.
Marqeta is currently addressing a potential delay in the delivery of clearing files from the Visa network., While these files are now being ingested and prioritized through our systems to restore full data visibility, customers may experience temporary discrepancies in data reporting or reconciliation against VSS reports for the impacted date. We are closely monitoring...
May 15, 5:16 PM
investigating
We receive 6 large files from Visa each day containing clearing for Marqeta customers. The last clearing file from the 14th of May has not yet been received from Visa.
Impacted customers will have a lower number than normal of clearing webhooks and VSS reports particular to this file are delayed.
We have reached out to Visa to understand what has happened, and to ensure the file is sent.
Once the file has been received by Marqeta, it will be immediately processed and we will update this i...
May 15, 9:12 AM
Private Sandbox Maintenance
Started: May 13, 5:04 PM
identified
We're making updates to how our private Sandbox environment handles and directs network traffic as part of ongoing infrastructure improvements. We expect this maintenance to be complete by May 22nd. Your users may lose the ability to interact with your Marqeta private sandbox. If so, please reach out to support@marqeta.com.
May 13, 5:04 PM
Elevated STIPs on the Pulse Network
Started: May 12, 7:48 AM
monitoring
Following up on our previous updates, Pulse has informed us that the responsible acquirer has implemented a change to resolve the root cause, and Marqeta has cross-verified that (STIP) levels returned to normal parameters as of 08:40 AM PT. Our engineering teams will continue to closely observe the stability of the Pulse network to ensure no further disruptions occur for your cardholders, and we will provide a final resolution summary once the monitoring period is successfully complete.
May 12, 4:23 PM
identified
Our joint technical investigation with the Pulse team has successfully isolated the source of the anomalous data to a single acquiring partner.
Pulse is actively working to engage the responsible acquirer to secure a path for remediation. Concurrently, Marqeta is escalating the issue with utmost priority.
We will provide an update as soon as we have confirmation of the fix and an estimated time to resolution from Pulse.
May 12, 10:20 AM
identified
To keep our customers updated , we have initiated a joint T.S session with Pulse team, and we are working jointly to investigate the root cause and secure a path for remediation. We will provide an update as soon as we have a confirmed fix or an estimated time to resolution.
May 12, 8:45 AM
identified
Marqeta Engineers have observed elevated STIPs on the Pulse network impacting some cardholders utilizing the Pulse network starting on 11th of May at 10:20 PM PDT. A dedicated response team has been assembled and has identified the technical issue as a processing failure within our systems when encountering a new data pattern originating from the Pulse network. To mitigate the impact and confirm the necessary fix, we have engaged the Pulse team for clarity on this new data behavior, and Pulse...
May 12, 7:48 AM
AWS Outage Impacting Marqeta Services
Started: May 8, 12:46 AM
monitoring
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.
May 11, 2:09 PM
monitoring
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.
May 8, 9:46 PM
monitoring
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.
May 8, 2:00 PM
monitoring
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.
May 8, 6:53 AM
identified
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.
May 8, 5:29 AM
identified
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.
May 8, 4:42 AM
identified
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.
May 8, 4:14 AM
identified
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.
May 8, 3:44 AM
identified
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.
May 8, 3:14 AM
identified
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.
May 8, 2:44 AM
identified
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.
May 8, 2:14 AM
identified
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.
May 8, 1:45 AM
identified
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.
May 8, 1:14 AM
investigating
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.
May 8, 12:46 AM
Delay in Diva reports and MQD endpoints
Started: May 5, 12:29 PM
identified
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 detaile...
May 5, 9:12 PM
identified
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.
May 5, 8:30 PM
identified
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.
May 5, 7:30 PM
identified
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.
May 5, 6:30 PM
investigating
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.
May 5, 5:30 PM
investigating
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.
May 5, 4:32 PM
investigating
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.
May 5, 3:29 PM
investigating
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.
May 5, 2:29 PM
investigating
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.
May 5, 1:29 PM
investigating
An external vendor's unexpected cluster maintenance starting from about 4:00 PM PST 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...
May 5, 12:29 PM
April 2026
3DS Service Degradation
Started: Apr 29, 5:04 PM
identified
Engineers have confirmed that the incident is now stabilized. We will provide a final update once full resolution is confirmed
Apr 29, 10:20 PM
identified
Work continues toward a full resolution. We will provide the next update when new information becomes available.
Apr 29, 9:15 PM
identified
Our engineering teams remain focused on implementing the resolution. We will provide another update in approximately 60 minutes or when new information is provided.
Apr 29, 8:08 PM
identified
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.
Apr 29, 7:04 PM
investigating
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.
Apr 29, 6:35 PM
investigating
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.
Apr 29, 6:04 PM
investigating
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.
Apr 29, 5:32 PM
investigating
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.
Apr 29, 5:04 PM
Increase Rate Of Magstripe Declines
Started: Apr 3, 7:44 PM
identified
Engineers are continuing to work to resolve the last few instances of this issue. We will update here once this work is complete.
Apr 4, 2:55 AM
identified
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.
Apr 3, 7:44 PM
Intermittent STIPs across multiple networks
Started: Apr 2, 8:31 PM
monitoring
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 reso...
Apr 3, 3:10 AM
identified
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 troubleshoo...
Apr 2, 8:31 PM
March 2026
Delay in bank file delivery
Started: Mar 17, 4:09 PM
identified
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.
Mar 17, 4:09 PM
STIPS on Master Card network
Started: Mar 12, 8:29 PM
monitoring
Marqeta Engineering team observed network disturbance resulting in STIPS on the Mastercard network, We observed two distinct periods of impact, starting around 11:14 AM and 12:45 PM Pacific Time , the status is currently stable and our team is actively engaged with MasterCard to understand the root cause.
We are continuously monitoring the network to ensure stability.
Mar 12, 8:29 PM