Guide
Service status
Check live API uptime and incident history, and subscribe to status updates.
API2Convert publishes a live status page at status.api2convert.com. It is the canonical place to check whether the API is operating normally, review recent uptime, and get notified about incidents. The status page is hosted independently of the API, so it stays reachable even when the API itself is affected by an outage.
What it shows
- Current availability — whether the API is up or down right now.
- Uptime history — the percentage of time the API was available over the last 24 hours, 7 days, 30 days and 90 days, plus a day-by-day calendar.
- Status updates — a timeline of recent incidents and maintenance announcements.
The status page tracks overall API availability (up / down); it does not report per-endpoint latency or per-format processing times. To measure your own usage and throughput, use the statistics endpoints.
Subscribe to updates
Use the Subscribe option on the status page to receive an email whenever the status changes or an incident is posted. This is the recommended way to hear about outages and planned maintenance — no polling required.
Service status vs. API statuses
Don't confuse the service status page with the API's own status values — they answer different questions:
| Concept | Where to look | What it tells you |
|---|---|---|
| Service status page | status.api2convert.com | Whether the whole API platform is operational right now, plus uptime history and incidents. |
| Job status | The status.code field on a job (e.g. downloading, completed, failed) |
How one of your conversion jobs is progressing. See Jobs & lifecycle. |
| Job status catalogue | GET /v2/statuses |
The list of every possible job status code and its meaning (no API key required). |
During an incident
If requests start failing with 500 responses or time out, check the status page first to see whether it is a known platform incident. While an incident is ongoing:
- Retry failed requests with exponential backoff rather than tight retry loops — see rate limits & contracts.
- Prefer webhooks & callbacks over polling, so queued jobs report in automatically once processing resumes.
- Distinguish a platform outage from a per-job problem: a genuine outage appears on the status page, whereas a single job that fails while the platform is healthy is usually an input or conversion error.