Status

All systems operational

Checked every 60 seconds from outside our own network
Dallas Compute and network Operational
Amsterdam Compute and network Operational
Portal Panel, API and billing Operational
Proxy gateway HTTP and SOCKS5 Operational
Looking glass Public network tools Operational

Advisories are published to @privatebyte and on the security page

Incident history

Past incidents.

Incidents that affected customer services, with the cause and what changed afterwards.

2026-07-31

Inbound traffic lost to a group of addresses in AmsterdamA virtual switch restart cleared the flow table fourteen hours earlier without causing an immediate fault. A later routine operation reapplied a partial rule set, interrupting inbound delivery. Flow state is now restored automatically on service start and reconciled every five minutes, with an alert on drift.

Resolved
2026-07-28

One IPv4 prefix unreachable for approximately 30 hoursStale routing registry objects left by a previous address lessor took effect when a transit provider rebuilt its prefix filters. Outbound traffic was unaffected; inbound was not delivered. The objects were removed and filters rebuilt. Registry and RPKI records are now checked daily.

Resolved
2026-04-22

Portal account-identifier confusionA mapping error meant a small number of accounts could briefly see another customer’s services within a session. Patched the same day and reported to the ICO within the statutory window. A regression test is pinned in CI.

Resolved