ChatGPT API incidents in November 2026

Slowdowns and failures our checks confirmed, newest first. Shorter slow spells only show on the live status page.

    1. DegradedAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 5 hours · peak 3.28 s, usually 1.14 s

      What happened →
    2. DegradedAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 5.5 hours · peak 3.03 s, usually 1.11 s

      What happened →
    1. DegradedAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 11 hours · peak 4.25 s, usually 1.07 s

      What happened →
    1. Slower than usualAmsterdam, San Francisco, Montreal

      , lasted 3.5 hours · peak 2.71 s, usually 1.02 s

      What happened →
    2. DegradedAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 11.5 hours · peak 3.48 s, usually 1.31 s

      What happened →
    1. DegradedAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 9.5 hours · peak 4.53 s, usually 1.13 s

      What happened →
    1. DegradedAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 3 hours · peak 8.63 s, usually 1.13 s

      What happened →
    1. Slower than usualSingapore

      , lasted 90 minutes · peak 2.24 s, usually 1.22 s

      What happened →

ChatGPT API status right now

How fast is your API around the world?

Run a free speed test from multiple cities and find out where your users are waiting. No setup, no account required.

Test my API

No account required · Takes about 30 seconds.