Live / Incidents / Limble
Limble: Errors accessing Limble for some users
Limble · limblecmms.comImpact: majorResolved2026-09-15 18:30 UTC
Public — what happened
Summary
Limble is now loading OK in Microsoft Edge. The Limble application is currently operational, and we’ve verified that the application is safe and secure.
At no time during this incident were Limble systems compromised. No customer data was accessed, exposed, altered or lost as a result of the incident. Limble was incorrectly marked as unsafe by some third-party security reputation services. We are continuing to work with those third party services to correct Limble's classification.
Some users on local networks implementing network-based security may still be experiencing issues. If possible, we recommend retrieving up-to-date web site classification data from your security vendor, or speci
Timeline
- Started — 2026-09-15 16:31 UTC
- Last update — 2026-09-15 18:30 UTC
- Resolved — 2026-09-16 15:50 UTC
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Limble against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Limble: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Limble report →