API Endpoint intermittent Connectivity Issues

What to do

• Check whether you use Marqeta Core API. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 9h 36m it lasted.

  Anything that failed between 2026-07-21 13:31 UTC and 2026-07-21 23:07 UTC may need a replay.

• Subscribe to Marqeta's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=marqeta works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Marqeta 3

1. identifiedJul 21, 2026, 1:31 PM UTC

   Marqeta engineering team is currently investigating an issue affecting a subset of our customers experiencing intermittent failures when accessing Marqeta API endpoints. Our engineering team has identified the issue and is actively working to remediate it .We will provide a further update within the next 30 minutes as our teams continue to work toward full resolution. We sincerely apologize for any disruption this may be causing to your operations and appreciate your patience as we work urgently to restore full service.

   provider

2. monitoringJul 21, 2026, 2:00 PM UTC

   On Tuesday, July 21, 2026, Marqeta engineering team investigated an issue affecting a subset of our customers experiencing intermittent failures when accessing Marqeta API endpoints. Marqeta engineering team has completed at 06:40 PT a configuration change as part of our ongoing remediation efforts. No further intermittent SSL handshake connection failures are currently observed .We are continuing to closely monitor our systems and analyze metrics to determine the root cause and ensure full service stability. We will share a resolving update once long term stability is confirmed.

   provider

3. resolvedJul 21, 2026, 11:07 PM UTC

   On July 21, 2026, a subset of customers experienced intermittent failures when accessing Marqeta API endpoints. The issue was caused by an insufficient number of service instances in a specific availability zone, which led to resource constraints and connection limit exhaustion under load. Our engineering team resolved the issue by scaling up instance capacity and significantly increasing connection limits to address the underlying scaling constraints. All affected services have returned to normal operation and we have confirmed stable performance across the platform after concluding a monitoring period. We sincerely apologize for any disruption this caused and thank you for your patience.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.