Status
NANOTESTING is operational.
Live signal sampled in the last 60 minutes. Component statuses refresh every 30 seconds. Subscribe to incident email updates by writing “status” to support@nanotesting.com.
Overall: Operational
Every component we measure is reporting healthy signal. Rows marked “not monitored here” are not included either way.
Components
- Operational
Marketing site + dashboard (Vercel)
This page was server-rendered by the same deployment, so the web tier answered. No independent uptime probe yet.
- Operational
Scanner worker pool
No scans in the last hour.
- Operational
Email delivery
No transactional email sent in the last hour.
- Not monitored here
Stripe billing
Card processing runs on Stripe. We do not probe it, so we will not claim it is healthy - check status.stripe.com.
- Not monitored here
Supabase managed Postgres
Not probed directly; a database outage would show up in the scan and email rows above. Upstream signal: status.supabase.com.
- Operational
Background jobs (scheduler cron)
Last cron run 3 minutes ago.
Recent incidents
No incidents in the last 30 days. We post post-mortems for any incident that lasted longer than 15 minutes or affected reporting deadlines.
Service-level commitment
Paid plans target 99.5% monthly uptime on the scan-submission API and the dashboard, with a 4-hour recovery objective for full outages. We credit Stripe invoices when we miss that target; see the refund policy for the credit procedure.