Is Contentful Down Right Now? Check if there is a current outage ongoing.

We are currently experiencing issues affecting Contentful Functions, which are intermittently failing to create and execute as expected. This disruption is due to a problem with one of our providers. Our team is actively monitoring the situation and working with the provider to resolve the issue as quickly as possible.

Some customers are experiencing issues logging in to Contentful via SSO. We have identified the cause and are working to mitigate the issue.

This issue is now resolved

This issue is now resolved, we will keep monitoring the situation before fully closing the incident. Customers should refresh their web app page to see the standard asset uploader again.

We are experiencing degraded performance on our Web App asset uploader. We have enabled a simpler fallback uploader that provides less functionality while we investigate the issue. Customers will need to reload the webapp to use the fallback uploader.

This issue is now resolved

This issue is now resolved, we will keep monitoring the situation before fully closing the incident. Customers should refresh their web app page to see the standard asset uploader again.

We are experiencing degraded performance on our Web App asset uploader. We have enabled a simpler fallback uploader that provides less functionality while we investigate the issue. Customers will need to reload the webapp to use the fallback uploader.

We have monitored the fix and have confirmed that this has mitigated the issue.

We have put a fix in place and customers should be able to use this capability as normal.

Some customers may be having issues with the Live Preview capabilities of Contentful. We have identified the cause and are working on implementing a fix.

We have monitored the fix and have confirmed that this has mitigated the issue.

We have put a fix in place and customers should be able to use this capability as normal.

Some customers may be having issues with the Live Preview capabilities of Contentful. We have identified the cause and are working on implementing a fix.

The scheduled maintenance on the snapshots database in the production environment has been successfully completed.All queued updates during the maintenance window have been processed, and the snapshot endpoint data is now fully up to date. You can continue to access and update snapshot data as usual.The Content Management API remained fully operational throughout the process.Thank you for your patience.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will be performing scheduled maintenance on the snapshots database in the production environment. The maintenance is expected to last approximately five hours.During this period, clients will be able to access and retrieve snapshot data as usual. However, any new updates to entries will be queued and delayed from appearing through the snapshot endpoints until the maintenance is complete.The Content Management API will continue to behave as expected.

The error rates are back to normal.

Error rates have dropped to normal levels and network connectivity issues have been resolved. We will continue to monitor the situation for the next few hours.

We are working with our services providers, and are now seeing a drop in error rates and a return to normal. We are monitoring the situation.

We are continuing to investigate what we believe to be network connectivity issues. The impact is limited to a small proportion of our total traffic. We will provide an update as soon as we have more information.

Some customers are experiencing increased errors or timeouts on the Content Delivery API and GraphQL API. We are currently investigating the issue.

We have confirmed that the issue was resolved.

We've noticed a short spike of latency and error rate for Content Preview API. We have already put a fix in place and are now monitoring the situation until we confirm it is fully resolved.

This incident has been resolved.

We have deployed a fix for this issue and are monitoring the results. Customer should no longer be experiencing these types of "duplicate key" errors.

We have identified an issue which was introduced in the past week where a small subset of customer requests are receiving the following error: "duplicate key value violates unique constraint "draft_entries_fts_space_id_entry_id_locale_unique": duplicate key value violates unique constraint "draft_entries_fts_space_id_entry_id_locale_unique". We have narrowed down the root cause and are working on a fix for the issue.

The issue has been resolved.

We have resolved the issue and are monitoring the situation.

The Personalization Management API is reporting "Bad Gateway" to all requests. We are investigating the issue.

This issue has been resolved.

We have identified the cause of the issue and implemented a fix. Customers are able to successfully get up to date schemas from Contentful's GraphAPI. We are continuing to monitor the situation.

We are investigating an issue with GraphQL schema registry. Some customers may not be able to get up to date schemas for Contentful GraphAPI

Transactional emails are functional again. Customers might need to retry transactional emails such as invitations and password resets which were affected during the period of the incident.

We have addressed the issue and are monitoring the situation.

Our engineering team are continuing to look into the cause of the issue with emails not being processed in Contentful.

