Intermittent STIPs across multiple networks

What to do

• Check whether you use Marqeta Core API, Payment Processing, Digital Wallets & Tokenization. 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 3d 22h it lasted.

  Anything that failed between 2026-04-02 20:31 UTC and 2026-04-06 18:32 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. identifiedApr 2, 2026, 8: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.

   provider

2. monitoringApr 3, 2026, 3: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.

   provider

3. resolvedApr 6, 2026, 6: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.

   provider

Corrections

None so far.

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