All systems operational
Checked every five minutes. 1 day of history so far, since 6 August 2026 — building toward 90. We do not backfill days we did not measure, so the record starts thin and stays true.
Storefront search
The engine your shoppers query directly. If this is green, searches are being answered.
Operational
100% over 1 day
Ingest API
internal checkWhere your store sends catalogue changes. Checked by issuing a real request through the application.
Operational
100% over 1 day
Website & dashboard
internal checknitrosearch.io and your merchant dashboard, rendered end to end.
Operational
100% over 1 day
Database
Your store records, sync history and analytics.
Operational
100% over 1 day
Cache & queue backend
Session, cache and the queue that background work is drawn from.
Operational
100% over 1 day
Background workers
The processes that apply your catalogue changes. A backlog shows here before it shows in search.
Operational
100% over 1 day
Connector builds
Whether the code behind each download passes its own tests, straight from GitHub Actions on main.
Public repositories, so you can check the same thing yourself.
What this page cannot tell you
- Two checks run inside the platform. The website and ingest API are exercised by issuing a real request through the application. That covers routing, the database and rendering — but not the network in front of it, so a DNS or edge failure would not appear here while you were seeing an outage. An external prober is the honest fix and is not built yet.
- If the sampler stops, nothing turns green. A component whose last check is more than 16 minutes old reads as “no recent data”, never as operational — so broken monitoring shows up as a problem rather than as good news.
- Days we did not measure stay blank. A grey bar means no samples, not a quiet day. Nothing is backfilled.