Started: May 3, 8:11 AM
monitoring
A fix has been implemented, and we are monitoring the results.
May 7, 6:07 AM
monitoring
A fix has been implemented, and we are monitoring the results.
May 6, 2:54 PM
investigating
We are continuing to investigate intermittent issues in the landscape.
May 6, 2:12 PM
monitoring
A fix has been implemented, and we are monitoring the results.
May 5, 5:24 PM
monitoring
We are still observing issues on the landscape with Workflows. Our team is actively working on a resolution and will provide further updates as progress is made.
May 5, 4:08 PM
monitoring
We are still observing issues on the landscape with Workflows. Our team is actively working on a resolution and will provide further updates as progress is made.
May 5, 12:50 PM
monitoring
We are actively monitoring the situation and will keep you informed of any further developments. Thank you
May 5, 10:32 AM
monitoring
We are actively monitoring the behaviour and will share further updates as needed. Thank you.
May 5, 8:37 AM
monitoring
we are in the process of rolling out the same changes across the remaining servers. We are actively monitoring the behaviour and will share further updates as needed. Thank you.
May 5, 6:35 AM
monitoring
A fix has been implemented, and the same changes are currently being applied to the remaining servers as well. We are monitoring the results closely and will keep you updated. Thank you.
May 5, 4:44 AM
monitoring
A fix has been implemented and we are monitoring the results.
May 4, 8:03 PM
investigating
We are continuing to investigate intermittent errors in the landscape.
May 4, 6:55 PM
investigating
We are still observing issues on the landscape (such as intermittent 500 errors and other errors when trying to log in). Our team is actively working on a resolution and will provide further updates as progress is made.
May 4, 5:47 PM
investigating
We are still observing issues on the landscape (such as intermittent 500 errors and other errors when trying to log in). Our team is actively working on a resolution and will provide further updates as progress is made.
May 4, 4:38 PM
investigating
We are still observing issues on the landscape (such as intermittent 500 errors and other errors when trying to log in). Our team is actively working on a resolution and will provide further updates as progress is made.
May 4, 3:26 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 4, 2:02 PM
identified
We have identified the issue, and traffic has been redirected to a healthy load balancer to restore access to NVF PRD tenants. Customers are now able to log in successfully. Our team is actively working on a permanent resolution. We are currently performing testing, and while some minor delays are expected, we will continue to provide further updates as progress is made.
May 4, 11:15 AM
identified
Traffic has been redirected to a healthy load balancer, and NVF PRD tenant access is restored. Customers can now log in. A permanent fix is in progress.
May 4, 11:00 AM
identified
We have identified the issue and traffic has been redirected to a healthy load balancer to restore access to NVF PRD tenants.
Customers are now able to login.
Our team is actively working on a permanent resolution and will provide further updates as progress is made.
May 4, 8:26 AM
identified
The issue has been identified, and we are currently working on fixing it. We will update you once we have further progress.
May 4, 6:02 AM
investigating
We are continuing to work on the issue and are actively making progress towards resolving it. We will share further updates as soon as we have more information.
May 4, 5:20 AM
investigating
We are still actively working on the issue and continuing our investigation to resolve it at the earliest. We will keep you updated with any progress.
May 4, 3:31 AM
investigating
We have identified the problematic server, and traffic has been redirected to a healthy load balancer to restore access to NVF PRD tenants.
Customers are now able to log in; however, they may experience some performance degradation and Adminui issues.
Our team is actively working on a permanent resolution and will provide further updates as progress is made.
May 3, 1:30 PM
investigating
We have identified the problematic server, and traffic has been redirected to a healthy load balancer to restore access to NVF PRD tenants.
Customers are now able to log in; however, they may experience some performance degradation.
Our team is actively working on a permanent resolution and will provide further updates as progress is made.
May 3, 10:31 AM
investigating
We have identified the problematic server, and traffic has been redirected to a healthy load balancer to restore access to NVF PRD tenants.
Customers are now able to log in; however, they may experience some performance degradation.
Our team is actively working on a permanent resolution and will provide further updates as progress is made.
May 3, 8:11 AM
investigating
Some customers may continue to experience errors or difficulty accessing NVF PRD tenants due to ongoing post-deployment technical issues.
Our team is actively working on the issue, and there is no change in status at this time.
We will provide further updates as soon as more information becomes available. We appreciate your patience.
May 3, 5:51 AM
investigating
Some customers may currently be experiencing errors or be unable to access NVF PRD tenants due to post-deployment technical issues.
Our team is actively working to resolve the issue, and we will provide further updates shortly.
We appreciate your patience and apologize for any inconvenience.
May 3, 3:35 AM
investigating
Some customers may currently be experiencing errors or unable to access NVF PRD tenants due to ongoing maintenance for the Ivanti Neurons for ITSM 2026.1 DROP#2 and Patch#5 Upgrade. Our team is actively working to complete this process, and we will provide further updates shortly. We appreciate your patience and apologize for any inconvenience.
May 2, 6:53 PM