Status
Measured, not promised
Every figure on this page is computed from the API's own request log and price tables, over the last 30 days, and recomputed every hour. The method for each is written out below it.
- 2.3M
- requests served
- Since Oct 2, 2026, 12:43 PM UTC, by 63 accounts.
- 47 ms
- median response time
- p95 449 ms. Server-side, every request, cached or not.
- 100%
- responses without a server error
- 0 responses with a 5xx status in the window.
- in the last hour
- Cardmarket last read
- Each source's most recent successful read is listed below.
Computed Nov 1, 2026, 12:42 PM UTC. Figures are recomputed at most every 60 minutes.
By day
The last thirty days
Requests, median latency and server errors per UTC day. A quiet day is a quiet day, not a gap in the log.
| Day | Requests | Volume | p50 | 5xx |
|---|---|---|---|---|
| Nov 1 | 35,812 | 45 ms | 0 | |
| Oct 31 | 70,096 | 36 ms | 0 | |
| Oct 30 | 76,018 | 38 ms | 0 | |
| Oct 29 | 72,619 | 37 ms | 0 | |
| Oct 28 | 300,667 | 27 ms | 0 | |
| Oct 27 | 203,486 | 30 ms | 0 | |
| Oct 26 | 75,225 | 37 ms | 0 | |
| Oct 25 | 86,388 | 35 ms | 0 | |
| Oct 24 | 83,339 | 35 ms | 0 | |
| Oct 23 | 76,474 | 37 ms | 0 | |
| Oct 22 | 79,275 | 39 ms | 0 | |
| Oct 21 | 78,523 | 41 ms | 0 | |
| Oct 20 | 74,789 | 39 ms | 0 | |
| Oct 19 | 80,719 | 74 ms | 0 | |
| Oct 18 | 80,210 | 68 ms | 0 | |
| Oct 17 | 59,601 | 77 ms | 0 | |
| Oct 16 | 41,444 | 64 ms | 0 | |
| Oct 15 | 70,376 | 65 ms | 0 | |
| Oct 14 | 47,031 | 65 ms | 0 | |
| Oct 13 | 37,440 | 70 ms | 0 | |
| Oct 12 | 51,828 | 69 ms | 0 | |
| Oct 11 | 84,868 | 72 ms | 0 | |
| Oct 10 | 55,797 | 64 ms | 0 | |
| Oct 9 | 57,016 | 64 ms | 0 | |
| Oct 8 | 36,997 | 77 ms | 0 | |
| Oct 7 | 40,751 | 70 ms | 0 | |
| Oct 6 | 41,075 | 86 ms | 0 | |
| Oct 5 | 36,351 | 81 ms | 0 | |
| Oct 4 | 68,370 | 71 ms | 0 | |
| Oct 3 | 54,838 | 80 ms | 0 | |
| Oct 2 | 23,919 | 86 ms | 0 |
Price sources
When each marketplace was last read
A quote's own updatedAt field carries this per card. Here it is per source, so a stalled feed shows up before a customer notices.
- Cardmarket
- in the last hour
- Nov 1, 2026, 12:42 PM UTC
- TCGplayer
- 7 hours ago
- Nov 1, 2026, 5:38 AM UTC
- Card Kingdom
- 7 hours ago
- Nov 1, 2026, 5:38 AM UTC
- Manapool
- 7 hours ago
- Nov 1, 2026, 5:38 AM UTC
Method
How every number is produced
Requests served
A count of rows in the request log for the window. Every authenticated call to the REST or GraphQL API writes one row after the response is sent, whatever the status code and whether or not the response came from cache. Unauthenticated probes and static assets are not counted; neither is traffic to this website.
Median response time
The time from a request reaching the billing gate to the response body being handed back to the web server, recorded on every row and summarised as the 50th and 95th percentiles. It is server-side: it does not include the network between you and us, or TLS. A figure measured from a client somewhere else will be higher, and how much higher depends on where the client is.
Responses without a server error
The share of responses in the window with a status below 500. A 4xx is the client's error and is counted as served; a 5xx is ours and is counted against us. This is not an uptime figure. A minute in which the API answered nobody because it was down leaves no rows and is therefore invisible here, which is why the day table shows volume alongside errors: a day with far fewer requests than its neighbours deserves a question.
Price freshness
The most recent fetched_at across all quotes from a source. A source is read on a schedule, nightly for Cardmarket and TCGplayer, so a figure of a few hours is normal and a figure of a few days means a feed has stalled.
What this page does not tell you
It has no external monitor and no incident history yet; the service has been logging since September 2026 and the window is capped at what exists. If you need a contractual number, the Scale plan carries a 99.95% uptime SLA.