ESET Outage History

A planned maintenance window affected three ESET services: ESET MSP Administrator, ESET PROTECT Hub, and ESET Business Account. The maintenance ran from 6:00 PM UTC to 9:00 PM UTC (UTC), lasting about 3 hours, during which these components were listed as maintenance on the ESET status page. Users may have experienced limited access to management and provisioning features during the window. The incident involved 3 components and was global in scope for the listed services. The provider posted two official updates during the window, noting progress and the eventual return to normal as maintenance completed.

The ESET PROTECT login experience was affected when some customers encountered a 502 Bad Gateway error while logging into the ESET PROTECT console. The issue impacted multiple regional deployments including Japan, Canada, Germany, Americas & Oceania, and Europe, Africa & Asia Pacific. The outage began at 9:25 AM UTC and was resolved by 10:05 AM UTC, lasting about 40 minutes. The ESET status page indicated an ongoing investigation and listed login service degradation, with two official updates during the incident. By 10:05 AM UTC all regions had returned to normal and users could access the console again. User reports during the window corroborated login issues.

The maintenance window began on 8:00 AM UTC and was resolved by 10:00 AM UTC. The ESET Threat Intelligence component underwent scheduled maintenance during this period, resulting in a brief interruption for users. The service was fully restored by the end of the window. ESET issued two status updates during the incident (start and end). The affected component was ESET Threat Intelligence.

The ESET MSP Administrator underwent a planned maintenance window from 8:05 AM UTC to 9:01 AM UTC, lasting about 56 minutes. During this period, the ESET MSP Administrator component was listed as undergoing maintenance on the status page, with updates provided, and the component returned to up status when the window concluded. The maintenance affected only the ESET MSP Administrator service, and two status updates documented the maintenance progression and completion.

ESET carried out a planned maintenance window affecting a broad set of cloud services, including ESET Inspect, ESET PROTECT, ESET Cloud Office Security for Microsoft 365 and Google Workspace, ESET Connect, ESET Secure Authentication, and related offerings. The maintenance was scheduled in advance and updates were provided during the window, with two status updates issued as it progressed. Users may have experienced temporary service adjustments while the changes were applied, but no extended outages were reported. The maintenance affected multiple components across regions, including Europe, the Americas and Asia Pacific deployments. The maintenance began at 7:00 AM UTC and concluded at 8:00 AM UTC.

The ESET PROTECT Web Console became unreachable, with some login attempts returning Error 503 - Service Unavailable. The outage affected regions including Europe, Africa, Asia Pacific; Americas and Oceania; Japan; Canada; and Germany, hindering administration for many users. The outage began on 1:10 PM UTC and was resolved by 3:05 AM UTC, lasting about 37 hours and 55 minutes.

Status updates: The provider issued two official updates during the incident, including the initial notice that the Web Console was unreachable and a later resolution indicating services were restored across the listed regions. The restoration was supported by the provider's cloud services partner working to restore the services.

ESET carried out scheduled maintenance affecting ESET Threat Intelligence TAXII.ESET.COM and ESET PROTECT Hub on 2025-07-01 UTC. The work began with the Threat Intelligence feed entering maintenance at 7:00 AM UTC, followed by the PROTECT Hub component starting maintenance at 8:00 AM UTC. The Threat Intelligence service remained in maintenance until 1:00 PM UTC, while PROTECT Hub returned to service earlier at 10:05 AM UTC. These windows reflect planned maintenance across both components, with services restored by the indicated times.

The provider published four official status updates during the maintenance window, documenting progress and restoration. For users, this was a scheduled activity rather than an unexpected outage, and services were brought back online as maintenance concluded.

An outage impacted ESET PROTECT outside the United States, starting at 6:55 AM UTC. Regions including Europe, Africa, Asia Pacific, Japan, and Canada experienced access issues, while the US location remained reachable. The outage left affected users unable to access or manage ESET PROTECT during the event.

Over roughly 36 minutes, ESET issued multiple status updates. By 7:25 AM UTC, restoration had begun in the EU and Japan regions, and by 7:31 AM UTC Germany and Canada were back online. A final note referenced local time as 09:24 CEST, indicating the EU region had restored. The incident ended with affected regions returning to normal operation.

Overall, the outage appeared regional rather than global, affecting multiple regions while the United States remained unaffected. The status page updates documented the progression from investigation to restoration.

ESET conducted a scheduled disaster recovery maintenance window for ESET Connect IDS in Canada. The work began at 7:00 AM UTC and was expected to last about 1 hour. Access to ESET Connect IDS services in Canada could be temporarily unavailable or degraded during this window.

The provider issued 2 status updates during the incident, and the maintenance concluded with services returning to normal by 8:00 AM UTC. The geographic impact was limited to the Canada region for ESET Connect IDS.

ESET carried out a planned maintenance window across multiple services and regions. ESET Connect was placed in maintenance for Europe, Africa, and Asia Pacific; Americas and Oceania; Japan; and Canada. ESET Threat Intelligence and ESET Secure Authentication also entered maintenance across several regions (Americas and Oceania; Germany; Canada). The window began at 5:00 AM UTC and ran until 2:00 PM UTC, during which affected components were briefly unavailable while updates were applied.

ESET posted 6 official updates detailing progress and restoration. By the end of the window, affected components were returned to normal operation. This was a scheduled operation and not an unexpected outage.