Pronto Outage History

Pronto is up right now

Pingoru has recorded 27 incidents for Pronto: 4 in the last 12 months and 0 in the last 90 days.

Source: status.pronto.io

27incidents recorded
4last 12 months
0last 90 days
6 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Pronto in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202612 of 744 (0%)
June 202600 of 720 (0%)
July 2026219 of 744 (3%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 520 (0%)

Incidents, newest first

Critical July 16, 2026 AWS CloudFront Outage 2h 38m Pronto Platform, Pronto Web App

Started Jul 16, 2026, 09:24 AM UTC· resolved Jul 16, 2026, 12:03 PM UTC

  1. investigating Jul 16, 2026, 09:24 AM UTC

    Pronto is currently unavailable for all users. Users may see errors or timeouts when loading the app or sending messages. The cause is an ongoing incident with Amazon Web Services (Amazon CloudFront), the network layer that routes traffic to Pronto's servers. Pronto's own systems are healthy, but requests are unable to reach them while the AWS incident is ongoing. AWS has confirmed the issue on their status page and is actively working on it. No messages or data have been lost. Messages sent while the service is unavailable may fail to send and will need to be resent once service is restored. We are monitoring the AWS incident closely and will post updates here as we learn more.

  2. monitoring Jul 16, 2026, 09:24 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. identified Jul 16, 2026, 09:25 AM UTC

    The issue has been identified and a fix is being implemented.

  4. identified Jul 16, 2026, 10:52 AM UTC

    The AWS incident affecting Pronto is still ongoing. While AWS works on their fix, our engineering team is implementing a workaround on our side to restore service without waiting for AWS's resolution. We'll post another update as soon as service is restored or we have more information. Thank you for your patience.

  5. monitoring Jul 16, 2026, 11:25 AM UTC

    AWS has deployed a mitigation for the issue and traffic is flowing again to Pronto. At this point in time, all Pronto services are back up. We continue to monitor AWS's issue and our services to ensure the service remains up.

  6. resolved Jul 16, 2026, 12:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 1, 2026 Auto scaling issues 16h

Started Jul 01, 2026, 09:30 PM UTC· resolved Jul 02, 2026, 01:30 PM UTC

  1. resolved Jul 02, 2026, 11:15 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.

Read the full incident report →

Major May 19, 2026 Web and Desktop App Loading Errors 2h 13m Pronto Web App

Started May 19, 2026, 09:30 PM UTC· resolved May 19, 2026, 11:43 PM UTC

  1. identified May 19, 2026, 09:30 PM UTC

    One of our upstream caching providers is experiencing an issue right now that is affecting loads of the Pronto web and desktop apps. We are working with them to get clarity on the outage and when to expect recovery. We will post updates here as we learn more. The Pronto mobile apps and backend continue to work without issue.

  2. identified May 19, 2026, 10:03 PM UTC

    Our upstream provider is aware and actively working to mitigate and resolve the issue. While our error rate has reduced, we are still seeing intermittent issues. If you experience issues, please try refreshing the page. We will provide more updates soon.

  3. monitoring May 19, 2026, 10:24 PM UTC

    Our provider has implemented a fix for the issue and we are not seeing errors on our end anymore. We will continue to monitor before fully resolving this incident.

  4. resolved May 19, 2026, 11:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 10, 2025 Slow loading times 2h 36m Pronto Platform, Pronto Web App

Started Dec 10, 2025, 04:44 PM UTC· resolved Dec 10, 2025, 07:21 PM UTC

  1. investigating Dec 10, 2025, 04:44 PM UTC

    We are experiencing slow loading times due to a slow caching database. We are investigating and will update as we know more.

  2. investigating Dec 10, 2025, 05:33 PM UTC

    We have added additional resources to stabilize the system, but are still working to identity the source of the increased load and figure out a root cause. We will continue to manually scale the system to keep it stable while we investigate.

  3. identified Dec 10, 2025, 05:59 PM UTC

    We have identified the root cause and are working to remediate.

  4. monitoring Dec 10, 2025, 06:59 PM UTC

    We have applied fixes for the issues and all metrics are back to normal levels. We will continue to monitor the performance for a little while before resolving.

  5. resolved Dec 10, 2025, 07:21 PM UTC

    This incident has been resolved. A postmortem will be posted shortly.

  6. postmortem Dec 10, 2025, 07:21 PM UTC

    During scheduled network maintenance at 04:00 MST, we applied routing changes to standardize the availability zones we use. Due to a developer error, the subnets in one AZ did not get the proper route to our user index database resource. This resulted in some user indexing jobs to fail. These jobs were configured with infinite retries and as these jobs continued to build up, fail, and get retried, it overwhelmed the queueing database. This caused cascading failures throughout the system as other jobs in the queue were delayed or failed. We mitigated by scaling up the database size. We then fixed the routing issue, as well as removing the infinite retry for the job. This resolved the issue. Moving forward, we will ensure that infrastructure code reviews better analyze route changes as well as job retry policy. We are also investigating auto-scaling solutions for our queueing database. We apologize for the degraded performance and appreciate your patience as we continue to improve Pronto for all of our customers.

Read the full incident report →

Critical October 20, 2025 Degraded service due to AWS outage 6h 50m Pronto Platform, Pronto Web App

Started Oct 20, 2025, 04:13 PM UTC· resolved Oct 20, 2025, 11:04 PM UTC

  1. identified Oct 20, 2025, 04:13 PM UTC

    AWS is recovering from a large-scale outage that is affecting Pronto's ability to scale up to meet the normal daily traffic increases. This is causing problems, including delaying push notifications, updating badge counts, and overall app performance. Course synchronization is also in a degraded state because many LMS sources are also affected by the AWS outage. We will continue to follow AWS's recovery closely.

  2. investigating Oct 20, 2025, 06:49 PM UTC

    Pronto is encountering errors within AWS and is currently experiencing connection errors. We suspect this is related to the AWS outage and are actively investigating.

  3. investigating Oct 20, 2025, 07:22 PM UTC

    We continue to investigate. The issues seems related to issues with AWS internal networking. We are attempting to find a way to mitigate the issue. For now, Pronto services are, by and large, unavailable. We apologize for the issue and will continue to provide updates as we learn more.

  4. monitoring Oct 20, 2025, 07:50 PM UTC

    AWS has mitigated some issues that have allowed us to increase capacity and get Pronto working again. We are still seeing intermittent scaling and network issues related to the AWS outage, but we have enough capacity now that Pronto is usable. Expect to see some intermittent errors and slowness as we work to increase capacity to our baseline needs for this time of day.

  5. monitoring Oct 20, 2025, 08:35 PM UTC

    As AWS service recovery continues, we are able to increase capacity. We are also seeing fewer internal networking errors. At this point, all Pronto services are running with normal response times and error rates. We will continue to closely monitor performance.

  6. resolved Oct 20, 2025, 11:04 PM UTC

    AWS has resolved their outage status and all of our metrics have been looking normal for the last couple of hours, so we can now resolve this incident. Thanks for your patience.

Read the full incident report →

Minor September 26, 2025 Online Status Issue 1h 35m Pronto Platform, Pronto Web App

Started Sep 26, 2025, 02:50 PM UTC· resolved Sep 26, 2025, 04:26 PM UTC

  1. investigating Sep 26, 2025, 02:50 PM UTC

    Online status indicators are currently having issues in Pronto. We are investigating.

  2. identified Sep 26, 2025, 03:04 PM UTC

    We have identified an issue causing unexpected behavior after a key rotation was performed during maintenance last night. We are deploying a fix.

  3. monitoring Sep 26, 2025, 03:12 PM UTC

    The fix has been deployed and online status indicators are working again. Please close and re-open the Pronto app to ensure your own indicator is working properly. We will monitor for a little while to ensure a full fix.

  4. resolved Sep 26, 2025, 04:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 2, 2025 Delayed notifications 21m Pronto Platform

Started Apr 02, 2025, 03:03 AM UTC· resolved Apr 02, 2025, 03:25 AM UTC

  1. investigating Apr 02, 2025, 03:03 AM UTC

    We are currently experiencing longer than normal delays delivering new message notifications. We are actively investigating the source of the issue and will update as we learn more.

  2. resolved Apr 02, 2025, 03:25 AM UTC

    We have resolved the issue and notification times are back to normal.

Read the full incident report →