Aeries Software Outage History
Aeries Software is up right nowPingoru has recorded 51 incidents for Aeries Software: 34 in the last 12 months and 12 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 8 of 720 (1%) |
| May 2026 | 9 | 65 of 744 (9%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 1 | 16 of 744 (2%) |
| August 2026 | 9 | 28 of 744 (4%) |
| September 2026 | 2 | 133 of 720 (19%) |
| October 2026 | 2 | 0 of 744 (0%) |
| November 2026 | 1 | 48 of 119 (40%) |
Incidents, newest first
Minor November 3, 2026 Increased Latency for some Hosted Customers 1d 23h AWS CA
Started Nov 03, 2026, 06:42 PM UTC· resolved Nov 05, 2026, 06:17 PM UTC
- investigating Nov 03, 2026, 06:42 PM UTC
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.
- monitoring Nov 03, 2026, 09:24 PM UTC
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.
- monitoring Nov 04, 2026, 03:13 PM UTC
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.
- investigating Nov 04, 2026, 04:32 PM UTC
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.
- monitoring Nov 04, 2026, 08:03 PM UTC
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.
- resolved Nov 05, 2026, 06:17 PM UTC
This incident has been resolved.
Minor October 22, 2026 Intermittent 503 Errors –
Started Oct 22, 2026, 03:00 PM UTC· resolved Oct 22, 2026, 03:00 PM UTC
- resolved Oct 22, 2026, 03:00 PM UTC
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.
Notice October 22, 2026 502 Gateway Errors (Partial Outage) 40m
Started Oct 22, 2026, 12:00 AM UTC· resolved Oct 22, 2026, 12:40 AM UTC
- resolved Oct 22, 2026, 12:00 AM UTC
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.
Major September 16, 2026 Partial Outage 15h 35m Aeries Software Issues
Started Sep 16, 2026, 03:35 PM UTC· resolved Sep 17, 2026, 07:10 AM UTC
- investigating Sep 16, 2026, 03:35 PM UTC
We are currently experiencing a partial outage and are actively investigating the cause. We will have an update for you in 30 minutes.
- monitoring Sep 16, 2026, 03:47 PM UTC
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.
- monitoring Sep 16, 2026, 04:07 PM UTC
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.
- monitoring Sep 16, 2026, 05:29 PM UTC
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. What's still affected: Enroll Path: When your staff approve an enrollment application in Enroll Path, the system creates (or updates) that student's record in Aeries. That final step, importing the approved student into Aeries, is temporarily unavailable. Activity Hero: Temporarily you will not have access to enable a new Activity Hero Integration.
- resolved Sep 17, 2026, 07:10 AM UTC
This incident has been resolved.
- postmortem Sep 17, 2026, 07:33 PM UTC
# 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.
Major September 3, 2026 Intermittent 503 Errors Affecting Some Customers 4d 21h AWS CA
Started Sep 03, 2026, 04:03 PM UTC· resolved Sep 08, 2026, 01:44 PM UTC
- 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.
Minor August 28, 2026 Latency, Reports Not Running 21m AWS CA
Started Aug 28, 2026, 08:51 PM UTC· resolved Aug 28, 2026, 09:13 PM UTC
- investigating Aug 28, 2026, 08:51 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.
- investigating Aug 28, 2026, 09:05 PM UTC
We are continuing to investigate this issue.
- investigating Aug 28, 2026, 09:05 PM UTC
Resolved - The reporting queue has returned to normal levels and report processing is stable. The issue is now resolved.
- investigating Aug 28, 2026, 09:07 PM UTC
Resolved - The reporting queue has returned to normal levels and report processing is stable. The issue is now resolved.
- resolved Aug 28, 2026, 09:13 PM UTC
This incident has been resolved.
Minor August 21, 2026 Latency, Reports Not Running 4h 43m AWS CA
Started Aug 21, 2026, 07:44 PM UTC· resolved Aug 22, 2026, 12:28 AM UTC
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
Minor August 19, 2026 Graduation Status, Profile, and Student Search Bar Not Working 3h 22m AWS CA, AWS TX
Started Aug 19, 2026, 04:13 PM UTC· resolved Aug 19, 2026, 07:35 PM UTC
- 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.
- monitoring Aug 19, 2026, 04:44 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 19, 2026, 07:35 PM UTC
This incident has been resolved.
Minor August 14, 2026 API Service Degradation 2h 9m AWS CA
Started Aug 14, 2026, 06:18 PM UTC· resolved Aug 14, 2026, 08:27 PM UTC
- 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.
- 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
- 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 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.
- 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.
- 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.
Minor August 13, 2026 API Service Degradation 3h 38m AWS CA
Started Aug 13, 2026, 07:02 PM UTC· resolved Aug 13, 2026, 10:41 PM UTC
- identified Aug 13, 2026, 07:02 PM UTC
The issue has been identified and a fix is being implemented.
- investigating Aug 13, 2026, 07:03 PM UTC
We are currently investigating this issue.
- identified Aug 13, 2026, 07:33 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Aug 13, 2026, 10:41 PM UTC
This incident has been resolved.
Notice August 13, 2026 API Service Degradation –
Started Aug 13, 2026, 03:12 PM UTC· resolved Aug 13, 2026, 03:12 PM UTC
- resolved Aug 13, 2026, 03:12 PM UTC
We identified an issue affecting API sync processing for some customers. Additional resources have been allocated across our API infrastructure, and syncs are now processing successfully. Our team will continue monitoring system performance.
Minor August 12, 2026 Increased Latency for Some Hosted Customers 11h 9m AWS CA
Started Aug 12, 2026, 07:21 PM UTC· resolved Aug 13, 2026, 06:31 AM UTC
- 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.
- identified Aug 12, 2026, 11:24 PM UTC
A configuration deployed in error created a performance issue. The change is being reverted.
- monitoring Aug 13, 2026, 04:33 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 13, 2026, 06:31 AM UTC
This incident has been resolved.
Major August 7, 2026 Partial Service Disruption Affecting Hosted Aeries Access 1h 1m AWS CA
Started Aug 07, 2026, 03:16 PM UTC· resolved Aug 07, 2026, 04:18 PM UTC
- 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.
- monitoring Aug 07, 2026, 03:34 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 07, 2026, 04:18 PM UTC
This incident has been resolved.
Minor August 5, 2026 Delayed Reports and Version Mismatch 1h 5m AWS CA
Started Aug 05, 2026, 10:02 PM UTC· resolved Aug 05, 2026, 11:07 PM UTC
- identified Aug 05, 2026, 10:02 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Aug 05, 2026, 10:14 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 05, 2026, 11:07 PM UTC
This incident has been resolved.
Minor July 22, 2026 Reports of latency, version mismatch, and trouble printing reports for some customers 15h 56m AWS CA
Started Jul 22, 2026, 04:14 PM UTC· resolved Jul 23, 2026, 08:11 AM UTC
- investigating Jul 22, 2026, 04:14 PM UTC
We are currently investigating this issue.
- identified Jul 22, 2026, 04:17 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 22, 2026, 04:28 PM UTC
A fix has been implemented and we are monitoring the results.
- 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.
- identified Jul 22, 2026, 09:57 PM UTC
The changes are still being tested. They are currently scheduled to be released and deployed tonight.
- monitoring Jul 23, 2026, 01:16 AM UTC
A release has been scheduled for deployment to address the performance issues with reporting services.
- resolved Jul 23, 2026, 08:11 AM UTC
This incident has been resolved.
Minor May 27, 2026 Reports of latency, slowness, and timeouts for some customers 1d 6h AWS CA
Started May 27, 2026, 04:05 PM UTC· resolved May 28, 2026, 10:57 PM UTC
- investigating May 27, 2026, 04:05 PM UTC
We are currently investigating this issue.
- monitoring May 27, 2026, 07:03 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 28, 2026, 10:57 PM UTC
This incident has been resolved.
Minor May 26, 2026 Reports of latency, version mismatch, and trouble printing reports for some customers 31m AWS CA
Started May 26, 2026, 10:36 PM UTC· resolved May 26, 2026, 11:07 PM UTC
- investigating May 26, 2026, 10:36 PM UTC
We are currently investigating this issue.
- resolved May 26, 2026, 11:07 PM UTC
This incident has been resolved.
Minor May 26, 2026 Reports of latency, slowness, and timeouts for some customers 3h 6m AWS CA
Started May 26, 2026, 06:23 PM UTC· resolved May 26, 2026, 09:30 PM UTC
- investigating May 26, 2026, 06:23 PM UTC
We are currently investigating this issue.
- investigating May 26, 2026, 09:29 PM UTC
We are continuing to investigate this issue.
- resolved May 26, 2026, 09:30 PM UTC
This incident has been resolved.
Minor May 22, 2026 Reports of latency, version mismatch, and trouble printing reports for some customers 16m AWS CA
Started May 22, 2026, 10:53 PM UTC· resolved May 22, 2026, 11:10 PM UTC
- investigating May 22, 2026, 10:53 PM UTC
We are currently investigating this issue.
- resolved May 22, 2026, 11:10 PM UTC
This incident has been resolved.
Minor May 19, 2026 Reports of latency, version mismatch, and trouble printing reports for some customers 28m AWS CA
Started May 19, 2026, 09:20 PM UTC· resolved May 19, 2026, 09:48 PM UTC
- investigating May 19, 2026, 09:20 PM UTC
We are currently investigating this issue.
- resolved May 19, 2026, 09:48 PM UTC
This incident has been resolved.
Minor May 18, 2026 Reports of latency, slowness, and timeouts for some customers 5h 55m AWS CA
Started May 18, 2026, 04:48 PM UTC· resolved May 18, 2026, 10:44 PM UTC
- investigating May 18, 2026, 04:48 PM UTC
We are currently investigating this issue.
- resolved May 18, 2026, 10:44 PM UTC
This incident has been resolved.
Notice May 8, 2026 Temporary Suspension of Canvas Integration 16h 28m Aeries Integrated Software
Started May 08, 2026, 01:32 AM UTC· resolved May 08, 2026, 06:00 PM UTC
- monitoring May 08, 2026, 01:32 AM UTC
In response to a recently reported security incident at Instructure (Canvas) Aeries has made the decision to temporarily disable the Canvas integration for all Aeries customers effective immediately. The action is purely precautionary in response to the incident at Canvas and is being taken to protect our shared student and staff data while we monitor the situation closely. What this means for you: - The Canvas integration will be temporarily unavailable. - All data within Aeries remains secure and fully accessible. - No action is required on your part at this time. We are actively monitoring the situation and coordinating with Instructure. We will restore the integration as soon as we are confident it is safe to do so, and we will provide an update by 10:00 AM pacific on Friday, May 8th, 2026. We understand this causes disruption to your workflows and apologize for the inconvenience. If you have any questions or concerns, please submit a ticket on support.aeries.com or call us at 888.324.5363. Thank you for your understanding and continued trust in Aeries.
- resolved May 08, 2026, 06:00 PM UTC
We are writing to follow up on yesterday’s important communications regarding the temporary suspension of your Canvas integration. While there is no evidence that Canvas API keys were compromised, we have taken the proactive step to generate new API keys for your Canvas integration. We have updated your Canvas Consumer ID and Secret Key. When you are ready, you can reconnect Canvas to Aeries by retrieving your new API key in the Aeries portal and updating your integration in the Canvas Portal. Their are support articles found on the email message sent to you that can assist with these steps. Reconnecting your Canvas integration is entirely at your discretion once you feel have received confirmation from Instructure that it is safe for your organization to proceed. If you have additional questions, you can submit a Support Ticket at support.aeries.com. Thank you for your patience and continued trust in Aeries. Sincerely, The Aeries Team
Minor May 7, 2026 Intermittent Latency Impacting Performance 5h 19m AWS CA
Started May 07, 2026, 06:02 PM UTC· resolved May 07, 2026, 11:21 PM UTC
- monitoring May 07, 2026, 06:02 PM UTC
A fix has been implemented and we're monitoring the results.
- resolved May 07, 2026, 11:21 PM UTC
This incident has been resolved.
Major May 6, 2026 Ongoing Incident: System Performance / Version Mismatch 18h 33m AWS CA
Started May 06, 2026, 11:25 PM UTC· resolved May 07, 2026, 05:59 PM UTC
- identified May 06, 2026, 11:25 PM UTC
The issue has been identified and a fix is being implemented.
- identified May 06, 2026, 11:26 PM UTC
We are continuing to work on a fix for this issue.
- monitoring May 06, 2026, 11:32 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring May 07, 2026, 03:00 PM UTC
We are continuing to monitor for any further issues.
- monitoring May 07, 2026, 05:58 PM UTC
We are continuing to monitor for any further issues.
- resolved May 07, 2026, 05:59 PM UTC
This incident has been resolved.
Minor April 20, 2026 Reports of latency, slowness, and timeouts for some customers 1h 9m AWS CA
Started Apr 20, 2026, 04:40 PM UTC· resolved Apr 20, 2026, 05:49 PM UTC
- identified Apr 20, 2026, 04:40 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Apr 20, 2026, 05:08 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 20, 2026, 05:49 PM UTC
This incident has been resolved.