VPSbitStatus
What runs, what failed, on which day. Rows appear when an event earns one.
12 locations · 19 coins · SLA 99.95% · no KYC · public canary
Now
Site, deploy flow, coin invoice page and panel are all serving. Treat this page as a dated log; it is not a hypervisor heartbeat for the fleet.
VPS from $4.80* — Core on the annual term (list $6/mo), one invoice for 12 months, no auto-charges. Dedicated with IPMI from $39.20/mo. Crypto invoice, no KYC.
Launch nowBy location
- Reykjavik (IS-RKV) - operational
- Amsterdam (NL-AMS) - operational
- Zurich (CH-ZRH) - operational
- Hong Kong (HK-HKG) - operational
- Tokyo (JP-TYO) - operational
- Frankfurt (DE-FRA) - operational
- Singapore (SG-SIN) - operational
- Stockholm (SE-STO) - operational
- Helsinki (FI-HEL) - operational
- Oslo (NO-OSL) - operational
- Luxembourg (LU-LUX) - operational
- Taipei (TW-TPE) - operational
Indicative RTT: looking glass. Canary: warrant canary.
Log
- Catalog and checkout went public. No sitewide incident on record.
Shorter history is not padded history. A young site has a young log.
How to read this
A fault on one customer box stays in that box's ticket. Rows here cover checkout, DNS and facilities we run as product lines. Credits follow the SLA, never this page. Support runs exclusively on panel tickets.
What earns a row here
Three event classes get dated entries. Product incidents: checkout, the invoice page, the panel or provisioning stuck past its published window - about 60 seconds for a VPS image, 2-4 hours for a dedicated rack. Facility events: power, upstream transit or filtering trouble at a named location. Scheduled work: maintenance windows that touch more than one tenant, posted before they start. Everything else - single-tenant reboots, rDNS edits, ticket backlogs - belongs to the panel, not to this log.
Keep yourself honest
Two habits make this page useful instead of decorative. Subscribe to the RSS feed or check the date after each renewal - a stalled log is a signal in itself. And when a row does appear, compare it with what your monitoring saw: the gap between a platform incident and your box is exactly the conversation worth having in a ticket.
Is this a live status API?
No. It is a page we date-stamp whenever something deserves a row.
Where do I report a box down?
Panel tickets are the only channel; support is handled exclusively there.
How fast is provisioning supposed to be?
VPS images target about 60 seconds after the payment watcher credits the invoice; dedicated racks take 2-4 hours. Slower than that earns a row in the log.
Ready to launch?
Build the box — VPS or bare metal — create the password, pay the invoice that follows.