Etail Solutions experienced a minor incident on December 18, 2025 affecting EVP RDP Application, lasting 27d 22h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Dec 18, 2025, 04:04 PM UTC
We are currently experiencing issues with the DNS provider and can confirm in Down Detector that there is a spike in issues. We will monitor the status and update here. Users may experience intermittent issues connecting to the EVP RDP Gateway.
- identified Dec 18, 2025, 06:13 PM UTC
We have identified an issue with the Microsoft MFA Authentication system that is now requiring all users to authenticate with an MFA device associated with their account. Each user login will need to register an MFA device with their account so they are prompted for a second authentication method in Microsoft Authenticator. Please log a ticket in the Helpcenter at https://etailsolutionsllc.atlassian.net/servicedesk/customer/user/login?destination=portals for assistance in setting up MFA for your user accounts.
- monitoring Dec 18, 2025, 06:54 PM UTC
A fix has been implemented and we are monitoring the results. Please log a ticket in the Helpcenter at https://etailsolutionsllc.atlassian.net/servicedesk/customer/user/login?destination=portals for assistance in setting up MFA for your user accounts.
- monitoring Dec 18, 2025, 06:55 PM UTC
We are continuing to monitor for any further issues.
- monitoring Dec 18, 2025, 11:26 PM UTC
Action Required - All EVP users must setup and configure MFA to connect to the EVP remote desktop application if you have not done so already. Please log a User/Password ticket in the HelpCenter for assistance in setting up MFA for your user accounts.
- monitoring Dec 19, 2025, 03:59 PM UTC
All issues are resolved. MFA is now required for EVP RDP. Please log a ticket in the Helpcenter at https://etailsolutionsllc.atlassian.net/servicedesk/customer/user/login?destination=portals for assistance in setting up MFA for your user accounts.
- resolved Jan 15, 2026, 02:33 PM UTC
This incident has been resolved.