Learning Customers Intermittent 503 Error
- investigating
Learning is experiencing intermittent 503 errors. To resolve, refresh your browser.
- identified
The issue has been identified and a fix is being implemented.
70 recorded Lessonly incidents since July 2025, with official updates, affected components, duration and resolution information.
Learning is experiencing intermittent 503 errors. To resolve, refresh your browser.
The issue has been identified and a fix is being implemented.
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.
This incident has been resolved.
We are currently investigating this issue.
Incident set to "Identified" at 4:32 AM PDT Incident set to "Monitoring" at 4:48 AM PDT
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
We have identified the cause of the slowness some customers have experienced, including slow page loads, delays generating LiveDocs and workspaces, and timeouts when publishing content through the API. The cause is an abnormally high volume of automated requests to our Content Manager service. We have stopped the source of the traffic and added capacity to the affected service, and performance is improving but has not yet fully returned to normal. Our teams are continuing to work on the fix and monitor the environment.
We have mitigated the slowness and degraded performance that some customers experienced, including slow page loads, delays generating LiveDocs and workspaces, and timeouts when publishing content through the API. The system performance has returned to normal levels. We are continuing to monitor the environment closely, and our teams will conduct a full Root Cause Analysis (RCA) and implement additional safeguards to prevent a recurrence.
The slowness and degraded performance that some customers experienced beginning has been resolved. Affected areas included slow page loads, delays generating LiveDocs and workspaces, and timeouts when publishing content through the API. Performance returned to normal levels at approximately 8:30 AM PDT and have remained stable since. Our teams will conduct a full Root Cause Analysis (RCA). We apologize for the disruption.
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.
This incident has been resolved.
We are investigating an issue affecting Seismic Learning where some learners may be unable to access learning content and are encountering server error messages within the Learning experience.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
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.
This incident has been resolved.
The Support Portal is currently unavailable. Our vendor is actively working to resolve the issue. In the meantime, please open support tickets by emailing [email protected].
We are continuing to work on a fix for this issue.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
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.
Some customers are experiencing slowness while navigating pages within their tenants.
Slowness issues have been resolved. Some web instances experienced transient issues which have since recovered. Teams are working to identify the root cause.
This incident has been resolved.
We are currently investigating this issue.
Identified as an issue with our video playback provider, "Vimeo".
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
Additional regions have been added as being impacted in US East regions. Seismic engineering is investigating possible root cause at Microsoft Azure services.
We are continuing to investigate this issue.
Microsoft Azure is experiencing issues in US regions. Our teams are working on mitigation efforts and in contact with Microsoft.
Seismic has re-routed some traffic to other regions to mitigate impact and continues to be in contact with Microsoft support on resolution of this incident.
Azure acknowledged connectivity issues with their WestUS region. Our teams have re-routed some traffic from US West to East regions to mitigate impact.
Seismic is in contact with Microsoft Azure and they are urgently working on restoring services. We'll continue to post updates as we have them.
We are continuing to work on a fix for this issue.
This issue is the result of an upstream networking incident affecting our cloud infrastructure provider (Microsoft Azure). They are implementing mitigations, including removing affected network components from their rotation and rerouting traffic. Our team is actively monitoring the situation and continuing to evaluate options to reduce impact for our customers. Not all customers are affected; impact may vary depending on region and traffic routing. We will post further updates as more information becomes available. We apologize for any disruption and appreciate your patience.
Starting at approximately 7:44 AM PT (14:44 UTC) on July 23, 2026, some customers began experiencing intermittent connectivity issues, elevated latency, or difficulty accessing Seismic. This is affecting tenants hosted in our West region infrastructure, with some downstream impact possible for other regions depending on traffic routing, primarily in East US regions. The issue stems from an underlying Microsoft Azure infrastructure event impacting their West US region, where a subset of Seismic's infrastructure is hosted. Azure has identified a potential trigger and has actively redirected traffic to healthier infrastructure as part of their mitigation efforts. Our engineering team is actively monitoring the situation alongside Azure's mitigation efforts and assessing impact across affected tenants. We will continue to provide updates as new information becomes available. What you might experience: Slow page loads, timeout errors, or temporary inability to access Seismic or specific features, such as Liveinsights, Microapps, and External Service Connections.
Azure has redirected traffic away from the affected network paths and is testing further mitigations, though these haven't yet restored full service. Their engineering teams are continuing to investigate and are working through additional options to resolve the issue. We don't have an estimated resolution time yet, but we're monitoring closely and will update this page as soon as anything changes.
Our cloud infrastructure provider (Microsoft Azure) has identified a likely cause of the networking incident and is actively deploying mitigation actions. Azure expects to have more information on the effectiveness of these actions within approximately 30 minutes and is closely monitoring for service recovery as the fix rolls out.
Seismic is starting to see recovery from Azure's efforts. Features returning and tenant access is restored for some clients.
We are seeing progress on recovery across East and West region tenants. Our cloud infrastructure provider (Microsoft Azure) identified a recent change strongly correlated with the incident in their West US region and has been rolling it back. That rollback is progressing and telemetry is confirming steady recovery. On our side, traffic has returned and affected services, including Insights, Apps, LiveSocial, and Tiled, are loading and operating as expected again. Some users may still experience slower-than-normal load times as systems fully stabilize. We are continuing to monitor service health closely and will confirm once the incident is fully resolved. Thank you for your patience throughout this event.
We are continuing to see recovery across East and West region tenants. Our cloud infrastructure provider (Microsoft Azure) has completed the rollback of the change linked to the networking incident, and telemetry is showing continued signs of recovery. On our side, connectivity has been restored and affected services, including Insights, Apps, LiveSocial, and Tiled, are operating normally. Most customers should be observing recovery at this time, though some may still experience slower-than-normal load times as systems fully stabilize. We are actively validating full restoration before marking this incident resolved, and continue to monitor service health closely alongside Azure. We will post another update once we have confirmed complete recovery. Thank you for your patience.
Tiled Microapps and Service Platform have recovered.
This incident is now resolved. Our cloud infrastructure provider (Microsoft Azure) has completed the rollback and full mitigation of the networking incident, and has finished the follow-up work to make the fix durable. Connectivity has been fully restored across our East and West region tenants, and all affected services, including Insights, Apps, LiveSocial, and Tiled, are operating normally. Telemetry confirms recovery is stable. If you continue to experience any issues, please reach out to support. Thank you for your patience throughout this event, and we apologize for the disruption this caused.
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.
This incident has been resolved.
We are currently investigating this issue.
Team's have addressed issues with slow loading, errors, and memory issues. All the backed up processes have cleared. Root cause is being investigated.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
We are aware of an issue affecting icon display in some Seismic tenants, caused by a service disruption experienced today by our third-party feature management provider, LaunchDarkly. To fully restore missing icons, our team needs to restart a number of internal services over the next several hours. During this process, some customers may experience brief, intermittent service disruptions. We expect any individual disruption to be short-lived, and we are working to complete these restarts as quickly as possible while minimizing impact. We will post updates here as work progresses and confirm once the issue is fully resolved. We apologize for any inconvenience this may cause.
Icons, library, and content property issues are now resolved for some tenants as services are restarted and full access is restored. We are seeing resolution in the WEST0, WEST1, WEST2, and WEST3 regions.
Additional regions continue to recover, including EAST regions and Southwest.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our team has already resolved the issue.
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.
This incident has been resolved.