Status pages on your domain
Publish selected monitors at /status/your-slug or behind a CNAME: 90 days of per-day uptime, incident history, your name and logo. Latency stays internal.
Platform · Monitors
Telemetry sees inside. Monitors check from outside.
Traces and logs only exist while requests arrive. A monitor keeps probing on a schedule — an HTTP request, a TCP connect, or a full Playwright browser flow — so you find out your site is down before a user tells you.
Service facts
The outside view, on a schedule
What a probe run looks like, by the numbers.
- 30 sfastest interval
- Every monitor has an interval down to 30 seconds, a timeout, and a failure threshold.
- 3probe types
- HTTP with full request control, TCP with optional TLS, and full @playwright/test browser flows.
- 90days of uptime bars
- Per-day availability and incident history on your public status page, on your own domain if you like.
Flap damping
One flaky probe never wakes anyone at 3am.
A monitor only goes down after N consecutive failures, and the first successful probe flips it back with an all-clear. Self-hosted Traceway is MIT licensed with every monitor type, status pages, and alerting included.
- HTTP checks
- Full request controlMethod, headers, auth, body; assert on status, body substring or regex, latency, and TLS days-left.
- TCP checks
- Optional TLSSend payload and expected response — databases, SMTP, anything that is not HTTP.
- Browser checks
- Real @playwright/testHeadless Chromium on a schedule; a login flow or checkout journey becomes the availability check.
- Failure evidence
- Screenshot + logsEvery failed browser run stores both, one click from the run history.
- Missed, never late
- Honest timelineA probe past its window is recorded as missed, so downtime never reads as a fabricated 100%.
On this line
Probes, pages, and post-mortems.
The whole incident lifecycle — detection, public story, write-up — in the same tool that holds the stack trace.
Incidents with a timeline
Incidents open and resolve themselves from state transitions; you rename them for users and post Investigating through Resolved updates while you work.
Post-mortems next to the incident
A WYSIWYG markdown editor with tags, one write-up per incident, searchable across titles, content, and tags, with a full activity log.
Wired into on-call
One Monitor Down rule covers every monitor in the project; pages deduplicate per monitor, and recovery resolves the page itself.
Plan note
Browser checks run where your scripts are trusted.
On Traceway Cloud, HTTP and TCP monitors and status pages are part of every plan. Browser checks are currently a self-hosted feature because they execute your scripts — runners connect outbound-only and never see server secrets.
Next stop
Stop paying for a separate uptime tool.
Monitors, status pages, incident timelines, post-mortems, alerting, and on-call in the tool that already holds your traces, logs, and errors.