Aptible Outage History

Aptible is up right now

Pingoru has recorded 50 incidents for Aptible: 16 in the last 12 months and 2 in the last 90 days.

Source: status.aptible.com

50incidents recorded
16last 12 months
2last 90 days
33 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Aptible 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 202621 of 720 (0%)
May 2026227 of 744 (4%)
June 20262339 of 720 (47%)
July 2026223 of 744 (3%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202610 of 586 (0%)

Incidents, newest first

Major February 13, 2025 Operations blocked - Route 53 propagation delays 57m Aptible Deploy

Started Feb 13, 2025, 11:51 PM UTC· resolved Feb 14, 2025, 12:48 AM UTC

  1. identified Feb 13, 2025, 11:51 PM UTC

    We've noticed that some Operations are failing due to Route53 record changes not propagating within the 10 minute time limit allowed by our platform. In order to prevent Apps and Databases DNS records from reaching an inconsistent state, we are temporarily blocking Operations. Performance and reachability of existing Apps and Database is not impacted.

  2. monitoring Feb 14, 2025, 12:26 AM UTC

    We are noticing Route 53 record requests succeeding in a normal time frame, and are lifting the operation block at this time. We'll continue to observe running operations to ensure stability.

  3. resolved Feb 14, 2025, 12:48 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 5, 2025 Database provision errors 10m Aptible Deploy

Started Feb 05, 2025, 08:02 PM UTC· resolved Feb 05, 2025, 08:13 PM UTC

  1. identified Feb 05, 2025, 08:02 PM UTC

    We've identified an error blocking the creation of new Databases on the platform, and our team is applying a fix. Reachability of your existing databases, and the ability to scale or restart them is not impacted.

  2. identified Feb 05, 2025, 08:03 PM UTC

    We are continuing to work on a fix for this issue.

  3. resolved Feb 05, 2025, 08:13 PM UTC

    This incident has been resolved.

Read the full incident report →