ESET Outage History

Starting at 1:18 PM UTC, users began experiencing intermittent connectivity to ESET LiveGrid servers, with security products reporting that the LiveGrid servers cannot be reached. This disruption affected LiveGrid checks and could delay threat intel updates for endpoints. The issue appeared to have broad reach, with reports continuing into the afternoon. The outage lasted about 2 hours and 32 minutes before resolution.

An outage affected ESET PROTECT consoles hosted in the EU cloud region, causing login failures due to a communication error. The incident began at Mar 4, 2026 8:15 AM UTC and disrupted authentication for EU-region users, with the affected component listed as ESET PROTECT / Europe, Africa, Asia Pacific. The outage was resolved by Mar 4, 2026 8:30 AM UTC.

An outage affected ESET PROTECT consoles hosted in the EU cloud region, causing login attempts to fail with a "Login failed: Communication error" message. The incident began at 8:06 AM UTC and was resolved by 8:10 AM UTC, lasting approximately 4 minutes. The ESET PROTECT / Europe, Africa, Asia Pacific component briefly showed degraded status before returning to normal. The provider issued two status updates during the incident describing the impact and the quick recovery.

The ESET MSP Administrator component underwent a scheduled maintenance window from 9:00 AM UTC to 10:00 AM UTC. During this period, access to the MSP console could be limited for some users, and a user reported issues shortly before maintenance began. The impact was confined to the ESET MSP Administrator component and did not indicate a broader service disruption. The provider posted two updates during the window: at the start of maintenance and at restoration.

ESET LiveGuard entered a planned maintenance window from 7:00 AM UTC to 3:00 PM UTC UTC. The status page shows LiveGuard moved to maintenance at 07:00 UTC and returned to up at 15:00 UTC, for an overall duration of approximately 8 hours. This was a scheduled maintenance event affecting the LiveGuard component.

ESET Inspect underwent a scheduled maintenance window across multiple regions. The maintenance affected four regional components: Europe, Africa, Asia Pacific; Americas, Oceania; Canada; and Japan. The maintenance began at Feb 26, 2026 8:05 AM UTC and concluded at Feb 26, 2026 4:00 PM UTC, during which access to ESET Inspect could be limited or degraded.

The status page published two updates during the window, and all regional components returned to normal by Feb 26, 2026 4:00 PM UTC. The total maintenance duration was approximately 7 hours and 55 minutes.

The ESET Threat Intelligence component underwent a planned maintenance window starting at 7:00 AM UTC and concluding at 9:00 AM UTC UTC. During this period the Threat Intelligence service was listed in maintenance, with access to related features potentially affected. The maintenance window lasted approximately 2 hours and the service returned to normal operation after the end time.

ESET Inspect components across Americas, Oceania, Europe, Africa, Asia Pacific, Canada, and Japan entered a scheduled maintenance window beginning at 8:00 AM UTC and completed at 4:01 PM UTC. The maintenance lasted approximately 8 hours and 1 minute and affected regional services during the window. The provider issued two status updates documenting the maintenance work and its completion.

On Feb 18, 2026 7:00 AM UTC a maintenance window began that affected cloud enrollment for ESET Connect and ESET PROTECT across multiple regions. By 10:25 AM UTC machines hosted in the cloud could not enroll in ESET PROTECT, blocking onboarding for customers in Canada, Germany, Europe, Africa, Asia Pacific, the Americas, Oceania, and Japan. The status page described a cloud enrollment issue causing degraded enrollment workflows during this period.

At 2:00 PM UTC a fix was deployed by ESET's development team and customers were asked to verify remediation. ESET Connect components (Americas, Oceania; Japan; Canada; Europe, Africa, Asia Pacific) moved to up by that time, while ESET PROTECT remained degraded and recovered later. By 4:25 PM UTC ESET PROTECT components were fully up across regions. The incident involved 9 affected components across ESET Connect and ESET PROTECT, and it spanned roughly 9 hours and 25 minutes. The service published four status updates during the incident.

ESET PROTECT users in Europe, Africa, and parts of Asia Pacific experienced errors when saving Syslog settings, causing partial configuration issues and degraded operation in those regions. ESET identified the problem and rolled out a fix gradually to affected instances across Europe, Africa, and Asia Pacific. The incident involved two official status updates from ESET during the remediation.