Incidents | MODX Cloud Incidents reported on status page for MODX Cloud https://status.modxcloud.com/ https://d1lppblt9t2x15.cloudfront.net/logos/a4e4303817bafbf281c037119d727983.png Incidents | MODX Cloud https://status.modxcloud.com/ en Washington DC 1 Experiencing Performance Issues 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. Washington DC 1 Experiencing Performance Issues 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. Amsterdam 3 Experiencing a Major Outage at This Time 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. Amsterdam 3 Experiencing a Major Outage at This Time 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. Backstage Failing to Queue 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. Brief DNS Resolution Interruption 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. Brief DNS Resolution Interruption 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. [Third Party Service] Network Solutions Service Issues 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. Washington DC 1 (WDC1) Site Availability Issue 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.