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
Collecting a baseline
Collecting a Git handshake baseline for GitHub from Amsterdam.
- Typical Git handshake time
- 244 ms
- Last 24 hours · usually 213 ms
- Slower Git handshake time
- 737 ms
- 95% of checks came in under this
- Failed requests
- 0
- Out of 828 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 | Collecting baseline | 431 ms | 189 ms | |
 San Francisco | Collecting baseline | 312 ms | 236 ms | |
 Montreal | Collecting baseline | 145 ms | 85 ms | |
 Singapore | Collecting baseline | 968 ms | 697 ms | |
 Tokyo | Collecting baseline | 332 ms | 181 ms | |
 Mumbai | Collecting baseline | 628 ms | 272 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 →- DegradedMumbai, Singapore, Tokyo
, lasted 2 hours · peak 1.28 s, usually 696 ms
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.
- Mumbai · some requests failed for about an hour · peak 699 ms, usually 284 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.