Status

What runs, what failed, on which day. Rows appear when an event earns one.

Published 2026-08-31 · Updated 2026-09-29 · NulNet Editorial

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.

By location

• Reykjavik (IS-RKV) - operational
• Amsterdam (NL-AMS) - operational
• Bucharest (RO-BUH) - operational
• Zurich (CH-ZRH) - operational
• Sao Paulo (BR-SAO) - operational
• Ashburn (US-ASH) - operational
• Hong Kong (HK-HKG) - operational
• Shanghai (CN-SHA) - operational
• Tokyo (JP-TYO) - operational
• Riga (LV-RIX) - operational
• Frankfurt (DE-FRA) - operational
• Dallas (US-DFW) - operational
• Mexico City (MX-MEX) - operational
• Singapore (SG-SIN) - operational
• Dubai (AE-DXB) - operational
• Cape Town (ZA-CPT) - operational
• Johannesburg (ZA-JNB) - operational
• Almaty (KZ-ALA) - operational
• Bangkok (TH-BKK) - operational
• Moscow (RU-MOW) - operational
• Saint Petersburg (RU-LED) - operational

Indicative RTT: looking glass. Canary: warrant canary.

Log

2026-08-31 - Catalog and checkout went public at nulnet.com. 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.