Aeries Software Outage History

Aeries Software is up right now

Aeries Software had 30 outages in the last 2 years totaling 194h 3m of downtime — averaging 1.2 incidents per month.

There were 30 Aeries Software outages since August 28, 2024 totaling 194h 3m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://aeriessoftware.statuspage.io

Minor August 21, 2026

Latency, Reports Not Running

Detected by Pingoru
Aug 21, 2026, 07:44 PM UTC
Resolved
Aug 22, 2026, 12:28 AM UTC
Duration
4h 43m
Affected: AWS CA
Timeline · 6 updates
  1. investigating Aug 21, 2026, 07:44 PM UTC

    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.

  2. investigating Aug 21, 2026, 08:14 PM UTC

    We are continuing to investigate reports of degraded performance and issues running reports. Our team remains actively engaged in identifying the root cause and will provide another update within 60 minutes.

  3. investigating Aug 21, 2026, 09:20 PM UTC

    We are still investigating reports of degraded performance and issues running reports. We will provide a further update within 60 minutes.

  4. investigating Aug 21, 2026, 10:19 PM UTC

    We continue to investigate the underlying cause of the degraded reporting performance. At the same time, we are actively provisioning a new reporting fleet based on our enhanced scaling architecture as part of our mitigation efforts. We will share another update within 60 minutes.

  5. monitoring Aug 21, 2026, 11:10 PM UTC

    The reporting queue has returned to normal levels, and report processing is functioning as expected. We are currently monitoring performance closely to confirm that systems remain stable and operating as expected. We will continue to provide updates as needed.

  6. resolved Aug 22, 2026, 12:28 AM UTC

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

Read the full incident report →

Minor August 19, 2026

Graduation Status, Profile, and Student Search Bar Not Working

Detected by Pingoru
Aug 19, 2026, 04:13 PM UTC
Resolved
Aug 19, 2026, 07:35 PM UTC
Duration
3h 22m
Affected: AWS CAAWS TX
Timeline · 3 updates
  1. investigating Aug 19, 2026, 04:13 PM UTC

    We are aware of an issue affecting the Graduation Status page, Student Profile page, and Student Search functionality. Our team is actively investigating the issue and working to restore normal service as quickly as possible. We will provide our next update within 60 minutes, or sooner if additional information becomes available.

  2. monitoring Aug 19, 2026, 04:44 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 19, 2026, 07:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 14, 2026

API Service Degradation

Detected by Pingoru
Aug 14, 2026, 06:18 PM UTC
Resolved
Aug 14, 2026, 08:27 PM UTC
Duration
2h 9m
Affected: AWS CA
Timeline · 5 updates
  1. investigating Aug 14, 2026, 06:18 PM UTC

    We are investigating reports of the API being unavailable. Our team is actively working to identify the cause and will provide an update within 30 minutes.

  2. investigating Aug 14, 2026, 06:29 PM UTC

    We have identified an issue affecting one of our API servers. To minimize customer impact, traffic has been redirected away from the affected server while our team continues to investigate and implement corrective actions. We are closely monitoring the environment and working to restore full service. Our next update will be provided within 60 minutes

  3. investigating Aug 14, 2026, 07:34 PM UTC

    We are continuing to investigate the issue affecting one of our API servers. At this time, there are no significant updates to share. Traffic remains redirected away from the affected server, and our team continues to monitor the environment and work toward resolution. We will provide another update within 60 minutes or sooner if new information becomes available. As a temporary workaround, customers using the Aeries API (not the OneRoster API) should ensure they are using the standard district.aeries.net base URL rather than the api base URL. The standard URL is load balanced and will help distribute traffic more effectively while we continue to address the issue.

  4. monitoring Aug 14, 2026, 07:53 PM UTC

    The unplanned maintenance has been completed, and OneRoster API services have been successfully restored. We are currently monitoring the environment to verify continued stability. Our team will continue to closely observe the environment and will provide an update within 60 minutes, or sooner should any changes occur.

  5. resolved Aug 14, 2026, 08:27 PM UTC

    This incident has been resolved. Our team completed additional corrective maintenance to rebalance workloads across the affected server, and continuous monitoring since has confirmed the environment remains stable. We apologize for any disruption this may have caused and thank you for your patience.

Read the full incident report →

Minor August 12, 2026

Increased Latency for Some Hosted Customers

Detected by Pingoru
Aug 12, 2026, 07:21 PM UTC
Resolved
Aug 13, 2026, 06:31 AM UTC
Duration
11h 9m
Affected: AWS CA
Timeline · 4 updates
  1. investigating Aug 12, 2026, 07:21 PM UTC

    We are currently investigating reports of increased latency and slower-than-normal performance affecting some Hosted customers. Our team has identified the source of the issue and is actively working to restore normal performance.

  2. identified Aug 12, 2026, 11:24 PM UTC

    A configuration deployed in error created a performance issue. The change is being reverted.

  3. monitoring Aug 13, 2026, 04:33 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 13, 2026, 06:31 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 7, 2026

