STATUS
Service status
Read from the running instance. The table below is rendered on the server from measured values, then refreshed in your browser from /api/v1/status.
Componentsregion Tokyo
| Component | State | Detail |
|---|---|---|
| API | operational | database 0.6 ms |
| Audio delivery | operational | 14% used |
| RSS feeds | operational | generated on request |
| Dashboard | operational | shares the API |
| Background jobs | operational | last sweep 93s ago |
States come from database latency, free disk space and the age of the last background sweep. There is no history page yet; this shows the current reading only.
How these are measured
- API
- A write-and-read round trip to the database on each check. Under 50 ms is operational.
- Audio delivery
- Free disk space in the data directory. Below 3 GB free, uploads are paused and this shows degraded.
- RSS feeds
- Feeds are generated on request, so this reflects the API check.
- Background jobs
- The sweep that clears expired sessions and publishes scheduled episodes. Degraded if it has not run in the last hour.