Platform status, without the polish.
The current state, the commitments written into the service agreement, where we announce incidents — and a log of the ones that happened.
How the platform is doing this minute.
All systems operational
Response and resolution times, in writing.
These are the figures from the service agreement itself — not estimates.
| Priority | First response | Resolution target |
|---|---|---|
| Critical | Within 1 hour | Within 24 hours |
| High | Within 2 hours | Within 48 hours |
| Medium | Within 4 hours | Up to 5 business days |
| Low | Within 8 hours | Up to 7 business days |
Escalation runs through three levels.
A critical fault gets a human response within one hour, then escalates until it is resolved.
L1 — support team
Initial triage and acknowledgment of the report, plus assignment to the right engineer.
L2 — technical manager
Extra resources allocated and senior engineers brought onto the issue.
L3 — senior management
Direct intervention to speed up resolution and prevent further impact on your business.
How you'll hear about an incident.
This page and the support page
Any incident that affects service is written here and updated until it closes, and the support page carries the channels and response times in full.
Official email from the @managely.cloud domain
Any formal commitment or notice comes from an email on the @managely.cloud domain — that is the only binding channel for formal requests.
Incidents that happened.
No incidents on record.
The first time an incident affects service, it gets written here with its date and a summary of what happened — unpolished.