Live infrastructure status

Network status

Real-time state of all fifteen VPSRento locations. Uptime bars cover the last 90 days per datacenter. Every incident gets a public retrospective — even the ones nobody noticed.

All systems operational Last checked: 2026-08-29 09:41 UTC

Locations — past 90 days

One bar per day. Indigo is a clean day, gold is degraded performance, red is an outage. Hover any bar for the date and details.

Iceland Reykjavik · IS1
100.00% / 90d
Switzerland Zurich · ZRH1
100.00% / 90d
Panama Panama City · PTY1
99.99% / 90d
Moldova Chisinau · KIV1
100.00% / 90d
Romania Bucharest · OTP1
99.98% / 90d
Netherlands Amsterdam · AMS1
99.97% / 90d
Russia Moscow · DME1
99.99% / 90d
Tonga Nuku'alofa · TBU1
100.00% / 90d
Cayman Islands George Town · GCM1
99.99% / 90d
Seychelles Victoria · SEZ1
99.98% / 90d
Belize Belize City · BZE1
99.99% / 90d
Bahamas Nassau · NAS1
100.00% / 90d
Bulgaria Sofia · SOF1
99.98% / 90d
Ukraine Kyiv · KBP1
99.97% / 90d
Hong Kong Hong Kong · HKG1
99.99% / 90d

Incident history

Every service-affecting event, documented after the fact. One incident in the past 90 days.

2026-06-14 · Amsterdam (AMS1) · Resolved

AMS1 core switch failure — degraded networking, 4h12m

Summary. At 03:17 UTC, the primary top-of-rack switch in our AMS1 rack stopped forwarding traffic on 22 of 48 ports. Roughly 40% of Amsterdam VPS instances lost external connectivity; the remainder saw elevated latency and packet loss on the redundant path. All services were fully restored by 07:29 UTC. No data was lost and no storage layer was affected.

Root cause. A failing ASIC on the primary switch's line card, triggered by a firmware bug in the buffer-management unit (vendor advisory PSIRT-2026-041, published after our incident). Automatic failover to the secondary switch engaged, but a misconfigured LACP hash on one aggregation group left 22 ports pinned to the dead unit.

Remediation. The faulty line card was replaced from on-site spares at 07:12 UTC and the LACP groups rebalanced. We have since applied the vendor firmware patch on all AMS1 and ZRH1 switches, added a quarterly automated failover drill that verifies every port group rather than just the master link, and deployed per-port forwarding telemetry so a partially dead switch pages us within 60 seconds instead of relying on aggregate link state.

Credits. The event breached our 99.9% monthly SLA for affected Amsterdam customers. SLA credits were applied automatically to all AMS1 services active during the window — no ticket required, per our SLA.

  • 03:17 UTC — Monitoring flags packet loss across 3 AMS1 hypervisors. On-call paged.
  • 03:24 UTC — Confirmed: primary ToR switch not forwarding on 22/48 ports. Failover partially engaged.
  • 03:41 UTC — Status page updated to "degraded performance" for Netherlands. Traffic shifted to secondary path.
  • 05:02 UTC — Datacenter remote hands dispatched to rack for line-card replacement.
  • 07:12 UTC — Line card replaced, LACP groups rebalanced, full forwarding restored.
  • 07:29 UTC — All checks green. Incident marked resolved. Total impact: 4h12m.
  • 2026-06-16 — Firmware patch validated in staging, rolled out to AMS1 and ZRH1.
  • 2026-06-21 — This retrospective published. SLA credits applied.

Subscribe without giving us anything. This page ships an RSS/Atom feed — point any feed reader at https://vpsrento.com/status.atom and you will get every incident and resolution as it happens.

We do not offer email notifications, for a simple reason: we do not have your email. We never asked for it.