Status
Last updated 2026-11-20
All 4 checks passed in the round at 2026-11-20 13:50 UTC.
| Component | Last check | Response time | Uptime |
|---|---|---|---|
| Website | Passed, 2026-11-20 13:50 UTC | 41 ms | 100% since 2026-11-20 (6 of 6 checks passed) |
| API | Passed, 2026-11-20 13:50 UTC | 59 ms | 100% since 2026-11-20 (6 of 6 checks passed) |
| Conversion servers | Passed, 2026-11-20 13:50 UTC | 267 ms | 100% since 2026-11-20 (6 of 6 checks passed) |
| Sign-in and dashboard | Passed, 2026-11-20 13:50 UTC | 63 ms | 100% since 2026-11-20 (6 of 6 checks passed) |
Daily results
every check passed at least 90% passed fewer passed no checks ran. Days are UTC.
Page generated at 2026-11-20 13:53 UTC. The same results as JSON: /status.json.
What we check
Every 5 minutes our site's own Worker, running on our hosting provider's network, makes these four requests at the same time. A check passes when the expected answer arrives within 10 seconds; anything else, including no answer, fails.
- Website. Loads the home page and expects HTTP 200 with the page naming PDFConversionAPI.
- API. Calls GET /health on api.pdfconversionapi.com and expects HTTP 200 with Status ok.
- Conversion servers. Asks the API for a stored file that doesn't exist. The request goes on to the conversion servers and their file storage, and a healthy answer is the API's own 404. It doesn't run a conversion.
- Sign-in and dashboard. Loads the sign-in page on app.pdfconversionapi.com and expects HTTP 200 with the page naming PDFConversionAPI.
What the figures mean
- Uptime is the share of checks that passed, counted from the first day with results, which is shown next to each figure. Time before that day isn't counted, and a figure is rounded down, so one failed check never shows as 100%.
- Daily results show one bar per UTC day for the last 90 days, from the day the checks began. A day with no bar color had no checks.
- Response time is how long the last check took to get the whole answer. The checks run inside our provider's network, so they don't see problems on the path between your servers and ours, and the times are not what your requests will measure.
- A failed check means our own request didn't get the expected answer. It can fail when the service works for most requests, and a problem can come and go between two checks.
This page reports what our checks saw. It is not a service level agreement or an uptime commitment, and we don't offer either.
If this page doesn't load
This page is served by the website, so when the website is down, so is this page. You can still ask the API directly; a healthy API answers with HTTP 200 and "Status":"ok":
curl -sS https://api.pdfconversionapi.com/healthIf your requests fail with an error, Errors says what each status code means and which ones to retry. To report a problem, write to support@pdfconversionapi.com with the x-request-id of a failed request.
The results as JSON
/status.json has the same results: for each component, the day checks began, the number of checks and how many passed, the last result with its time, status code and response time, the last failed check, and the totals per day. It is regenerated at most once a minute.