Incident history

Slowdowns and failures our checks confirmed over the last 7 days, newest first. Shorter slow spells show on each service's own page.

    1. GitHub Git handshakeSlower than usualMumbai

      , lasted 90 minutes · peak 581 ms, usually 280 ms

      What happened →
    2. GitHub Git handshakeDegradedAmsterdam, Mumbai, Singapore

      , lasted 4 hours · peak 1.20 s, usually 711 ms

      What happened →
    1. GitHub Git handshakeDegradedAmsterdam, Mumbai, Singapore, Tokyo

      , lasted 3 hours · peak 1.21 s, usually 709 ms

      What happened →
    2. GitHub Git handshakeDegradedAmsterdam, Mumbai, Singapore

      , lasted 2.5 hours · peak 1.19 s, usually 708 ms

      What happened →
    3. Jev APIDegradedAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 3.5 hours · peak 4.99 s, usually 106 ms

      What happened →
    4. GitHub Git handshakeDegradedAmsterdam, Mumbai, Tokyo

      , lasted 2 hours · peak 657 ms, usually 280 ms

      What happened →
    5. Claude APIDegradedAmsterdam, Mumbai, San Francisco, Montreal

      , lasted 2 hours · peak 7.39 s, usually 1.25 s

      What happened →
    6. DeepSeek APISlower than usualMumbai, Singapore, Tokyo

      , lasted 2 hours · peak 1.50 s, usually 631 ms

      What happened →
    7. GitHub Git handshakeDegradedAmsterdam, Mumbai, San Francisco, Tokyo

      , lasted 2 hours · peak 940 ms, usually 190 ms

      What happened →
    1. GitHub Git handshakeDegradedAmsterdam, Mumbai, Singapore, Tokyo

      , lasted 2 hours · peak 1.39 s, usually 707 ms

      What happened →
    2. DeepSeek APISlower than usualAmsterdam, Mumbai, Singapore, Montreal

      , lasted 2 hours · peak 1.67 s, usually 741 ms

      What happened →
    3. GitHub Git handshakeDegradedAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 7.5 hours · peak 1.29 s, usually 708 ms

      What happened →
    4. , lasted 2 hours · peak 487 ms, usually 188 ms

      What happened →
    1. ChatGPT APISlower than usualAmsterdam, Mumbai, Singapore, Tokyo, Montreal

      , lasted 5.5 hours · peak 3.56 s, usually 1.58 s

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

      , lasted 2 hours · peak 2.11 s, usually 1.28 s

      What happened →
    3. ChatGPT APISlower than usualMontreal

      , lasted 90 minutes · peak 1.84 s, usually 1.12 s

      What happened →
    4. Claude APIDegradedAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 4.5 hours · peak 7.69 s, usually 1.17 s

      What happened →
    5. GitHub Git handshakeDegradedAmsterdam, Mumbai, Singapore, Tokyo

      , lasted 2 hours · peak 1.09 s, usually 708 ms

      What happened →
    6. Claude APISlower than usualSan Francisco, Singapore, Tokyo

      , lasted 2 hours · peak 2.74 s, usually 1.26 s

      What happened →
    1. Claude APISlower than usualMumbai, Tokyo, Montreal

      , lasted 3 hours · peak 2.94 s, usually 1.11 s

      What happened →
    2. GitHub Git handshakeDegradedAmsterdam, Mumbai, Tokyo

      , lasted 2 hours · peak 882 ms, usually 190 ms

      What happened →
    3. ChatGPT APIDegradedAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 2 hours · peak 3.22 s, usually 1.20 s

      What happened →
    4. ChatGPT APISlower than usualSan Francisco

      , lasted 90 minutes · peak 1.83 s, usually 1.10 s

      What happened →
    5. GitHub Git handshakeDegradedAmsterdam, Mumbai, Tokyo

      , lasted 2 hours · peak 539 ms, usually 276 ms

      What happened →

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.