Partial Service Disruption Affecting Hosted Aeries Access

Detected by Pingoru
Aug 07, 2026, 03:16 PM UTC
Resolved
Aug 07, 2026, 04:18 PM UTC
Duration
1h 1m
Affected: AWS CA
Timeline · 3 updates
  1. identified Aug 07, 2026, 03:16 PM UTC

    We have identified the source of the issue, and our team is actively working to restore access for affected districts. We will continue to provide updates as progress is made.

  2. monitoring Aug 07, 2026, 03:34 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 07, 2026, 04:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 5, 2026

Delayed Reports and Version Mismatch

Detected by Pingoru
Aug 05, 2026, 10:02 PM UTC
Resolved
Aug 05, 2026, 11:07 PM UTC
Duration
1h 5m
Affected: AWS CA
Timeline · 3 updates
  1. identified Aug 05, 2026, 10:02 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Aug 05, 2026, 10:14 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 05, 2026, 11:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 22, 2026

Reports of latency, version mismatch, and trouble printing reports for some customers

Detected by Pingoru
Jul 22, 2026, 04:14 PM UTC
Resolved
Jul 23, 2026, 08:11 AM UTC
Duration
15h 56m
Affected: AWS CA
Timeline · 7 updates
  1. investigating Jul 22, 2026, 04:14 PM UTC

    We are currently investigating this issue.

  2. identified Jul 22, 2026, 04:17 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jul 22, 2026, 04:28 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. identified Jul 22, 2026, 08:01 PM UTC

    We are reverting the status to "Identified" as it has been determined that the issue requires engineering changes to fully resolve. Our operations team is monitoring reporting capacity until a fix is released and deployed.

  5. identified Jul 22, 2026, 09:57 PM UTC

    The changes are still being tested. They are currently scheduled to be released and deployed tonight.

  6. monitoring Jul 23, 2026, 01:16 AM UTC

    A release has been scheduled for deployment to address the performance issues with reporting services.

  7. resolved Jul 23, 2026, 08:11 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 27, 2026

Reports of latency, slowness, and timeouts for some customers

Detected by Pingoru
May 27, 2026, 04:05 PM UTC
Resolved
May 28, 2026, 10:57 PM UTC
Duration
1d 6h
Affected: AWS CA
Timeline · 3 updates
  1. investigating May 27, 2026, 04:05 PM UTC

    We are currently investigating this issue.

  2. monitoring May 27, 2026, 07:03 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 28, 2026, 10:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 7, 2026

Intermittent Latency Impacting Performance

Detected by Pingoru
May 07, 2026, 06:02 PM UTC
Resolved
May 07, 2026, 11:21 PM UTC
Duration
5h 19m
Affected: AWS CA
Timeline · 2 updates
  1. monitoring May 07, 2026, 06:02 PM UTC

    A fix has been implemented and we're monitoring the results.

  2. resolved May 07, 2026, 11:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 6, 2026

Ongoing Incident: System Performance / Version Mismatch

Detected by Pingoru
May 06, 2026, 11:25 PM UTC
Resolved
May 07, 2026, 05:59 PM UTC
Duration
18h 33m
Affected: AWS CA
Timeline · 6 updates
  1. identified May 06, 2026, 11:25 PM UTC

    The issue has been identified and a fix is being implemented.

  2. identified May 06, 2026, 11:26 PM UTC

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

  3. monitoring May 06, 2026, 11:32 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring May 07, 2026, 03:00 PM UTC

    We are continuing to monitor for any further issues.

  5. monitoring May 07, 2026, 05:58 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved May 07, 2026, 05:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 8, 2026

Reports of 503 Error - The Service is Unavailable

Detected by Pingoru
Apr 08, 2026, 02:48 PM UTC
Resolved
Apr 08, 2026, 09:25 PM UTC
Duration
6h 36m
Affected: AWS CA
Timeline · 3 updates
  1. investigating Apr 08, 2026, 02:48 PM UTC

    We are currently investigating this issue.

  2. monitoring Apr 08, 2026, 03:02 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 08, 2026, 09:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 23, 2026

Aeries Communications SSO

Detected by Pingoru
Feb 23, 2026, 06:48 PM UTC
Resolved
Feb 24, 2026, 04:45 PM UTC
Duration
21h 56m
Affected: AWS CA
Timeline · 3 updates
  1. investigating Feb 23, 2026, 06:48 PM UTC

    Customers are reporting an error during SSO login to Aeries Communications. The previous incident for this issue was closed prematurely, and we are actively continuing the investigation.

  2. monitoring Feb 24, 2026, 09:14 AM UTC

    Issue remedied on affected servers. SSO function for those affected is being monitored

  3. resolved Feb 24, 2026, 04:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 28, 2026

