PyPI logo

PyPI JSON API status

How long one request to the PyPI JSON API takes from 6 cities, checked every 30 minutes.

  • Package registry
  • PyPI
Copy link

Last checked Every 30 minutes

Responding normally from 6 cities

PyPI JSON API is responding normally from all 6 cities.

Typical response time
13 ms
Last 24 hours · usually 14 ms
Slower response time
123 ms
95% of checks came in under this
Failed requests
0
Out of 855 requests in 24 hours
Open incidents
0
None right now

PyPI JSON API by city

The latest response time from each test location against its usual value. Each mark in the strip is one check.

CityStatusNowUsualLast 24 hours
NetherlandsAmsterdamNormal11 ms12 ms
United StatesSan FranciscoNormal71 ms62 ms
CanadaMontrealNormal121 ms16 ms
SingaporeSingaporeNormal42 ms15 ms
JapanTokyoNormal13 ms11 ms
IndiaMumbaiNormal11 ms11 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

Response time for each check, as the median across all cities.

0 ms20 ms40 ms06:0009:0012:0015:0018:0021:0000:0003:00
Median across cities, each check (UTC)Usual (14 ms)

Recent incidents

All incidents →
  1. DegradedMontreal

    , lasted 90 minutes · peak 330 ms, usually 17 ms

    What happened →
  2. DegradedMontreal

    , lasted 7 hours · peak 327 ms, usually 17 ms

    What happened →
  3. DegradedMontreal

    , lasted 90 minutes · peak 289 ms, usually 19 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.

  • Montreal · slower for about an hour · peak 401 ms, usually 16 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 250 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.

Full method →

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.