Resources · System Status

Status. Live, subscribable, signed.

Safeguard publishes per-tier system status with live availability, incident history, and subscribable notifications.

All systems operational

Updated continuously · last refresh moments ago

Live
Shared Cloud
Operational
Dedicated Cluster
Operational
VPC-isolated
Operational
Sovereign
Operational
Marketplace
Operational
Live data on status.safeguard.sh.
Subscribe

Pick a channel that fits your stack.

Email digest

Subscribe with your email to get incident notifications and weekly status digests.

Subscribe

RSS feed

Drop the feed into your reader of choice. Same incidents, no email.

feed.xml

Webhook

POST callbacks with a custom payload schema. Signed with HMAC, replay-safe.

Configure

Slack / Teams

Native integrations for enterprise tiers. Route incidents to the channel that owns the on-call rota.

Enterprise
What we publish

Five things, consistently.

Per-tier availability

Live availability metrics broken out by deployment tier — Shared, Dedicated, VPC, Sovereign, and Marketplace.

Incident history

Full incident history for the last 90 days is public. The complete archive is available to customers on request.

Root cause analyses

Every material incident receives a public RCA within five business days of resolution — timeline, root cause, and remediation actions.

Scheduled maintenance

Maintenance windows are published at least 7 days in advance with affected tiers, start time, and expected duration.

Sub-processor status

Operational status for material sub-processors that affect customer-facing features. Cross-linked from the Trust Center.

Sub-processor status is cross-linked from the Trust Center.

Past incidents

Recent and resolved.

Brief regional latency degradation

April 18, 2026·37 minutes
Resolved

Inference latency in the eu-west region exceeded baseline by 3.2x due to a noisy-neighbour issue on a shared GPU pool. Traffic was failed over to a sibling region; full recovery confirmed at 14:42 UTC.

Full RCA

Third-party feed sync delay

March 2, 2026·2 hours 11 minutes
Resolved

A delay in the upstream vulnerability feed caused new CVE entries to appear with a multi-hour lag. The feed catch-up completed without data loss; affected enrichment jobs were re-run on resolution.

Full RCA

Scheduled maintenance — control-plane upgrade

February 14, 2026·55 minutes
Resolved

Planned control-plane rolling upgrade. Inference and read-only endpoints remained available throughout; mutation endpoints had a brief queue during the leader transition.

Full RCA
Communication SLA

When you hear from us.

During an active P1, updates land every 30 minutes until resolution.

P1
Critical

Within 15 min

Initial notification within 15 minutes of detection. Updates every 30 minutes for the duration of an active P1.

P2
High

Within 1 hour

Initial notification within one hour of detection. Updates at meaningful state changes through to resolution.

P3
Medium

Within 4 hours

Initial notification within four hours of detection. Single update on resolution plus a written summary.

P4
Low

Next business day

Acknowledged on the next business day. Bundled into the weekly status digest with the resolution note.

Subscribe before you need to.

Pick a channel, point it at the right inbox or webhook, and forget about it until something happens — which is exactly when you want it to work.