Identified - We have been receiving reports from customers that their websites are being blocked when end users are using Microsoft Edge in Strict mode. This is due to an incorrect tracker classification for some of Contenful’s domains (cdn.contentful.com). We are following up with the classification service owner to have Contentful domains removed from this list in order to mitigate this issue.
Oct 22, 2025 - 20:52 UTC
Resolved -
The issue is now resolved.
Nov 5, 12:47 UTC
Monitoring -
We have rolled out a fix for the issue and users should now be able to load their Live Preview content again.
Nov 5, 12:42 UTC
Identified -
Customers using Chrome 142 or above are experiencing load failure for Preview iFrames due to missing local-network-access permissions. We have identified the cause and are testing a fix.
Nov 5, 10:46 UTC
Resolved -
This issue is now resolved.
Nov 5, 10:25 UTC
Monitoring -
We have put a fix in place for this issue and API tokens should no longer return a 401 Unauthorized error
Nov 5, 10:05 UTC
Investigating -
Our team has identified that a recent backfill task caused tokens created over five years ago to become invalid. We are working on a fix and will continue to monitor the situation.
Nov 5, 09:04 UTC
Resolved -
This issue is now resolved.
Nov 3, 19:24 UTC
Monitoring -
We've reverted the old token invalidation changes. Tokens that were previously resulting in unauthenticated errors should now be working again.
We will continue to monitor the situation.
Nov 3, 19:21 UTC
Identified -
We are currently experiencing an issue that is causing validation errors during token creation.
Additionally, our team has identified that a recent backfill task caused tokens created over five years ago to become invalid.
We have deployed a fix to correct these token expirations and are running a backfill to update affected tokens.
We are continuing to monitor the situation closely and will provide further updates as they become available.
We apologize for any inconvenience this may cause.
Nov 3, 18:24 UTC
Resolved -
The issue is resolved.
Oct 23, 15:18 UTC
Identified -
We've spotted that something has gone wrong with Personalization UI and some APIs. We're currently investigating the issue, and will provide an update soon.
Oct 23, 15:11 UTC