Status and service level

What the API is committed to, and what it has actually done. Both are here because a target without a measurement is a sentence, and a measurement without a target is a number nobody can hold us to.

Last request served 5 minutes ago

Availability, 30 days

99.753%

39,232 calls · target 99.5%

Availability, 24 hours

100.000%

0 of 1,330 failed

Median response

25 ms

over 30 days

95th percentile

100 ms

target under 800 ms

How long a request takes

Counts rather than an average, because a mean hides the tail completely: a hundred fast calls and one that took eight seconds average out to something healthy, and the eight seconds is the one you noticed.

under 25 ms88.0%

under 50 ms5.8%

under 100 ms2.1%

under 250 ms0.4%

under 500 ms0.8%

under 1000 ms2.3%

under 2500 ms0.3%

under 5000 ms0.2%

over 5000 ms0.1%

What we commit to

99.5% of API calls answered: Measured over a calendar month, counting only failures that are ours. A 402 is the price working, a 404 is a request for something absent, and a 429 is a quota doing its job — none of those is an outage, and counting them would let a mistyped slug read as one while hiding a real failure inside the noise.
95% of calls under 800 ms: Server time, from request to response. It excludes the network between us and you, which we cannot measure and will not claim to.
Notice before anything breaks: A removed field or a changed meaning gets thirty days’ notice by email to every account with a key. Adding a field is not a breaking change and will happen without warning.
If a month misses: a month of the plan, credited without being asked for: Applied from this page’s own numbers rather than on request. Somebody who has to notice and complain to be compensated is somebody being charged for our failure to notice.

The limits of this page

This is one machine in one place. There is no failover, so a hardware fault or a network partition at the host is an outage, and the honest expectation is hours rather than seconds. The measurement is taken inside the server: a request that never reached us cannot appear here, which is precisely the failure you are most likely to experience and least likely to see reflected. Planned maintenance is announced in advance and counted against the number like any other downtime — an availability figure with the bad days excluded is not an availability figure.

Something broken? How to reach us.

How long a request takes

under 25 ms88.0%

under 50 ms5.8%

under 100 ms2.1%

under 250 ms0.4%

under 500 ms0.8%

under 1000 ms2.3%

under 2500 ms0.3%

under 5000 ms0.2%

over 5000 ms0.1%

What we commit to

99.5% of API calls answered

Measured over a calendar month, counting only failures that are ours. A 402 is the price working, a 404 is a request for something absent, and a 429 is a quota doing its job — none of those is an outage, and counting them would let a mistyped slug read as one while hiding a real failure inside the noise.

95% of calls under 800 ms

Server time, from request to response. It excludes the network between us and you, which we cannot measure and will not claim to.

Notice before anything breaks

A removed field or a changed meaning gets thirty days’ notice by email to every account with a key. Adding a field is not a breaking change and will happen without warning.

If a month misses: a month of the plan, credited without being asked for

Applied from this page’s own numbers rather than on request. Somebody who has to notice and complain to be compensated is somebody being charged for our failure to notice.