Claude 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 11 hours · peak 4.98 s, usually 1.53 s

      What happened →
    2. Slower than usualAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 11 hours · peak 2.67 s, usually 1.56 s

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

      , lasted 9.5 hours · peak 2.21 s, usually 968 ms

      What happened →
    2. Slower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 10 hours · peak 2.04 s, usually 972 ms

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

      , lasted 11.5 hours · peak 2.16 s, usually 984 ms

      What happened →
    2. Slower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 2 hours · peak 2.13 s, usually 919 ms

      What happened →
    3. Slower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 5.5 hours · peak 1.96 s, usually 937 ms

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

      , lasted 3 hours · peak 2.01 s, usually 928 ms

      What happened →
    2. Slower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 3 hours · peak 1.72 s, usually 936 ms

      What happened →
    3. Slower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 2.5 hours · peak 1.85 s, usually 1.04 s

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

      , lasted 6 hours · peak 2.48 s, usually 1.04 s

      What happened →
    2. Slower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 2 hours · peak 1.74 s, usually 982 ms

      What happened →
    3. Slower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 4 hours · peak 2.13 s, usually 982 ms

      What happened →
    4. Some requests failedAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 4.5 hours · peak 1.97 s, usually 858 ms

      What happened →
    5. Slower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 2.5 hours · peak 2.07 s, usually 868 ms

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

      , lasted 90 minutes · peak 1.83 s, usually 982 ms

      What happened →
    2. Slower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 5 hours · peak 1.92 s, usually 1.02 s

      What happened →
    3. Slower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 2.5 hours · peak 1.81 s, usually 1.01 s

      What happened →
    4. Slower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 4.5 hours · peak 1.77 s, usually 1.05 s

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

      , lasted 3.5 hours · peak 1.97 s, usually 756 ms

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

      , lasted 4 hours · peak 2.26 s, usually 1.10 s

      What happened →
    3. Slower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 4 hours · peak 2.36 s, usually 1.09 s

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

      , lasted 13.5 hours · peak 2.30 s, usually 1.03 s

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

      , lasted 3 hours · peak 2.13 s, usually 1.12 s

      What happened →
    2. Slower than usualAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 6 hours · peak 2.31 s, usually 1.12 s

      What happened →
    3. Slower than usualAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 5.5 hours · peak 2.37 s, usually 1.13 s

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

      , lasted 3.5 hours · peak 2.21 s, usually 1.10 s

      What happened →
    2. Slower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 3.5 hours · peak 2.35 s, usually 1.10 s

      What happened →
    3. Slower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 4.5 hours · peak 1.74 s, usually 1.11 s

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

      , lasted 7 hours · peak 1.68 s, usually 1.00 s

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

      , lasted 3.5 hours · peak 1.74 s, usually 1.12 s

      What happened →
    2. Slower than usualAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 3 hours · peak 1.70 s, usually 1.07 s

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

      , lasted 9 hours · peak 2.23 s, usually 983 ms

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

      , lasted 5 hours · peak 3.34 s, usually 1.07 s

      What happened →
    3. Slower than usualAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 5.5 hours · peak 1.95 s, usually 1.13 s

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

      , lasted 8.5 hours · peak 2.17 s, usually 1.00 s

      What happened →
    2. Slower than usualAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 3.5 hours · peak 1.98 s, usually 1.12 s

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

      , lasted 2.5 hours · peak 2.21 s, usually 905 ms

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

      , lasted 6.5 hours · peak 2.53 s, usually 1.11 s

      What happened →
    3. Slower than usualAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 9.5 hours · peak 2.41 s, usually 1.11 s

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

      , lasted 90 minutes · peak 2.36 s, usually 1.04 s

      What happened →
    2. Slower than usualAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 3.5 hours · peak 2.06 s, usually 1.01 s

      What happened →
    3. Slower than usualAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 6 hours · peak 2.23 s, usually 1.01 s

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

      , lasted 11 hours · peak 2.22 s, usually 1.02 s

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

      , lasted 90 minutes · peak 2.29 s, usually 1.03 s

      What happened →
    3. Slower than usualAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 6 hours · peak 2.06 s, usually 1.14 s

      What happened →
    4. Slower than usualAmsterdam, Mumbai, San Francisco, Singapore, Montreal

      , lasted 3 hours · peak 1.75 s, usually 1.07 s

      What happened →
    1. Slower than usualSan Francisco, Singapore, Tokyo, Montreal

      , lasted 90 minutes · peak 1.63 s, usually 1.08 s

      What happened →

Claude 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.