All systems operational.

The web machine ran on a shared vCPU. A single in-process PDF render exhausted its CPU credits; the machine stopped serving requests and could not restart quickly afterwards. cybertwin.io was unavailable for under 30 minutes. This entry was posted after the fact on 2026-09-14 — no status post went out during the event, which missed the 30-minute posting target below.

What changed

• The web machine now runs on a dedicated CPU (performance-1x).
• Public sample PDFs are served prebuilt instead of rendered per request.
• A render guard limits in-process PDF rendering on the web process.

When something does happen, we aim to post here within 30 minutes of detection, follow up as the event develops, and publish a public post-mortem within 5 business days. Honest scope: we are a small team without a 24/7 pager rotation yet — these are the targets we hold ourselves to, not a contractual guarantee (see /sla for what is contractual).