IAM Cloud incident

Legacy (CDM v2) Portal unreachable via Chrome

Minor Resolved View vendor source →

IAM Cloud experienced a minor incident on April 21, 2025, lasting 1d 6h. The incident has been resolved; the full update timeline is below.

Started
Apr 21, 2025, 10:13 AM UTC
Resolved
Apr 22, 2025, 04:40 PM UTC
Duration
1d 6h
Detected by Pingoru
Apr 21, 2025, 10:13 AM UTC

Update timeline

  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.