StatusCast Outage History

Started Sep 05, 2026, 01:00 PM UTC· resolved Sep 05, 2026, 01:00 PM UTC

1. investigating Sep 05, 2025, 01:00 PM UTC

   Our team is excited to announce the official rebrand of 4me to the name Xurrent. Our refreshed look and updated identity capture the essence of our business, our platform, our vision, and its value. Our new look is being rolled out in a new website, marketing materials, and the Xurrent application! Important Dates: 5 September (today!) A press release announced the rebrand launch. Our new Website is live! Check it out at www.xurrent.com. 7 September All communications from Xurrent will emanate from our new domain, www.xurrent.com. This means emails and any other official communications. What Does This Mean for You? Starting now you’ll see our new branding in emails, on the website, and in other communications. Rest assured, this change won’t affect your current services. Thanks for being a valued part of the Xurrent (formerly 4me) family. While our appearance is evolving, our dedication to providing top-quality products and exceptional customer support remains unchanged. Our mission and values continue to drive us as we grow towards a dynamic and collaborative future.

Read the full incident report →

Started Aug 01, 2026, 05:45 PM UTC· resolved Aug 01, 2026, 05:45 PM UTC

1. investigating Aug 01, 2025, 05:45 PM UTC

   As of August 1st, 2024 we have removed the link to the Legacy Incident Editor from the admin portal to ensure that users maintain a unified experience and are able to take advantage of all of our latest improvements to the incident creation process.

Read the full incident report →

Started Jul 30, 2026, 01:30 PM UTC· resolved Aug 01, 2026, 05:07 PM UTC

1. investigating Jul 30, 2025, 01:30 PM UTC

   StatusCast engineers were alerted earlier that some users were experiencing sporadic issues attempting to connect to the status page and admin portal. Our hosting provider, Microsoft Azure, has alerted us via their status page that they are experiencing some network issues globally. We will provide an update as soon as more information is available.

2. monitoring Jul 30, 2025, 02:44 PM UTC

   Access to status pages has remained stable and Azure has updated their status indicating failover processes have been engaged to improve their service availability. StatusCast's engineers will continue to watch this closely and will post additional updates as necessary.

3. monitoring Jul 30, 2025, 08:47 PM UTC

   StatusCast's application has continued to remain stable. Our engineers will continue to watch the system closely as Microsoft has not fully closed out the event on their side. For more specific details on Azure's issue please refer to their status page. We will provide additional updates as necessary.

4. resolved Jul 30, 2025, 10:00 PM UTC

   Microsoft has closed the issue on their side and StatusCast's platform continues to operate as expected. Once Microsoft has published more details on this we will provide here in the form of an RCA.

5. resolved Aug 01, 2025, 05:07 PM UTC

   FROM MICROSOFT: Mitigation Statement - Azure Front Door Issues accessing a subset of Microsoft services Tracking ID: KTY1-HW8 What happened? Between approximately at 11:45 UTC and 19:43 UTC on 30 July 2024, a subset of customers may have experienced issues connecting to a subset of Microsoft services globally. Impacted services included Azure App Services, Application Insights, Azure IoT Central, Azure Log Search Alerts, Azure Policy, as well as the Azure portal itself and a subset of Microsoft 365 and Microsoft Purview services. What do we know so far? An unexpected usage spike resulted in Azure Front Door (AFD) and Azure Content Delivery Network (CDN) components performing below acceptable thresholds, leading to intermittent errors, timeout, and latency spikes. While the initial trigger event was a Distributed Denial-of-Service (DDoS) attack, which activated our DDoS protection mechanisms, initial investigations suggest that an error in the implementation of our defenses amplified the impact of the attack rather than mitigating it. How did we respond? Customer impact began at 11:45 UTC and we started investigating. Once the nature of the usage spike was understood, we implemented networking configuration changes to support our DDoS protection efforts, and performed failovers to alternate networking paths to provide relief. Our initial network configuration changes successfully mitigated majority of the impact by 14:10 UTC. Some customers reported less than 100% availability, which we began mitigating at around 18:00 UTC. We proceeded with an updated mitigation approach, first rolling this out across regions in Asia Pacific and Europe. After validating that this revised approach successfully eliminated the side effect impacts of the initial mitigation, we rolled it out to regions in the Americas. Failure rates returned to pre-incident levels by 19:43 UTC - after monitoring traffic and services to ensure that the issue was fully mitigated, we declared the incident mitigated at 20:48 UTC. Some downstream services took longer to recover, depending on how they were configured to use AFD and/or CDN. What happens next? Our team will be completing an internal retrospective to understand the incident in more detail. We will publish a Preliminary Post Incident Review (PIR) within approximately 72 hours, to share more details on what happened and how we responded. After our internal retrospective is completed, generally within 14 days, we will publish a Final Post Incident Review with any additional details and learnings. To get notified when that happens, and/or to stay informed about future Azure service issues, make sure that you configure and maintain Azure Service Health alerts – these can trigger emails, SMS, push notifications, webhooks, and more: https://aka.ms/ash-alerts. For more information on Post Incident Reviews, refer to https://aka.ms/AzurePIRs. Finally, for broader guidance on preparing for cloud incidents, refer to https://aka.ms/incidentreadiness.

