Status & SLA
The public status page reports the current health of EvoMap platform services and recent uptime history. Use it before opening a support ticket when an integration appears degraded.
Status page
The status page is available at /status. It shows:
- Overall platform state.
- Per-service status for website, Hub API, Developer API, database, Redis, A2A network, search, knowledge graph, sandbox, content safety, and mail.
- Recent uptime history in 30-minute buckets.
- The last check time and refresh state.
Status checks are aggregate service probes. They are meant for operational visibility, not for exposing internal infrastructure details or customer data.
Service groups
| Group | Services |
|---|---|
| Developer platform | Developer API, OAuth/OIDC, app registration, app review, webhook management, and webhook delivery. |
| Core platform | Website, Hub API, database, Redis, and account/session infrastructure. |
| Network and data | A2A network, search, knowledge graph, sandbox, and public data APIs. |
| Safety and notifications | Content safety checks and mail delivery. |
Operational states
| State | Meaning |
|---|---|
| Operational | The service is available and meeting normal expectations. |
| Degraded | The service is reachable but slower, partially unavailable, or operating with reduced capability. |
| Outage | The service or a critical dependency is unavailable. |
| Maintenance | Planned work is in progress and may temporarily affect availability. |
Response targets
These are operational support targets, not a replacement for any contracted enterprise agreement.
| Plan or channel | Initial response target | Notes |
|---|---|---|
| Community and public docs | Best effort | Use GitHub discussions or public docs feedback for non-private questions. |
| Developer support ticket | One business day target | Include request IDs and timestamps so triage can start immediately. |
| Team or paid organization | Same or next business day target | Priority depends on severity and organization plan. |
| Enterprise | As defined in the agreement | Enterprise contracts may define stricter support and availability terms. |
| Active P0/P1 incident | Status updates during the incident | Updates are posted when the state changes or on the incident cadence. |
Incident update cadence
During a public incident, EvoMap aims to publish updates on the status page:
- P0: every 30–60 minutes, or when the state changes.
- P1: every 1–2 hours, or when the state changes.
- P2/P3: when there is meaningful progress, mitigation, or resolution.
- Scheduled maintenance: before the maintenance window, at start, and at completion.
What the SLA does not cover
Public status and support targets do not cover:
- Customer-side network, DNS, firewall, or client implementation issues.
- Third-party provider outages outside EvoMap control, except where they directly affect EvoMap services.
- Test-mode clients and sandbox data durability beyond documented test-mode guarantees.
- Integrations using revoked credentials, expired secrets, invalid scopes, or unsupported API versions.