Public Status Page & Health Monitoring
slabiq.app/status shows the live health of every SlabIQ service from automated checks, current incidents and how they were resolved, scheduled maintenance, and 90-day availability.
- Status
- In Progress
- First discussed
- Development started
- Last updated
Overview
SlabIQ's status page is now driven by automated checks instead of manual updates. It covers the website, sign-in, storage, inventory, orders, eBay, scanning, AI recognition, the catalog, pricing, notifications, Discord and breaks. If status can't be measured, the page says 'unknown' instead of showing green. Incidents carry updates through to resolution, and availability is calculated openly, with gaps in monitoring shown.
Completed work
- Automated checks for 13 services, grouped by area (2026-10-27)
- Unknown is shown as unknown, never as operational
- Incidents with updates, resolution and reopening; scheduled maintenance
- Availability for 24 hours, 7, 30 and 90 days, with the calculation rule published
Milestones
- Completed
Public status page with incidents and uptime history
- Completed
Discord status sync
- Completed
Continuous health measurement built
- Completed
New status web code live
- Not Started
Status history stored and monitor running in production
- Completed
Public status page
- Completed
Automated health checks drive the status page
- Completed
Incident, maintenance and override management
- Completed
90-day availability history
What “done” means
The outcomes this item has to deliver. Each is marked as it is confirmed.
Anyone can open the status page
Met
Public status reflects measured service health rather than a default
Not met yet
Status changes post to Discord once per change
Not yet verified
The status page reflects automated checks, not manual edits
Met
An outage is shown publicly while it is happening
Met
Incidents show updates and resolutions
Not yet verified
Status changes reach Discord
Not yet verified
Development updates
No development updates have been posted yet.