Incident Report: Temporary Inaccessibility of a Single Application Server Following EPP/EDR Upgrade

  • Print

Introduction

On 16 November 2026, one of the uKnowva application servers became temporarily inaccessible following an EPP/EDR package upgrade. The upgrade introduced firewall rule changes that blocked the web service traffic required by the application.

Our team investigated the issue, identified the cause, and restored application accessibility by removing the upgraded package and reverting the associated firewall rules. 

This article covers the incident, its impact, resolution, and preventive measures to avoid similar disruptions.

Incident Overview

On 16 November 2026, a scheduled EPP/EDR package upgrade on one of the application servers led to a temporary accessibility issue. The application instance hosted on that server became unavailable to users, while the server and its underlying services remained operational.

The disruption was limited to this single application instance. All other application servers and hosted instances continued functioning normally.

Incident details:

Particulars

Details

Incident Date

16 November 2026

Incident Started

6:09:10 PM

Incident Ended

7:16:28 PM

Affected Component

Single application server

Triggering Activity

EPP/EDR package upgrade

Primary Cause

Firewall rules blocking web service traffic

Incident Status

Resolved

Root Cause

The issue originated from an EPP/EDR package upgrade performed on one of the application servers.

Following the upgrade, the package introduced or modified certain firewall rules that blocked the web service traffic required by the application. Although the server itself remained accessible and its underlying services continued running, the firewall restrictions prevented users from accessing the application instance hosted on that server.

The investigation confirmed that the issue did not originate from server unavailability or stopped application services. Instead, the firewall rule changes introduced during the security package upgrade prevented the application from receiving the necessary web traffic.

Consequently, the affected application instance became temporarily inaccessible until the firewall restrictions were removed.

Investigation and Findings

After identifying the application accessibility issue at approximately 6:09:10 PM, our team began investigating the affected server to determine the reason behind the disruption.

The investigation focused on checking server availability, verifying the status of the underlying services, and examining the changes introduced during the recent EPP/EDR package upgrade.

The findings established the following:

  • Server Availability: The affected application server remained accessible throughout the incident.

  • Service Status: The underlying server services continued running and did not experience any reported interruption.

  • Firewall Configuration: Certain firewall rules introduced or modified following the EPP/EDR upgrade blocked the web service traffic required by the application.

  • Impact Scope: The accessibility issue affected only the application instance hosted on the upgraded server. Other application servers and instances remained operational.

These findings helped isolate the problem to the firewall configuration rather than the application services or overall server availability.

Resolution

Once our team identified the firewall rule changes as the cause of the issue, the following actions were taken to restore application accessibility:

1. Removed the Upgraded EPP/EDR Package: The recently upgraded package was removed from the affected application server to prevent the associated firewall restrictions from continuing to affect web service connectivity.

2. Reverted Firewall Rule Changes: The firewall rules introduced or modified during the package upgrade were reverted or removed.

3. Restored Web Service Traffic: The required web service traffic was unblocked, allowing the application server to receive the necessary requests.

4. Restored Application Accessibility: Following these changes, users could access the application instance hosted on the affected server again.

These actions resolved the connectivity issue and restored normal application accessibility.

Incident Timeline

The following timeline outlines the key events from the initial identification of the issue to its resolution.

Time

Activity

6:09:10 PM

Application accessibility issue identified on the affected application server.

During investigation

Server accessibility and running services verified. Firewall rules introduced following the EPP/EDR upgrade identified as the cause.

During resolution

Upgraded EPP/EDR package removed, associated firewall rules reverted or removed, and web service traffic unblocked.

7:16:28 PM

Incident resolved and application accessibility restored.

All timestamps are in the incident's recorded local time.

Impact Assessment

The incident had a limited impact on application availability because it affected only one application server and the application instance hosted on it.

During the incident period, users attempting to access the affected application instance experienced temporary inaccessibility. However, the issue did not affect the availability of other application servers or their hosted application instances.

The server itself remained operational, and its underlying services continued running. The disruption was specifically related to blocked web service traffic caused by the firewall rule changes.

The incident lasted from 6:09:10 PM to 7:16:28 PM, after which the affected application instance became accessible again.

Preventive Measures

To reduce the possibility of similar incidents during future security package upgrades, our team has identified the following preventive measures:

1. Controlled Validation of EPP/EDR Upgrades

EPP/EDR package upgrades will undergo validation in a controlled environment before deployment on production application servers, wherever feasible. This will help identify potential configuration changes or compatibility issues before they affect live application instances.

2. Firewall Rule Review

Firewall rule changes introduced during security package upgrades will be reviewed and validated to ensure they do not block essential application traffic or interfere with existing server configurations.

3. Post-Upgrade Application Checks

Post-upgrade checks will verify application accessibility, web service connectivity, and the functionality of underlying services. These checks will help identify connectivity issues immediately after an upgrade.

4. Monitoring of Production Upgrades

Upgrade activities performed on production application servers will be monitored to identify unexpected changes or service disruptions promptly. This will enable our team to investigate and address potential issues before they cause prolonged accessibility problems.

Conclusion

This incident highlights the importance of validating security upgrades and reviewing firewall configurations before deployment. 

Our team has implemented preventive measures, including controlled upgrades and post-upgrade checks, to maintain application availability and minimize similar disruptions in the future. 

If you have any questions or need additional support, feel free to contact us at This email address is being protected from spambots. You need JavaScript enabled to view it..

Was this Article helpful?