IAM Cloud Outage History

IAM Cloud is up right now

IAM Cloud had 16 outages in the last 2 years totaling 4171h 40m of downtime — averaging 0.7 incidents per month.

There were 16 IAM Cloud outages since June 24, 2024 totaling 4171h 40m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.iamcloudstatus.com

Notice April 15, 2026

Legacy (CDM v2) license validation issue

Detected by Pingoru
Apr 15, 2026, 08:01 AM UTC
Resolved
Apr 15, 2026, 10:03 AM UTC
Duration
2h 2m
Timeline · 3 updates
  1. investigating Apr 15, 2026, 08:01 AM UTC

    Incident Summary: V2 (Legacy) – customers presented with license expiry notification Services affected: CDM v2 (Legacy) Current impact: We are aware of an issue with CDM v2 (legacy) license verification. Customers will be unable to access CDM v2 until a reset operation is performed. Latest resolution status: Impacted customers should raise a ticket via our helpdesk and a reset will be applied. We are working on root cause in order to apply a global fix. Fix ETA: 11:00 BST Next update: 10:30 BST

  2. monitoring Apr 15, 2026, 08:44 AM UTC

    Incident Summary: V2 (Legacy) – customers presented with license expiry notification Services affected: CDM v2 (Legacy) Current impact: We are aware of an issue with CDM v2 (legacy) license verification. Customers will be unable to access CDM v2 until a reset operation is performed. Latest resolution status: We are in the process of rolling out a global fix, resolution state is being monitored. Fix ETA: 10:00 BST (complete) Next update: 10:30 BST

  3. resolved Apr 15, 2026, 10:03 AM UTC

    Incident Summary: V2 (Legacy) – customers presented with license expiry notification Services affected: CDM v2 (Legacy) Current impact: None. Latest resolution status: The global fix has been applied and v2 customers are working as expected. Root cause investigations will continue. Fix ETA: n/a - fix complete Next update: n/a - fix complete

Read the full incident report →

Notice February 17, 2026

Cloud Drive Mapper - mapping groups unavailable

Detected by Pingoru
Feb 17, 2026, 02:26 PM UTC
Resolved
Feb 17, 2026, 05:15 PM UTC
Duration
2h 48m
Affected: Cloud Drive Mapper
Timeline · 2 updates
  1. investigating Feb 17, 2026, 02:26 PM UTC

    Incident Summary: We are currently investigating an issue with CDM v3.19 and below whereby mapping groups are unavailable. Impacted customers are recommended to update to v3.22 where possible as this version is not affected. Services affected: Cloud Drive Mapper v3.19 and below Current impact: Users on v3.19 and below will not receive their mapping groups when using CDM. Latest resolution status: Critical Incident team is mobilised and are working on a fix. Fix ETA: TBC at present Next update: 15.30

  2. resolved Feb 17, 2026, 05:15 PM UTC

    Incident Summary: CDM users on versions v3.19 and below cannot use mapping groups. Services affected: Cloud Drive Mapper v3.19 and below Current impact: None Latest resolution status: Service has been restored by rolling back a Release made this afternoon to our API. Fix ETA: Change rollback completed at 15:10. Next update: N/a. Root Cause Analysis and Critical Incident follow up are initiated.

Read the full incident report →

Minor October 9, 2025

Microsoft Azure failure impacting IAM Cloud services

Detected by Pingoru
Oct 09, 2025, 09:30 AM UTC
Resolved
Oct 09, 2025, 02:17 PM UTC
Duration
4h 47m
Affected: Cloud Drive MapperIris (admin portal)
Timeline · 4 updates
  1. investigating Oct 09, 2025, 09:30 AM UTC

    Incident Summary: Global service impact due to MS Azure failure Regions impacted: Global Services affected: CDM v2 Legacy & v3 Iris Current impact: CDM users will be experiencing a intermittent service with possible degraded performance Iris users cannot use the service to administer users or tenancies Latest resolution status: We are observing a significant Microsoft issue which is impacting IAM Cloud. We are currently monitoring the issue but are reliant on Microsoft to restore service. Fix ETA: Dependent on Microsoft Next update: 12:00

  2. monitoring Oct 09, 2025, 09:53 AM UTC

    Incident Summary: Global service impact due to MS Azure failure Regions impacted: Global Services affected: CDM v2 Legacy & v3 Iris Current impact: CDM users will be experiencing a intermittent service with possible degraded performance Iris users cannot use the service to administer users or tenancies Latest resolution status: We are currently monitoring the issue but are reliant on Microsoft to restore service. https://admin.cloud.microsoft/?#/servicehealth/:/alerts/MO1168665 Fix ETA: Dependent on Microsoft Next update: 12:30

  3. monitoring Oct 09, 2025, 12:13 PM UTC

    Incident Summary: Global service impact due to MS Azure failure Regions impacted: Global Services affected: CDM v2 Legacy & v3 Iris Current impact: CDM and Iris performance is largely restored to normal following MS rollout of remediation to affected Azure Front Door resources Latest resolution status: MS estimate that 96% of impacted resources have now been recovered. Fix ETA: Dependent on Microsoft Next update: 15:00

  4. resolved Oct 09, 2025, 02:17 PM UTC

    Incident Summary: Global service impact due to MS Azure failure Regions impacted: Global Services affected: CDM v2 Legacy & v3 Iris Current impact: Services are available as normal Latest resolution status: MS state that all primary resources are now recovered; Azure customers using Azure Front Door (AFD) should see consistent availability, with slightly higher latencies decreasing as additional resources are recovered Fix ETA: Resolved Next update: n/a

