Linewize incident

Group-Based Filtering for On-Premise Servers

Minor Resolved View vendor source →

Linewize experienced a minor incident on July 24, 2026 affecting Linewize Filter and Smoothwall Filter (Australia) and 1 more component, lasting 4h 38m. The incident has been resolved; the full update timeline is below.

Started
Jul 24, 2026, 03:49 PM UTC
Resolved
Jul 24, 2026, 08:28 PM UTC
Duration
4h 38m
Detected by Pingoru
Jul 24, 2026, 03:49 PM UTC

Affected components

Linewize FilterSmoothwall Filter (Australia)Smoothwall Filter (New Zealand)Smoothwall Filter (United Kingdom)Edtech Insights (USA)

Update timeline

  1. investigating Jul 24, 2026, 03:49 PM UTC

    We are currently investigating an issue affecting Group-Based Filtering for customers behind an on-premise server. During this time, group-based policies may not be applied as expected. Our engineering team is actively working to identify the root cause and restore normal functionality as quickly as possible. We will provide additional updates as more information becomes available. We appreciate your patience and apologize for any inconvenience this may cause.

  2. investigating Jul 24, 2026, 03:49 PM UTC

    We are currently investigating an issue affecting Group-Based Filtering for customers behind an on-premise server. During this time, group-based policies may not be applied as expected. Our engineering team is actively working to identify the root cause and restore normal functionality as quickly as possible. We will provide additional updates as more information becomes available. We appreciate your patience and apologize for any inconvenience this may cause.

  3. identified Jul 24, 2026, 08:00 PM UTC

    Our engineering team has identified the root cause of the issue affecting Group-Based Filtering for customers filtering through an on-premise server. A fix has been developed and is currently being implemented. While the work is still in progress and the issue has not yet been fully resolved, we expect Group-Based Filtering functionality to be fully restored within the next few hours. We will provide another update once the implementation is complete. Thank you for your patience as we work to restore full service.

  4. identified Jul 24, 2026, 08:00 PM UTC

    Our engineering team has identified the root cause of the issue affecting Group-Based Filtering for customers filtering through an on-premise server. A fix has been developed and is currently being implemented. While the work is still in progress and the issue has not yet been fully resolved, we expect Group-Based Filtering functionality to be fully restored within the next few hours. We will provide another update once the implementation is complete. Thank you for your patience as we work to restore full service.

  5. resolved Jul 24, 2026, 08:28 PM UTC

    The issue affecting Group-Based Filtering for customers filtering through an on-premise server has now been resolved. Our engineering team has completed the implementation of the fix, and Group-Based Filtering functionality should now be operating normally. If you are still experiencing any issues, please contact our Support team so we can investigate your specific environment further. Thank you for your patience while we worked to restore full functionality. Back to current status SUBSCRIBE Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription