Skip to main content
OpenAI

Elevated error rates with some U.S. business Mastercards

Operational Lasted 3d 21h · started · OpenAI's page

Level
confirmed
Worst impact
Operational

Summary

OpenAI says some U.S. business Mastercards are seeing payment declines, which can prevent API automatic recharges and one-time credit purchases. The provider has applied a mitigation and is monitoring the affected services to confirm recovery.

Written by anthropic/claude-haiku-5.5 from OpenAI's own updates.

What to do

  • Check whether your product depends on OpenAI. 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 21h it lasted.

    Anything that failed between 2026-11-06 18:38 UTC and 2026-11-10 16:06 UTC may need a replay.
  • Subscribe to OpenAI's feed to hear about the next one first. RSS feed

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

Updates from OpenAI 4

  1. identified

    Investigating — We’re seeing payment declines on some U.S. business Mastercards. Affected cards have numbers beginning with 544015, 546400, 543502, 543799, or 512998. Some cards beginning with 513989 are also affected. For API customers, this can prevent automatic recharges and one-time credit purchases. If your prepaid balance runs out, your API requests may fail. If you use one of these cards, we recommend adding a card from a different issuer before your next payment, even if you haven’t seen a decline. If an API credit purchase has already failed, use the new card to retry the purchase. We’re working with our payment partners and will share updates here.

    provider

  2. identified

    Investigating — We’re seeing payment declines on some U.S. business Mastercards. Affected cards have numbers beginning with 544015, 546400, 543502, 543799, or 512998. Some cards beginning with 513989 are also affected. For API customers, this can prevent automatic recharges and one-time credit purchases. If your prepaid balance runs out, your API requests may fail. If you use one of these cards, we recommend adding a card from a different issuer before your next payment, even if you haven’t seen a decline. If an API credit purchase has already failed, use the new card to retry the purchase. We’re working with our payment partners and will share updates here.

    provider

  3. monitoring

    We’ve applied a mitigation and are monitoring the affected services to confirm recovery.

    provider

  4. resolved

    All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-a701810e96

Is OpenAI still down?

No, this incident was resolved 2026-11-10 16:06 UTC. For OpenAI's live state, see https://down.guide/providers/openai.

How long did it last?

3d 21h, from 2026-11-06 18:38 UTC to 2026-11-10 16:06 UTC, by the times OpenAI posted.

What caused it?

OpenAI hasn't published a root cause. If it does, it shows here.

Where does this come from?

OpenAI's official status page, https://status.openai.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.