Probing health endpoint… If you’re seeing something we’re not, email support@instantpwa.com.
Filter by component to see past incidents affecting a specific system.
Two edge PoPs served stale embed.js for ~14 minutes after a config rollout. No functional impact; new visitors received the fresh script on retry.
A queue worker in eu-west-1 stopped consuming after a dependency restart. Messages queued for up to 22 minutes before catch-up processing.
A transient throttle on our primary SMTP provider added ~90s median delay for magic-link and password-reset emails. Automatic failover engaged.
Elevated auth latency after a database failover test. No sign-in failures; median login time returned to normal within 8 minutes.
Approximately 0.4% of impression/install events were rejected for 6 minutes due to a schema-cache miss after a routine migration. Client-side retry recovered most events.
Our on-call responder acknowledges P1 incidents (site or embed script down for paying customers) within 30 minutes, 24/7. P2 issues (feature degradation) are acknowledged during business hours. Post-mortems for P1 incidents are published here within 5 business days.
This page shows our current known status. For continuous uptime monitoring we recommend running your own healthcheck against https://instantpwa.com/api/public/health.