Reports of Error Message and Unable to login

Detected by Pingoru
Jan 28, 2026, 07:55 PM UTC
Resolved
Jan 28, 2026, 08:24 PM UTC
Duration
28m
Affected: AWS CA
Timeline · 2 updates
  1. investigating Jan 28, 2026, 07:55 PM UTC

    We are currently investigating this issue.

  2. resolved Jan 28, 2026, 08:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 13, 2026

Reports of latency and slowness for some customers

Detected by Pingoru
Jan 13, 2026, 08:36 PM UTC
Resolved
Jan 14, 2026, 04:03 PM UTC
Duration
19h 26m
Affected: AWS CA
Timeline · 3 updates
  1. identified Jan 13, 2026, 08:36 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Jan 14, 2026, 12:25 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 14, 2026, 04:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 7, 2025

Reports of latency and slowness

Detected by Pingoru
Nov 07, 2025, 04:48 PM UTC
Resolved
Nov 07, 2025, 05:45 PM UTC
Duration
57m
Affected: AWS CA
Timeline · 3 updates
  1. investigating Nov 07, 2025, 04:48 PM UTC

    We are currently investigating this issue.

  2. identified Nov 07, 2025, 04:55 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Nov 07, 2025, 05:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 6, 2025

Aeries Communication SSO

Detected by Pingoru
Nov 06, 2025, 10:02 PM UTC
Resolved
Nov 06, 2025, 11:46 PM UTC
Duration
1h 44m
Affected: Aeries Software Issues
Timeline · 3 updates
  1. investigating Nov 06, 2025, 10:02 PM UTC

    We have received reports and are investigating login issues to ParentSquare for Aeries Communications customers. Please stand by for further updates.

  2. monitoring Nov 06, 2025, 11:36 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Nov 06, 2025, 11:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 21, 2025

Reports of intermittent 500 Error

Detected by Pingoru
Oct 21, 2025, 02:57 PM UTC
Resolved
Oct 21, 2025, 03:50 PM UTC
Duration
52m
Affected: AWS CA
Timeline · 4 updates
  1. investigating Oct 21, 2025, 02:57 PM UTC

    We are currently investigating this issue.

  2. identified Oct 21, 2025, 03:34 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Oct 21, 2025, 03:43 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 21, 2025, 03:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 9, 2025

Connection errors

Detected by Pingoru
Oct 09, 2025, 05:29 PM UTC
Resolved
Oct 09, 2025, 09:04 PM UTC
Duration
3h 35m
Affected: AWS CA
Timeline · 3 updates
  1. investigating Oct 09, 2025, 05:29 PM UTC

    We are currently investigating this issue.

  2. monitoring Oct 09, 2025, 05:46 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Oct 09, 2025, 09:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 2, 2025

Reports of intermittent 503 error

Detected by Pingoru
Oct 02, 2025, 02:52 PM UTC
Resolved
Oct 02, 2025, 03:26 PM UTC
Duration
33m
Affected: AWS CA
Timeline · 2 updates
  1. investigating Oct 02, 2025, 02:52 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 02, 2025, 03:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 1, 2025

Runtime Error - TX API

Detected by Pingoru
Oct 01, 2025, 03:29 PM UTC
Resolved
Oct 01, 2025, 04:54 PM UTC
Duration
1h 25m
Affected: AWS TX
Timeline · 3 updates
  1. identified Oct 01, 2025, 03:29 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Oct 01, 2025, 04:01 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Oct 01, 2025, 04:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 11, 2025

503 Error - The Service is Unavailable

Detected by Pingoru
Sep 11, 2025, 02:23 PM UTC
Resolved
Sep 11, 2025, 04:14 PM UTC
Duration
1h 50m
Affected: AWS CA
Timeline · 3 updates
  1. investigating Sep 11, 2025, 02:23 PM UTC

    We are actively investigating this issue.

  2. identified Sep 11, 2025, 03:09 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Sep 11, 2025, 04:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 27, 2025

Degraded Performance

Detected by Pingoru
May 27, 2025, 04:45 PM UTC
Resolved
May 28, 2025, 02:48 PM UTC
Duration
22h 2m
Affected: AWS CA
Timeline · 4 updates
  1. investigating May 27, 2025, 04:45 PM UTC

    We are currently experiencing degraded performance. Our engineers are currently investigating.

  2. identified May 27, 2025, 05:35 PM UTC

    The issue has been identified and will be addressed during a maintenance window tonight. Performance has improved and is expected to remain operational for the rest of the business day.

  3. identified May 27, 2025, 07:51 PM UTC

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

  4. resolved May 28, 2025, 02:48 PM UTC

    This incident has been resolved.

Read the full incident report →