BitVPS
启动服务器

服务 状态

四个数据中心共 16 个组件的实时基础设施健康状况。由我们 ASN 之外的外部探针每 20 秒轮询一次；原始数据公开发布，包括不良数据。

更新时间 22:16 UTC 可用率窗口 90 天 外部探针 · 20 秒间隔
BitVPS network status

计划维护 即将进行

Anycast DDoS shield · NVMe firmware upgrade on one storage shelf, rolling.

2026-06-21 00:00 UTC 于 24 d 1 h · ~43 分钟

组件与 90 天历史

下方每个柱形代表一天，颜色表示当天最差状态。悬停柱形可查看日期及当天摘要。

Compute · IS-RKV

Iceland
100.00 % 90 天可用率
正常运行

Compute · NL-AMS

Netherlands
100.00 % 90 天可用率
正常运行

Compute · RO-BUH

Romania
100.00 % 90 天可用率
正常运行

Compute · CH-ZRH

Switzerland
100.00 % 90 天可用率
正常运行

Network · IS-RKV

Iceland
100.00 % 90 天可用率
正常运行

Network · NL-AMS

Netherlands
100.00 % 90 天可用率
正常运行

Network · RO-BUH

Romania
99.98 % 90 天可用率
正常运行

Network · CH-ZRH

Switzerland
99.97 % 90 天可用率
正常运行

Block storage · IS-RKV

Iceland
99.96 % 90 天可用率
正常运行

Block storage · NL-AMS

Netherlands
100.00 % 90 天可用率
正常运行

Block storage · RO-BUH

Romania
99.97 % 90 天可用率
正常运行

Block storage · CH-ZRH

Switzerland
100.00 % 90 天可用率
正常运行

Web control panel

100.00 % 90 天可用率
正常运行

Billing & payments

100.00 % 90 天可用率
正常运行

Anycast DDoS shield

100.00 % 90 天可用率
正常运行

Docs & marketing site

100.00 % 90 天可用率
正常运行
2026-02-27 — 2026-05-27
正常运行 性能下降 部分中断 重大中断

近期 事故

所有组件最近 14 次已解决事故——每次页面加载时由探针自动刷新。

May 27, 2026 07:08–07:55 UTC

部分中断 Block storage · RO-BUH

Zoned-namespace firmware upgrade on a subset of drives. 已完全解决，后续跟进事项内部追踪中。

47 分钟 停机时间
May 23, 2026 12:37–12:45 UTC

性能下降 Block storage · IS-RKV

Rebalance of a hot cell into a cooler shelf. 已完全解决，后续跟进事项内部追踪中。

8 分钟 停机时间
May 5, 2026 10:07–10:29 UTC

性能下降 Compute · CH-ZRH

IOMMU group re-mapping required a short guest stun — ~5% of hosts affected. 已完全解决，后续跟进事项内部追踪中。

22 分钟 停机时间
Apr 27, 2026 19:17–19:23 UTC

性能下降 Compute · NL-AMS

Host-agent crash loop after a dependency rollout — ~11% of hosts affected. 已完全解决，后续跟进事项内部追踪中。

6 分钟 停机时间
Apr 19, 2026 12:11–13:05 UTC

部分中断 Network · CH-ZRH

DDoS event absorbed — peak 22 Gbps, scrubbed to edge. 已完全解决，后续跟进事项内部追踪中。

54 分钟 停机时间
Apr 14, 2026 11:30–12:11 UTC

部分中断 Network · RO-BUH

Asymmetric routing detected at BIX Bucharest. 已完全解决，后续跟进事项内部追踪中。

41 分钟 停机时间
Apr 13, 2026 10:27–10:47 UTC

性能下降 Block storage · CH-ZRH

Erasure-coding reconstruction throttled after a double disk failure. 已完全解决，后续跟进事项内部追踪中。

20 分钟 停机时间
Apr 9, 2026 07:40–08:01 UTC

性能下降 Block storage · RO-BUH

NVMe device failure, RAID rebuild in progress. 已完全解决，后续跟进事项内部追踪中。

21 分钟 停机时间
Apr 7, 2026 18:11–18:56 UTC

重大中断 Block storage · IS-RKV

Rebalance of a hot cell into a cooler shelf. 已完全解决，后续跟进事项内部追踪中。

45 分钟 停机时间
Apr 3, 2026 08:59–09:07 UTC

性能下降 Compute · IS-RKV

Hypervisor-level memory pressure investigation — ~11% of hosts affected. 已完全解决，后续跟进事项内部追踪中。

8 分钟 停机时间
Mar 28, 2026 19:45–19:51 UTC

性能下降 Block storage · IS-RKV

Object-store index promotion briefly held the write lock. 已完全解决，后续跟进事项内部追踪中。

6 分钟 停机时间
Mar 16, 2026 16:33–16:41 UTC

性能下降 Block storage · IS-RKV

Slow-query regression on the metadata service. 已完全解决，后续跟进事项内部追踪中。

8 分钟 停机时间
Mar 6, 2026 19:53–19:59 UTC

性能下降 Compute · IS-RKV

IOMMU group re-mapping required a short guest stun — ~5% of hosts affected. 已完全解决，后续跟进事项内部追踪中。

6 分钟 停机时间

月度可用率 汇总

全部 17 个组件按月汇总的服务可用率。低于 99.99 % 的月份将触发 SLA 信用补偿——详见 SLA。

May 2026
99.990 %
可用率
Apr 2026
99.982 %
可用率
Mar 2026
99.999 %
可用率
Feb 2026
99.996 %
可用率
Jan 2026
99.997 %
可用率
Dec 2025
99.992 %
可用率

Status & SLA 常见问题

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.