rawctxStatus

Live platform telemetry

rawctx is accepting production traffic.

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

Checked: Jun 13, 2026, 10:56:23 AMPrimary 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, search path, and hub-api health endpoints.

8Operational 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
Operational82ms

API gateway

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

Source
GET /health
Detail
hub-api 0.2.0
Operational130ms

Tenant routing

The public tenant context endpoint resolves the active Hub workspace.

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

Catalog search path

The package search route can return a small public result page through the active search path.

Source
GET /api/search
Detail
search response returned
Operational226ms

Database

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

Source
GET /health/deep
Detail
ok
Operational226ms

Cache layer

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

Source
GET /health/deep
Detail
ok
Operational226ms

Search index

Deep health reports the configured package search backend state.

Source
GET /health/deep
Detail
ok
Operational226ms

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/health82ms
Tenant routingOperational/api/tenant/context130ms
Catalog search pathOperational/api/search?page=1&size=1&sort=recent327ms
DatabaseOperational/health/deep226ms
Cache layerOperational/health/deep226ms
Search indexOperational/health/deep226ms
Migration modeOperational/health/deep226ms

Persisted status history

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

OperationalJun 13, 2026, 10:46:52 AM8 / 8 checks operationalRecorded: Jun 13, 2026, 10:46:54 AM
DegradedJun 13, 2026, 10:32:03 AM7 / 8 checks operationalRecorded: Jun 13, 2026, 10:32:07 AM
OperationalJun 13, 2026, 10:16:59 AM8 / 8 checks operationalRecorded: Jun 13, 2026, 10:17:02 AM
OperationalJun 13, 2026, 10:02:09 AM8 / 8 checks operationalRecorded: Jun 13, 2026, 10:02:10 AM
OperationalJun 13, 2026, 9:46:53 AM8 / 8 checks operationalRecorded: Jun 13, 2026, 9:46:54 AM
DegradedJun 13, 2026, 9:31:54 AM4 / 8 checks operationalRecorded: Jun 13, 2026, 9:31:57 AM
OperationalJun 13, 2026, 9:16:57 AM8 / 8 checks operationalRecorded: Jun 13, 2026, 9:16:59 AM
OperationalJun 13, 2026, 9:01:58 AM8 / 8 checks operationalRecorded: Jun 13, 2026, 9:02:00 AM
OperationalJun 13, 2026, 8:47:00 AM8 / 8 checks operationalRecorded: Jun 13, 2026, 8:47:02 AM
OperationalJun 13, 2026, 8:32:01 AM8 / 8 checks operationalRecorded: Jun 13, 2026, 8:32:02 AM
OperationalJun 13, 2026, 8:17:01 AM8 / 8 checks operationalRecorded: Jun 13, 2026, 8:17:03 AM
OperationalJun 13, 2026, 8:01:51 AM8 / 8 checks operationalRecorded: Jun 13, 2026, 8:01:53 AM

Incident notes

No active incident detected by live checks.

Active incidentOperational

No active incident detected by live checks.

Recent maintenance noteJun 6, 2026

Package search indexing was tuned after a short delay on Jun 6, 2026. Published package pages remained available while indexing caught up.

Need status notifications?Subscribe

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