Jev API status
How fast the Jev API starts answering from 6 cities, checked every 30 minutes.
- AI API
- TypeSafe
- jev-1.13.0
Last checked Every 30 minutes
Responding normally from 6 cities
Jev API is responding normally from all 6 cities.
- Typical full response time
- 162 ms
- Last 24 hours · usually 159 ms
- Slower full response time
- 286 ms
- 95% of checks came in under this
- Failed requests
- 0
- Out of 852 requests in 24 hours
- Open incidents
- 0
- None right now
Jev API by city
The latest full response time from each test location against its usual value. Each mark in the strip is one check.
| City | Status | Now | Usual | Last 24 hours |
|---|---|---|---|---|
| Normal | 181 ms | 171 ms | ||
| Normal | 68 ms | 83 ms | ||
| Normal | 109 ms | 93 ms | ||
| Normal | 223 ms | 240 ms | ||
| Normal | 133 ms | 147 ms | ||
| Normal | 270 ms | 278 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
Full response time for each check, as the median across all cities.
Recent incidents
All incidents →- Slower than usualSingapore
, lasted 90 minutes · peak 387 ms, usually 241 ms
What happened → - Slower than usualSingapore
, lasted 90 minutes · peak 386 ms, usually 241 ms
What happened → - Slower than usualSingapore
, lasted 90 minutes · peak 402 ms, usually 240 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.
- Singapore · slower for about an hour · peak 383 ms, usually 241 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.