System status
All systems operational.
{{ updated }} · Sydney production, Melbourne backups · Subscribe to updates
{{ k.v }}
{{ k.l }}
{{ t.t }}
01 · Components
Ninety days, every service.
OperationalDegradedOutageMaintenance
{{ c.n }}
{{ c.d }}
{{ c.up }}
● {{ c.s }}
90 days agoToday
02 · Model health
Uptime is not enough. We publish whether the models are still fair.
{{ m.k }}● {{ m.s }}
{{ m.n }}
{{ r.k }}{{ r.v }}
Model card →
Thresholds are published on each model card. A breach pauses the model for new mandates and is posted here as an incident within 24 hours.
03 · Incident history
Every incident, with the post-mortem.
Posted within 15 minutes of detection, updated every 30 minutes until resolved, post-mortem within five business days. Model-fairness breaches are incidents too.
{{ k.v }}
{{ k.l }}
{{ i.date }}
{{ i.t }}
{{ i.meta }}
{{ i.sev }}
{{ l.t }}{{ l.k }} {{ l.d }}
Post-mortem. {{ i.pm }}
04 · Scheduled maintenance
{{ m.when }}
{{ m.t }}
{{ m.d }}
Impact: {{ m.impact }}
Maintenance windows are Sundays 02:00–05:00 AEST, announced ten business days ahead. Candidate conversations and consent writes are never taken offline.
05 · Subscribe
Hear it from us first.
Email, SMS or webhook for incidents and maintenance. Procurement and security teams can also pull the JSON feed into their own dashboards.
{{ c.t }}
Subscribed.
{{ subMsg }}
Status APIGET status.suitorly.com/v1/summary
{{ apiJson }}
No auth. Cached 60 seconds. Webhook events: incident.opened, incident.updated, incident.resolved, maintenance.scheduled, model.threshold_breached.