We are continuing to investigate this issue.

We are investigating an issue where customers are not receiving emails from Contentful (e.g new user invites, customer password resets).

We have resolved the issue.

We have addressed the issue and are monitoring the situation.

Some free-tier customers are experiencing errors on management and delivery APIs.

We have addressed the issue and are monitoring the situation.

Some free-tier customers are experiencing errors on our content management and delivery APIs. We're investigating the issue.

Users may have been unable to see webhook definitions in the user interface. Webhook delivery is not affected. We have identified the issue and put a fix in place. Users may need to refresh the page if they are unable to see webhook definitions.

We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Ninetailed management API experienced a partial outage due to database issues.

This issue has been resolved.

Some users may have encountered issues uploading assets to Contentful. A change has been put in place, but users may need to refresh the page if they are still encountering this error.

The increased error rate and latency was confirmed to be subsided.

We observed recovery for the past 30 minutes. We are monitoring the situation and investigating further the cause to prevent it to resurface.

We identified an increase of latency and timeouts on the Management and Preview Content APIs. We are investigating the root cause.

We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

We have identified and corrected an issue with the App Definition screen being unavailable for all users. Reloading the page should restore any missing functionality.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

This incident has been resolved.

We have put a mitigation in place and are seeing a reduction in errors. We will continue to monitor the situation.

We are investigating an issue with uploading custom app bundles.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We identified an issue that occurred on Jan. 21st between 14:29 (UTC) and 18:09 (UTC) where our GraphQL Delivery API was returning error responses for requests containing Shopify data queries. A fix was deployed which resolved the issue, and we are continuing to investigate the root cause in depth.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Some users might experience degradation in the web app's responsiveness. We are investigating the issue.

Transactional emails are fully operational again.

We have identified an issue where transactional emails are not being sent. This means that newly added users may not be receiving invitational emails.

All transactional emails are being sent out again for changes to workflows, tasks and comments.

We have an ongoing partial outage on transactional emails. Customers are no longer receiving email notifications as a result of changes to workflows, tasks or comments. Customers will need to go into the Contentful WebApp to review the state of tasks, comments or workflows as a result. We apologise for any inconvenience this may cause.

Transactional emails are fully operational again.

Transactional emails are not being processed by our email provider. Password reset emails, invites, task mentions and similar notifications are impacted.

This incident has been resolved.

The cache purge was completed and we confirmed the recovery of the missing fields. We will continue to monitor the recovery for the next few minutes.

We have deployed a fix for the issue. We are in the process of purging all the cache for malformed responses, which should be the last step of the mitigation.

We discovered an issue in our Content APIs that resulted in some fields being omitted in the API response. We have identified the causing issue and are working on a change.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Customers are still experiencing high error rates on the Contentful Management API (CMA) and the Contentful WebApp. We have identified the cause of the issue and are working on a fix.

We are continuing to investigate this issue

We are investigating an issue with the Contentful Management API (CMA). This also affects the Contentful WebApp.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have identified the cause of the issue and have deployed a fix

Our Content Management API is currently operating in degraded mode and some customers are experiencing elevated errors.; this API also powers our Web App and therefore customers are seeing elevated errors in the WebApp also. We are investigating the issue.

This incident has been resolved.

We have identified the issue and deployed a fix. File uploads in the web app should work as expected. We continue to monitor the situation.

We are currently investigating this issue.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Contentful customers experienced a brief outage on Contentful Content Management API between 16:24 and 16:29 UTC. This is now recovered and we are monitoring the situation.

This incident has been resolved.

We have identified the issue and are working to resolve it.

We are currently investigating this issue.

This incident has been resolved.

