Aeries Outage History

Aeries customers experienced latency, slowness, and timeouts affecting the AWS CA component over a 30.9-hour period. The service team investigated the issue and implemented a fix. The incident was resolved after monitoring confirmed the fix was effective.

Aeries experienced latency issues, version mismatches, and printing problems that affected some customers for 32 minutes. The AWS CA component was impacted during this incident. The service team investigated and resolved all issues.

Aeries experienced latency, slowness, and timeout issues affecting some customers for 3.1 hours. The incident impacted the AWS CA component. The service has been fully restored and the incident was resolved.

Aeries experienced latency issues, version mismatches, and printing problems that affected some customers for 17 minutes. The AWS CA component was impacted during this incident. The service team investigated and resolved all issues.

Aeries experienced latency issues, version mismatches, and printing problems that affected some customers for 16.7 hours. The AWS CA component was impacted during this incident. The service has been fully restored and the incident was resolved.

Aeries experienced latency, slowness, and timeout issues affecting some customers for 6.1 hours. The problem impacted the AWS CA component. The incident was resolved after investigation and remediation efforts.

Aeries temporarily suspended its Canvas integration for all customers as a precautionary measure following a security incident at Instructure (Canvas), affecting workflows that rely on the integration between the two platforms. The suspension lasted 16.5 hours while Aeries coordinated with Instructure and monitored the situation to ensure student and staff data remained protected. Aeries resolved the incident by generating new API keys for all customers and providing instructions for reconnecting the Canvas integration at each organization's discretion.

The Aeries service experienced intermittent latency issues affecting the AWS CA component for 5.4 hours. A fix was implemented and monitored before the incident was resolved. The issue was classified as minor impact.

The Aeries system experienced a major incident involving system performance issues and version mismatches that affected the AWS CA component for 18.6 hours. A fix was identified and implemented, followed by monitoring to ensure stability. The incident was fully resolved after confirming no further issues occurred.

Aeries experienced latency, slowness, and timeouts affecting some customers due to issues with AWS CA components. A fix was implemented and the service was monitored until the incident was fully resolved after 1.2 hours.