Read the full incident report →

Notice July 30, 2025

MFA is coming to Iris

Detected by Pingoru
Jul 30, 2025, 04:06 PM UTC
Resolved
Jul 30, 2025, 04:06 PM UTC
Duration
—
Affected: Iris (admin portal)
Timeline · 1 update
  1. resolved Jul 30, 2025, 04:06 PM UTC

    Over the coming 4 weeks we are going to be enabling email-based MFA on our Iris portal. This will happen in several phases over the coming weeks. There isn't anything you need to do, as it will be enabled automatically. If you run into any issues, or temporarily need to disable it, please contact our support team at [email protected] Many thanks, The IAM Cloud team

Read the full incident report →

Minor April 21, 2025

Legacy (CDM v2) Portal unreachable via Chrome

Detected by Pingoru
Apr 21, 2025, 10:13 AM UTC
Resolved
Apr 22, 2025, 04:40 PM UTC
Duration
1d 6h
Timeline · 3 updates
  1. investigating Apr 21, 2025, 10:13 AM UTC

    This is reoccurrence of the previous issue on the 18th April. Incident Summary: The legacy CDM Portal (portal.iamcloud.net) has been classified as unsafe when using Chrome, FireFox maybe affected too. Services affected: Legacy CDM (v2) Current impact: CDM v2 administrators will be unable to reach the Portal if using Chrome and potentially FireFox. Our suggested workaround is to use a different browser (e.g. Edge). Latest resolution status: A workaround is currently available. We have provided feedback to the browser vendors to inform them that the site has been incorrectly classified as unsafe. Next update: TBC

  2. investigating Apr 22, 2025, 10:11 AM UTC

    This is reoccurrence of the previous issue on the 18th April. Incident Summary: The legacy CDM Portal (portal.iamcloud.net) has been incorrectly classified as unsafe by the Google Safe Browsing service when using the Chrome and Firefox browsers. Services affected: Legacy CDM (v2) Current impact: CDM v2 administrators will be unable to reach the Portal if using Chrome or Firefox. Our suggested workaround is to use a different browser (e.g. Edge). Latest resolution status: A workaround is currently available. We have provided feedback to Google to inform them that the site has been incorrectly classified as unsafe. However, due to the issue having surfaced multiple times, we expect that it may reoccur after the next correction is made. We have initiated additional work to provide a permanent fix which we hope to be in place by the end of the week. Next update: 17:00 or when resolved

  3. resolved Apr 22, 2025, 04:40 PM UTC

    This incident has been resolved now, however we're continuing to work on a long term fix.

Read the full incident report →

Minor April 17, 2025

Legacy (CDM v2) Portal unreachable via Chrome / Firefox

Detected by Pingoru
Apr 17, 2025, 10:33 AM UTC
Resolved
Apr 18, 2025, 06:33 AM UTC
Duration
20h
Timeline · 8 updates
  1. investigating Apr 17, 2025, 10:33 AM UTC

    This is reoccurrence of the previous issue on the 7th April. Incident Summary: The legacy CDM Portal (portal.iamcloud.net) has been classified as unsafe when using Chrome & Firefox browsers Services affected: Legacy CDM (v2) Current impact: CDM v2 administrators will be unable to reach the Portal if using Chrome or Firefox. Our suggested workaround is to use a different browser (e.g. Edge). Latest resolution status: A workaround is currently available. We have provided feedback to the browser vendors to inform them that the site has been incorrectly classified as unsafe. Next update: 12:30

  2. identified Apr 17, 2025, 11:03 AM UTC

    We have revalidated the domain and are awaiting propagation.

  3. identified Apr 17, 2025, 01:25 PM UTC

    We are still waiting for the propagation to replicate. Latest resolution status: Edge can be used. Next update: When the issue is resolved.

  4. identified Apr 17, 2025, 02:11 PM UTC

    We are continuing to work on a fix for this issue.

  5. identified Apr 17, 2025, 02:16 PM UTC

    We have revalidated the domain with Google. Next update: 16:15

  6. identified Apr 17, 2025, 03:31 PM UTC

    No status change. Next update: When the issue is resolved.

  7. monitoring Apr 17, 2025, 04:38 PM UTC

    We have revalidated the domain with Google. Googles process documentation states that it can be a couple of days before verification is processed. We will continue to monitor the situation and we ask that affected Admins use Microsoft Edge while this issue persists.

  8. resolved Apr 18, 2025, 06:33 AM UTC

    The issue is now resolved and users can access the legacy Portal as normal via Chrome and Firefox. Thank you for your patience whilst Google corrected the unsafe site classification.