Read the full incident report →

Started Jul 22, 2026, 04:30 PM UTC· resolved Jul 22, 2026, 04:30 PM UTC

1. investigating Jul 22, 2025, 04:30 PM UTC

   StatusCast and 4me’s support team are ready to take the next step in migrating our support services from StatusCast’s legacy ticketing system to using 4me directly for all change requests and incidents. This next step in integrating StatusCast’s operations to 4me will ultimately provide you with much more insight into requests you submit and their status. What is changing? On Wednesday, July 24th 2024 StatusCast’s support portal will be shifted to https://4me-statuscast-portal.4me.com/, this self service portal will be your new resource to submit new tickets and view the status of any existing ones that you have submitted. This new portal will give you a more accurate status of the ticket, and in the event that you request a change or run into an issue that requires development work, you will have visibility into the status of that from a development to a QA, to a production perspective. Also, customers will be able to find answers to their questions by walking through the portal that contains a knowledge base which will be extended as we go along. We are very excited to bring this extended visibility to our customers as we believe it’s a major step forward in the support that we provide. As a result of this change, emailing [email protected] will no longer open tickets. You will need to access the self-service portal to submit and access support requests. A link to this self service portal has been added to StatusCast’s admin portal and you can access it by selecting the Settings > Help Center > Support Tickets Existing StatusCast administrators have been granted access to this new portal. To access the StatusCast Portal, go to https://xurrent-statuscast-portal.xurrent.com/ and start with ‘Forgot your 4me password?’(1) so that you can get sent an email to register your support portal password. If you do not get an email while doing this you may not have been granted automated access, in that case you can self register by clicking “Register as New User”(2): The StatusCast Portal requires you to use an email address and to set up a password with 18 characters.

Read the full incident report →

Started Jul 05, 2026, 01:00 PM UTC· resolved Jul 05, 2026, 01:00 PM UTC

