Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Linewize Outage History

Every past Linewize outage tracked by IsDown, with detection times, duration, and resolution details.

There were 64 Linewize outages since January 2023. The 14 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor March 12, 2026

March 2026: Linewize Filter Service Degradation

Detected Mar 12, 2026 1:44 AM EDT · Resolved Mar 12, 2026 2:12 AM EDT · Duration 28 minutes

Linewize Filter experienced degraded service in the Australian region for 28 minutes, impacting the ability to view parents, users and groups, run syncs, receive timely red flag alerts, and access Classwize logins. The affected components included School Manager and Classwize, with the engineering team working to restore normal service levels.

Minor March 11, 2026

March 2026: Mac Agent 3.7.3 Connectivity Issue and Temporary Workarounds

Detected Mar 11, 2026 11:23 AM EDT · Resolved Mar 16, 2026 2:00 AM EDT · Duration 5 days

Linewize's Mac Agent version 3.7.3 automatic update caused high memory usage and intermittent internet connectivity drops on certain Mac devices. The issue was specific to the auto-update process, while manual installations of the same version remained stable. The engineering team identified the root cause and deployed a hotfix, with temporary workarounds including full reinstallation of the agent or switching affected devices to DNS filtering mode.

Minor February 23, 2026

February 2026: Microsoft Edge Issue - Webpages not Loading Intermittently

Detected Feb 23, 2026 4:00 PM EST · Resolved Apr 14, 2026 8:30 AM EDT · Duration about 2 months

A Microsoft browser update caused Linewize's browser extension to fail starting automatically on some Windows devices using Microsoft Edge, resulting in webpages loading indefinitely or hanging during startup, particularly on lower-specification devices. The issue was identified as a conflict between Chromium engine changes and the extension's initialization process, which caused browser saturation and timeouts that prevented proper web filtering. Linewize's engineering team developed an architectural redesign of the extension startup process and deployed partial fixes while working toward a complete solution through quality assurance testing.