GitHub Git handshake status
How long a Git handshake with GitHub takes from 6 cities, checked every 30 minutes.
- Git hosting
- GitHub
Last checked Every 30 minutes
Responding normally from 6 cities
GitHub Git handshake is responding normally from all 6 cities.
- Typical Git handshake time
- 219 ms
- Last 24 hours · usually 213 ms
- Slower Git handshake time
- 719 ms
- 95% of checks came in under this
- Failed requests
- 0
- Out of 864 requests in 24 hours
- Open incidents
- 0
- None right now
GitHub Git handshake by city
The latest handshake from each test location against its usual value. Each mark in the strip is one check.
| City | Status | Now | Usual | Last 24 hours |
|---|---|---|---|---|
 Amsterdam | Normal | 205 ms | 196 ms | |
 San Francisco | Normal | 222 ms | 230 ms | |
 Montreal | Normal | 75 ms | 79 ms | |
 Singapore | Normal | 743 ms | 714 ms | |
 Tokyo | Normal | 186 ms | 190 ms | |
 Mumbai | Normal | 308 ms | 290 ms |
- Normal
- Slower than usual
- Some requests failed or degraded
- No check, or ours couldn't be verified
Colours compare each city with its own usual value, not with other services or cities. In the strip, grey marks are normal checks.
Last 24 hours
Git handshake time for each check, as the median across all cities.
Recent incidents
All incidents →- Slower than usualMumbai
, lasted 90 minutes · peak 581 ms, usually 280 ms
What happened → - DegradedAmsterdam, Mumbai, Singapore
, lasted 4 hours · peak 1.20 s, usually 711 ms
What happened → - DegradedAmsterdam, Mumbai, Singapore, Tokyo
, lasted 3 hours · peak 1.21 s, usually 709 ms
What happened →
Brief slowdowns in our checks
Two or more slow checks in a row over the last seven days that didn't last long enough to count as an incident.
- Amsterdam · slower for about an hour · peak 509 ms, usually 190 ms
- San Francisco · slower for about an hour · peak 743 ms, usually 235 ms
- Montreal · slower for about an hour · peak 606 ms, usually 84 ms
How these checks work
- Every 30 minutes, each of our 6 test locations sends 3 requests to every service on this page.
- We compare each result with the same city's usual value over the last 7 days. A city is slower than usual above 1.5× that value (and at least 100 ms more), and degraded above 2.5×.
- If 10% or more of a city's recent requests fail, it shows "Some requests failed"; from 25% it is degraded.
- One city has to stay that way for 90 minutes before we show it. When 3 or more cities see it at the same time, we show it straight away. It takes 90 minutes of normal checks to clear.
- Each city also fetches two small files from two unrelated networks. If both are slow too, the problem is most likely on our side, and we say so instead of blaming the service.
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.
No account required · Takes about 30 seconds.