Webroot incident
Frankfurt EU18 was currently experiencing a degradation in service
Webroot experienced a minor incident on June 24, 2026 affecting Frankfurt EU18, lasting 18h 29m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 24, 2026, 03:38 PM UTC
Frankfurt EU18 is currently experiencing a degradation in service. Teams have identified that the farm is still experiencing slowness and are currently working to resolve the issue. We appreciate your patience. Updates for this issue will be sent every 2 hours or if there are significant updates, whichever comes first. Tracking Number: IM3950211
- investigating Jun 24, 2026, 05:38 PM UTC
Frankfurt EU18 is currently experiencing a degradation in service. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Updates for this issue will be sent every 2 hours or if there are significant updates, whichever comes first. Tracking Number: IM3950211
- investigating Jun 24, 2026, 07:42 PM UTC
Frankfurt EU18 is currently experiencing a degradation in service. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Updates for this issue will be sent every 2 hours or if there are significant updates, whichever comes first. Tracking Number: IM3950211
- investigating Jun 24, 2026, 09:43 PM UTC
Frankfurt EU18 is currently experiencing a degradation in service. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Updates for this issue will be sent every 4 hours or if there are significant updates, whichever comes first. Tracking Number: IM3950211
- investigating Jun 25, 2026, 01:43 AM UTC
Frankfurt EU18 is currently experiencing a degradation in service. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Updates for this issue will be sent every 4 hours or if there are significant updates, whichever comes first. Tracking Number: IM3950211
- investigating Jun 25, 2026, 05:43 AM UTC
Frankfurt EU18 is currently experiencing a degradation in service. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Updates for this issue will be sent every 2 hours or if there are significant updates, whichever comes first. Tracking Number: IM3950211
- investigating Jun 25, 2026, 07:43 AM UTC
Frankfurt EU18 is currently experiencing a degradation in service. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Updates for this issue will be sent every 2 hours or if there are significant updates, whichever comes first. Tracking Number: IM3950211
- resolved Jun 25, 2026, 10:07 AM UTC
Frankfurt EU18 was experiencing a degradation in service. The issue is now resolved. We appreciate your patience. Tracking Number: IM3950211
- postmortem Jun 25, 2026, 05:40 PM UTC
# Incident Report **Tracking number:** IM3950211 PM1011655 **Incident window:** June 24, 2026, from 07:00 GMT to 09:45 GMT, on June 25, 2026 **Services affected:** OpenText™ Enterprise Service Management **RCA target completion date:** July 10, 2026 **Overview** On June 24, 2026, at 09:51 GMT, Incident Management was engaged to investigate performance degradation in the EU18 environment. **Impact** Service performance was degraded. **Resolution** The investigation revealed that the recent release to our 26.2 version introduced a regression into the product related to the CMDB function. After investigating the issue, the related component was reverted to the 26.1 release while an updated hotfix is being created to address the issue in future deployments. This was completed and service was restored at 08:40 GMT. Full validation was complete by 09:55 GMT, ending the impact.