Logitech Outage History

Logitech is up right now

Pingoru has recorded 34 incidents for Logitech: 1 in the last 12 months and 0 in the last 90 days.

Source: status.logitech.com

34incidents recorded
1last 12 months
0last 90 days
4 daystypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Logitech in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 551 (0%)

Incidents, newest first

Notice January 8, 2026 Logitech Options+ and G HUB macOS Certificate Issue 3d 14h Logitech Options+, Logitech GHUB

Started Jan 08, 2026, 04:54 PM UTC· resolved Jan 12, 2026, 07:12 AM UTC

  1. investigating Jan 08, 2026, 04:54 PM UTC

    A new ‘patch’ installer for Logitech Options+ and G HUB is now available to fix an issue that caused the apps to stop working on macOS. To download and learn more, please see this page. https://support.logi.com/hc/articles/37493733117847

  2. resolved Jan 12, 2026, 07:12 AM UTC

    A new ‘patch’ installer for Logitech Options+ and G HUB is now available to fix an issue that caused the apps to stop working on macOS. To download and learn more, please see this page. https://support.logi.com/hc/articles/37493733117847

Read the full incident report →

Major December 17, 2024 Logitech Circle: Service Issue with Circle 1 Cameras 2d 6h Video Recording

Started Dec 17, 2024, 07:01 PM UTC· resolved Dec 20, 2024, 01:24 AM UTC

  1. identified Dec 17, 2024, 07:01 PM UTC

    We have identified an issue with Circle 1 cameras not being able to connect and are working on a fix.

  2. monitoring Dec 19, 2024, 07:45 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Dec 20, 2024, 01:24 AM UTC

    This incident has been resolved.

Read the full incident report →