Status pages for health checks: a public status page at IPv64.net
A status page shows visitors without a login whether your services are running: the state of every selected health check, uptime of the last 90 days as bars, notices and past incidents. Every status page has its own address under ipv64.net/healthchecks2/status/.
Overview
- You manage the pages under Statusseiten in the bar of the health checks (ipv64.net/healthchecks2/statuspages).
- Up to 10 status pages per account, each with up to 20 groups and 100 checks in total.
- Your health checks can go on a status page – online, local and hybrid.
- Visitors only see the name, state and uptime of the checks. Targets, error messages and data of your account are not on the page.
- The status pages in the portal are independent of the status pages in Node64; the two are not synced.
Create a status page
- New status page
Under Statusseiten, click Neue Statusseite. - Title and address
A title (up to 120 characters) and optionally a description. You can choose the address yourself; leave it empty and IPv64.net picks a random one. - Assign checks
Name the groups (e.g. “Websites”, “Network”) and pick a group for each check in the list, or nicht zeigen (do not show). Wie in den Healthchecks pre-fills the assignment with the groups of your checks. - Save
Open the page with Ansehen (view) or Vorschau (preview).
Groups without checks are not shown. After saving, three more empty groups are ready.
Address
The address is https://ipv64.net/healthchecks2/status/<name>, e.g. https://ipv64.net/healthchecks2/status/my-services.
- 3–64 characters: lowercase letters, digits and single hyphens, not at the start or end.
- Each address exists only once across all accounts. If it is taken or reserved (e.g.
admin,api,status), the form shows an error. - If you change the address, the old one stops working at once. After a status page is deleted, its address becomes free again.
Settings
| Setting | Effect |
|---|---|
| Language | like the browser (German for a German browser, otherwise English), German or English. Visitors switch with the link at the bottom of the page. |
| Colours | like the device (light or dark as the visitor has set it), light or dark |
| View | List (90 days) – one row per check with 90 daily bars (default) – or Cards (6 hours) – one small tile per check with its state, one bar per hour for the last 6 hours, uptime over those 6 hours and the average response time |
| Public | off: the page is only reachable via the preview link with ?key=…; everyone else gets “not found”. Do not share the preview link. |
| Show incidents | list of the incidents of the last 14 days (check, start, duration) below the checks |
| Reload | the page reloads itself every minute (e.g. for a screen in the office) |
What visitors see
- An overall state at the top: All systems operational, Some systems are degraded or Some systems are down.
- For each check the state Operational, Degraded (partially down or flapping), Outage, Paused or No data.
- For each check one bar per day for the last 90 days – green from 99.9 %, light green from 99 %, yellow from 95 %, otherwise red, grey without measurements – and the uptime over 90 days. On a phone the page shows the last 30 days.
- In the Cards view, instead one tile per check with one bar per hour (last 6 hours, the current one included), uptime over those 6 hours and the average response time (Ø, only for checks with a response time).
- Times in your account's time zone (set under notifications, default Europe/Berlin).
The page is cached for up to 60 seconds; changes to the status page apply immediately. Search engines do not index status pages (noindex).
Notices
Below the form of a status page you publish notices – as notice, maintenance or incident, with a title and optional text. They appear at the top of the status page. Erledigt marks a notice as resolved; it then stays visible for 7 more days. Wieder öffnen undoes that. Up to 100 notices per page.
JSON for your own displays
The same data is available as JSON without a login – append .json to the address:
curl "https://ipv64.net/healthchecks2/status/my-services.json"
Fields: title, status (up, degraded, down, unknown), url, updated_at, groups (per group name and checks with name, status, uptime_90d) and notices. Any origin may fetch it (CORS). About 60 requests per minute per address are possible; above that IPv64.net answers 429.
Manage via API
You can also create status pages and notices via API v2 (/hc2/status-pages).
Found a mistake or missing something? Tell us in the v64.tech forum. · Updated: 2026-11-10