Linewize Outage History

Linewize is up right now

Pingoru has recorded 2 incidents for Linewize: 2 in the last 12 months and 0 in the last 90 days.

Source: status.linewize.net

2incidents recorded
2last 12 months
0last 90 days
3 hourstypical duration
Incidents per month
012MayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%MayJunJulAugSepOctNov0%
Pingoru began tracking Linewize in May 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
May 202611 of 744 (0%)
June 202600 of 720 (0%)
July 202615 of 744 (1%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 66 (0%)

Incidents, newest first

Minor July 24, 2026 Group-Based Filtering for On-Premise Servers 4h 38m Linewize Filter, Linewize Filter (Linewize Filter — Australia), Linewize Filter (Linewize Filter — USA), Linewize Filter (Linewize Filter — New Zealand) and 1 more

Started Jul 24, 2026, 03:49 PM UTC· resolved Jul 24, 2026, 08:28 PM UTC

  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. 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.

  3. 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

Read the full incident report →

Minor May 5, 2026 Issue With Blocking Sites 35m Linewize Filter, Linewize Filter (Linewize Filter — USA), Linewize Filter (Linewize Filter — United Kingdom)

Started May 05, 2026, 01:23 PM UTC· resolved May 05, 2026, 01:59 PM UTC

  1. investigating May 05, 2026, 01:23 PM UTC

    We are currently experiencing an issue which is causing over blocking on some websites that should be allowed. Our engineering team is currently looking at the issue and any updates will be communicated through this page as soon as we have more information. Thank you for your patience as we work through this matter.

Read the full incident report →