Resolved · 2d ago · Wed, Jul 1, 9:30 PM UTC (9:30 PM UTC)
As morning traffic increased our auto scaling rules did not trigger properly. As a result, response times were slow or would time out. We manually scaled up the system and are working to identify and fix the issue with autoscaling.
Pronto is currently operational as of . All monitored components are functioning normally.
How do I check if Pronto is down?▼
You can check Pronto status in real time at netbeep.com/status/pronto. This page monitors the official Pronto status page and shows current component health, active incidents, and uptime history.
What should I do during a Pronto outage?▼
During a Pronto outage, check this page for real-time updates. Review the active incidents section for details on affected components and estimated resolution. You can also visit the official status page at https://status.pronto.io for announcements directly from Pronto.
What is Pronto's current status?▼
Pronto is operational. Visit netbeep.com/status/pronto for real-time updates including component health, active incidents, and uptime history.
How many Pronto components does Netbeep monitor?▼
Pronto has 2 monitored components. 2 are operational.
How often does Pronto go down?▼
Pronto outage frequency varies. Netbeep tracks all incidents reported on the official Pronto status page. Visit this page to see current status, uptime percentages, and incident history.
Notion
Figma
Airtable
Asana
Linear
Dropbox