- Detected by Pingoru
- Jul 23, 2026, 03:05 PM UTC
- Resolved
- Jul 24, 2026, 06:19 AM UTC
- Duration
- 15h 14m
Affected: ProvisioningService AutomationAccess Management
Timeline · 5 updates
-
investigating Jul 23, 2026, 03:05 PM UTC
We are currently experiencing an outage affecting the HelloID WUS login portals. We are investigating the root cause and will provide an update as soon as more information is available.
-
investigating Jul 23, 2026, 03:47 PM UTC
HelloID is currently affected by an issue in the Azure West US region that is impacting web applications. We are monitoring Azure’s status and will provide an update through this incident when new information is available.
-
investigating Jul 23, 2026, 04:07 PM UTC
Microsoft Azure has now also updated its status page regarding the ongoing issue. You can access the statuspage here: https://azure.status.microsoft/en-gb/status We are continuing to monitor the situation and will provide further updates as soon as more information becomes available.
-
monitoring Jul 23, 2026, 07:17 PM UTC
The HelloID portals are available again. We are continuing to monitor the service closely to ensure stability. Microsoft Azure has reported that a recent change was strongly correlated with the issue and that rollback actions are currently in progress. Azure telemetry is showing initial signs of recovery, and Microsoft is monitoring service health and traffic recovery.
-
resolved Jul 24, 2026, 06:19 AM UTC
The HelloID portals have been fully operational and stable for some time. No further impact has been observed, and this incident is now resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 14, 2026, 03:53 PM UTC
- Resolved
- Jul 15, 2026, 10:20 AM UTC
- Duration
- 18h 27m
Affected: Service AutomationService AutomationService Automation
Timeline · 3 updates
-
investigating Jul 14, 2026, 03:53 PM UTC
Newly created Automation Variables and recent updates to existing variable values are currently not being reflected. Existing Automation Variables remain available during script execution, but they continue to use their previous values instead of the updated ones. Scheduled Automation Tasks are not affected by this issue. Our team is actively investigating the root cause and working on a resolution. We will provide further updates as soon as more information becomes available.
-
monitoring Jul 14, 2026, 06:34 PM UTC
We have implemented a fix that resolves this issue. If you continue to experience problems with automation variables not reflecting newly created or updated values, please create a ticket through the TOPdesk selfservice portal. Our support team will investigate your situation and assist you as quickly as possible.
-
resolved Jul 15, 2026, 10:20 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2026, 06:53 AM UTC
- Resolved
- Jun 15, 2026, 07:18 AM UTC
- Duration
- 3d
Affected: Service AutomationService AutomationService AutomationAccess ManagementAccess ManagementAccess Management
Timeline · 5 updates
-
investigating Jun 12, 2026, 06:53 AM UTC
Some users have reported that they cannot access applications they should have access to. We are currently investigating the issue. We will share an update as soon as we have more information.
-
investigating Jun 12, 2026, 09:12 AM UTC
Our investigation has shown that these issues may also impact access to HelloID Service Automation products and delegated forms. Our teams are actively investigating the issue and working to resolve it as quickly as possible. We will continue to share updates through as new information becomes available.
-
identified Jun 12, 2026, 10:21 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 12, 2026, 01:53 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 15, 2026, 07:18 AM UTC
The issue has been resolved. Please note that it may be necessary to reassign the affected groups to ensure the credential sets are added correctly. If you continue to experience issues after reassigning the groups, please contact our support team: https://tools4ever-support.topdesk.net/ We apologize for any inconvenience caused.
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 02:24 PM UTC
- Resolved
- Jun 11, 2026, 01:28 PM UTC
- Duration
- 2d 23h
Affected: Access ManagementAccess Management
Timeline · 4 updates
-
investigating Jun 08, 2026, 02:24 PM UTC
SSO applications based on OpenID Connect are currently not working. The JWKS document returns the following error: “Something went wrong.” We are investigating the issue and will provide an update as soon as more information is available.
-
identified Jun 10, 2026, 07:14 AM UTC
The issue has been identified, and a fix is scheduled to be implemented. To apply this fix, downtime of the HelloID customer portal is required. During the implementation, HelloID will be temporarily unavailable. This downtime will not affect any scheduled processes or planned executions during this period. We will create a separate statuspage incident for this maintenance window, where all relevant updates and progress information will be communicated.
-
monitoring Jun 10, 2026, 08:24 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 11, 2026, 01:28 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 14, 2026, 01:51 PM UTC
- Resolved
- Apr 15, 2026, 01:57 PM UTC
- Duration
- 1d
Affected: Access Management
Timeline · 3 updates
-
identified Apr 14, 2026, 01:51 PM UTC
At this moment, we're experiencing issues with AD login to HelloID. We're investigating the issue.
-
monitoring Apr 14, 2026, 02:00 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 15, 2026, 01:57 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 14, 2026, 11:21 AM UTC
- Resolved
- Apr 15, 2026, 01:57 PM UTC
- Duration
- 1d 2h
Affected: Provisioning
Timeline · 4 updates
-
investigating Apr 14, 2026, 11:22 AM UTC
At this moment, we're currently experiencing an issue with processing an evaluation and/or enforcement. We're investigating the issue.
-
monitoring Apr 14, 2026, 12:55 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Apr 14, 2026, 12:56 PM UTC
We are continuing to monitor for any further issues.
-
resolved Apr 15, 2026, 01:57 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 14, 2026, 11:19 AM UTC
- Resolved
- Apr 16, 2026, 01:07 PM UTC
- Duration
- 2d 1h
Affected: ProvisioningProvisioning
Timeline · 5 updates
-
identified Apr 14, 2026, 11:19 AM UTC
At this moment, we're experiencing an issue with HelloID where you can ancounter the errormessage "'Enable-RemoteMailbox' is not recognized". We're investigating the issue
-
identified Apr 14, 2026, 11:22 AM UTC
We are continuing to work on a fix for this issue.
-
identified Apr 14, 2026, 12:55 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Apr 15, 2026, 01:53 PM UTC
A fix has been implemented within the newest HelloID agent version. Please make sure your HelloID agent is updated to the most recent version to ensure the fix is applied. We will continue to monitor the results.
-
resolved Apr 16, 2026, 01:07 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 02, 2026, 09:02 AM UTC
- Resolved
- Apr 02, 2026, 10:08 AM UTC
- Duration
- 1h 6m
Affected: ProvisioningProvisioning
Timeline · 2 updates
-
investigating Apr 02, 2026, 09:02 AM UTC
We are experiencing an issue where only a limited number of actions are started in HelloID through the on-premise agent, which may result in delays or timeouts. Our team is actively investigating the cause.
-
resolved Apr 02, 2026, 10:08 AM UTC
The issue has been resolved, we'll keep monitoring the situation.
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 12:55 PM UTC
- Resolved
- Mar 02, 2026, 01:30 PM UTC
- Duration
- 35m
Affected: Provisioning
Timeline · 2 updates
-
identified Mar 02, 2026, 12:55 PM UTC
At the moment, the Built-in Azure AD Actions cannot be executed. We are aware of the issue and are currently working on a hotfix to resolve it. We apologize for the inconvenience.
-
resolved Mar 02, 2026, 01:30 PM UTC
A hotfix has been implemented, and the actions should now be executed successfully again. We'll keep monitoring the situation.
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 11:05 AM UTC
- Resolved
- Feb 26, 2026, 02:14 PM UTC
- Duration
- 1d 3h
Affected: ProvisioningService AutomationAccess Management
Timeline · 2 updates
-
monitoring Feb 25, 2026, 11:05 AM UTC
We are currently experiencing issues with the delivery of emails to the domains @live.nl, @msn.com, @outlook.com, and @hotmail.com. To restore our email reputation, we have disabled email sending from training tenants. This is a preventive measure to ensure that emails to these domains can be delivered correctly again as soon as possible. For more information about the original incident, please refer to: https://helloid.statuspage.io/incidents/n6pl5ykzxv45 We will keep you informed of further developments via the status page.
-
resolved Feb 26, 2026, 02:14 PM UTC
After investigation, it has been determined that the issue is not related to HelloID, nor to the mail provider used by HelloID. As a result, the precautionary measure to disable the mail functionality in the training tenants is no longer necessary. The mail functionality has therefore been re-enabled in the training tenants.
Read the full incident report →
- Detected by Pingoru
- Feb 24, 2026, 09:06 AM UTC
- Resolved
- Feb 26, 2026, 01:32 PM UTC
- Duration
- 2d 4h
Affected: ProvisioningService AutomationAccess Management
Timeline · 3 updates
-
investigating Feb 24, 2026, 09:06 AM UTC
We’re currently experiencing issues with email delivery to the domains @live.nl, @msn.com, @outlook.com and @hotmail.com due to a problem at our mail provider. Emails that have already been sent are in a retry queue and will be delivered automatically once the issue has been resolved. Our mail provider is aware of the problem and is actively investigating it. We will provide an update as soon as more information becomes available.
-
monitoring Feb 26, 2026, 08:36 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 26, 2026, 01:32 PM UTC
After investigation, it has been determined that the issue is not related to HelloID, nor to the mail provider used by HelloID.
Read the full incident report →
- Detected by Pingoru
- Feb 21, 2026, 09:56 AM UTC
- Resolved
- Mar 25, 2026, 09:33 AM UTC
- Duration
- 31d 23h
Affected: ProvisioningProvisioningProvisioning
Timeline · 3 updates
-
identified Feb 21, 2026, 09:56 AM UTC
We are currently experiencing an issue where the HelloID on-premise agent may have lost its connection and did not automatically recover. You can resolve this by manually restarting the three HelloID services. For instructions, see: https://docs.helloid.com/en/agent/restart-an-agent.html We are actively working on a permanent solution for this connectivity issue. Our apologies for the inconvenience.
-
monitoring Feb 23, 2026, 10:21 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 25, 2026, 09:33 AM UTC
The issue has been resolved, we'll keep monitoring the situation.
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 09:04 AM UTC
- Resolved
- Feb 20, 2026, 03:11 PM UTC
- Duration
- 6h 7m
Affected: ProvisioningProvisioning
Timeline · 3 updates
-
investigating Feb 20, 2026, 09:04 AM UTC
We are experiencing an issue where only a limited number of actions are started in HelloID through the on-premise agent, which may result in delays or timeouts. Our team is actively investigating the cause.
-
monitoring Feb 20, 2026, 09:44 AM UTC
A fix has been implemented. In some cases, the connection to the HelloID on-premise agent may have been interrupted. The connection should restore automatically or can be re-established by restarting the HelloID services. We will continue to monitor the situation.
-
resolved Feb 20, 2026, 03:11 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 10, 2025, 12:01 PM UTC
- Resolved
- Dec 12, 2025, 08:01 AM UTC
- Duration
- 1d 20h
Affected: ProvisioningProvisioningProvisioning
Timeline · 4 updates
-
identified Dec 10, 2025, 12:01 PM UTC
We have identified an issue may cause some HelloID evaluations or enforcements to fail. We are currently preparing a fix. In the meantime, if an evaluation or enforcement fails, please retry the action until it succeeds.
-
identified Dec 10, 2025, 12:19 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Dec 11, 2025, 02:22 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Dec 12, 2025, 08:01 AM UTC
The issue has been resolved, we'll keep monitoring the situation.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 12:03 PM UTC
- Resolved
- Nov 18, 2025, 03:51 PM UTC
- Duration
- 3h 48m
Affected: ProvisioningProvisioningProvisioningService AutomationService AutomationService AutomationAccess ManagementAccess ManagementAccess Management
Timeline · 2 updates
-
identified Nov 18, 2025, 12:03 PM UTC
We are experiencing network issues in HelloID due to Global Cloudflare network issues. More information can be found on this page - https://www.cloudflarestatus.com/
-
resolved Nov 18, 2025, 05:51 PM UTC
Cloudflare services are currently operating normally. We are no longer observing elevated errors or latency.
Read the full incident report →
- Detected by Pingoru
- Nov 12, 2025, 12:50 PM UTC
- Resolved
- Nov 12, 2025, 02:24 PM UTC
- Duration
- 1h 33m
Affected: ProvisioningProvisioningService AutomationService AutomationAccess ManagementAccess Management
Timeline · 3 updates
-
investigating Nov 12, 2025, 12:50 PM UTC
At this moment, we're experiencing slow responses within HelloID. We're investigating the issue.
-
identified Nov 12, 2025, 01:03 PM UTC
The issue has been identified and a fix has been implemented
-
resolved Nov 12, 2025, 02:24 PM UTC
The issue has been resolved, we'll keep monitoring the situation.
Read the full incident report →
- Detected by Pingoru
- Sep 09, 2025, 08:33 AM UTC
- Resolved
- Sep 10, 2025, 11:58 AM UTC
- Duration
- 1d 3h
Affected: ProvisioningProvisioningProvisioning
Timeline · 5 updates
-
investigating Sep 09, 2025, 08:33 AM UTC
We’re currently experiencing a visual bug in the field mapping interface, where all actions appear as configured. This display is incorrect and does not reflect the actual configuration. Please note: this is a visual issue only and does not impact any actions in the target system.
-
identified Sep 10, 2025, 08:45 AM UTC
The issue has been identified and a fix is being implemented.
-
identified Sep 10, 2025, 08:52 AM UTC
We will start implementing the fix for the field mapping display issue at 11:00 CEST. No impact on system functionality is expected during this process. We’ll provide an update once the deployment is complete.
-
monitoring Sep 10, 2025, 09:30 AM UTC
A fix has been deployed to resolve the display issue in field mapping. If you don’t see the changes right away, try clearing your browser cache. We will continue to monitor the results closely.
-
resolved Sep 10, 2025, 11:58 AM UTC
The visual bug in the field mapping display has been resolved. If the changes are not immediately visible, please refresh your browser cache. In case the issue persists, please contact Tools4ever support.
Read the full incident report →
- Detected by Pingoru
- Jul 31, 2025, 08:54 AM UTC
- Resolved
- Jul 31, 2025, 01:18 PM UTC
- Duration
- 4h 24m
Affected: Access Management
Timeline · 3 updates
-
investigating Jul 31, 2025, 08:54 AM UTC
Multi-Factor Authentication (MFA) via HelloID is partially unavailable. We are investigating the cause and working on a solution. Our apologies for the inconvenience.
-
monitoring Jul 31, 2025, 09:11 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 31, 2025, 01:18 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 23, 2025, 02:50 PM UTC
- Resolved
- Jun 23, 2025, 06:56 PM UTC
- Duration
- 4h 5m
Affected: ProvisioningProvisioning
Timeline · 3 updates
-
investigating Jun 23, 2025, 02:50 PM UTC
We are currently experiencing issues with our platform services. As a result, domain validation and email validation may not function as expected. Other parts of the platform may also be affected. Our team is actively investigating and working to resolve the issue. We will provide updates as soon as more information is available. Thank you for your patience.
-
investigating Jun 23, 2025, 03:28 PM UTC
We are continuing to investigate this issue.
-
resolved Jun 23, 2025, 06:56 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 14, 2025, 01:41 PM UTC
- Resolved
- Feb 14, 2025, 05:08 PM UTC
- Duration
- 3h 26m
Affected: Access ManagementAccess Management
Timeline · 2 updates
-
identified Feb 14, 2025, 01:41 PM UTC
Due to a temporary issue, HelloID applications, including the HelloID authenticator, are currently unavailable for download and installation from the Google Play Store. Rest assured, we are actively working to resolve this matter as quickly as possible. Please note that any HelloID applications already installed on your devices will continue to function without interruption. Thank you for your understanding and patience.
-
resolved Feb 14, 2025, 05:08 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 14, 2025, 11:12 AM UTC
- Resolved
- Feb 04, 2025, 01:13 PM UTC
- Duration
- 21d 2h
Affected: Service AutomationService Automation
Timeline · 2 updates
-
monitoring Jan 14, 2025, 11:12 AM UTC
The phase-out of task data sources will be rolled out in stages following the 2025.01 release. Each tenant will receive one HelloID incident notification specifying which resources have been updated to indicate that the migration has been completed. Once all tenants have been migrated, this status message will be closed. The new PowerShell data sources will run on the local Service Automation Agent. Please ensure that it is active and has the appropriate permissions. For testing purposes, you may execute some migrated resources and verify the output to ensure it meets the expected results.
-
resolved Feb 04, 2025, 01:13 PM UTC
All migrations have been executed.
Read the full incident report →
- Detected by Pingoru
- Dec 10, 2024, 08:17 AM UTC
- Resolved
- Dec 10, 2024, 09:30 AM UTC
- Duration
- 1h 12m
Affected: ProvisioningService AutomationAccess Management
Timeline · 3 updates
-
identified Dec 10, 2024, 08:17 AM UTC
We will be implementing a hotfix regarding the issues we've encountered yesterday. This should only take about 10 minutes.
-
monitoring Dec 10, 2024, 08:40 AM UTC
Hotfix has been implemented and we're monitoring the situation
-
resolved Dec 10, 2024, 09:30 AM UTC
We'll keep monitoring the situation
Read the full incident report →
- Detected by Pingoru
- Dec 09, 2024, 01:09 PM UTC
- Resolved
- Dec 10, 2024, 08:40 AM UTC
- Duration
- 19h 31m
Affected: Access Management
Timeline · 3 updates
-
identified Dec 09, 2024, 01:09 PM UTC
At this moment the application catalog and starting end-user applications isn't working. We have identified the issue and are working on a hotfix.
-
monitoring Dec 09, 2024, 05:39 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Dec 10, 2024, 08:40 AM UTC
A new hotfix has been implemented
Read the full incident report →
- Detected by Pingoru
- Oct 25, 2024, 06:52 AM UTC
- Resolved
- Oct 25, 2024, 06:52 AM UTC
- Duration
- —
Affected: Service Automation
Timeline · 3 updates
-
investigating Oct 24, 2024, 07:22 PM UTC
We currently experience degraded performance on delegated form and product actions. In some cases, incidents are not shown. We are investigating this issue.
-
monitoring Oct 24, 2024, 07:46 PM UTC
A temporary fix has been implemented and we are monitoring the results.
-
resolved Oct 26, 2024, 06:52 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 05, 2024, 05:58 PM UTC
- Resolved
- Oct 08, 2024, 01:50 PM UTC
- Duration
- 2d 19h
Affected: Access ManagementAccess Management
Timeline · 4 updates
-
identified Oct 05, 2024, 05:58 PM UTC
The Azure AD sync with HelloID has stopped functioning. We have identified the issue and are actively working on a resolution. Currently, the sync cannot start, meaning changes will not be synced. However, there will be no mutations, so existing operations that rely on the synced data will not be affected.
-
identified Oct 07, 2024, 07:14 AM UTC
As a result of the ongoing Azure sync issue with HelloID, you may see the license information in the HelloID portal displaying as zero for all users. We are actively working on resolving this matter. Thank you for your patience.
-
monitoring Oct 07, 2024, 09:37 AM UTC
We have implemented a fix and we are currently monitoring the situation.
-
resolved Oct 08, 2024, 01:50 PM UTC
This incident has been resolved.
Read the full incident report →