Platform status

RunMyCampus platform status

A reading taken when you opened this page, from checks the platform runs on itself. It is not a history and not an uptime figure.

Status is unknown

6 of 7 components read operational. Read at 2026-11-01T10:01:26.106684+00:00 · Same reading as JSON

The register

Each row says what its check actually asks, so a green row is read for what it is. Two rows share one check, and one row has none.

Platform gateway Asks the background workers how many tasks are waiting or running. With no worker broker configured it says so.
operational
Celery broker not configured (synchronous mode).
Authentication Checks that the sign-in route resolves and the user table can be read.
operational
Authentication entry route and user store reachable.
Tenant portals Runs one liveness query against the primary datastore.
operational
Primary datastore responding to liveness probe.
REST API Looks for a delivered webhook in the last 24 hours and for more than 100 deliveries pending longer than 2 hours.
operational
Webhook dispatch pipeline heartbeat nominal.
Payments Checks that the parent fee routes and their health handler are registered. It does not call a payment processor.
operational
Parent finance routes and health probe registered.
Notifications Uses the same webhook delivery check as the REST API row. It does not send a test message.
operational
Webhook dispatch pipeline heartbeat nominal.
Marketplace No check exists for this component, so it reads unknown.
unknown
No live marketplace probe.

No active public incidents.

No maintenance windows published.

How your own school is doing. A school runs on its own subdomain, and a campus with an edge box keeps working on its own network.
Past outages. Only incidents marked public and not yet resolved are listed, and no uptime percentage is published.
Whether a payment processor or an email provider is up. Those belong to the processor, and this page does not ask them.