RouterPlex StatusBack to RouterPlex ↗

RouterPlex service status

All monitored services are responding.

See current availability and the checks behind it.

Checks every minuteMonitoring since 2026-09-12 20:19:00 UTC

Service availability

API gateway

Public API gateway reachability. Does not generate a model response.

Operational
Observed uptime · 30d100.000%
Average check time13 ms
Monitoring coverage100.0%
2026-08-14Today
40 recorded checks · 0 failedLast check:

Website

Public site over HTTPS.

Operational
Observed uptime · 30d100.000%
Average check time47 ms
Monitoring coverage100.0%
2026-08-14Today
40 recorded checks · 0 failedLast check:

Platform readiness

Account backend, database connection, and gateway readiness.

Operational
Observed uptime · 30d100.000%
Average check time26 ms
Monitoring coverage100.0%
2026-08-14Today
40 recorded checks · 0 failedLast check:

Model catalog

The published catalog contains available model routes.

Operational
Observed uptime · 30d100.000%
Average check time22 ms
Monitoring coverage100.0%
2026-08-14Today
40 recorded checks · 0 failedLast check:

Documentation

Public developer documentation over HTTPS.

Operational
Observed uptime · 30d100.000%
Average check time56 ms
Monitoring coverage100.0%
2026-08-14Today
40 recorded checks · 0 failedLast check:

AvailableFailed checksIncomplete coverageNo data

Select a day for its check counts and uptime.

Incident history

No interruptions detected during the recorded monitoring period.

How availability is measured

Observed uptime is successful scheduled HTTP checks divided by recorded checks. Missed checks are reported separately as monitoring coverage and unknown minutes. Gray days have no data. Time before monitoring started is not included.

These probes check public HTTPS reachability and response content. Platform readiness also checks the database and gateway. They do not submit a payment or generate a model response; an individual upstream model or payment provider can fail while these checks pass.

The availability objective is 99.9%. This is an internal reliability target, not a contractual SLA or a promise of service credits. A 30-day period at 99.9% allows 43.2 minutes outside the target. Observed checks are an approximation of availability between samples.

The monitor and this page run separately from the application server. They share Cloudflare infrastructure with the public service, so this is not independent multi-provider or multi-region measurement. Outage records begin with the first failed probe. No history is backfilled.