BitVPS
Launch server

Service status

Live infrastructure health across 16 components in four datacenters. Polled every 20 seconds by external probes outside our ASN; measurements are published raw, including the bad ones.

Updated 23:32 UTC Uptime window 90 days External probes · 20 s cadence
BitVPS network status

Scheduled maintenance Upcoming

Network · CH-ZRH · Upstream carrier swap — BGP reconvergence inside 90 seconds.

2026-07-19 22:00 UTC in 7 d 22 h · ~80 min

Components and 90-day history

Each bar below is one day, coloured by worst observed state. Hover a bar for the date & per-day summary.

Compute · IS-RKV

Iceland
100.00 % 90-day uptime
Operational

Compute · NL-AMS

Netherlands
100.00 % 90-day uptime
Operational

Compute · RO-BUH

Romania
99.98 % 90-day uptime
Operational

Compute · CH-ZRH

Switzerland
99.96 % 90-day uptime
Operational

Network · IS-RKV

Iceland
100.00 % 90-day uptime
Operational

Network · NL-AMS

Netherlands
100.00 % 90-day uptime
Operational

Network · RO-BUH

Romania
99.96 % 90-day uptime
Operational

Network · CH-ZRH

Switzerland
99.97 % 90-day uptime
Operational

Block storage · IS-RKV

Iceland
100.00 % 90-day uptime
Operational

Block storage · NL-AMS

Netherlands
99.98 % 90-day uptime
Operational

Block storage · RO-BUH

Romania
99.98 % 90-day uptime
Operational

Block storage · CH-ZRH

Switzerland
100.00 % 90-day uptime
Operational

Web control panel

100.00 % 90-day uptime
Operational

Billing & payments

100.00 % 90-day uptime
Operational

Anycast DDoS shield

99.97 % 90-day uptime
Operational

Docs & marketing site

100.00 % 90-day uptime
Operational
2026-04-13 — 2026-07-11
Operational Degraded Partial Major

Recent incidents

Last 14 resolved events across all components — auto-refreshed on every page load from our probes.

Jun 25, 2026 08:47–09:49 UTC

Partial outage Compute · CH-ZRH

IOMMU group re-mapping required a short guest stun — ~3% of hosts affected. Fully resolved; follow-up actions tracked internally.

62 min downtime
Jun 24, 2026 07:45–07:55 UTC

Degraded performance Compute · IS-RKV

Hypervisor-level memory pressure investigation — ~9% of hosts affected. Fully resolved; follow-up actions tracked internally.

10 min downtime
Jun 20, 2026 10:15–10:27 UTC

Degraded performance Network · RO-BUH

ICMP rate-limit mis-tune surfaced during a probe sweep from SwissIX Zurich. Fully resolved; follow-up actions tracked internally.

12 min downtime
Jun 10, 2026 15:48–16:27 UTC

Partial outage Network · RO-BUH

IPv6 routing anomaly on carrier GTT (AS3257). Fully resolved; follow-up actions tracked internally.

39 min downtime
Jun 2, 2026 07:46–08:31 UTC

Partial outage Compute · RO-BUH

NUMA imbalance briefly elevated p99 boot times on — ~4% of hosts affected. Fully resolved; follow-up actions tracked internally.

45 min downtime
Jun 1, 2026 19:21–20:06 UTC

Partial outage Anycast DDoS shield

L4 scrubbing capacity briefly saturated during a large amplification attack. Fully resolved; follow-up actions tracked internally.

45 min downtime
May 29, 2026 15:14–15:51 UTC

Partial outage Block storage · NL-AMS

Object-store index promotion briefly held the write lock. Fully resolved; follow-up actions tracked internally.

37 min downtime
May 28, 2026 08:45–08:51 UTC

Degraded performance Compute · NL-AMS

IOMMU group re-mapping required a short guest stun — ~5% of hosts affected. Fully resolved; follow-up actions tracked internally.

6 min downtime
May 28, 2026 13:09–13:28 UTC

Degraded performance Anycast DDoS shield

False-positive mitigation affecting legitimate traffic. Fully resolved; follow-up actions tracked internally.

19 min downtime
May 27, 2026 07:08–07:55 UTC

Partial outage Block storage · RO-BUH

Zoned-namespace firmware upgrade on a subset of drives. Fully resolved; follow-up actions tracked internally.

47 min downtime
May 23, 2026 12:37–12:45 UTC

Degraded performance Block storage · IS-RKV

Rebalance of a hot cell into a cooler shelf. Fully resolved; follow-up actions tracked internally.

8 min downtime
May 5, 2026 10:07–10:29 UTC

Degraded performance Compute · CH-ZRH

IOMMU group re-mapping required a short guest stun — ~5% of hosts affected. Fully resolved; follow-up actions tracked internally.

22 min downtime
Apr 27, 2026 19:17–19:23 UTC

Degraded performance Compute · NL-AMS

Host-agent crash loop after a dependency rollout — ~11% of hosts affected. Fully resolved; follow-up actions tracked internally.

6 min downtime
Apr 19, 2026 12:11–13:05 UTC

Partial outage Network · CH-ZRH

DDoS event absorbed — peak 22 Gbps, scrubbed to edge. Fully resolved; follow-up actions tracked internally.

54 min downtime

Monthly uptime rollup

Aggregate service uptime across all 17 components, by month. Months below 99.99 % trigger an SLA credit — see SLA.

Jul 2026
99.995 %
uptime
Jun 2026
99.980 %
uptime
May 2026
99.990 %
uptime
Apr 2026
99.982 %
uptime
Mar 2026
99.999 %
uptime
Feb 2026
99.996 %
uptime

Status & SLA FAQ

How we measure uptime, what counts as a Tier-1 incident, where to subscribe and how post-mortems are published.

How is uptime measured?
We measure uptime per service component (compute, network, storage, control plane) at one-minute granularity from independent probes in five regions. Daily and monthly figures are weighted by incident severity: a major outage counts at 100%, a partial outage at 70%, and degraded performance at 30% of its measured duration.
What counts as a Tier-1 incident?
A Tier-1 incident is a region-wide loss of customer-facing service: control-plane unreachable, all compute in a datacenter offline, or a network partition that prevents customers from reaching healthy nodes. Tier-1 events trigger an immediate banner here, an out-of-band post-mortem within 72 hours and a credit on the next invoice if SLA thresholds are breached.
Where can I subscribe to status updates?
Subscribe via the RSS feed at /status/rss for incident-only notifications, or watch the JSON endpoint at /status/feed.json for machine-readable polling. We do not offer email subscriptions — they require user accounts and we run an account-free status surface deliberately.
Do you publish post-mortems?
Yes. Every Tier-1 and Tier-2 incident receives a written post-mortem within 72 hours: timeline, root cause, customer impact, mitigation and remediation work. Post-mortems are linked from the incident entry below and clearsigned with the same PGP key used on the warrant canary, so authenticity can be verified offline.
What's the difference between Tier-1 and Tier-2 incidents?
Tier-1 is region-wide customer impact (full outage, control-plane loss). Tier-2 is partial impact: a single rack, a single transit provider degraded, or a control-plane subsystem (billing, console) impaired while compute keeps running. Both get post-mortems; only Tier-1 is eligible for SLA credits under our published 99.95% target.