All systems operational

System status.

Live health check, run on every visit. Three components: the web app you're reading, the database underneath it, and the content layer between them. Numbers reflect this request, not a rolling average.

Last checked:

Live checks

Component health

  • Web Application

    Server-rendered pages on the global edge platform.

    563 ms
    All systems normal
  • Database

    Primary data store backing the CMS, blog, and admin.

    454 ms
    All systems normal
  • Content Layer

    Pages + blog content served from the CMS repository.

    563 ms
    All systems normal
Incident history

Recent incidents

No user-visible incidents to report. The site has been on its current stack since 2024 and we will record any incident here with the date, the impact, and what we did about it.

What counts as "user-visible": anything a visitor or customer could plausibly notice. Brief degradations under 60 seconds that no real user hit get filed internally, not here.

About this page

How status works here

This page runs a live health probe on each request. There is no rolling 90-day uptime average — that would require running synthetic monitors against ourselves, and the operating team is too small for the result to be more honest than the numbers above.

If something looks wrong, refresh first (cached responses may lag the real state by up to 30 seconds), then tell us what you're seeing. Each of the five product brands operates on its own domain — if a specific brand site is down, the relevant status surface lives on that domain, not here.