--- service: "IronTree" status: "up" reports_last_hour: 0 reports_last_12_hours: 0 baseline_reports_per_hour: 0 checked_at: "2026-11-01T08:49:35.341Z" url: "https://instatus.com/now/irontree.co.za" official_status_page: "https://status.irontree.co.za" website: "https://irontree.co.za" --- # Is IronTree down? No, it's up. 0 reports in the last hour. ## Official updates - **Scheduled maintenance – virtual machine restarts, 29 October 2026, 20:00–00:00 SAST** (COMPLETED, 2026-10-29T18:00:00.000Z): The scheduled maintenance has been completed. - **Virtual machine service interruption – 28–29 October 2026** (RESOLVED, 2026-10-28T18:00:00.000Z): On the evening of 28 October 2026, a processor compatibility update was applied to our virtual infrastructure platform to support new compute hosts. After the change, our automated workload-balancing service attempted to move some virtual machines between hosts. These moves could not complete, and a small number of client virtual machines were placed in an error state between 20:22 on 28 October and 04:22 on 29 October 2026 (SAST). Services on the affected virtual machines were unavailable from that point. The issue was identified on the morning of 29 October 2026. From 08:42, our engineers shut down, migrated and restarted each affected virtual machine, and all were restored and verified. No data was lost. To complete the update, the remaining virtual machines will be restarted during scheduled maintenance tonight, 29 October 2026, from 20:00 to 00:00 (SAST): https://status.irontree.co.za/incidents/3t8z99r97d8s We are reviewing our change process to include automated platform services in impact assessments. We apologise for the disruption. If you have any questions, please contact our support team at vps@irontree.co.za. - **Security advisory: Node2Shell / HTTP2Shell (CVE-2026-111497)** (IDENTIFIED, 2026-10-26T14:01:30.000Z): A critical vulnerability (CVE-2026-111497) has been disclosed in the Brotli compression library used by Node.js and a number of other software platforms. Under certain conditions, an attacker could use specially crafted data to crash an affected application or potentially run code on the server. At the time of writing, no exploitation in the wild has been publicly reported. What IronTree is doing We have patched or are patching the IronTree-managed platforms that are affected. We have scanned hosted servers for affected components and will contact clients whose servers show signs of them. We are adding network-level protections where we can. What our scans can and cannot tell you Our scans can show that Node.js or related components are present on a server. They cannot tell us whether your specific application is actually exposed. That depends on how the software vendor built and configured the application. Many applications include their own copy of Node.js, which our scans may not fully detect. What we recommend Contact your software vendor to confirm whether your application is affected and when a fix will be available. Apply vendor updates as soon as they are released. Fixed Node.js versions are 22.23.4, 24.22.1 and 26.12.1 or later. Don’t replace a runtime bundled inside a vendor application yourself. Wait for the vendor’s update. If you have questions or would like help coordinating with your vendor, please contact IronTree Support. - **PHP Vulnerabilities** (IDENTIFIED, 2026-10-22T11:31:49.000Z): On 21 October 2026 the PHP project disclosed two critical remote code execution vulnerabilities, CVE-2026-109618 and CVE-2026-109619 (“php2shell”). They affect PHP installations that serve web requests, going back to PHP 5.4. Exploitation attempts have been reported in the wild. IronTree platforms: patching and mitigation of affected IronTree systems is in progress. Status updates for specific services will be posted separately. Client-hosted systems: clients are responsible for patching PHP and the applications that run on it. Please update to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35 (or your distribution’s patched package), restart PHP services, and upgrade any end-of-life PHP versions as soon as possible. IronTree is identifying vulnerable client systems and will contact affected clients directly. We encourage you to review you applications for the affected PHP version and should you suspect your applications are vulnerable, you should patch as soon as possible. If you’d like extra snapshots or backups taken before patching, contact support by emailing vps@irontree.co.za - **IronTree Platform Migrations** (INPROGRESS, 2026-10-12T18:00:00.000Z): Scheduled maintenance is currently in progress. We will provide updates as necessary. ## IronTree outage FAQ ### Is IronTree down right now? No, it's up. 0 reports in the last hour. ### Is IronTree down for everyone or just me? It looks like it's just you. Reports for IronTree are at their usual level, so try reloading, checking your connection, or signing out and back in. ### What problems are people reporting with IronTree? Nobody has said what's broken with IronTree in the last hour. If something isn't working for you, pick it above so others can see. ### When was the last IronTree outage? Reports for IronTree haven't spiked in the last 30 days. ### Does IronTree have a status page? Yes. IronTree posts updates on its official status page, which currently says operational. [Go to status page](https://status.irontree.co.za/) ### What can I do if IronTree isn't working? Check this page and IronTree's status page for updates, and wait a few minutes before trying again. Skip reinstalling: if it's an outage, the fix is on their side. ### How do I report a IronTree problem? Hit “I have an issue too” at the top of this page and pick what's broken. Your report shows on the live chart within a minute, and you can leave a comment to tell others what you're seeing. ### How does Instatus Now know? We combine reports from people on this page with IronTree's official status page, which we check every minute.