Aeries Software incident
Intermittent 503 Errors Affecting Some Customers
Aeries Software experienced a major incident on September 3, 2026 affecting AWS CA, lasting 4d 21h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 03, 2026, 04:03 PM UTC
Some customers are currently experiencing a 503 error. Our team is actively investigating the issue and working to determine the root cause. We will provide another update within 60 minutes.
- monitoring Sep 03, 2026, 05:02 PM UTC
We have identified the issue affecting districts and portals, and our engineers are actively working toward a resolution. We will share another update within the next 60 minutes.
- monitoring Sep 03, 2026, 05:50 PM UTC
Traffic is actively rebalancing across our infrastructure, and service recovery is progressing. We will share additional updates as needed.
- identified Sep 04, 2026, 02:32 PM UTC
Some customers are currently experiencing slowness and 503 errors. Our team has determined the underlying cause and is evaluating the best path forward to resolve it. We will provide another update within 60 minutes.
- identified Sep 04, 2026, 03:37 PM UTC
Some customers are currently experiencing intermittent slowness and 503 errors. Our team has identified the cause of the issue and is actively working toward a resolution. We will provide our next update within 60 minutes.
- monitoring Sep 04, 2026, 04:06 PM UTC
Traffic rebalancing is ongoing across our infrastructure, and we are seeing continued improvement in service performance. We will share further updates as they become available.
- monitoring Sep 04, 2026, 08:37 PM UTC
Services remain stable, and we are continuing to implement infrastructure enhancements designed to improve reliability and address the stability issues experienced by some customers. We'll continue to monitor the situation closely and provide updates as needed.
- monitoring Sep 04, 2026, 10:01 PM UTC
Services remain stable, and ongoing infrastructure improvements are underway to enhance reliability and address known stability concerns. We will continue to monitor the environment and provide updates as needed.
- resolved Sep 08, 2026, 01:44 PM UTC
This incident has been resolved.