Is LMS365 down?
Last checked 7m agoNo incidents right now.
LMS365 is operational right now. Last checked 7m ago; the most recent incident resolved 4d ago.
Real-time LMS365 status, recent outages, and incident history — pulled directly from LMS365's official status page at https://status.lms365.com every 5 minutes. Pingoru tracks 16 LMS365 services and has captured 6 incidents in the last 90 days (100.00% uptime). Get email, Slack, Discord, or webhook alerts the moment LMS365 reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Learn365 North EuropeLearn365 United StatesLearn365 JapanLearn365 AustraliaLearn365 CanadaLearn365 United KingdomLearn365 GermanyLearn365 SwitzerlandLearn365 Government Community CloudLearn365 Government Community Cloud High
Timeline · 2 updates
- identified · Sep 04, 2026, 03:49 PM UTC
We are currently experiencing an issue with course completions, mostly regarding courses with SCORM packages, where the package/course will be completed, but the course will remain as In-Progress with a 100% completion percentage. The issue has been identified and a hotfix will be released.
- resolved · Sep 14, 2026, 09:46 PM UTC
A fix has been successfully deployed to address the issue affecting SCORM course completions. Following the deployment, SCORM completion behavior has been restored to its expected state, and courses should now correctly reflect the learner’s completion status instead of remaining In Progress after successful completion. The issue is considered resolved, and SCORM course completion should now function as expected across the affected environments.
Latest: A fix has been successfully deployed to address the issue affecting SCORM course completions. Following the deployment, SCORM completion behavior has been restored to its expected …
-
- Perform & Engage 365 Application
Timeline · 2 updates
- identified · Aug 10, 2026, 11:23 AM UTC
We have identified an issue affecting email notifications for customers using the legacy Perform & Engage (Weekly10) notification configuration. Our investigation found that Amazon Web Services (AWS), which supports this legacy email infrastructure, flagged an issue with the associated account and temporarily paused email sending from this service. As a result, some notification emails sent through the legacy configuration may not be delivered. Customers using the default notification sender ([email protected]) are not affected. As a mitigation, we are proactively migrating affected organizations from the legacy configuration to the default notification sender and notifying impacted administrators of the sender address change. Our teams are actively working to complete these migrations and minimize further impact. We will provide further updates as needed.
- resolved · Aug 11, 2026, 01:43 PM UTC
All affected customers have now been successfully migrated to Azure Communication Services and have been informed of the change. Email notification delivery has been restored for the impacted organizations, and no further action is required from customers. If you have any questions or experience any further issues, you can always create a support ticket through our Help Center.
Latest: All affected customers have now been successfully migrated to Azure Communication Services and have been informed of the change. Email notification delivery has been restored for t…
-
- Started Sep 10, 2026, 03:49 PM UTC · Resolved Sep 11, 2026, 09:46 PM UTC · 1d 5h
- Started Aug 10, 2026, 11:23 AM UTC · Resolved Aug 10, 2026, 05:45 PM UTC · 6h 22m