Increased Latency for some Hosted Customers
Monitoring - We have identified contributing factors behind the elevated database server CPU utilization that caused intermittent slowness for some districts, and corrective changes have been implemented. System performance has been stable for the past several hours. Our team will continue to closely monitor the environment, including during the morning hours when the issue has occurred, to confirm the fixes are effective. We appreciate your patience.
Nov 04, 2026 - 12:03 PST
Investigating - We are currently investigating reports of intermittent slowness impacting some districts. Our team is actively working to determine the root cause and restore normal performance. We will continue to provide updates as we learn more.
Nov 04, 2026 - 08:32 PST
Update - System performance remains stable at this time. Our team is continuing to closely monitor the environment while investigating the root cause of the elevated CPU utilization that caused intermittent slowness for some districts. We appreciate your patience and will provide further updates as our investigation continues.
Nov 04, 2026 - 07:13 PST
Monitoring - We are continuing to investigate the root cause of the issue that resulted in elevated CPU utilization on one of our SQL Servers and caused intermittent slowness for some districts. System performance remains stable at this time. We appreciate your patience and will provide additional updates as more information becomes available.
Nov 03, 2026 - 13:24 PST
Investigating - One of our SQL Servers experienced extended high CPU usage, causing Districts to experience slowness. The affected SQL Server has recovered from high CPU usage, and we are still investigating the root cause of this issue.
Nov 03, 2026 - 10:42 PST

About This Site

Our platform is continuously monitored for outages, slowdowns, or other issues. Should there be any interruptions in service, we'll provide status updates here.

Uptime over the past 90 days. View historical uptime.
Aeries Cloud Services Degraded Performance
AWS CA Degraded Performance
AWS TX Operational
Aeries Software Issues Operational
Aeries Records Transfer Operational
Aeries.com Operational
App Management Service Operational
Aeries Licensing Service Operational
Phone Issues Operational
Deprecated Operational
Aeries Hosted Service Operational
Irvine CA Operational
Support Portal Operational
Aeries Integrated Software Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Nov 5, 2026

No incidents reported today.

Nov 4, 2026

Unresolved incident: Increased Latency for some Hosted Customers.

Nov 3, 2026

Nov 2, 2026

No incidents reported.

Nov 1, 2026

No incidents reported.

Oct 31, 2026

No incidents reported.

Oct 30, 2026

No incidents reported.

Oct 29, 2026

Aeries Update - 10.26.10.29 (CA)
Completed - The scheduled maintenance has been completed.
Oct 29, 22:01 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 29, 22:00 PDT
Scheduled - We will be undergoing scheduled maintenance during this time.
Oct 29, 15:43 PDT
Aeries Update - 10.26.10.29 (TX)
Completed - The scheduled maintenance has been completed.
Oct 29, 20:01 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 29, 20:00 PDT
Scheduled - We will be undergoing scheduled maintenance during this time.
Oct 29, 15:43 PDT

Oct 28, 2026

No incidents reported.

Oct 27, 2026

Aeries Update - 10.26.10.27 (CA)
Completed - The scheduled maintenance has been completed.
Oct 27, 22:01 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 27, 22:00 PDT
Scheduled - We will be undergoing scheduled maintenance during this time.
Oct 27, 17:26 PDT
Aeries Update - 10.26.10.27 (TX)
Completed - The scheduled maintenance has been completed.
Oct 27, 20:01 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 27, 20:00 PDT
Scheduled - We will be undergoing scheduled maintenance during this time.
Oct 27, 17:26 PDT

Oct 26, 2026

No incidents reported.

Oct 25, 2026

No incidents reported.

Oct 24, 2026

Unscheduled Maintenance
Completed - The scheduled maintenance has been completed.
Oct 24, 01:00 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 24, 00:00 PDT
Scheduled - Aeries will perform unscheduled maintenance to replace TLS certificates on our database servers. The Certificate Authority revoked the existing certificates, so replacement is required to keep connections trusted and secure.

Aeries SIS will be intermittently unavailable for approximately 60 minutes during this window. Active sessions will be disconnected, so please save your work beforehand. No action is required on your part.
Oct 23, 18:30 PDT

Oct 23, 2026

No incidents reported.

Oct 22, 2026

Intermittent 503 Errors
Resolved - 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 already have monitoring and an automated process that requests additional capacity as usage approaches the limit. In this case, traffic rose faster than that process could respond. We are adjusting our capacity thresholds so that headroom is increased earlier, and we are 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.
Oct 22, 08:00 PDT
Incident History Powered by Atlassian Statuspage