All systems operational
Status for RoutMe infrastructure. If something here says operational and your integration disagrees, the checklist further down covers the causes we see most often.
API
OperationalREST endpoints at api.routme.io, authentication, and everything you call directly.
Message processing
OperationalOutbound sends handed to the channel, and inbound messages accepted from it.
Agent runtime
OperationalAgent nodes, tool and MCP calls, and flow execution.
Webhook delivery
OperationalEvents pushed to your endpoints, including retries and backoff.
Dashboard
Operationalapp.routme.io, the flow builder, and conversation logs.
Analytics
OperationalDelivery and read reporting, and usage counters for billing.
What each state actually means
Status pages are only useful if the words on them are precise. These are ours.
- Operational
Working as expected. Normal error rates and no elevated latency.
- Degraded
Still working, but slower or failing intermittently. Retries generally succeed and messages are not lost, they are late.
- Partial outage
One component or one channel is unavailable while the rest continues. Queued work resumes when it returns.
- Major outage
A core component is unavailable. Posted here immediately, with updates at least every 30 minutes until it is resolved.
How we handle an incident
Detect
Monitoring on error rates, latency, and delivery patterns alerts us, ideally before a customer does.
Post
Anything with customer-visible impact is posted here with the components affected, even while the cause is still unknown.
Update
Major incidents get an update at least every 30 minutes, whether or not there is progress to report.
Follow up
Once resolved, we publish what happened, what the impact was, and what changes as a result.
Five things that look like an outage
Most reports that reach support during a green status resolve to one of these. Working through them first is usually faster than waiting on a reply.