Skip to content

Outage tracker

360Learning: incident history

The last 24 hours in detail, 360Learning's declared incident record, and our regional check results beside it.

← Back to 360Learning's check readings

We started checking 360Learning on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me when 360Learning reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is 360Learning's own statement from its status page, with our regional reading beside it.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what 360Learning's own status page declared. Below it, any public chatter we saw about 360Learning and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what 360Learning's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Unverified user reportsNo reports about 360Learning in the last 24 hours, which is not evidence that nothing is wrong.
360Learning's status pageNo incident declared in the last 24 hours.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is 360Learning's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention 360Learning next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

  • Confirmation probe07:52 UTC, Europe: our own first failed reading prompted an extra probe. Result: 360Learning answered normally.

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East100.00%433
US-West99.70%330
Europe99.67%304
Asia-Pacific100.00%183

Their declared record

360Learning's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

Delays in email notificationsMinor incident
Oct 7, 2026, 2:44 PM UTC to Oct 7, 2026, 9:12 PM UTC (6h 28m)resolved
their latest update (Oct 7, 2026, 9:12 PM UTC): This incident has been resolved.
AI features are downMinor incident
May 29, 2026, 3:30 PM UTC to May 29, 2026, 9:18 PM UTC (5h 48m)resolved
their latest update (May 29, 2026, 9:18 PM UTC): A fix has been applied successfully. The platform is now up and running. We maintain reinforced monitoring to accompany this return to normal.
Search Functionality Currently UnavailableMinor incident
Apr 27, 2026, 12:18 PM UTC to Apr 28, 2026, 6:49 AM UTC (18h 31m)resolved
their latest update (Apr 28, 2026, 6:49 AM UTC): The incident was resolved yesterday at 6pm.
Search Functionality Currently UnavailableMinor incident
Apr 13, 2026, 2:31 PM UTC to Apr 13, 2026, 4:18 PM UTC (1h 48m)resolved
their latest update (Apr 13, 2026, 4:18 PM UTC): We confirm that the issue is solved and our services are back to normal. We apologize for the inconvenience. If you are still experiencing any issues or have questions or concerns, please contact our support team on the webform on our help center at https://support.360learning.…
AI features downMinor incident
Jan 27, 2026, 11:22 AM UTC to Jan 27, 2026, 3:56 PM UTC (4h 34m)resolved
their latest update (Jan 27, 2026, 3:56 PM UTC): A fix has been applied successfully. AI features are now up and running. We maintain reinforced monitoring to accompany this return to normal.
Issues with AI featuresMinor incident
Dec 5, 2025, 3:25 PM UTC to Dec 8, 2025, 8:14 AM UTC (2d 16h)resolved
their latest update (Dec 8, 2025, 8:14 AM UTC): We confirm that the issue is solved and our services are back to normal. We apologize for the inconvenience. If you are still experiencing any issues or have questions or concerns, please contact our support team on the webform on our help center at https://support.360learning.co…
Issue with AI featuresMinor incident
Nov 13, 2025, 2:00 PM UTC to Nov 13, 2025, 5:18 PM UTC (3h 18m)resolved
their latest update (Nov 13, 2025, 5:18 PM UTC): We confirm that the issue is solved and our AI services are back to normal. We apologize for the inconvenience. If you are still experiencing any issues or have questions or concerns, please contact our support team on the webform on our help center at https://support.360learni…
CDN issueAll systems operational
Oct 29, 2025, 4:07 PM UTC to Oct 29, 2025, 4:17 PM UTC (10 min)resolved
their latest update (Oct 29, 2025, 4:17 PM UTC): The service has been reconfigured to avoid the CDN. The platform is now operational. We maintain reinforced monitoring to accompany this return to normal.
Platform unavailableMajor outage
Oct 22, 2025, 8:38 AM UTC to Oct 22, 2025, 2:33 PM UTC (5h 55m)resolved
their latest update (Oct 22, 2025, 2:33 PM UTC): This incident has been resolved, we apologize for the inconvenience it may have caused.
High latencies on some actionsMinor incident
Oct 9, 2025, 9:01 AM UTC to Oct 9, 2025, 2:24 PM UTC (5h 23m)resolved
their latest update (Oct 9, 2025, 2:24 PM UTC): This incident has now been resolved, we apologize for the inconvenience it caused.

Showing the 10 most recent of 50 incidents 360Learning has declared in the history we hold.

These entries are 360Learning's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

360Learning's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.