2026-05-27
Brief dashboard slowdown
A local dev environment on the web app experienced a reload spike during auth changes. Service recovered without data loss.
This page is meant to build trust: current service health, recent incidents, and the operational shape of the platform that manages scans, connectors, and the dashboard.
A quick read on the services that power the onboarding and dashboard experience.
Connects scan sessions, pairing exchanges, dashboards, and signed connector heartbeats.
Captures lead details, issues pairing codes, and waits for the first heartbeat from the plugin.
Shows site intelligence, incidents, approvals, and the action timeline for signed work.
Handles authenticated traffic between WordPress sites and the orchestration layer.
Good status pages show context, not just a green dot.
A local dev environment on the web app experienced a reload spike during auth changes. Service recovered without data loss.
The public scan endpoint was not allowing a local preview origin until the allowance list was updated and redeployed.
A pair of connector credentials was reissued during the scan flow hardening work. No active production sites were affected.
The goal is to communicate the same calm operational posture the product promises.
The service is operating normally and the user path should work as expected.
We saw a change worth watching, but the system is still usable and no user action is needed yet.
Status is part of the product story, not an afterthought.
Operational transparency is a feature. If the platform feels safe, it should be able to say so clearly.
Run the free scan and see the same operational model from the visitor side.