Demo build. Every business shown is fictional, data is synthetic and partner integrations are simulated.What is real here
AGORA
Sign inStart a free trial
Menu
BusinessesAgenciesGroupsPricingDocsTrust
Scan your siteSign inStart a free trial

System status

Component status comes from the same SLO burn-rate monitors that page the on-call team. This page refreshes every minute.

All systems operational
Updated

Components

Projections and feedsSLO 99.95% · p95 under 100 ms · last hour: 2 requests, 0.0% errors, p95 14 msOperational
MCP serverSLO 99.95% · p95 under 150 ms · last hour: 0 requests, 0.0% errorsOperational
Checkout and bookingSLO 99.90% · p95 under 800 ms · last hour: 0 requests, 0.0% errorsOperational
Trust edgeSLO 99.99% · p95 under 20 ms · last hour: 2 requests, 0.0% errors, p95 14 msOperational
Handoff linksSLO 99.95% · p95 under 200 ms · last hour: 0 requests, 0.0% errorsOperational
Public APISLO 99.90% · p95 under 500 ms · last hour: 4 requests, 0.0% errors, p95 23 msOperational
Console and dashboardsSLO 99.90% · p95 under 2000 ms · last hour: 80 requests, 0.0% errors, p95 53 msOperational

Open incidents

No open incidents.

Recently resolved

No incidents in the recent history of this host.

How we communicate during an incident

Every update uses one of these templates, so you always know what stage an incident is at.

investigating

{component}: elevated errors

We are investigating elevated error rates on {component} since {start}. Agents may see failed requests; retries are safe (requests are idempotent). Next update within 30 minutes.

identified

{component}: cause identified

We have identified the cause of the {impact} on {component} and are applying a fix. Next update within 30 minutes.

monitoring

{component}: fix deployed, monitoring

A fix is deployed for {component}. Error rates are back within the SLO; we are monitoring before closing the incident.

resolved

{component}: resolved

{component} has been operating within its SLO since {now}. A post-incident review follows within 5 business days for incidents longer than 30 minutes.

monitoring

Scheduled maintenance: {component}

Scheduled maintenance on {component} from {start}. No downtime is expected; requests may be slower for a few minutes.

Source: GET /v1/status (self-serve SLO monitor) · SLO burn-rate monitors (spec 20.1): fast burn 14.4x on 1 h and 5 min, slow burn 6x on 6 h · Demo host: one process; measured at the origin.. JSON: /status?format=json.