Status site
Operational
The independent status frontend is online.
This page is intended to stay reachable even when parts of the main platform are impaired.
Nestarc Webhooks
Status
Live health, incident updates, and maintenance notices.
UnknownChecking live systems
Live monitoring data could not be read from the source endpoint.
Component health is derived from the primary API health endpoint and refreshed directly in your browser.
- Last checked
- Waiting for live data
- Refresh cadence
- Every 60s
- Source
- Live health endpoint
Live checks update in the browser. If this stays unknown after deploy, confirm the API CORS allowlist includes https://status.nestarc.dev.
Primary API
Unknown
Live API health data could not be fetched.
The status site is reachable, but the upstream health endpoint did not return a usable response.
Database
Unknown
Database dependency status is currently unknown.
This component reflects the database indicator exposed by the upstream health endpoint.
Redis
Unknown
Redis dependency status is currently unknown.
This component reflects the Redis indicator exposed by the upstream health endpoint.
Monitored source
https://webhook.nestarc.dev/api/v1/health
Publication policy
Open incidents are updated as a visible timeline. New entries are appended with absolute timestamps instead of silently rewriting prior states.
Deployment model
This site is intended for Cloudflare Pages atstatus.nestarc.devso communication can stay reachable even when the primary app path is impaired.
Support path
If you need confirmation for customer-facing impact, contact[email protected]and reference the incident title shown on this page.
Active incidents
Open incidents
No active incidents
No user-facing incidents are currently open. The live system summary above remains the primary source for current component health.
Scheduled maintenance
Planned work
No scheduled maintenance
Planned maintenance windows will be posted here ahead of time with expected impact and start times.
Incident history
Recent history
No published incident history yet
Resolved incidents will remain visible here so users can review what happened, when it started, and how communication was handled.
Communication standard
Status updates should reduce ambiguity, not add to it.
This page communicates impact first, then timing, then the current state of investigation. It intentionally avoids uptime marketing or optimistic language during uncertain events.
When incidents are active, updates should be appended instead of silently edited. When incidents are resolved, history should remain visible long enough for users to verify how communication was handled.