# Support and status
Where to get help when something is not working, where to manage your account, and where to check whether the service is healthy right now.
How to get unblocked when something isn't working, and where to check whether the
service is healthy.
## Getting help
- **Email**: [support@pdfblocks.com](mailto:support@pdfblocks.com). Include the
action you called, the request (with your key redacted), and the full
`application/problem+json` error body if you got one. See
[Errors](/docs/api/errors) for how to read it.
- **Support page**: [www.pdfblocks.com/support](https://www.pdfblocks.com/support).
When you write in, the response's `type` URL and the `errors` field-to-message map
from a failed response are the fastest way for us to reproduce the problem.
## Account and usage
Manage your API keys, plan, and usage from the
[dashboard](https://dashboard.pdfblocks.com). Rotate a leaked key there, and
check usage there rather than inferring it from responses. See
[Authentication](/docs/api/authentication) for key handling.
## Service status
Current service health, uptime history, and incident updates are published on our
status page: [pdfblocks.statuspage.io](https://pdfblocks.statuspage.io). You can
subscribe there to be notified when an incident is opened or resolved.
The API runs across [multiple regional endpoints](/docs/api/regions-and-data-residency),
so an issue in one region does not necessarily affect another; the status page
reports health per region. To report a suspected outage that isn't reflected
there, contact [support@pdfblocks.com](mailto:support@pdfblocks.com).
## Availability expectations
PDF Blocks is designed for high availability: the API is stateless (nothing is
stored between requests) and it is served from redundant regional endpoints, so
you can fail over to another region if you need to.
<Note>
These are engineering expectations, not a contractual guarantee. A formal
uptime SLA is not published yet; if your use case requires committed
availability terms, contact
[support@pdfblocks.com](mailto:support@pdfblocks.com).
</Note>
Email: support@pdfblocks.com. Include the
action you called, the request (with your key redacted), and the full
application/problem+json error body if you got one. See
Errors for how to read it.
When you write in, the response’s type URL and the errors field-to-message map
from a failed response are the fastest way for us to reproduce the problem.
Manage your API keys, plan, and usage from the
dashboard. Rotate a leaked key there, and
check usage there rather than inferring it from responses. See
Authentication for key handling.
Current service health, uptime history, and incident updates are published on our
status page: pdfblocks.statuspage.io. You can
subscribe there to be notified when an incident is opened or resolved.
The API runs across multiple regional endpoints,
so an issue in one region does not necessarily affect another; the status page
reports health per region. To report a suspected outage that isn’t reflected
there, contact support@pdfblocks.com.
PDF Blocks is designed for high availability: the API is stateless (nothing is
stored between requests) and it is served from redundant regional endpoints, so
you can fail over to another region if you need to.
These are engineering expectations, not a contractual guarantee. A formal
uptime SLA is not published yet; if your use case requires committed
availability terms, contact
support@pdfblocks.com.
