All systems operational.
A continuous read on the Interline service. The live API check on this page hits production from your browser every time you load it. Incident history below is the source of record.
The probe hits /api/v1/health, which verifies the database connection. Latency is measured from the browser to the API and back.
- APIREST endpoints serving the workspace and integrations.Operational
- FrontendWorkspace web app and marketing site.Operational
- DatabasePrimary Postgres cluster and read replicas.Operational
- Email deliveryTransactional email and inbound classifier ingestion.Operational
- AI inferenceDrafting, classification, and parsing pipelines.Operational
- Object storageIllustrations, generated PDFs, document templates.Operational
Service status reflects the last automated probe. Manual degradations are flagged on the incident log below.
Last ninety days.
The platform has not experienced a customer-impacting incident in the trailing ninety days. When one occurs, it is recorded here with a write-up of cause, impact, and mitigation.
Past incidents older than ninety days are archived to the changelog under a fix tag.
What we commit to.
| Tier | Uptime target | Response time | Maintenance windows |
|---|---|---|---|
| Pilot | Best effort | One business day | As needed, advance notice |
| Practice | 99.9% | Four hours, business | Weekends, 02:00 – 06:00 UTC |
| Firm | 99.95% | Fifteen minutes, 24/7 | By arrangement |
SLA credits, escalation paths, and notification mechanics live in the order form. We do not announce maintenance windows here; we email the workspace owner a minimum of seventy-two hours ahead.
For incident notifications and post-mortems, email [email protected] to be added to the operations distribution list. RSS and webhook subscriptions are on the roadmap.