docs Support
hosted
Support
This page covers the hosted service at uptimepage.dev.
Where to write
| Reason | Where |
|---|---|
| Anything about your account or the hosted service | hello@uptimepage.dev |
| Security vulnerabilities | security@uptimepage.dev, subject [SECURITY] |
| Bugs and feature requests in the product | GitHub issues |
| Abuse from a monitor or status page we host | hello@uptimepage.dev, see the Abuse Policy |
Please do not report vulnerabilities through GitHub issues. The Security Policy has the disclosure timeline and what is in scope.
What to include
A monitor or organization name gets us to the right data quickly. If a check is behaving in a way you did not expect, the monitor name, roughly when it happened, and what you expected instead is usually enough. If the API or an integration returned an error, send the whole error response and the request that produced it.
Service level
We run the hosted service on a best-effort basis. There is no service-level agreement, no uptime guarantee, and no financial credits for downtime. If you need a contractual guarantee, run your own instance, where the availability is yours to engineer, or write to us about a custom arrangement.
Planned maintenance is posted on our own status page, which runs on this product.
Status of the service itself
Our status page is a normal uptimepage status page, monitored by a separate instance, so an outage here does not take the status page with it. Subscribe there if you want to be told before you notice.
Self-hosting
If you run your own instance, support is the GitHub issue tracker and the Troubleshooting page. We read every issue, but we do not run your instance and cannot see your data. Include your version, your deployment shape, and the relevant log lines.