Status

RackWatch.io operational status.

Current state of the public RackWatch services. This page is checked at least once per business day; an automated, continuously-monitored status page is on the 90-day roadmap.

All systems operational
Last manually verified 2026-05-03 · Next refresh: within 1 business day
Marketing site (rackwatch.io)
Public site, pricing, demo, legal pages. Hosted on Railway with Let's Encrypt TLS.
200 OK
Operational
Demo dashboard (rackwatch.io/dashboard.html)
Public read-only dashboard with our home-lab fleet (8 hosts, 24/7).
Telemetry < 5 min
Operational
Stripe webhook (license issuance)
Subscription checkouts trigger ed25519 license-key delivery via Resend.
Last delivery OK
Operational
Resend (transactional email)
License-key delivery and customer email. DKIM/SPF/DMARC verified.
Healthy
Operational
Docker Hub image (rackwatch/platform)
Multi-arch platform image (linux/amd64 + linux/arm64). Trial path pulls from here.
Pulls verified
Operational
GitHub agent repo (rackwatch/rackwatch-agent)
Open-source agent source under Apache 2.0. Public install.sh references binaries served from rackwatch.io/downloads.
Reachable
Operational

How this page is currently maintained: manually, once a business day. We open the URLs above, run a test webhook through Stripe, send a license email through Resend, and pull the Docker image from a clean machine. If anything fails, this page is updated within an hour and active subscribers get an email. Automated uptime probes (planned: Upptime on a separate hosting provider so a RackWatch-side outage doesn't take this page down with it) are on the 90-day roadmap.

Recent incidents

No incidents reported.
RackWatch went live in early access on 2026-04-20. We'll post any outage, partial degradation, or maintenance window here, with a brief post-mortem. Subscribers get an email at the same time.

Reporting an outage

If you're seeing problems with rackwatch.io that aren't reflected here, the fastest path:

Note that this status page covers the public RackWatch.io services. It does not cover your self-hosted RackWatch instance — that runs on your hardware, on your network. If your platform is down, the platform on your hardware is what to look at first; the operations page has restore and disaster-recovery procedures.