Thought Industries had 36 outages in the last 2 years totaling 57h 4m of downtime — averaging 1.5 incidents per month.
There were 36 Thought Industries outages since June 11, 2024 totaling 57h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.
We have detected and are investigating a Cloudflare-related issue.
We are working with Cloudflare support to resolve this issue.
This incident has been resolved.
We’re aware of an issue that’s currently affecting access to the platform. Our Engineering team is reviewing the situation and working diligently to resolve it. Updates will be posted here as they become available.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating the issue
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
Incident has been resolved
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have detected and are investigating a SCORM issue in the EU region.
We are continuing to investigate the issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
There are still some SCORM issues in the EU region. Continuing to investigate.
This incident has been resolved.
We have detected and are investigating a Rustici SCORM issue in the US region.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and we are working on fixing it.
We are continuing to work on a fix for this issue. Also, apart from broken images, all other functionality is still working as expected.
We are continuing to work on a fix for this issue. Also, apart from broken images, all other functionality is still working as expected.
A fix has been implemented and we are monitoring the platform.
This incident has been resolved.
We are aware of an issue for learners viewing PDFs in the Thought Industries Platform and are working on a resolution.
We are continuing to investigate this issue.
This incident has been resolved.
Between 5:30 PM and 5:50 PM PST platform monitoring detected a third period of elevated 503 errors that self-resolved. We have deployed further changes to mitigate the issue and are monitoring the results.
Cloudflare is aware of, and investigating an issue which potentially impacts multiple customers. Some Thought Industries customers are impacted.
Cloudflare issues still persist. Cloudflare are continuing to investigate: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
Cloudlfare issues still persist. Cloudlfare has indentified the issue and a fix is being implemented. Cloudlfare are continuing working on restoring service for application services customers. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
A fix has been implemented by Cloudflare and they believe the incident to be resolved, however they are continuing to monitor. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
Cloudflare is reporting their services are now operating normally. We will continue to monitor for any further issues with the Thought Industries platform.
Cloudflare services are now operating normally and the impact to Thought Industries is resolved.
We’re aware of an issue that’s currently affecting parts of the platform. Our Engineering team is reviewing the situation and working diligently to resolve it. Updates will be posted here as they become available.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We’re aware of an issue that’s currently affecting parts of the platform. Our Engineering team is reviewing the situation and working diligently to resolve it. Updates will be posted here as they become available.
We are continuing to investigate this issue.
This incident has been resolved.
AWS global outage affecting multiple services since GMT 8AM this morning
AWS global outage affecting multiple services
AWS is reporting that the underlying cause has been resolved and all services are currently in the process of backfilling. Reporting remains impacted by the outage.
This incident has been resolved.
We are currently investigating this issue.
No specific cause, just intermittent slowness.
Platform is stable again. Continuing to monitor
Some parts of the site are still slow. Investigating.
Possible issue with caching, but mostly transient.
Platform is stable again. Continuing to monitor
This incident has been resolved.
A Cloudflare security rule enabled yesterday evening for blocking specific malicious activity incorrectly / intermittently blocked legitimate traffic - we’ve adjusted our security settings to resolve the issue.
Investigating high latency, and some scorm issues.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the situation.
This incident has been resolved.
Between 13:15 and 17:08 UTC on 2025-08-25, users of the TI platform experienced slower than normal response times due to an internal scaling issue. The component which controlled internal DNS resolution failed to scale under load, resulting in higher-than-expected response times at peak traffic. The infrastructure team identified the root cause and manually scaled the DNS resolvers, restoring response times to expected levels. An update will shortly be applied to enable auto-scaling for this internal component, ensuring that this issue does not re-occur. We apologize for the inconvenience and are committed to ensuring improved reliability going forward.
We are currently investigating a disruption to the Reporting service
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are actively investigating availability issues
We are continuing to investigate this issue.
We believe we have identified the root cause and are working on releasing a fix.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have detected an issue in course content and test behavior - a fix is being worked on and will be deployed shortly.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Between 10:00 AM and 4:30 PM PST an intermittent, internal DNS issue resulted in elevated error rates and increased load times across the platform - this issue has been resolved. We will be closely monitoring the platform to ensure no further functionality is affected.
Between 11:19 and 11:31 AM EDT we experienced intermittent service disruption. We are investigating the cause of the incident.
Between 6:02 and 6:12 AM EST an on-going external vulnerability scan / DDoS attack impacted the US platform and resulted in intermittent availability issues during the stated 10-minute window. The internal team and our automated infrastructure provided a quick resolution to this issue and infra team will continue to review and improve our systems to ensure service disruptions are minimized.
Due to an issue identified with a recent release, we had to revert a fix for metadata not reflecting in custom domain that caused issues with cross domain in SSO. This release caused login issues with a small subset of clients using Single Sign-On (SSO). Our team actively reverted and the issue is now resolved.