Order a server

Service status, incidents and maintenance

Where to check whether something is wrong on our side, how we post incidents and maintenance, and how to get them by email, Atom feed or JSON.

updated · 3 min read

If something seems wrong with your server or the panel, check rack4.io/status first. It shows what we know, as we know it.

What the status page shows

  • Components: the control panel and API, billing and payments, each location (New York for now) and the network, each with its state now: operational, degraded performance, partial outage, major outage or under maintenance.
  • Uptime over up to 90 days: one bar per day. Hover a day (or read it with a screen reader) for its uptime and any incidents. On a phone it shows the last 30 days.
  • Open incidents and maintenance at the top, each with its updates and times in UTC.
  • Incident history: every incident and maintenance window we have posted, at /status/history.

How it is measured

Every minute the control plane records each component's state. A location goes down when the hosts its servers run on stop checking in; billing shows degraded when calls to our payment server (BTCPay) fail. When we post an incident, its impact shows on the components it affects until it is resolved.

Uptime counts a minute of major outage as down and a minute of partial outage as half down. Degraded performance and announced maintenance count as up. We always announce maintenance on the status page before it starts.

These checks run inside our own hosting, so on their own they can't see a failure only outsiders hit. Since 29 October 2026 the control panel and billing checks also ask two public DNS resolvers (Cloudflare and Google) every minute whether rack4.io and my.rack4.io resolve, and show a major outage if they don't. Before that, a nameserver mistake made both names unreachable from 23 to 24 October 2026 while the panel and billing still showed 100%; the status page and status.json mark that period as a known gap and link the incident, which is also in the incident history. Uptime is counted from 22 October 2026, when monitoring began.

Get updates by email

Enter your address under "Get status updates by email" on the status page, then use the link in the confirmation email. We send nothing else until you confirm. After that you get an email when we post an incident, update or resolve it, and when maintenance is scheduled, starts and ends.

If you have an account, you can skip the confirmation: in the panel, open Account, then status emails, and turn them on with one click. It uses your account's confirmed address.

Every status email has a one-click unsubscribe link, and we delete your address when you use it.

In the panel

While an incident or maintenance affects you, a banner at the top of every panel page says so. Problems with the control panel, billing or the network show to everyone; a problem in a location shows only if you have a server there. Dismiss a banner with its × and it stays hidden for that incident.

Feeds and monitoring

  • Atom feed: https://rack4.io/status/feed.xml
  • JSON: https://rack4.io/status.json, the same as GET https://my.rack4.io/api/v1/status, which needs no API token (60 requests a minute per address).
bash
curl -s https://rack4.io/status.json | jq -r '.status.description'

If the status page says everything is fine and your server still isn't, open a ticket and tell us what you see.

Ready when you are

Order a server