Synthetic checks
HTTP, DNS, TCP and browser journeys from six regions. Every check carries a trace you can open.
path-levelEverything OK?
Prove it.
Okpwe watches your services, tracks your SLOs and publishes a status page your customers can trust.
Checks from six regions. No agent to install.
Example status page
All systems operational
API99.98%
Web app100%
Checkout99.94%
Background jobs99.99%
Example uptime, 90 days. One incident shown in grey.
Checks, SLOs and a public page, without three tools.
Okpwe replaces the patchwork of a monitor, a spreadsheet and a static page. One service model feeds all three.
SLOs and error budgets
Define the target once. Okpwe tracks the burn rate and routes alerts to the people who own the service.
burn alertingStatus page
Publish incidents, maintenance and history on your own domain. Subscribers get the update, not a tweet.
custom domainAlert on what users feel, not on every spike.
A single slow pod is noise. A burning error budget is signal. Okpwe pages you when the budget is on pace to run out, and stays quiet when it is not.
Target99.9 percent over 30 days
Fast burn14.4x over one hour
Slow burn6x over six hours
Error budget remaining30 days
Example data. Your budget is calculated from your own checks.
Quiet when it should be.
An on-call rotation that only fires on a real SLO risk is a rotation people can keep. Okpwe groups related failures into one incident and suppresses the duplicates.
09:42Checkout check fails in two regions
09:44Incident opened, on-call paged once
09:47Status page updated automatically
10:12Recovered, budget burn recorded
One price for the whole rotation.
Team
Per service
For teams with a customer-facing SLO.
- Unlimited checks
- Burn-rate alerting
- Custom domain and subscribers
- Incident timeline
Enterprise
Custom
For regulated and private installs.
- Self-hosted option
- SSO and audit log
- Support during incidents
Know it is OK before your users do.
Add one check and one SLO. The first status page is live in minutes.