- Detected by Pingoru
- May 15, 2026, 04:15 PM UTC
- Resolved
- May 15, 2026, 05:06 PM UTC
- Duration
- 50m
Affected: Web ApplicationWeb Application
Timeline · 3 updates
-
investigating May 15, 2026, 04:15 PM UTC
We are currently investigating an issue affecting the Web Application in the AWS EU & AWS NA region. During this time, users may experience intermittent delays and errors within the Contentstack user interface, particularly when the entry page is not loading. If you experience this issue, please perform a hard refresh of the page. Our engineering team has been mobilized and is actively working to identify the root cause and restore normal service. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].
-
monitoring May 15, 2026, 05:00 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 15, 2026, 05:06 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 09, 2026, 11:19 AM UTC
- Resolved
- May 09, 2026, 11:19 AM UTC
- Duration
- —
Affected: Web ApplicationWeb ApplicationWeb ApplicationWeb ApplicationWeb ApplicationWeb ApplicationWeb Application
Timeline · 1 update
-
resolved May 09, 2026, 11:19 AM UTC
An industry-wide security vulnerability known as "Copy Fail" (CVE-2026-31431) was publicly disclosed. This critical vulnerability affected the Linux operating systems used across most major cloud providers. Resolution We are writing to let you know that our engineering team has successfully completed the full remediation of this vulnerability across all of our cloud infrastructure. The official security patches have been completely deployed, and post-upgrade validation has been performed to ensure all systems are running securely. Customer Impact & Actions Required * Action Required: None. Our services are fully patched and secure, and you do not need to make any changes on your end. * Service Impact: No service interruptions occurred during this security update. Security and reliability remain our highest priorities. If you have any questions or require further information, please feel free to reach out to our support team at [email protected]
Read the full incident report →
- Detected by Pingoru
- Apr 11, 2026, 06:18 AM UTC
- Resolved
- Apr 11, 2026, 07:32 AM UTC
- Duration
- 1h 13m
Affected: Web ApplicationContent Management APIContent Delivery APIImage Delivery APIGraphQL Delivery APIAssets APIWebhook DispatcherMarketplace - Web ApplicationMarketplace - Installed AppsLaunch - Web ApplicationLaunch - Management APILaunch - Content Delivery Network (CDN)Launch - Edge ServicesPersonalize - Web ApplicationPersonalize - Management APIPersonalize - Edge APIPersonalize - AnalyticsAutomation UIAutomation APIBrandKit UIBrandKit API
Timeline · 4 updates
-
investigating Apr 11, 2026, 06:18 AM UTC
We are currently investigating an issue impacting all services in the AWS EU region, which may result in a full outage for users. Our engineering team has been engaged and is actively working to identify the root cause and restore services as quickly as possible. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].
-
identified Apr 11, 2026, 07:04 AM UTC
The issue has been identified within the ingress controller during an ongoing AWS EKS Kubernetes cluster upgrade, which led to a disruption impacting all services in the AWS EU region. Our team has isolated the root cause and is actively implementing a fix to restore normal traffic routing. Services are expected to recover as the remediation progresses.
-
monitoring Apr 11, 2026, 07:18 AM UTC
A fix has been implemented, and traffic has been restored. We are currently monitoring the results to ensure continued stability.
-
resolved Apr 11, 2026, 07:32 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 06:04 PM UTC
- Resolved
- Apr 09, 2026, 06:13 PM UTC
- Duration
- 9m
Affected: Content Management API
Timeline · 3 updates
-
investigating Apr 09, 2026, 06:04 PM UTC
We are currently experiencing issues with Single and Bulk Publishing/Unpublishing, Releases, Search, and Entries. As a result, customers may observe delays in seeing entries reflected on the entry list page. We are also noticing issues with Webhooks, which may lead to delays or loss of invocations. Our team is actively working to resolve the issue and will share further updates as they become available. Please reach out to Contentstack Support if you require assistance.
-
monitoring Apr 09, 2026, 06:10 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 09, 2026, 06:13 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 21, 2026, 05:24 AM UTC
- Resolved
- Mar 21, 2026, 06:45 AM UTC
- Duration
- 1h 20m
Affected: Content Management APIContent Delivery APIImage Delivery APIGraphQL Delivery APIAssets APIMarketplace - Web ApplicationMarketplace - Installed AppsPersonalize - Web ApplicationPersonalize - Management APILaunch - Web ApplicationLaunch - Management APIAutomation UIAutomation APIBrandKit UIBrandKit API
Timeline · 4 updates
-
investigating Mar 21, 2026, 05:24 AM UTC
We are currently investigating a outage affecting multiple services in the Microsoft Azure NA region. During this time, users may experience service unavailability and API errors. Our engineering team has been mobilized and is actively working to identify the root cause and restore normal service. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].
-
investigating Mar 21, 2026, 06:10 AM UTC
Our engineering team continues to actively investigate the issue affecting multiple services in the Microsoft Azure NA region. Users may continue to experience service unavailability and API errors. We are working to identify the root cause and will provide another update as soon as more information becomes available. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].
-
monitoring Mar 21, 2026, 06:40 AM UTC
The issue affecting multiple services in the Microsoft Azure NA region has been mitigated and services are operating normally. Our team will continue monitoring system performance to ensure stability. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].
-
resolved Mar 21, 2026, 06:45 AM UTC
This incident has been fully resolved and all systems are operating normally. Thank you for your patience while we worked to restore the services.
Read the full incident report →
- Detected by Pingoru
- Feb 12, 2026, 11:03 AM UTC
- Resolved
- Feb 12, 2026, 11:57 AM UTC
- Duration
- 54m
Affected: Launch - Content Delivery Network (CDN)
Timeline · 3 updates
-
identified Feb 12, 2026, 11:03 AM UTC
Customers in the Azure NA region may experience timeouts when accessing applications deployed on Launch, which may impact existing deployments. Our team is actively investigating the issue and working toward a resolution. We are closely monitoring the situation and will provide updates as more information becomes available. If you experience any issues accessing our services, please contact our Customer Success team for assistance.
-
monitoring Feb 12, 2026, 11:35 AM UTC
A fix is being applied, and we are actively monitoring the situation. If you still face a timeout, affected customers are requested to redeploy their applications to ensure full restoration of service.
-
resolved Feb 12, 2026, 11:57 AM UTC
This incident has been resolved. If you are still experiencing any issues, please redeploy your application or contact our Customer Support for assistance.
Read the full incident report →
- Detected by Pingoru
- Feb 07, 2026, 12:42 PM UTC
- Resolved
- Feb 06, 2026, 04:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Feb 07, 2026, 12:42 PM UTC
On February 6 at 22:00 UTC, we experienced a temporary issue in the Azure NA region that impacted scheduled publishing operations. We want to assure you that immediate (non-scheduled) publishing operations were not affected by this incident. Our engineering team promptly investigated and resolved the root cause. All scheduled publishing functionality has now been fully restored, and all impacted scheduled publish jobs have been successfully recovered and published. You can continue scheduling content for publishing as usual. If you have any questions or continue to experience issues, please contact the Contentstack Support team for assistance.
Read the full incident report →
- Detected by Pingoru
- Feb 06, 2026, 09:46 AM UTC
- Resolved
- Feb 06, 2026, 10:33 AM UTC
- Duration
- 46m
Affected: Content Management API
Timeline · 4 updates
-
investigating Feb 06, 2026, 09:46 AM UTC
We are currently investigating an issue affecting Content Management (CMA) services in the Azure NA region. During this time, users may experience failures or delays with publishing and data management (CRUD) activities. Our engineering team is actively working toward a resolution. We are monitoring the situation closely and will provide further updates as they become available. If you encounter persistent issues, please reach out to the Contentstack Support team for assistance.
-
identified Feb 06, 2026, 10:13 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Feb 06, 2026, 10:23 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 06, 2026, 10:33 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 27, 2026, 02:58 PM UTC
- Resolved
- Jan 26, 2026, 08:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jan 27, 2026, 02:58 PM UTC
A scheduled cache server engine upgrade caused the Contentstack Web Application to become unavailable from 08:00 AM to 09:30 AM UTC on Jan 26, 2026, affecting user login and application operations. The cache server became unresponsive during a planned backup operation, exhibiting unexpected behavior that was not observed during similar upgrades in other regions and environments. To resolve the issue, the engine upgrade was rolled back and traffic was redirected to the stable version, fully restoring service functionality. We are currently working with the hyperscalers to identify the root cause and are simultaneously analyzing our internal procedures to improve the overall operational process for future upgrades.
Read the full incident report →
- Detected by Pingoru
- Jan 23, 2026, 06:30 AM UTC
- Resolved
- Jan 23, 2026, 06:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jan 27, 2026, 11:20 AM UTC
A standard security upgrade to Node.js 24 with OpenSSL 3 was deployed as part of our security hardening efforts. The upgrade introduced stricter RSA-PSS signature validation per RFC 8017 standards, changing the default salt length from a previously lenient range (32-222) to strictly enforcing 32 for SHA-256. This impacted webhook functionality for configurations using RSA-based certificates with salt lengths greater than 32. Upon identifying the impact, the update was promptly reverted to restore normal operations.
Read the full incident report →
Critical January 12, 2026 - Detected by Pingoru
- Jan 12, 2026, 02:03 PM UTC
- Resolved
- Jan 12, 2026, 07:19 PM UTC
- Duration
- 5h 15m
Affected: Automation UIAutomation API
Timeline · 7 updates
-
investigating Jan 12, 2026, 02:03 PM UTC
We are currently experiencing issues affecting our Automate connectors. This may impact existing and new automation The team is actively investigating and working toward a resolution. We are monitoring the situation closely and will share updates as more information becomes available. If you encounter any difficulties accessing our services, please contact our Customer Success team for assistance.
-
identified Jan 12, 2026, 02:32 PM UTC
We have identified the root cause of the issue and are currently applying a fix. We will post the next update as soon as we have confirmed the resolution. Please contact Customer Success if you require immediate assistance.
-
identified Jan 12, 2026, 04:13 PM UTC
We are continuing to work on a fix for this issue.
-
identified Jan 12, 2026, 05:12 PM UTC
Our team is actively working on a resolution.
-
identified Jan 12, 2026, 06:13 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Jan 12, 2026, 07:15 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jan 12, 2026, 07:19 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 08, 2026, 03:50 PM UTC
- Resolved
- Jan 08, 2026, 05:06 PM UTC
- Duration
- 1h 16m
Affected: Web ApplicationMarketplace - Web ApplicationLaunch - Web ApplicationPersonalize - Web ApplicationAutomation UIBrandKit UI
Timeline · 4 updates
-
investigating Jan 08, 2026, 03:50 PM UTC
Some customers using SSO may currently experience difficulties accessing the Contentstack application. The team is actively investigating the issue and working toward a resolution. We are closely monitoring the situation and will share updates as more information becomes available. If you encounter any difficulties accessing our services, please contact our Customer Success team for assistance.
-
identified Jan 08, 2026, 04:15 PM UTC
The issue has been identified, and a fix is currently being implemented.
-
monitoring Jan 08, 2026, 04:37 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jan 08, 2026, 05:06 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 08, 2026, 11:47 AM UTC
- Resolved
- Jan 08, 2026, 12:28 PM UTC
- Duration
- 41m
Affected: Web ApplicationContent Management APIContent Delivery APIImage Delivery APIGraphQL Delivery APIAssets APIWebhook Dispatcher
Timeline · 5 updates
-
investigating Jan 08, 2026, 11:47 AM UTC
We are currently experiencing issues affecting our web application, GraphQL, Delivery APIs, and content management services. This may impact both Publish and Get calls. The team is actively investigating and working toward resolution. We are monitoring the situation closely and will share updates as more information becomes available. If you encounter any difficulties accessing our services, please contact our Customer Success team for assistance.
-
identified Jan 08, 2026, 12:14 PM UTC
The issue has been identified, and a fix is currently being implemented. We are monitoring the situation closely and will share updates as more information becomes available. If you encounter any difficulties accessing our services, please contact our Customer Success team for assistance.
-
monitoring Jan 08, 2026, 12:22 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Jan 08, 2026, 12:23 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jan 08, 2026, 12:28 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 18, 2025, 12:43 AM UTC
- Resolved
- Dec 18, 2025, 02:51 AM UTC
- Duration
- 2h 7m
Affected: Content Management APIContent Delivery API
Timeline · 4 updates
-
investigating Dec 18, 2025, 12:43 AM UTC
We are currently experiencing issues with Publishing/Unpublishing, Releases, Search, Taxonomy, Entries, and other CMA services. Our team is actively working to resolve these issues and will provide updates as soon as more information becomes available. If you experience any difficulties accessing our services, please reach out to our Customer Success team for assistance.
-
identified Dec 18, 2025, 01:20 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Dec 18, 2025, 02:30 AM UTC
Publishing/Unpublishing, Releases, Search, Taxonomy, Entries, and other CMA services are working as expected. However, you may notice some delay when viewing the publish queue and webhook logs. We're actively monitoring the results. If you’re facing any problems, Contentstack Support is available at [email protected].
-
resolved Dec 18, 2025, 02:51 AM UTC
This incident has been resolved. All services are now working as expected.
Read the full incident report →
- Detected by Pingoru
- Dec 11, 2025, 12:24 AM UTC
- Resolved
- Dec 10, 2025, 11:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Dec 11, 2025, 12:24 AM UTC
Publish activity is working as expected. However, you may notice some delay when viewing the publish logs. If you’re facing any problems, Contentstack Support is available at [email protected].
Read the full incident report →
- Detected by Pingoru
- Dec 10, 2025, 09:30 PM UTC
- Resolved
- Dec 10, 2025, 09:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Dec 10, 2025, 09:54 PM UTC
We experienced intermittent issues with our Content Management API due to high disk usage on the message broker service. A fix has been implemented, and we are currently monitoring the results. You may notice slowness in the publish queue and publish activity. If you’re facing any problems, Contentstack Support is available at [email protected].
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 12:02 PM UTC
- Resolved
- Nov 18, 2025, 06:52 PM UTC
- Duration
- 6h 50m
Affected: Content Delivery APIContent Delivery APIContent Delivery APIContent Delivery APIContent Delivery APIContent Delivery APIContent Delivery APIGraphQL Delivery APIGraphQL Delivery APIGraphQL Delivery APIGraphQL Delivery APIGraphQL Delivery APIGraphQL Delivery APIGraphQL Delivery APIAssets APIAssets APIAssets APIAssets APIAssets APIAssets APIAssets APILaunch - Web ApplicationLaunch - Web ApplicationLaunch - Web ApplicationLaunch - Management APILaunch - Management APILaunch - Management APILaunch - Content Delivery Network (CDN)Launch - Content Delivery Network (CDN)Launch - Content Delivery Network (CDN)Launch - Edge ServicesLaunch - Edge ServicesLaunch - Edge ServicesLaunch - Web ApplicationLaunch - Web ApplicationAutomation UIAutomation UILaunch - Management APILaunch - Management APIAutomation APIAutomation APILaunch - Content Delivery Network (CDN)Launch - Content Delivery Network (CDN)Launch - Web ApplicationLaunch - Web ApplicationLaunch - Edge ServicesLaunch - Edge ServicesLaunch - Management APILaunch - Management APIAutomation UIAutomation UIAutomation UIAutomation UILaunch - Content Delivery Network (CDN)Launch - Content Delivery Network (CDN)Automation UIAutomation APIAutomation APIAutomation APIAutomation APILaunch - Edge ServicesLaunch - Edge ServicesAutomation API
Timeline · 10 updates
Read the full incident report →
- Detected by Pingoru
- Nov 16, 2025, 10:53 PM UTC
- Resolved
- Nov 17, 2025, 12:20 AM UTC
- Duration
- 1h 27m
Affected: Content Management API
Timeline · 4 updates
-
investigating Nov 16, 2025, 10:53 PM UTC
We are currently experiencing issues with Single and Bulk Publishing/Unpublishing, Releases, Search, and Entries. As a result, customers may observe delays in seeing entries reflected on the entry list page. We are also noticing issues with Webhooks, which may lead to delays or loss of invocations. Our team is actively working to resolve the issue and will share further updates as they become available. Please reach out to Contentstack Support if you require assistance.
-
identified Nov 16, 2025, 11:54 PM UTC
A spike on our third-party service cluster caused Publish/Unpublish requests to queue, impacting Single and Bulk Publishing/Unpublishing, Releases, Search, and Entries. Also, webhooks have been affected. The third-party team has upgraded our cluster, and we are actively monitoring to ensure full functionality is restored.
-
monitoring Nov 17, 2025, 12:08 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Nov 17, 2025, 12:20 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 03, 2025, 07:18 AM UTC
- Resolved
- Nov 03, 2025, 07:25 AM UTC
- Duration
- 6m
Affected: Content Management API
Timeline · 4 updates
-
investigating Nov 03, 2025, 07:18 AM UTC
We are currently experiencing issues with Publishing/Unpublishing and webhook execution. As a result, customers may encounter delays in seeing entries on the entry list page. Our team is actively working to resolve these issues and will provide updates as soon as we have more information. If you experience any difficulties accessing our services, please reach out to our Customer Success Team for assistance.
-
identified Nov 03, 2025, 07:19 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Nov 03, 2025, 07:21 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Nov 03, 2025, 07:25 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 04, 2025, 04:55 AM UTC
- Resolved
- Sep 04, 2025, 06:29 AM UTC
- Duration
- 1h 34m
Affected: Automation API
Timeline · 3 updates
-
investigating Sep 04, 2025, 04:55 AM UTC
We are currently experiencing a service degradation in our AWS North America region for Automate. Customers may encounter delays when executing automations. Our team is investigating the issue.If you encounter any problems while accessing our services, please do not hesitate to contact our Customer Success Team.
-
identified Sep 04, 2025, 05:29 AM UTC
We have identified the root cause of the degradation affecting our Automate service in the AWS North America region. Our team is now implementing a fix. We will provide another update shortly.
-
resolved Sep 04, 2025, 06:29 AM UTC
This incident has been resolved. The fix has been deployed, and our Automate service is now operating normally. All automations are processing without delay. We apologize for any inconvenience this may have caused.
Read the full incident report →
- Detected by Pingoru
- Aug 29, 2025, 03:48 PM UTC
- Resolved
- Aug 29, 2025, 04:14 PM UTC
- Duration
- 25m
Affected: Launch - Content Delivery Network (CDN)
Timeline · 3 updates
-
investigating Aug 29, 2025, 03:48 PM UTC
We are currently experiencing an incident that is impacting the availability and performance of our Launch - AWS NA - Delivery service. Our engineering and security teams are actively working to mitigate the attack and restore normal operations as quickly as possible. You may experience slow loading times, intermittent connectivity, or temporary unavailability during this period. We will provide updates as soon as more information becomes available. Thank you for your patience and understanding.
-
monitoring Aug 29, 2025, 04:01 PM UTC
The recent incident has been mitigated, and all operations have returned to normal. Our team will continue to closely monitor the situation to ensure ongoing stability and performance. Thank you for your patience and support.
-
resolved Aug 29, 2025, 04:14 PM UTC
The issue has been mitigated and services are operating normally. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2025, 02:20 PM UTC
- Resolved
- Jun 17, 2025, 05:14 PM UTC
- Duration
- 2h 54m
Timeline · 5 updates
-
investigating Jun 17, 2025, 01:43 PM UTC
This is to notify that we are currently experiencing issues with our Live Chat service. We are actively working to resolve the issue and will provide updates as they become available. Until then, for any assistance, please reach out to our Support Team at [email protected].
-
investigating Jun 17, 2025, 02:20 PM UTC
Our team is still actively investigating the root cause. We are making progress and will provide another update as soon as new information is available. In the meantime, please continue to direct all support requests to our Support Team at [email protected].
-
investigating Jun 17, 2025, 04:02 PM UTC
We have successfully identified the root cause of the problem. Our engineers are now actively working on implementing a fix. We will send a confirmation once the issue is resolved and the service is stable. For any immediate needs, please continue to reach out to our Support Team at [email protected].
-
monitoring Jun 17, 2025, 04:46 PM UTC
We have implemented a fix for the ongoing issues with our Live Chat service and are currently monitoring the system to ensure stability and complete service restoration. We will provide a final update once we have confirmed the issue is completely resolved.
-
resolved Jun 17, 2025, 05:14 PM UTC
We can now confirm that the issue with our Live Chat service has been fully resolved and the service is stable. The root cause was identified, and a fix was successfully implemented. Thank you for your patience and understanding as we worked to resolve this matter. Our Live Chat is now available for all support inquiries.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2025, 09:35 PM UTC
- Resolved
- Jun 12, 2025, 09:35 PM UTC
- Duration
- —
Affected: Launch - Web ApplicationLaunch - Web ApplicationLaunch - Management APILaunch - Management APILaunch - Content Delivery Network (CDN)Launch - Content Delivery Network (CDN)Launch - Edge ServicesLaunch - Edge ServicesLaunch - Web ApplicationLaunch - Web ApplicationLaunch - Management APILaunch - Management APILaunch - Content Delivery Network (CDN)Launch - Content Delivery Network (CDN)Launch - Web ApplicationLaunch - Web ApplicationLaunch - Edge ServicesLaunch - Edge ServicesLaunch - Management APILaunch - Management APILaunch - Content Delivery Network (CDN)Launch - Content Delivery Network (CDN)Launch - Edge ServicesLaunch - Edge Services
Timeline · 5 updates
-
investigating Jun 12, 2025, 06:38 PM UTC
Please be informed that sites hosted on Contentstack Launch are currently experiencing 500 errors due to an ongoing Cloudflare outage. Our CDN provider is currently experiencing an issue that may be impacting site performance or availability. Our team is actively working with Cloudflare to expedite resolution. We appreciate your understanding and patience during this time. For any urgent concerns, please don’t hesitate to contact our Customer Success Team.
-
investigating Jun 12, 2025, 07:12 PM UTC
Our team is actively monitoring the state of the Cloudflare Outage. We will continue to provide updates as more information becomes available. You can also track real-time updates on the Cloudflare Status Page. https://www.cloudflarestatus.com/
-
monitoring Jun 12, 2025, 08:20 PM UTC
Cloudflare services have begun to recover, and Launch sites appear to be gradually coming back online. Cloudflare is actively working to fully restore stability. We’re closely monitoring the situation and will share updates as things progress.
-
monitoring Jun 12, 2025, 09:10 PM UTC
Launch sites have been fully recovered as services have resumed from Cloudflare. We are closely monitoring the situation and will share updates as it progresses.
-
resolved Jun 12, 2025, 09:35 PM UTC
Earlier today, there was an unexpected period of downtime with our Contentstack platform. Around 2 PM ET, we experienced an upstream outage that affected our Launch service. This stemmed from technical issues with our CDN provider (Cloudflare), a service we rely on for speed and reliability. We know this disruption was likely very frustrating to you, as it was to us. Cloudflare service full availability took 3 hours 12 minutes to return, and Contentstack Launch service was fully restored immediately. Although it's rare to see major services go down, it did happen this time - and we're continuing to attempt to learn more about what happened here (as are many other Cloudflare customers). Thank you for your patience and continued trust. We will review our system to improve the reliability of our CDN provider. We’re committed to delivering the dependable, enterprise-grade experience you expect. If you have any concerns or feedback, we are here to help.
Read the full incident report →
- Detected by Pingoru
- May 27, 2025, 01:43 PM UTC
- Resolved
- May 27, 2025, 08:31 PM UTC
- Duration
- 6h 47m
Affected: Launch - Edge ServicesLaunch - Edge ServicesLaunch - Edge ServicesLaunch - Edge ServicesLaunch - Edge ServicesLaunch - Edge Services
Timeline · 5 updates
-
identified May 27, 2025, 01:43 PM UTC
We're currently experiencing an issue with Launch Edge Functions deployments. If your latest deployment shows "FAILED" status and your project contains Launch Edge Functions, please do not attempt to redeploy until further notice. Redeploying under these conditions could potentially disrupt your live website functionality. Our team is actively working to resolve this issue, and we appreciate your patience during this time. If your latest deployment is not in a "FAILED" state, then no issue is expected.
-
identified May 27, 2025, 03:14 PM UTC
We have identified the issue and are still investigating this issue and will provide an update as soon as more information becomes available.
-
identified May 27, 2025, 04:33 PM UTC
We are still investigating this issue and will provide an update as soon as more information becomes available.
-
monitoring May 27, 2025, 08:29 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 27, 2025, 08:31 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 12, 2025, 07:30 PM UTC
- Resolved
- May 12, 2025, 07:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 13, 2025, 07:04 AM UTC
We experienced issues with our email service in the AWS NA region between May 12, 13:30 MDT and May 13, 00:30 MDT, which resulted in delays or failures in email delivery for some users. If you haven’t received expected emails, we recommend resending them. Our team has identified and resolved the issue. No other services were impacted. For any questions or assistance, please contact our Customer Success Team.
Read the full incident report →