Aptem Outage History

We've identified the cause of the performance issue and are rolling it out across the platform. Performance has been restored for some customers, and we're continuing to apply the fix to the remaining servers. As part of this, the Checkpoint module has been temporarily disabled. We'll post another update as more customers are restored.

We've identified the cause of the performance issue and are rolling out a fix across the platform. Performance has already improved for some customers, and we're continuing to apply the fix to the remaining servers. As part of this, checkpoint has been temporarily disabled. We'll post another update as performance is restored for more customers.

Our email provider has confirmed this is part of a wider, global issue affecting Microsoft's mail servers, not something specific to Aptem, and Microsoft are actively working to resolve it on their end. We're monitoring the situation closely and will post further updates here as soon as we have more information.

We have identified the cause of the issue and are working to resolve it

We're aware that some customers are unable to retrieve Microsoft Teams meeting transcripts within Aptem. This follows a recent change by Microsoft to tenant-level admin controls for transcript access. Affected customers' Microsoft 365 administrators can resolve this by updating a setting in their Teams admin centre; full guidance is available https://support.aptem.co.uk/hc/en-gb/articles/37763090942482-Enabling-Microsoft-Graph-access-to-Teams-meeting-transcripts on our Help Centre. Once this change has been made, the service will return to normal.

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

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

The issue has been identified. The resolution may cause a brief interruption in availability - up to 5 minutes. This will not impact all customers.

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

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

We are continuing to experience a high level of errors with the Century integration, resulting in degraded functionality. Our team has actively engaged with Century, who have identified the cause and we are currently awaiting an update from their team. We will provide further updates as soon as more information becomes available.

We have identified the issue. It primarily affects emails sent to Microsoft, and we are working on a solution. We will provide further updates as soon as more information becomes available.

We are still experiencing ongoing email deliverability issues when sending messages to Microsoft consumer email domains, including outlook.com, @hotmail.com, and @live.com. Emails to these domains from Aptem may be delayed or not delivered. We are actively working with our email service provider and Microsoft to investigate and resolve the issue as quickly as possible. We will provide further updates as soon as more information becomes available.

The cause of the issue affecting Marking Aid has been identified. We are continuing to work with the provider to implement a fix. Some users may still experience issues when editing or configuring new learning plans, while existing learning plans continue to operate as expected.

Our teams have confirmed the cause of the issue and a fix has been implemented and is currently being tested. Once testing is complete, we will deploy the fix to resolve the issue.

We have completed testing and confirmed that the fix resolves the issue. Our third-party provider has begun the deployment process. We will provide confirmation once full functionality has been restored.

Aptem have identified a technical issue with one of our 3rd-party Cloud providers. We're in currently in communication with the supplier to understand the impact and resolution timelines. Users will continue to be unable to load pages or access the Aptem Assess product while this issue persists. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

We are currently experiencing an issue where the 2024/25 ILR schema is no longer available when attempting to export ILR batches. As a result, batch exports using this schema are not possible at the moment. Our team is investigating and working on a resolution. We will provide an update as soon as a fix is in place.

We've identified an issue affecting the ILR 24/25 schema export functionality, currently preventing essential batch file generation. We understand this is critical for your operations and apologise for the disruption. We're aware that July 31st is a crucial date for many year-end activities, and to avoid further disruption, we have opted to implement the fix overnight. Full functionality will be restored by tomorrow morning, Friday, August 1st. We will post an update once the fix is confirmed live. Thank you for your patience.

Integration with BKSB is working fine except for the automatic redirect to the BKSB tests. We are currently waiting for a resolution from our partner BKSB.

Our partner BKSB are continuing to work on providing a resolution.

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

We've completed an interim fix which means customers can now run the ILR Batch Export successfully. However, there is still an issue with the performance meaning the export will take approximately 3 times as long to run. We will be releasing a hotfix tomorrow night (16th April) in the Maintenance Window to resolve this performance issue.

The fix has now been tested and is ready to be deployed as planned in tonight's maintenance window.

We are in the process of rolling out a resolution which will re-delete previously deleted Aims. Our expectation is the majority of customers will have this issue resolved by 18:00 Friday April 11th. Customers are still advised to avoid making changes to ILRs until this situation is resolved. Please raise a support ticket if you have any questions.

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

A fix was deployed which rectified issues for some users, however further validation this morning has identified a secondary problem affecting a subset of users. Aptem are actively investigating this issue now.