GitLab Git handshake status
How long a Git handshake with GitLab takes from 6 cities, checked every 30 minutes.
- Git hosting
- GitLab
Last checked Every 30 minutes
Collecting a baseline
Collecting a Git handshake baseline for GitLab from Amsterdam.
- Typical Git handshake time
- 335 ms
- Last 24 hours · usually 324 ms
- Slower Git handshake time
- 480 ms
- 95% of checks came in under this
- Failed requests
- 0
- Out of 828 requests in 24 hours
- Open incidents
- 0
- None right now
GitLab 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 | 302 ms | 300 ms | |
 San Francisco | Collecting baseline | 287 ms | 267 ms | |
 Montreal | Collecting baseline | 220 ms | 222 ms | |
 Singapore | Collecting baseline | 420 ms | 440 ms | |
 Tokyo | Collecting baseline | 346 ms | 348 ms | |
 Mumbai | Collecting baseline | 446 ms | 454 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 3.5 hours · peak 864 ms, usually 459 ms
- Slower than usualMumbai
, lasted 9 hours · peak 951 ms, usually 458 ms
- Slower than usualMumbai, Singapore
, lasted 5.5 hours · peak 853 ms, usually 455 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.
- San Francisco · slower for about an hour · peak 531 ms, usually 274 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.