Read the full incident report →

Major April 2, 2025

A Subset of users may experience problems authenticating to the IAM Cloud Platform.

Detected by Pingoru
Apr 02, 2025, 08:26 AM UTC
Resolved
Apr 02, 2025, 10:21 AM UTC
Duration
1h 55m
Affected: Microsoft 365
Timeline · 3 updates
  1. investigating Apr 02, 2025, 08:26 AM UTC

    A Subset of users may experience problems authenticating to the IAM Cloud Platform. Engineers are working to resolve this issue as a priority and we will provide further updates ASAP. We apologise for the inconvenience. IAM Cloud Technical Support http://support.iamcloud.com [email protected] Phone (UK): +44 118 324 0000

  2. monitoring Apr 02, 2025, 09:03 AM UTC

    We have rolled out a mitigation and are monitoring the impact. We are working with affected customers to ensure the validity of the fix.

  3. resolved Apr 02, 2025, 10:21 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 1, 2025

US based clients are unable to access portal.iamcloud.net

Detected by Pingoru
Apr 01, 2025, 03:32 PM UTC
Resolved
Apr 01, 2025, 04:55 PM UTC
Duration
1h 22m
Timeline · 3 updates
  1. investigating Apr 01, 2025, 03:32 PM UTC

    Users in the US region are unable to login to the IAM Cloud Portal. We are investigating and apologize for any inconvenience caused.

  2. identified Apr 01, 2025, 04:12 PM UTC

    The issue has been identified and a fix will be implemented within the next hour.

  3. resolved Apr 01, 2025, 04:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 13, 2025

Issue affecting IRIS portal

Detected by Pingoru
Mar 13, 2025, 01:09 PM UTC
Resolved
Mar 13, 2025, 02:11 PM UTC
Duration
1h 2m
Timeline · 2 updates
  1. investigating Mar 13, 2025, 01:09 PM UTC

    We are aware of an issue affecting customers where they are unable to edit mapping groups in our admin portal, Iris. We are investigating this at the moment and the team is actively working on this. Update will be provided in 1 hour.

  2. resolved Mar 13, 2025, 02:11 PM UTC

    The team has identified an issue in a release where mapping groups configuration failed via Iris. We have patched the release and validated the fix. We are putting in mitigation for this defect in future release testing. Mapping group editing is now restored on services. Thank you for your patience.

Read the full incident report →

Major January 13, 2025

A subset of users in the US may experience problems authenticating to the IAM Cloud Platform.

Detected by Pingoru
Jan 13, 2025, 08:40 PM UTC
Resolved
Jan 13, 2025, 09:03 PM UTC
Duration
22m
Affected: Microsoft 365
Timeline · 2 updates
  1. investigating Jan 13, 2025, 08:40 PM UTC

    A subset of users in the US region may experience problems authenticating to the IAM Cloud Platform. Engineers are working to resolve this issue as a priority and we will provide further updates ASAP. We apologise for the inconvenience. IAM Cloud Technical Support http://support.iamcloud.com [email protected] Phone (UK): +44 118 324 0000

  2. resolved Jan 13, 2025, 09:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 30, 2024

Issues connecting to a subset of Azure services

Detected by Pingoru
Jul 30, 2024, 12:45 PM UTC
Resolved
Jul 31, 2024, 07:33 AM UTC
Duration
18h 48m
Timeline · 3 updates
  1. monitoring Jul 30, 2024, 12:45 PM UTC

    We're aware of the current Azure service status issue - https://azure.status.microsoft/en-gb/status / https://x.com/AzureSupport/status/1818257201145712898 At this stage we're unsure if it will affect any of our services, but we're monitoring the situation.

  2. monitoring Jul 30, 2024, 02:26 PM UTC

    Microsoft are still investigating a Network Infrastructure issue affecting a subset of Microsoft services, Azure service page last updated 13:56 UTC on 30 July 2024. We have noticed some networking components coming back online on our services.

  3. resolved Jul 31, 2024, 07:33 AM UTC

    This incident has been resolved.

Read the full incident report →