Incidents reported on status page for MODX Cloud https://status.modxcloud.com/ https://d1lppblt9t2x15.cloudfront.net/logos/a4e4303817bafbf281c037119d727983.png https://status.modxcloud.com/ en https://status.modxcloud.com/incident/845307 Wed, 18 Mar 2026 19:10:00 -0000 https://status.modxcloud.com/incident/845307#917f7cfc20006449fac4ea91c2f162ab61cf6b83dac5a728c3c74c3649ad1b48 # Service Incident Report - March 9, 2026 ## Summary On March 9, 2026, MODX Cloud experienced an outage affecting all customer platforms between 9:26 AM and 1:27 PM Central Time (approximately 4 hours). This incident was caused by our infrastructure provider incorrectly changing the network configuration, blocking public Internet access to our servers. Service was restored without data loss beginning at 10:18 AM. We are working with our vendor on additional proactive measures and processes to prevent similar future issues. ## What Happened Our infrastructure provider introduced a new automated self-serve platform in February. An error in this platform failed to record cleared payments. Despite our account being in good standing, this triggered an automated suspension of network access which incorrectly flagged our account as past due. This automated suspension occurred despite our account having explicit instructions requiring contact with both our account representative and our operations team prior to any service changes not initiated by our operations team. No account status notifications were sent via email or phone to us or to our account representative. We have confirmed this issue affected multiple customers. When the outage began, our team immediately contacted our infrastructure provider's account representative, who confirmed he was unaware of any account problems, and opened a Severity 1 ticket with support. After escalation, the provider confirmed they had received our payment but failed to process it correctly. ## Timeline (Central Time) **9:26 AM** - Outage detected, all platforms offline **9:39 AM** - Infrastructure provider's account manager contacted **10:09 AM** - Provider confirmed payment located, began restoration **10:18 AM** - Public Platforms restored (~52 minutes) **11:44 AM** - Private Server restoration began (~2.5 hours after detection) **1:27 PM** - All services confirmed operational (~4 hours) **1:39 PM** - Final platform recovery completed ## Impact - All MODX Cloud customers and sites were affected - Sites were unavailable for 1-4 hours depending on platform type - No data loss or corruption occurred - Recovery required extensive manual intervention by our team ## What We Did Our team responded immediately: - Contacted our infrastructure provider within 13 minutes of detection - Escalated through multiple channels when initial response was inadequate - Manually restored application services as infrastructure came back online - Verified all platforms were operational before declaring resolution ## Root Cause This outage was entirely outside our control and resulted from our infrastructure provider's internal payment processing failure. We had paid our account in full and on time. The provider has acknowledged this was their error. ## What We're Doing to Prevent This We are taking the following actions: **Immediate:** - Demanded a formal incident review from our infrastructure provider (ongoing) - Required a revision of their escalation procedures for mission-critical accounts **Short-term:** - Implement additional account monitoring and notification systems independent of the vendor's tooling - Establish redundant communication channels and methods with our provider - Evaluating multi-provider redundancy options to reduce single-point-of-failure risk **Long-term:** - Comprehensive infrastructure diversification assessment - Evaluate failover capabilities across multiple providers ## Our Commitment This incident has shown us that even paid, current accounts with major publicly traded infrastructure providers are vulnerable to administrative errors beyond our control. While we cannot prevent our providers from making mistakes, we are committed to: - Reducing recovery time through better processes and redundancy - Improving our ability to detect and respond to provider-side issues - Ensuring this type of extended outage cannot happen again We take full accountability for the impact this had on your operations, regardless of the cause. Your trust in MODX Cloud is our highest priority. ## Questions or Concerns If you have questions about this incident or how it affected your specific services, please contact our support team or reach out to me directly. We appreciate your patience and understanding during this incident. Thanks, The MODX Cloud Team https://status.modxcloud.com/incident/845307 Mon, 09 Mar 2026 18:27:00 -0000 https://status.modxcloud.com/incident/845307#fdbbead9f4c45802611e4f1449233f8ef5329c316d8821e914a2e2df9eeeb5bd All services are now back online. ## What Happened? A configuration change made in error by our infrastructure provider disabled network access for all platforms. Our platforms and systems were unaffected. Once we identified the issue, we contacted our provider to rectify the situation. ## Next Steps We're working with our provider to determine the events and actions that led to this outage. If you have questions or there are any issues with your individual sites, please do not hesitate to contact us at support@modxcloud.com. https://status.modxcloud.com/incident/845307 Mon, 09 Mar 2026 16:54:00 -0000 https://status.modxcloud.com/incident/845307#71b1727aad3562fe69a1f2f8e3f5119c8ea2ae1402d99a9de6a95f21092c0cfa We're still making some adjustments to bring some of the customer Private Servers back online. https://status.modxcloud.com/incident/845307 Mon, 09 Mar 2026 16:41:00 -0000 https://status.modxcloud.com/incident/845307#9e9fe56dd019b8126d3c48e9baddb6dbe949a3e2b16ebea5975929648521cebc Customer Private Servers are coming back online. The networking issue has been resolved and all sites and servers should be available normally over the next few minutes. Please let us know if your sites are not online properly via support@modxcloud.com https://status.modxcloud.com/incident/845307 Mon, 09 Mar 2026 16:13:00 -0000 https://status.modxcloud.com/incident/845307#e8f1d8e0d0da0975040eb8289cb56362c941ba2544fdcb79846e3dfe264d1589 We continue to work with our infrastructure partner to resolve the issue and bring all Private Server platforms back online. The servers are online however network has been affected. https://status.modxcloud.com/incident/845307 Mon, 09 Mar 2026 15:41:00 -0000 https://status.modxcloud.com/incident/845307#6d852f63a293b44e8bac3830022d460b4dfb9c30c2bb5ad919d23b08f89bc21d We're still working with our infrastructure partner to bring our Private Server platforms back online at this time. https://status.modxcloud.com/incident/845307 Mon, 09 Mar 2026 15:20:00 -0000 https://status.modxcloud.com/incident/845307#5e8d4b92ce316407befbfd4599af50075b44984173ca05ac37df746d5989519b Our infrastructure provider is resolving the issue now. Services are coming back online at this time. We will continue to monitor to ensure all systems come back online normally. https://status.modxcloud.com/incident/845307 Mon, 09 Mar 2026 15:11:00 -0000 https://status.modxcloud.com/incident/845307#b750d61a707152a8c08f38261047981e8586c993fec7658b4b1562c9bb913f54 Our infrastructure partner is working on a resoution at this moment. Hopefully, services will start coming back online soon. https://status.modxcloud.com/incident/845307 Mon, 09 Mar 2026 14:57:00 -0000 https://status.modxcloud.com/incident/845307#7ba7ce8db0000dee8e459c11d7cf649d0cbab58720a649febda4a53359cfbc83 The issue appears to be with our infrastructure partner. We're working with them right now to restore services ASAP> https://status.modxcloud.com/incident/845307 Mon, 09 Mar 2026 14:41:00 -0000 https://status.modxcloud.com/incident/845307#351b8fcbeec6cb9ed980ef9eb5937cfce8f3dffa6aa69c284ba70adf04e4ce79 All services at MODX Cloud are currently inavailable. We're investigating the issues and will have an update shortly. https://status.modxcloud.com/incident/820345 Sat, 07 Feb 2026 05:36:00 -0000 https://status.modxcloud.com/incident/820345#402f7f369d1ff10c1eaecefef4b4e17eff1233868b6cd4c5598653e31dd50f04 The traffic surge has been mitigated and system performance has stabilized. We will continue monitoring. https://status.modxcloud.com/incident/820345 Sat, 07 Feb 2026 05:13:00 -0000 https://status.modxcloud.com/incident/820345#7a7853971e9ad0c3af2a9c187241901a3840fd0db2becac1b0fd5dbcfa06db0e We have increased protections against elevated bot traffic originating from specific countries, improving platform responsiveness. Most sites should no longer be impacted. We will continue monitoring traffic and deploying additional traffic rules. https://status.modxcloud.com/incident/820345 Sat, 07 Feb 2026 04:27:00 -0000 https://status.modxcloud.com/incident/820345#beb0023e017663f17ff0c241bd243f1a960951151856e4e94e5bcf11e7ab48ae N American platforms are experiencing elevated bot traffic leading to DDoS conditions. Some sites may experience degraded traffic. https://status.modxcloud.com/incident/814239 Thu, 29 Jan 2026 16:25:00 -0000 https://status.modxcloud.com/incident/814239#5c6aaf893ed238234fb1a3d7f67940fea25207aea7cbe5a6ace32c1f6f0326a2 ## Root Cause Analysis - Service Disruption Thursday, Jan 29, 2026 **Impact:** Certain MODX Cloud Dashboard functions, Backstage functions, CloudEdge, and some queued operations were unavailable for approximately 4 hours. **What happened:** The outage was caused by a DNS configuration issue that prevented an internal TLS certificate from renewing automatically. This caused several services to stop functioning properly. **Resolution and preventative measures:** We've corrected the DNS configuration and taken additional steps to prevent similar incidents: - Implemented enhanced monitoring to detect certificate renewal issues before they impact service - Updated our internal procedures to prevent similar configuration errors from happening again and to catch potential problems earlier We apologize for the disruption and appreciate your patience while we resolved this issue. https://status.modxcloud.com/incident/814239 Thu, 29 Jan 2026 14:24:00 -0000 https://status.modxcloud.com/incident/814239#18fb971ba50e999d520f0538d53302a7820eb44e3cade2490f53f9cd48209a3c Services should be coming back online if they are not already back online. Please let us know if you continue to have issues. https://status.modxcloud.com/incident/814239 Thu, 29 Jan 2026 14:04:00 -0000 https://status.modxcloud.com/incident/814239#bab3481a0bd554bf043bbfe80c9ccc7f8c4f44dc319a2424666c886d6f140295 We have identified the issue and are actively working to resolve. This issue will affect Cloud Dashboard, CloudEdge, Updates inside Cloud Dashboard and several other services. https://status.modxcloud.com/incident/814239 Thu, 29 Jan 2026 09:14:00 -0000 https://status.modxcloud.com/incident/814239#cdb2983613c9c000277004d650bd71d5a4f91aaa09c18c7608ef52292398fb16 We have had reports and are aware of issues with the Cloud Dashboard that is affecting new Cloud creations and possible other Dashboard actions. We will aim to have this resolved as soon as possible. https://status.modxcloud.com/incident/787921 Wed, 17 Dec 2025 02:18:00 -0000 https://status.modxcloud.com/incident/787921#c10c03baf763fa691356cede9469a4bdee0e034b9bb2850b874f8791b15dfbb8 There was a brief outage for sites on our Texas 3 platform (paas3.tx). This outage seems to have only affected customer with sites using PHP 8.3. It has been resolved. https://status.modxcloud.com/incident/785457 Fri, 12 Dec 2025 21:33:00 -0000 https://status.modxcloud.com/incident/785457#a610a0a829d96f50a6f0c19e5c05b27153a5329bc52c64bdf854dac4531e1a3e It appears that GoDaddy has resolved the issue at this time. https://status.modxcloud.com/incident/785457 Fri, 12 Dec 2025 21:32:00 -0000 https://status.modxcloud.com/incident/785457#c26004b1b86333132b844476b232746e4c49acbd6ab58669371cb368f0f7a1f8 It appears that customers who uses GoDaddy Nameservers may experience site unavailability until it's resolved. https://status.modxcloud.com/incident/750069 Thu, 23 Oct 2025 18:03:00 -0000 https://status.modxcloud.com/incident/750069#92d8c49a17122963cc2228b850aefec687b9e66e0c4d7c4331e61e1069c9de54 We have identified the issue and resolved it. There was a flood of malicious traffic which we isolated and terminated. Things should be completely recovered now. https://status.modxcloud.com/incident/750069 Thu, 23 Oct 2025 17:44:00 -0000 https://status.modxcloud.com/incident/750069#b7bcd89d4272cf4ea2d7cef3dd86766833989d1736c357439f5a814bf31bda60 We're investigating performance issues affecting the Washington 1 (paas1.wdc) platform. We're working to identify the cause and restorer functionality as soon as possible. https://status.modxcloud.com/incident/740058 Wed, 08 Oct 2025 17:46:00 -0000 https://status.modxcloud.com/incident/740058#a70e66c2211d636d9085a72c4c04b2032d03e81febf752968cd0f23646e78493 We have identified the source of the issue and have resolved it. Services and sites are now coming back online. https://status.modxcloud.com/incident/740058 Wed, 08 Oct 2025 17:30:00 -0000 https://status.modxcloud.com/incident/740058#8768587606131d73602c030f1d1a1cd07b272a7acf4ec99afc80e7ec95eff2d6 We're investigating the cause of an outage of our Amsterdam 3 Platform (paas3.ams). Sites are not currently serving traffic and our team is working to resolve quickly. https://status.modxcloud.com/incident/730068 Tue, 23 Sep 2025 13:00:00 -0000 https://status.modxcloud.com/incident/730068#ee75a26fb4f53a8d46acacd0de4fb25cd70dd539adefee158272277d60d5edcf We received reports of an issue where Backstage was failing to queue deploys. Upon investigation, we found increased load hitting the API. We've expanded the resources to the API and things have resolved. We are currently investigating if any further actions are needed. https://status.modxcloud.com/incident/721257 Tue, 09 Sep 2025 16:28:00 -0000 https://status.modxcloud.com/incident/721257#be2391b4ff79ad154b2f0ed035f8e594a64eeaec735fcb1c24ca48ab4b92991a We're investigating a brief disrution for DNS resolution on a number of sites on our platforms. While the event only lasted a couple of minutes, we're still seeking to determine the cause and take any necessary action to prevent it from happening in the future if possible. https://status.modxcloud.com/incident/701490 Wed, 06 Aug 2025 16:00:00 -0000 https://status.modxcloud.com/incident/701490#c94bd74f996a36f0bacc10be6edf76c8e631e1c8cde79aa4c6b1ba359784cef1 It appears that the Network Solutions services have recovered and that sites that use NetSol as their domain registrar or DNS provider are back online. https://status.modxcloud.com/incident/700868 Thu, 31 Jul 2025 13:44:00 -0000 https://status.modxcloud.com/incident/700868#038a3ee61ddaf09c5a77faf151442cda1146fe66ca184e60c3a2abdb7e270a8e This morning, monitors alerted our team to a high-volume, automated vulnerability scan on our Washington DC 1 platform (paas1.wdc). This is a fairly common annoyance for all web hosts; however, there was a configuration issue with our server-side firewall, and this allowed the attack to continue long enough to affect some customer sites due to the volume of requests. We have fully mitigated the issue, and all sites are operating normally at this time. There's no action required, and no sites were at risk of harm.