System status.
- Key database unavailable2026-09-26 20:50 UTC → 2026-09-26 22:50 UTC
The API-key database stopped answering, so requests that needed a key check failed. Market data itself was unaffected. From 22:50 UTC, requests with existing keys were served from a replicated copy of key records while the database recovered. On 27 Sep the key database moved to a dedicated paid instance.
- Key database unavailable2026-09-25 05:00 UTC → 2026-09-25 17:45 UTC
The API-key database stopped answering, so requests that needed a key check failed. Market data itself was unaffected. Continuous 05:00–14:00 UTC, intermittent (HTTP 503) until 17:45.
- Key database unavailable2026-09-24 11:31 UTC → 2026-09-24 14:16 UTC
The API-key database stopped answering, so requests that needed a key check failed. Market data itself was unaffected. Requests returned HTTP 503.
- Key database unavailable2026-09-23 12:35 UTC → 2026-09-23 13:46 UTC
The API-key database stopped answering, so requests that needed a key check failed. Market data itself was unaffected. Also brief HTTP 503s at 05:15 and 08:30 UTC.
- Key database unavailable2026-09-22 12:45 UTC → 2026-09-22 16:30 UTC
The API-key database stopped answering, so requests that needed a key check failed. Market data itself was unaffected. Requests returned HTTP 503. Payment notifications in this window were delayed and later reconciled.
- Key database unavailable2026-09-21 16:01 UTC → 2026-09-21 16:16 UTC
The API-key database stopped answering, so requests that needed a key check failed. Market data itself was unaffected.
- Key database unavailable2026-09-18 13:35 UTC → 2026-09-18 16:25 UTC
The API-key database stopped answering, so requests that needed a key check failed. Market data itself was unaffected. Requests returned HTTP 500/524.
- Key database unavailable2026-09-17 09:31 UTC → 2026-09-17 10:20 UTC
The API-key database stopped answering, so requests that needed a key check failed. Market data itself was unaffected. Requests returned HTTP 500/524.
- Key database unavailable2026-09-15 08:35 UTC → 2026-09-15 10:15 UTC
The API-key database stopped answering, so requests that needed a key check failed. Market data itself was unaffected. Requests returned HTTP 500/524.
- Intermittent key-check errors2026-09-14 05:00 UTC → 2026-09-14 13:31 UTC
Some requests failed with HTTP 500 ("Usage tracking failed") while the key database shed load. Most requests succeeded.
- Key database unavailable2026-09-09 13:00 UTC → 2026-09-10 14:30 UTC
The API-key database stopped answering, so requests that needed a key check failed. Market data itself was unaffected. Caused by lock contention on key records; fixed by migration 017 on 10 Sep. Requests hung without a response for much of this window.
- Key database unavailable2026-09-08 15:20 UTC → 2026-09-08 17:48 UTC
The API-key database stopped answering, so requests that needed a key check failed. Market data itself was unaffected. Requests returned HTTP 5xx.
- Key database unavailable2026-09-04 11:01 UTC → 2026-09-04 13:31 UTC
The API-key database stopped answering, so requests that needed a key check failed. Market data itself was unaffected.
- Key database unavailable2026-09-03 13:20 UTC → 2026-09-03 13:31 UTC
The API-key database stopped answering, so requests that needed a key check failed. Market data itself was unaffected.
A monitor on a separate server calls the API every 5 minutes the way a customer would, including a request with a real API key, and keeps its own record. Uptime is measured against the checks that should have run: a missed check counts as downtime, and if the monitor stops reporting this page says the status is unknown rather than operational. Bars show daily uptime over the last 90 days: green ≥99.5%, gold ≥95%, red below.
Incidents are listed above; fixes are documented in the changelog. Machine readers: poll /health for real-time freshness metadata.