# Rack4 system status

> All systems operational. Updated 2 Nov 2026, 04:11 UTC.

Source: https://rack4.io/status · JSON: https://rack4.io/status.json · Atom feed: https://rack4.io/status/feed.xml · Incident history: https://rack4.io/status/history

## Components

| Component | Status | Uptime (90 days) | Monitored since |
| --- | --- | --- | --- |
| Control panel & API | Operational | 100.00% | 22 Oct 2026 |
| Billing and payments | Operational | 100.00% | 22 Oct 2026 |
| New York | Operational | 88.40% | 22 Oct 2026 |
| Network | Operational | 100.00% | 22 Oct 2026 |

Uptime is worked out from a check every minute, over the last 90 days or since monitoring began if that's later. A minute of major outage counts as down, a minute of partial outage as half down; degraded and maintenance minutes count as up. Days before monitoring began have no data and don't count.

The checks run inside Rack4's own hosting. Since 29 Oct 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; before that they couldn't see a public DNS failure.

- Control panel & API, 23 Oct 2026, 00:02 UTC to 24 Oct 2026, 05:45 UTC: rack4.io and my.rack4.io didn't resolve publicly for 29 h 43 min (wrong nameservers at the registrar). The checks then ran only inside our hosting, so they show 100% for those days; nobody outside could reach the panel or pay. Details: https://rack4.io/status/incidents/inc_fd5ouudjnyovjqls
- Billing and payments, 23 Oct 2026, 00:02 UTC to 24 Oct 2026, 05:45 UTC: rack4.io and my.rack4.io didn't resolve publicly for 29 h 43 min (wrong nameservers at the registrar). The checks then ran only inside our hosting, so they show 100% for those days; nobody outside could reach the panel or pay. Details: https://rack4.io/status/incidents/inc_fd5ouudjnyovjqls

## Open incidents

None.

## Maintenance

None scheduled.

## Last 14 days

### vpsnine.com unreachable: DNS misconfiguration

Incident · Resolved · impact: major · Control panel & API, Billing and payments, New York

- 24 Oct 2026, 05:45 UTC, Resolved: From 23 Oct 00:02 to 24 Oct 05:45 UTC, about 30 hours, vpsnine.com and my.vpsnine.com didn't resolve. On 17 Oct the domain's nameservers at the registrar were set to the wrong pair of Cloudflare nameservers; Cloudflare kept answering until it marked the zone as moved, and then every name under vpsnine.com stopped working. The website, the control panel and API, billing, email and the New York host's link to the control plane were all down, which is why New York shows 2.15% and 75.97% uptime for those two days. The control panel and billing show 100% for those days because their checks run inside our hosting, where the domain still worked: that figure is wrong for anyone outside. This was before launch: no customer servers existed and no orders could be placed. We corrected the nameservers at the registrar and service came back as DNS caches refreshed.

Details: https://rack4.io/status/incidents/inc_fd5ouudjnyovjqls