Status
Tenvey is not running yet.
There is no service in operation, so there is no uptime to report and no incident history to show. This page exists now so there is one address to check later, and it describes what it will report then.
The components this page will cover
- Not yet running
API
The endpoints the dashboard and the public scan will read from.
- Not yet running
Monitoring workers
The checks themselves, on the schedule each feature page describes.
- Not yet running
Dashboard
The signed-in interface: reports, settings and billing.
- Not yet running
Notifications
Email and webhook delivery for alerts and scheduled reports.
What this page will report.
Written down before the service starts, so the standard is set while there is nothing to defend.
- A state for each component
- Each component above will carry its own state rather than one badge standing in for the whole system, so a delivery problem does not read as an outage of the checks. Every state pairs a colour with a differently shaped icon, the way status is written everywhere else on this site.
- Incidents while they are open
- An incident gets written up while it is still running — what is affected, what is known so far and what is being done about it — rather than once it is comfortable to describe. It stays on the page afterwards with the times it actually had.
- Uptime measured from outside
- Tenvey will watch its own API, workers, dashboard and delivery with the same checks it runs on customer sites, reaching them over the public internet instead of from inside its own network. The uptime figure on this page will come from those checks, and it appears once there is a measured window behind it.
Write to contact and say you want to hear when the service starts. There is no signup box on this page, because a form that posts nowhere is worse than no form. The first release will be listed in the changelog on the day it ships, and this page changes on the same day.