A fix has been deployed which has resolved the issue. We are running a job to pick up all content type changes which were made but not reflected in GraphQL API in the past hour. This will be completed in the next 30 mins. (Customer affected can also republish their content types again if they don't wish to wait).

Some customers may be experiencing delays in changes to their content types being reflected in the GraphQL Content API. We have identified the cause and are working on mitigating the issue

We discovered a bug that could have resulted in stale 400 responses being returned by the Contentful GraphAPI. It has been resolved and the stale responses have been purged from the cache.

We have identified that introspection queries in Graph-API were returning stale content for a subset of customers. The issue has been identified and a fix has been rolled out.

Incident is now resolved.

A fix has been deployed, we are monitoring the situation.

We have noticed an issue with external references, that might lead to external content being stale. We are working on a fix.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating an issue on the Contentful Content Management API (CMA) which is affecting customers on our free tier.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

This incident has been resolved.

The issue has been resolved and all APIs are in normal operating state. We will continue to monitor the situation.

We are continuing to investigate this issue.

We are currently investigating an issue across Contentful Content Management and Content Delivery APIs where customers are seeing increased error rates.

This incident has been resolved.

The issue has been resolved and uploads on the Contentful WebApp are back to normal working state.

While our mitigation has resolved the issue of customers receiving errors when uploading assets, the following functionality is not currently available. - Rotate/Resize/Crop Images in the Contentful WebApp - Upload of images from third parties We continue to work on this issue.

Customers who are still experiencing errors uploading files to Contentful WebApp should refresh the page and retry the upload.

Some customers are experiencing errors when uploading files to Contentful WebApp. We have initiated a temporary mitigation (which is limited to direct uploads).

Between 12:00 and 12:20 UTC some customers on Premium tier experienced a spike in errors on the Contentful Content Management API (CMA). This may also have impacted usage of the Contentful Web App.

This incident has been resolved.

Some customers are experiencing increased errors on content management API in the US data residency region.

This incident has been resolved, and our services have been fully restored.

We see traffic recovering to normal levels and are monitoring the situation.

We see the errors recovering slowly on the side of our upstream providers. Additionally, we're working on our side on mitigating the issue.

We're investigating elevated error rates for our CDA and Images API. We suspect that the cause is an incident on one of our upstream CDN providers.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and we are working towards a fix.

We are continuing to investigate the issue. We continue to see some errors in the EU data residency region related to Content Delivery APIs as well as assets and images.

EU data-residency customers might experience increased error rates on across our Content Delivery APIs.

This incident has been resolved.

We scaled the cache invalidation infrastructure for the affected customers and saw the back pressure of the queues come back down to normal levels. We continue to monitor the situation, so the issue doesn't reappear.

We're investigating an issue where a small minority of our customers might see delayed cache invalidation on our content delivery network after publish that might result in some of their end users seeing stale content for longer than expected.

Between 14:50 and 14:55 (UTC) some customers spaces on shared infrastructure experienced a spike in errors across our Content Delivery APIs (Content Delivery API, GraphQL Delivery API). The issue has been resolved.

Between 12:36 and 12:56(UTC) customers on our shared infrastructure experienced elevated errors on our GraphAPI. We applied a fix for the issue and the API is operating as normal again.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Some customers on our Team tier as still experiencing issues where they can publish successfully but the cache is not purged immediately so the are receiving stale content from Contentful's Delivery APIs. We have identified the cause of the issue and are working on a fix.

We are investigating an issue where a subset of customers (on Team tier) are experiencing delays with publishing and content being out of date.

All issues with extensions using unpkg.com have been resolved.

We are monitoring reported issues with apps hosted from unpkg.com. Extensions that are using unpkg.com to load the App SDK are affected.

This incident has been resolved.

After a partial overload condition in the Webhooks system operation is returning back to normal. We are currently monitoring the situation.

We have detected an issue with our Webhooks system that we are currently investigating. Customer may experience delays in Webhooks triggers.

This incident has been resolved. We see all systems fully operational again.

The elevated errors were caused by a faulty GraphQL node and affected a small single digit percentage of requests only. We resolved the problem and are monitoring the situation to ensure the error doesn't reappear.

We're currently investigating a single digit percentage increase above normal GraphQL error rates.

This incident has been resolved.

We are currently investigating. The impact is limited to few select spaces.

This incident has been resolved.

A fix is in place and we are monitoring the situation

We are currently investigating this issue.