1. investigating Jul 05, 2025, 01:00 PM UTC

   In keeping with our commitment to security and transparency we wanted to inform you that our provider for SMS, Twilio, has alerted our security team to an incident that occurred. Below is the statement we received from Twilio which gives a detailed account of the incident and what has been done: —-------------------------------------- Twilio has been notified by one of our backup carriers, iBasis, that IdentifyMobile inadvertently exposed certain SMS-related data sent by iBasis publicly on the internet that included personal data. We are writing to inform you that some of your personal data and non-personal data (such as data related to marketing campaigns) was accessed by a security research group while it was publicly exposed by IdentifyMobile. Although this incident was outside Twilio’s control, we take it very seriously and are committed to helping you understand the full impact. What do you need to know? In order to deliver messages in specific regions, Twilio relies on numerous carriers to maximize deliverability to their final destinations. Twilio was notified that iBasis (a Twilio backup carrier) had used IdentifyMobile (iBasis's further backup carrier) who inadvertently enabled public access on an AWS S3 Bucket during development work. Information contained in this bucket was made public from May 10-15, 2024, and accessed between May 13-14, 2024. Based on a joint investigation between IdentifyMobile and Amazon AWS, we learned that a portion of this data was accessed by the Chaos Computing Club (CCC). CCC is a security research group that identifies security issues; CCC has confirmed that they are not holding any data downloaded from the AWS S3 Bucket. We do not have evidence that allows us to confirm that no other third party accessed the data. Twilio does not own this bucket, and none of our systems have been compromised in connection with this data exposure. This incident was the result of actions taken by IdentifyMobile and outside of Twilio’s control. While we continue collaborating with these carriers to bring you the most accurate information regarding this exposure, the portion of data exposed by IdentifyMobile related to SMS sent between January 1, 2024 and May 15, 2024, and included: Mobile number SMS message content SMS Sender ID SMS Timestamp What have we done so far? Twilio initiated our incident response process to rapidly investigate this matter. Twilio escalated this issue to the iBasis executive team; subsequently, we’ve done an analysis on the data logs that were compromised to provide you with as much information as possible. Out of an abundance of caution, we have ceased sending traffic to iBasis where possible. iBasis informed Twilio that it has stopped routing with IdentifyMobile. We will continue working with our 3rd party carriers to get you any additional details that may arise from this incident. What do you need to do? We recommend reviewing the SMS traffic you sent between January 1, 2024 and May 15, 2024, discussing the implications of an exposure with your internal team(s) and deciding if you need to engage with impacted individuals. If you need additional information regarding this incident, we are here to support you throughout this situation. We deeply regret any inconvenience this may cause and appreciate your understanding and cooperation. —-------------------------------------- What has StatusCast done? Once StautsCast’s security team was alerted an audit was performed to try and determine the potential impact this had on our service. Based on Twilio’s report it is possible that some notifications sent through StatusCast’s service would have been sent using the iBasis carrier. Based on the report data would have included the recipient's phone number as well as the SMS message. SMS notifications in StatusCast are designed to be brief and to drive users to the status page. SMS messages do not include recipients name or other personal identifiable information(PII). As always in StatusCast you have the right to choose whether SMS notifications are sent or not. SMS options can be controlled in the Settings and Integration sections of the application if you wish to review your configurations. At this time there are no additional action items for StatusCast to take in regards to its application or infrastructure, however we will maintain close communication with Twilio and if any additional information is released we will pass it along through our own status page. StautsCast has partnered with Twilio for years and they have maintained a strong commitment to security and transparency. We will take that as well as this incident into consideration as we continue to offer SMS notifications in the application. If you have any additional questions please reach out to us at [email protected]

Read the full incident report →

Started Jun 07, 2026, 01:00 PM UTC· resolved Jun 07, 2026, 01:00 PM UTC

1. investigating Jun 07, 2025, 01:00 PM UTC

   Following the acquisition by 4me, we have been preparing to integrate StatusCast’s support operations into 4me’s infrastructure. By combining our support operations with 4me’s, our customers will have the advantage of 24x7 support and the number of available representatives will almost quadruple. To take the first step forward in officially merging these teams we will be removing the live chat option available in the admin portal starting on Friday June 7th, 2024. You can continue to be to communicate with support through email([email protected]) or by accessing our current support portal. In the coming months, you will notice several changes in how StatusCast's support is provided. This will involve the introduction of a new and improved support portal for tracking any change requests or issues that you have logged with support. Additionally, more tools and auditing information will be made available in the application, and there will be an increase in the help and knowledge resources accessible directly. We are very excited to be expanding our support offering with 4me and know that it will ultimately help our community of valued customers and users!

Read the full incident report →

Started Apr 22, 2026, 02:21 AM UTC· resolved Oct 02, 2026, 02:53 AM UTC

1. identified Oct 29, 2025, 04:01 PM UTC

   We understand there is a global outage for MS Azure. Our team is aware of the issue. Status pages and the admin portal may not be accessible. We apologize for any inconvenience.

2. investigating Oct 29, 2025, 06:17 PM UTC

   The Microsoft Azure outage is still affecting cnames for domains, but not the status.page domain. You may use https://yourpagename.status.page to access your page and the admin portal login. We apologize for any inconvenience.

3. resolved Oct 30, 2025, 05:40 AM UTC

   Services are operational now. This event has been resolved.

Read the full incident report →

Started Apr 04, 2026, 01:37 PM UTC· resolved Apr 04, 2026, 06:30 PM UTC

1. investigating Apr 04, 2026, 01:37 PM UTC

   Engineers have been alerted to delays in notification processing. We are currently investigating and will follow-up with further details.

2. resolved Apr 04, 2026, 06:30 PM UTC

   At 9:37 AM EDT an incident occurred which delayed incident notification processing. The incident was fully resolved by 2:30 PM EDT. More details on the root cause will follow. Subscribers would still see status pages as expected, but incident notification would have been delayed.

Read the full incident report →

Started Apr 04, 2026, 12:19 AM UTC· resolved Apr 05, 2026, 09:00 PM UTC

1. identified Apr 04, 2026, 12:19 AM UTC

   At approximately 8:19PM EDT, StatusCast’s engineers were alerted that some status page and admin applications were inaccessible. The team identified that its hosting partner, Microsoft, was experiencing some issues in its US East region related to app services and SQL databases connections. As of 9:03PM EDT services have been restored and StatusCast’s team is currently working with Microsoft to fully investigate the incident. Once the team has completed it’s investigation we will follow up with an RCA. At this time StatusCast should be operating fully as expected, if you continue to have any further issues please contact us at [email protected]

2. resolved Apr 04, 2026, 01:03 AM UTC

   As of 9:03PM EDT services have been restored and StatusCast’s team is currently working with Microsoft to fully investigate the incident. Once the team has completed it’s investigation we will follow up with an RCA.

3. resolved Apr 05, 2026, 09:00 PM UTC

   In working with Microsoft, StatusCast’s team confirmed that the disruption was due to an outage with SQL Databases located in Azure’s US East region which is where StatusCast is primarily hosted: StatusCast itself was impacted by this outage from approximately 8:19 PM EDT and had fully recovered by 9:03 PM EDT. StatusCast’s team will continue to work closely with Microsoft to further optimize its offering to help ensure that impact of service provider outages is as minimal as possible.

Read the full incident report →

Started Apr 02, 2026, 01:00 PM UTC· resolved Apr 02, 2026, 01:00 PM UTC

1. investigating Apr 02, 2026, 01:00 PM UTC

   We are very excited to announce that StatusCast has been acquired by 4Me! Since 2013 we have been working hard to close the gap between service outages and those who are impacted, and this acquisition is one large step further in our journey of providing critical information to those who need it most. The inclusion of StatusCast's features will aid 4Me in it's mission to modernize service management for organizations. Click here to read more!

Read the full incident report →

Started Mar 08, 2026, 03:01 PM UTC· resolved Mar 08, 2026, 04:22 PM UTC

1. investigating Mar 08, 2026, 03:01 PM UTC

   We are experiencing SMS delivery delays when sending messages to Telefonica Network In Mexico. Our engineers are working with our carrier partner to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.

2. investigating Mar 08, 2026, 03:12 PM UTC

   We are continuing our investigation and have discovered SMS Latin America is affected by SMS delivery delays when sending messages to Telefonica Network in Mexico.

3. monitoring Mar 08, 2026, 04:22 PM UTC

   We are observing recovery in SMS delivery delays when sending messages to Telefonica Network in Mexico. We will continue monitoring the service to ensure a full recovery. We will provide another update in 2 hours or as soon as more information becomes available.

Read the full incident report →

Started Feb 27, 2026, 02:53 PM UTC· resolved Feb 27, 2026, 02:53 PM UTC

1. investigating Feb 27, 2026, 02:53 PM UTC

   Xurrent Acquires Zenduty SANTA BARBARA, Calif., February 27, 2025 – Xurrent™, the service and operations management platform purpose-built for modern enterprises and managed services providers, has acquired Zenduty, a leader in cutting-edge incident and alert management solutions. This acquisition marks another significant milestone in Xurrent’s ongoing journey to transform IT and redefine how organizations handle major incidents from start to finish. Phil Christianson, Xurrent’s Chief Product Officer, remarked, “Xurrent is excited to announce a major advancement in our ITOM capabilities. Our StatusCast acquisition last April enhanced our platform to dramatically improve organizations’ abilities to communicate details of major incidents. Now, with the acquisition of Zenduty, we will enable IT to automate and streamline incident resolution and root cause remediation, ensuring faster fixes and preventing repeat incidents.” Zenduty is an innovator in incident and alert management. The platform has earned a reputation for enabling incident commanders to swiftly gather the right teams into a virtual war room, triage issues and drive resolution rapidly. By integrating Zenduty with Xurrent’s robust IT Service Management (ITSM) capabilities, customers will enjoy comprehensive, end-to-end IT operations and service management capabilities within a single, unified platform. This integration ensures that when a major incident occurs, organizations can not only manage and resolve the issue swiftly but also implement a structured approach to prevent it from recurring. Zenduty empowers incident commanders to coordinate response teams effectively, while Xurrent’s ITSM platform ensures tasks are assigned to the right teams, tracked and completed on time, driving continuous improvement between incidents. By integrating Zenduty with Xurrent’s ITSM platform, organizations gain the following key benefits: Automating virtual war rooms for rapid incident response. Managing and resolving incidents swiftly. Ensuring accountability for post-incident remediation task completion. “The combination of Zenduty’s top-quality incident and alert management tools with the power of Xurrent’s world-class IT Service Management, will enable our customers to fully take control of their IT operations and service management with a more modern, connected and automated approach,” said Kevin McGibben, Xurrent CEO. “With Xurrent, teams take action sooner, resolve incidents faster, and ensure they never happen again — completing critical tasks with efficiency, accuracy and full accountability.” About Xurrent Xurrent™ streamlines ITSM and IT Operations Management with AI-powered automation. Our platform simplifies workflows, enhances collaboration, and boosts productivity. Built for scalability, Xurrent seamlessly adapts to the evolving needs of modern enterprises, minimizing effort while maximizing efficiency. Learn more at www.xurrent.com. About Zenduty Zenduty is an end-to-end incident and on-call management solution that provides cross-channel alerts via email, phone, SMS, Slack, and Microsoft Teams to ensure your team is promptly notified during service downtimes. Designed to enhance incident response efficiency, Zenduty offers features such as customizable alerting, on-call scheduling, and seamless integrations with over 150 tools, including Datadog, Jira, and Slack. Organizations utilizing Zenduty have reported significant improvements, including reduced downtime, a 50% enhancement in Mean Time to Acknowledge (MTTA) and Mean Time to Resolve (MTTR), and cost savings. For more information, visit www.zenduty.com. Press Release: https://www.xurrent.com/press-release/xurrent-acquires-zenduty-completing-the-incident-response-and-remediation-loop/

Read the full incident report →

Started Feb 23, 2026, 02:00 PM UTC· resolved Feb 24, 2026, 02:00 AM UTC

1. investigating Feb 23, 2026, 02:00 PM UTC

   StatusCast engineers noted some processing degradation that may have caused delays in some actions.

2. resolved Feb 24, 2026, 02:00 AM UTC

   The team has identified the issue.

Read the full incident report →

Started Feb 04, 2026, 10:30 PM UTC· resolved Feb 05, 2026, 02:00 AM UTC

1. investigating Feb 04, 2026, 10:30 PM UTC

   StatusCast engineers noted a background processing degradation that caused delays in some actions from being completed in a timely fashion.

2. resolved Feb 05, 2026, 02:00 AM UTC

   This has been resolved. We apologize for any inconvenience.

Read the full incident report →

Started Dec 29, 2025, 11:00 PM UTC· resolved Dec 29, 2025, 11:00 PM UTC

1. investigating Dec 29, 2025, 11:00 PM UTC

   The domain for accessing StatusCast's support portal has been updated to https://xurrent-statuscast-portal.xurrent.com/. While the old domain will redirect to our current one we recommend updating your bookmarks appropriately.

Read the full incident report →

Started Nov 25, 2025, 07:24 PM UTC· resolved Nov 25, 2025, 10:06 PM UTC

1. investigating Nov 25, 2025, 07:24 PM UTC

   StatusCast engineers identified a backup in its background processing that is causing delays in some actions from being completed in a timely fashion.

2. investigating Nov 25, 2025, 08:32 PM UTC

   Engineers have determined the root cause of the backup in processing. During this time we have scaled out the service that is responsible to help clear out the remaining items faster.

3. resolved Nov 25, 2025, 10:06 PM UTC

   Services should be operating as expected.

Read the full incident report →

Started Nov 16, 2025, 01:00 AM UTC· resolved Nov 27, 2025, 08:00 PM UTC

1. investigating Nov 16, 2025, 01:00 AM UTC

   StatusCast engineers have been alerted to a possible performance impacting event affecting status pages and the admin application response times. This event is not impacting notification processing. We apologize for this inconvenience and will provide an update shortly.

2. resolved Nov 18, 2025, 07:00 PM UTC

   All services should be fully functional and performing regularly.

3. resolved Nov 27, 2025, 08:00 PM UTC

   StatusCast's engineers determined that at approximately 8:00PM EST on November 15th 2024, several of StatusCast's application servers experienced an issue that caused the response time to spike. StatusCast's infrastructure in Azure is designed to perform scaling procedures for services under duress, and for all but one of the application services in question this was done successfully restoring the service to an acceptable level of performance. The remaining application service in the EU did not correctly scale and stayed in a degraded state for multiple days. On November 18th engineers were alerted that some customers were still experiencing load time delays and at that point the last server was corrected. After this event occurred StatusCast's DevOps team began an audit of all scaling procedures to ensure that application services across our Azure operational regions adhere to a consistent scaling process and to ensure that monitoring is properly deployed to all services as having a single application service remaining in a degraded state for days is not acceptable.

Read the full incident report →

Started Nov 05, 2025, 11:42 PM UTC· resolved Nov 05, 2025, 11:42 PM UTC

1. identified Oct 29, 2025, 04:04 PM UTC

   Between 15:45 UTC on 29 October and 00:05 UTC on 30 October 2025, customers and Microsoft services leveraging Azure Front Door (AFD) experienced latencies, timeouts, and errors. The AFD & CDN delivery services continue to be stable and are running as expected. Out of an abundance of caution, all service management operations (including creation, updates, deletions, and purges) to AFD via portal or APIs continue to remain temporarily suspended. We are working on a comprehensive plan to gradually reenable these in a phased approach, while ensuring the platform remains stable. We will continue to share periodic updates as we make progress. Next Update will be by 01:00 UTC on 31 Oct 2025 or sooner.

2. monitoring Oct 31, 2025, 01:08 AM UTC

   The Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated at 00:05 UTC on 30 October 2025 and remains at normal operating levels. As we complete our full investigation and implement further safe checks, service management operations (create, update, delete, purge, etc.) are temporarily unavailable. We will notify customers once the restriction is lifted, and we will be sending periodic communication on the progress. Next Update will be by 19:00 UTC on 31 Oct 2025 or sooner as event warrant.

3. monitoring Oct 31, 2025, 08:03 PM UTC

   Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated at 00:05 UTC on 30 October 2025 and remain at normal operating levels. As we complete our full investigation and implement further safe checks, service management operations (create, update, delete, purge, etc.) are temporarily unavailable. We are working to provide an ETA on when we can lift the restriction and will continue sending periodic communication on the progress via Azure Service Health. The next update will be by 19:00 UTC on 01 November 2025 or sooner as events warrant.

4. monitoring Oct 31, 2025, 09:35 PM UTC

   Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated at 00:05 UTC on 30 October 2025 and remain at normal operating levels. As we complete our full investigation and implement further safe checks, service management operations (create, update, delete, purge, etc.) are temporarily unavailable. Our current expectation is to lift the restriction on 05 November 2025, and we will continue sending periodic communication on the progress via Azure Service Health. The next update will be by 19:00 UTC on 01 November 2025 or sooner as events warrant.

5. monitoring Nov 01, 2025, 07:41 PM UTC

   Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated at 00:05 UTC on 30 October 2025 and remain at normal operating levels. As we complete our full investigation and implement further safe checks, service management operations (create, update, delete, purge, etc.) are temporarily unavailable. Our current expectation remains to lift the restriction on 05 November 2025, and we will continue sending periodic communication on the progress via Azure Service Health. The next update will be by 19:00 UTC on 02 November 2025 or sooner as events warrant.

6. monitoring Nov 02, 2025, 08:31 PM UTC

   Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated at 00:05 UTC on 30 October 2025 and remain at normal operating levels. As we complete our full investigation and implement further safe checks, service management operations (create, update, delete, purge, etc.) are temporarily unavailable. Our current expectation remains to lift the restriction on 05 November 2025, and we will continue sending periodic communication on the progress via Azure Service Health. The next update will be by 03:00 UTC on 03 November 2025 or sooner as events warrant.

7. monitoring Nov 02, 2025, 09:07 PM UTC

   Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated at 00:05 UTC on 30 October 2025 and remain at normal operating levels. As we complete our full investigation and implement further safe checks, service management operations (create, update, delete, purge, etc.) are temporarily unavailable. Our current expectation remains to lift the restriction on 05 November 2025, and we will continue sending periodic communication on the progress via Azure Service Health. The next update will be by 03:00 UTC on 03 November 2025 or sooner as events warrant.

8. monitoring Nov 03, 2025, 03:02 AM UTC

   Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated at 00:05 UTC on 30 October 2025 and remain at normal operating levels. As we complete our full investigation and implement further safe checks, service management operations (create, update, delete, purge, etc.) are temporarily unavailable. Our current expectation remains to lift the restriction on 05 November 2025, and we will continue sending periodic communication on the progress via Azure Service Health. The next update will be by 19:00 UTC on 03 November 2025 or sooner as events warrant.

9. monitoring Nov 04, 2025, 12:14 AM UTC

   Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated at 00:05 UTC on 30 October 2025 and remain at normal operating levels. As part of completing our full investigation and safe checks, performing service management operations (create, update, delete, purge, etc.) were made temporarily unavailable. Restrictions on service management operations have been removed for this Azure subscription ID. Please allow approximately 30–40 minutes for changes to fully propagate to edge sites. We expect all restrictions across subscriptions, including other subscriptions under your tenant, to be lifted by 05 November 2025. Updates on progress will continue via Azure Service Health. The next update will be provided by 22:00 UTC on 04 November 2025, or sooner if circumstances change.

10. monitoring Nov 04, 2025, 12:25 AM UTC

    We acknowledge that previous communication may have contained information meant for another list of customers. We apologize for the inconvenience and request you to note the following. Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated at 00:05 UTC on 30 October 2025 and remain at normal operating levels. As we complete our full investigation and implement further safe checks, service management operations (create, update, delete, purge, etc.) are temporarily unavailable. The workflow to manage and rotate Bring Your Own Certificate (BYOC) certificates has been re-enabled. We will monitor the progress of working through the queue of necessary rotations. We will continue to provide regular updates on progress. Our current expectation remains to lift the restriction on 05 November 2025. The next update will be by 22:00 UTC on 04 November 2025 or sooner as events warrant.

11. monitoring Nov 04, 2025, 03:27 AM UTC

    In preparation for lifting the service management restrictions, an incorrect communication was sent indicating an early removal. Our current date for lifting all control plane restrictions remains 05 November 2025. The next update will be provided by 22:00 UTC on 04 November 2025, or sooner.

12. monitoring Nov 04, 2025, 10:22 PM UTC

    Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated at 00:05 UTC on 30 October 2025 and remain at normal operating levels. As we complete our full investigation and implement further safe checks, service management operations (create, update, delete, purge, etc.) are temporarily unavailable. We continue to hit our milestones toward the expectation to lift this restriction on 05 November 2025. The next update will be sent to confirm once this has happened, or sooner if events warrant.

13. identified Nov 05, 2025, 11:36 PM UTC

    Latest Update: As of 23:00 UTC on 5 November, 2025 restrictions on Azure Front Door (AFD) and Content Delivery Network (CDN) service management operations have been removed. You may now resume normal operations on the AFD service management plane. For enhanced safety and protection, we have extended the configuration propagation times up to 45 minutes. Additional platform enhancements which are underway are expected to optimize the propagation times further. Previous Context: Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated by 00:05 UTC on 30 October 2025 and remain at normal operating levels. We previously notified you that, as part of completing our full investigation and safe checks, performing service management operations (create, update, delete, purge, etc.) were temporarily restricted. This notification is to confirm that those temporary restrictions no longer apply. Next Steps: As mentioned in our Preliminary PIR we are completing an internal retrospective to understand the incident in more detail. Once this is completed, which is expected within approximately 7 days, we will publish our final Post Incident Review (PIR) - including a link to register for an Azure Incident Retrospective livestream, discussing the incident and our learnings. Azure Front Door frequently asked questions (FAQ) | Microsoft Learn

14. resolved Nov 05, 2025, 11:42 PM UTC

    Latest Update: As of 23:00 UTC on 5 November, 2025 restrictions on Azure Front Door (AFD) and Content Delivery Network (CDN) service management operations have been removed. You may now resume normal operations on the AFD service management plane. For enhanced safety and protection, we have extended the configuration propagation times up to 45 minutes. Additional platform enhancements which are underway are expected to optimize the propagation times further. Previous Context: Azure Front Door (AFD) and Content Delivery Network (CDN) delivery data planes were fully mitigated by 00:05 UTC on 30 October 2025 and remain at normal operating levels. We previously notified you that, as part of completing our full investigation and safe checks, performing service management operations (create, update, delete, purge, etc.) were temporarily restricted. This notification is to confirm that those temporary restrictions no longer apply. Next Steps: As mentioned in our Preliminary PIR we are completing an internal retrospective to understand the incident in more detail. Once this is completed, which is expected within approximately 7 days, we will publish our final Post Incident Review (PIR) - including a link to register for an Azure Incident Retrospective livestream, discussing the incident and our learnings. Azure Front Door frequently asked questions (FAQ) | Microsoft Learn

Read the full incident report →