Incidentsby GlyphESET PROTECT: Agent replication may fail with 502 error
Oct 20, 09:13 UTCOct 20, 11:13 UTC
Duration
2h 1m
Impact
Major
Root cause
Not disclosed
ESET, 90 days
12 incidents
Affected
Europe, Africa, Asia PacificAmericas, OceaniaJapanCanadaGermanyESET PROTECT - Europe, Africa, Asia PacificESET PROTECT - Americas, OceaniaESET PROTECT - JapanESET PROTECT - CanadaESET PROTECT - Germany
Final update
This incident has been resolved.
Timeline
- Resolved · Oct 20, 11:13 UTC
This incident has been resolved.
- Monitoring · Oct 20, 09:49 UTC
A fix was deployed and we are monitoring the behavior.
- Investigating · Oct 20, 09:13 UTC
We are investigating reports of HTTP errors 502 received on Agent's attempt to connect to the ESET PROTECT servers. You may notice that the Last connected time is not current.
More from ESET
Full historyIntermittent Microsoft Entra ID SSO Login Issues – ESET PROTECTstill openESET PROTECT Hub outagelasted 18h 31mSome users may experience degraded ESET PROTECT web console performancelasted 26d 15hIssue with logging in to hybrid EBA/MSP accountlasted 41h 49mESET PROTECT's Integration with Microsoft services is not possible.lasted 6d 8hESET PROTECT | Slowdown in log processinglasted 2d 13h