Current Status by Service
Uptime calculated over the last 90 days · single-node, single-regionus-bedroom-1 — 6 services
Incident History
All timestamps UTC · retention: as long as the operator remembers
Showing 4 of 1,208 incidents. Older incidents were lost when Terminal.app was force-quit.
Infrastructure Audit
5 questions · ~20 seconds · no data leaves this pageRate your datacenter.
Answer five questions about where your coding agents actually run. You'll get a certified SLA grade, an annualized downtime figure, and a compliance certificate you can show to nobody in particular.
—
Press 1–4 to answer
Migration path
Your agents deserve a real runtime.
us-bedroom-1 was never a datacenter. It's a laptop with a lid, one charger, and a human scheduler who goes to lunch. Fabriqa runs your coding agents in isolated cloud sandboxes that don't care about any of that.
Capability
us-bedroom-1 (your laptop)
Fabriqa cloud agents
Uptime
✕Ends when the lid doesMedian session: 41 minutes
✓Runs until the job is doneYour laptop is just a client
Parallel agents
✕3, then the fans winThermal throttle at ~92°C
✓As many as you queueEach in its own sandbox
Isolation
✕Your SSH keys and ~/Blast radius: your whole life
✓Disposable environmentsBlast radius: one container
Recovery
✕You, eventuallyMean time to notice: 6h 20m
✓Automatic retries + logsMean time to notice: 0m
Café WiFi
✕Is the networkCaptive portal = total outage
✓Is just your view of itReconnect, work is still there
Migrate out of us-bedroom-1
Fabriqa cloud agents aren't released yet. Join the early-access list and we'll email you once — when they're ready.
Fabriqa target SLA
99.9%
Roughly 8h 45m of downtime per year, versus the 207 days your nightstand is currently posting.