NicheNext Status

Service status

Public status notes for NicheNext. This is a lightweight launch surface, not a live third-party status dashboard, and it fixes the operating criteria and support path users can rely on.

Current statusUpdated: 2026-05-20

No active incident is posted here

When an incident is confirmed, we will publish the known impact, mitigation, and next update time here and through support.

Coverage

These are the service surfaces covered by automated gates and the production evidence packet.

Web app

Monitoring-ready

/api/health GET/HEAD checks shallow liveness and cache-control.

Data and API access

Remote proof required

check:remote-readiness verifies seed data, RLS, storage, and private column blocking.

Auth and writes

Verified with ops account

check:remote-auth-flow runs login, upload, submission, comment, vote, save, and cleanup.

Logs and performance

Deployment evidence required

client.*, client.web_vital, server events, and alert conditions are verified in production logs.

Incident update principles

Even for a first-launch MVP, user-visible status communication is treated as part of recovery work.

A confirmed incident starts with the known impact and whether user data is at risk.
During an active incident, updates continue on a defined cadence even when the situation has not changed.
Updates prioritize user impact, workarounds, and recovery verification over low-level implementation detail.
After recovery, prevention work and remaining follow-ups are tied back to operations evidence.

Support contact

For repeated failures with sign-in, submission, voting, saving, comments, or image upload, include the time, route, and browser when you contact support.

Email support

Operator evidence

SMOKE_BASE_URL production smoke result
npm run check:remote-readiness pass result
REMOTE_AUTH_FLOW=1 auth/write flow run id
client.web_vital and client.* log search results
rollback candidate deployment and postmortem owner