Is Aeries Software down?

Resolved (8:40 AM PT) The issue is resolved. Error rates returned to normal (about 0.014%, the same as before the incident) by 8:30 AM and stayed there while traffic kept growing. The component that routes requests to the right district used less than half of its new capacity at peak. Root cause: The morning traffic surge exceeded the default concurrency limit of our request-routing component. Requests over that limit were turned away before they reached the Aeries application, which is why users saw a 503 error. Impact: Some requests failed with a 503 error between about 8:05 AM and 8:30 AM PT. At the peak, around 8:20 AM, roughly 9–10% of requests were affected. Most requests succeeded throughout, and a retry or page refresh would often have worked. Data: We found no data impact. The errors occurred before requests reached the application, and no data was altered. Next steps: We are adding alerting so that approaching the capacity limit is flagged before it affects users. We are also reviewing capacity across the rest of our infrastructure and looking at ways to make the routing step more efficient. Monitoring (8:28 AM PT) We increased the routing component’s capacity from 1,000 to 5,000 concurrent requests. Rejected requests dropped to zero at 8:28 AM, and we are monitoring error rates as traffic continues to grow. Identified (8:25 AM PT) We confirmed the Aeries application servers were healthy and passing health checks. We traced the errors to a capacity limit on the component that routes each request to the right district, and we are increasing that capacity. Investigating (8:05 AM PT) We are seeing intermittent 503 errors for some requests to Aeries SIS and are investigating. Refreshing the page or retrying may resolve the error.

On 10/21/2026, between 5:00 PM and 5:40 PM Pacific, some customers received 502 errors when trying to access Aeries. The cause was a configuration change that was deployed in error. We reverted the change and service was fully restored after about 40 minutes. We apologize for the disruption, and we are reviewing our deployment process to help prevent this from happening again.

We are currently experiencing a partial outage and are actively investigating the cause. We will have an update for you in 30 minutes.

The cause of the latency, timeout errors and inability to log in has been identified, and mitigation efforts are underway. We are currently monitoring the environment while the changes take effect and are seeing progress toward resolution.

We are currently in a monitoring phase following the implementation of a fix to address the outage. While system stability has improved, we have identified an impact to certain third-party integrations. As a result, the Enroll Path and ActivityHero integration endpoints have been temporarily disabled while we work to restore full functionality. We will continue to provide updates as progress is made.

System performance has stabilized and remains steady. The remaining work is restoring the Enroll Path and ActivityHero integrations, which were temporarily disabled as part of the mitigation. Our engineering team is targeting a fix later tonight to restore full functionality. This will be our final update until that fix has been deployed and verified — we will post again as soon as full functionality is confirmed restored.

This incident has been resolved.

# Incident Report  _Aeries platform including Enroll Path and ActivityHero performance and login issues on September 16, 2026 — service has been restored._  ## Overview  On the morning of September 16, 2026, customers across the Aeries hosted platform experienced significant slowness, timeout errors, and difficulty logging in. Our team identified the cause and began working on a fix immediately, and by approximately 9:30 AM Pacific system performance had stabilized. Two specific functions remained unavailable while we finished the fix: completing an approved Enroll Path enrollment into a student's Aeries record and setting up a new ActivityHero integration. Both were fully restored at 10:00 PM Pacific, when the permanent fix was deployed.  ## Details  Starting around 8:15 AM Pacific, customers began reporting slow page loads, error messages, and an inability to log in. Our support and engineering teams were already investigating within about ten minutes, identified the underlying cause, and applied an initial remediation at 8:47 AM Pacific. The issue stemmed from a software release earlier that day that included extra background logging that had not been fully removed before it went live. Under real-world traffic, that logging placed an unexpected, heavy load on our servers, which is what produced the slowness and errors customers experienced.  ## Timeline \(all times Pacific\):  8:15 AM — Customers begin experiencing slowness, timeout errors, and login failures.  8:47 AM — Initial remediation applied to relieve load on the database servers.  9:00 AM — Performance improvement first observed, improving progressively over the following half hour.  9:30 AM — Performance stabilized and remained steady for the remainder of the day.  10:00 PM — Permanent fix deployed; both affected functions fully restored.  12:00 AM — Incident formally closed.  ## Mitigation  To relieve the load on our database servers while we prepared a permanent fix, we disabled our connection to a shared configuration service that was amplifying the volume of background logging. That service is also used by Enroll Path and ActivityHero for a couple of specific actions, so as a side effect, two things were temporarily unavailable: completing an approved Enroll Path enrollment into a student's Aeries record and setting up a new ActivityHero integration. Neither feature was the source of the issue. Enroll Path applications could still be submitted and reviewed, and existing ActivityHero integrations continued to run normally throughout. Customers began seeing improved performance at approximately 9:00 AM Pacific, with conditions improving progressively over the following half hour. By approximately 9:30 AM, performance had stabilized and remained steady for the remainder of the day. At 10:00 PM Pacific, we deployed a permanent fix that removed the excess logging and fully restored both functions. The incident was formally closed at midnight Pacific.  With this specific issue resolved, we've turned our attention to preventing this class of issue going forward:  * Adding a formal impact assessment and an additional review step before changes go live, so effects like this are caught before release.  * Communicating this new review standard across our entire engineering team.  * Building a dedicated testing environment where we can load-test upcoming releases under realistic traffic before they reach customers.  ## Conclusion  We sincerely apologize for the disruption this caused for the schools and districts that rely on Aeries every day. We know how important reliable access to this system is, and we will continue investing in the testing and review processes that keep it dependable.

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.

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.

Traffic is actively rebalancing across our infrastructure, and service recovery is progressing. We will share additional updates as needed.

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.

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.

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.

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.

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.

This incident has been resolved.

We are investigating reports of degraded performance and difficulties running reports. Our team is actively working to identify the cause and will provide an update within 30 minutes.

We are continuing to investigate this issue.

Resolved - The reporting queue has returned to normal levels and report processing is stable. The issue is now resolved.

Resolved - The reporting queue has returned to normal levels and report processing is stable. The issue is now resolved.

This incident has been resolved.