First-party platform monitoring

rawctx first-party checks are operational.

Live checks are passing for the web surface and API health path. Dependency rows below show the current reported state.

This status view is first-party monitoring operated by rawctx. It reports rawctx probes, not independent uptime verification or an SLA measurement.

Checked: Aug 9, 2026, 7:13:02 PMPrimary source: public-apiResponse budget: 2.5s per probe

Current checks

These cards are generated on request from the current Next.js render, public routing checks, and hub-api health endpoints.

6Operational checks0Degraded checks0Outage checks0Unknown checks

Operational0ms

Web surface

The public status page rendered successfully inside the current Hub deployment.

Source: Next.js server render
Detail: status page rendered

Operational91ms

API gateway

The hub-api lightweight health endpoint is reachable and returning JSON.

Source: GET /health
Detail: hub-api 0.2.0

Operational117ms

Tenant routing

The public tenant context endpoint resolves the active Hub workspace.

Source: GET /api/tenant/context
Detail: tenant context returned

Operational91ms

Database

Deep health reports whether the application database can answer a simple query.

Source: GET /health/deep
Detail: ok

Operational91ms

Cache layer

Deep health reports Redis readiness when the cache layer is configured.

Source: GET /health/deep
Detail: ok

Operational91ms

Migration mode

Health metadata reports the active tenancy and migration posture.

Source: GET /health/deep
Detail: multitenant

Probe log

Machine-readable status is available at /api/status and uses HTTP 503 when the overall state is an outage.

Status JSON

Web surfaceOperational/status0ms

API gatewayOperational/health91ms

Tenant routingOperational/api/tenant/context117ms

DatabaseOperational/health/deep91ms

Cache layerOperational/health/deep91ms

Migration modeOperational/health/deep91ms

Persisted status history

These rows are stored by the hub-api status snapshot worker from the public /api/status JSON feed.

OperationalAug 9, 2026, 7:01:52 PM6 / 6 checks operationalRecorded: Aug 9, 2026, 7:01:53 PM

OperationalAug 9, 2026, 6:46:54 PM6 / 6 checks operationalRecorded: Aug 9, 2026, 6:46:55 PM

OperationalAug 9, 2026, 6:31:57 PM6 / 6 checks operationalRecorded: Aug 9, 2026, 6:31:58 PM

OperationalAug 9, 2026, 6:16:56 PM6 / 6 checks operationalRecorded: Aug 9, 2026, 6:16:57 PM

OperationalAug 9, 2026, 6:01:52 PM6 / 6 checks operationalRecorded: Aug 9, 2026, 6:01:53 PM

OperationalAug 9, 2026, 5:46:55 PM6 / 6 checks operationalRecorded: Aug 9, 2026, 5:46:56 PM

OperationalAug 9, 2026, 5:31:52 PM6 / 6 checks operationalRecorded: Aug 9, 2026, 5:31:53 PM

OperationalAug 9, 2026, 5:16:57 PM6 / 6 checks operationalRecorded: Aug 9, 2026, 5:16:58 PM

OperationalAug 9, 2026, 5:02:01 PM6 / 6 checks operationalRecorded: Aug 9, 2026, 5:02:02 PM

OperationalAug 9, 2026, 4:46:59 PM6 / 6 checks operationalRecorded: Aug 9, 2026, 4:47:00 PM

OperationalAug 9, 2026, 4:31:58 PM6 / 6 checks operationalRecorded: Aug 9, 2026, 4:31:59 PM

OperationalAug 9, 2026, 4:17:00 PM6 / 6 checks operationalRecorded: Aug 9, 2026, 4:17:01 PM

Incident notes

No active incident detected by live checks.

Active incidentOperational

No active incident detected by live checks.

Recent maintenance noteJun 6, 2026

Public lookup indexing was tuned after a short delay on Jun 6, 2026. Primary public pages remained available while indexing caught up.

Need status notifications?Subscribe

Subscribe by email while the public notification channel is being formalized.