Degraded. Servers Australia is up but having problems.
Servers Australia is reporting degraded performance as of November 14, 2026. Expect slower responses or more errors. The affected components are listed below.
How we know: the official Servers Australia status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works
Status report ·
Servers Australia Status Summary
As of 19:00 UTC on 14 November 2026, Servers Australia is reporting degraded performance. PulsAPI checked Servers Australia's official status page and found 27 of 28 components operational, with 2 active incidents. The latest incident, "Service Disruption to rack B8 in Syncom SYD2 Datacenter", was on Nov 4, 2026 and lasted 14h 3m.
Cite as: PulsAPI, “Servers Australia status”, checked 14 November 2026, 19:00 UTC. https://www.pulsapi.com/services/servers-australia
Servers Australia Component Status
1 of 28 Servers Australia components are impaired. Worst problems listed first.
1degraded27operational
Services » Network Storage
Degraded
Data Centres » Equinix BR1
Operational
Data Centres » Equinix ME1
Operational
25 more components tracked
Their status is in the bar above. Free accounts see every component by name.
Also tracking Data Centres » Equinix PE2, Data Centres » Equinix SY1, Data Centres » Equinix SY3, Data Centres » Equinix SY4, Data Centres » NextDC B1, Data Centres » SYD2, Data Centres » Vocus - Albany, Regions » Brisbane, Regions » Melbourne, Regions » New Zealand, Regions » Perth, Regions » Sydney, and 13 more.
Component statuses may change independently during partial outages.
Recent Servers Australia Outages & Incidents
Incident history from the official Servers Australia status page, including resolution updates.
Service Disruption to rack B8 in Syncom SYD2 DatacenterResolved Nov 4, 2026 · 14h 3mResolved
The network switch in rack B8 at our SYD2 datacentre has remained stable following the replacement of a faulty power supply.
Engineers have confirmed that both power supplies are operating normally and the switch has returned to full service.
This incident is now resolved. Thank you for your patience and understanding while our engineers worked to restore service.
---
[2026-11-04T22:46:55.526+11:00] (monitoring) Further investigation has identified a faulty power supply as the cause of the original outage.
During testing, the faulty power supply caused a second, brief interruption to service. Engineers have now isolated and replaced the faulty unit, and confirmed that both power supplies are operating normally.
The switch has returned to service, and we are continuing to monitor it closely to ensure ongoing stability.
---
[2026-11-04T22:32:19.524+11:00] (monitoring) Engineers attending site identified fault indicators on both power supplies in the affected network switch.
Both power supplies have been replaced, and the switch has returned to service.
We are closely monitoring the device to ensure it remains stable while we continue investigating the cause of the failure.
---
[2026-11-04T22:04:02.611+11:00] (investigating) Engineers are investigating a down switch in rack B8 of the Syncom SYD2 datacentre.
Further works are underway to identify the source of the disruption and updates will be provided as soon as possible.
S3 Object Storage – Intermittent Service DisruptionsStarted Oct 29, 2026Investigating
We have made significant progress in restoring stability to our S3 Object Storage service.
The storage issue identified as the primary cause of the intermittent disruptions has now been resolved, and the affected portion of the storage cluster has returned to normal operation.
The cluster is continuing to recover from the earlier disk failure, and some background recovery operations remain ongoing.
Our team is closely monitoring service performance and working with our hardware vendor to address the remaining recovery and capacity concerns.
While we expect service stability to improve following this recovery, we are continuing to monitor for further disruptions before considering the incident fully resolved.
We will provide further updates as the situation progresses.
---
[2026-10-30T06:58:39.576+11:00] (identified) Since late last night, we have been experiencing intermittent disruptions to our S3 Object Storage service, which may result in requests timing out or failing.
The issue is occurring as our storage cluster continues to recover and rebalance data following a storage disk (OSD) failure.
Our team has been working around the clock to maintain service stability and minimise disruptions. We have engaged our hardware vendor's support team and are continuing to investigate the underlying cause and work towards a permanent resolution.
We are actively monitoring the service and taking steps to restore access when disruptions occur.
We will provide further updates as our investigation progresses.
Critical PHP Vulnerabilities (CVE-2026-109618 and CVE-2026-109619)Started Oct 23, 2026Investigating
<h2>Critical PHP Security Vulnerabilities – Plesk Security Update</h2>
The PHP project released security updates on <b>21 October 2026</b> addressing two vulnerabilities, both rated Critical.
As Plesk includes and uses PHP, these vulnerabilities may affect Plesk installations.
These vulnerabilities are within PHP itself and are not vulnerabilities in the Plesk application code.
<br>
<b>Identified Vulnerabilities:</b>
- <a href="https://www.cve.org/CVERecord?id=CVE-2026-109618">CVE-2026-109618</a><br>
- <a href="https://www.cve.org/CVERecord?id=CVE-2026-109619">CVE-2026-109619</a>
<br>
<h3>Affected and Patched Product Versions</h3>
<b>PHP on Plesk Obsidian for Linux</b>
<br>
<b>PHP 8.5</b><br>
Affected: 8.5.11 and below
Patched: 8.5.12
<br>
<b>PHP 8.4</b><br>
Affected: 8.4.26 and below
Patched: 8.4.27
<br>
<b>PHP 8.3</b><br>
Affected: 8.3.35 and below
Patched: 8.3.36
<br>
<b>PHP 8.2</b><br>
Affected: 8.2.34 and below
Patched: 8.2.35
<br>
<b>PHP 8.1 (End of Life)</b><br>
Affected: 8.1.34 (built before 21 October 2026)
Patched: 8.1.34 (built on 21 October 2026)
<br>
<b>PHP 8.0 (End of Life)</b><br>
Affected: 8.0.30 (built before 21 October 2026)
Patched: 8.0.30 (built on 21 October 2026)
<br>
<b>PHP 7.4 (End of Life)</b><br>
Affected: 7.4.33 (built before 21 October 2026)
Patched: 7.4.33 (built on 21 October 2026)
<br>
<h3>PHP on Plesk Obsidian for Windows</h3>
<b>PHP 8.5</b><br>
Affected: 8.5.11 and below
Patched: 8.5.12
<br>
<b>PHP 8.4</b><br>
Affected: 8.4.26 and below
Patched: 8.4.27
<br>
<b>PHP 8.3</b><br>
Affected: 8.3.35 and below
Patched: 8.3.36
<br>
<b>PHP 8.2</b><br>
Affected: 8.2.34 and below
Patched: 8.2.35
<br>
<h3>Plesk Obsidian – Internal PHP Engine</h3>
<b>Plesk for Linux (sw-engine component)</b>
<br>
Affected versions:<br>
- Plesk Obsidian 18.0.80 Update 10 and below
- Plesk Obsidian 18.0.81 through Update 3
<br>
Patched versions:<br>
- Plesk Obsidian 18.0.80 Update 11 (18.0.80.11)
- Plesk Obsidian 18.0.81 Update 4 (18.0.81.4)
<br>
<b>Plesk for Windows (plesk-engine component)</b>
<br>
Affected versions:<br>
- Plesk Obsidian 18.0.80 Update 10 and below
- Plesk Obsidian 18.0.81 through Update 3
<br>
Patched versions:<br>
- Plesk Obsidian 18.0.80 Update 11 (18.0.80.11)
- Plesk Obsidian 18.0.81 Update 4 (18.0.81.4)
<br>
<h3>Action Required</h3>
Customers operating Plesk servers are strongly encouraged to review their installed Plesk and PHP versions and apply the relevant security updates as soon as possible.
<br>
<b>To update your Plesk installation:</b>
<br>
1. Log into your Plesk control panel.<br>
2. Navigate to Tools & Settings > Updates and Upgrades.<br>
3. Install the latest applicable Plesk updates, including version 18.0.80.11 or 18.0.81.4, depending on your installed release.<br>
4. Verify your installed Plesk version under Tools & Settings > Server Components.<br>
5. Review your installed PHP versions under Tools & Settings > PHP Settings.<br>
6. Ensure all applicable PHP versions have been updated to the patched releases listed above.
<br>
<b>Important:</b> For end-of-life PHP versions such as 7.4, 8.0 and 8.1, the PHP version number may remain unchanged after patching. The build date and installed package information should be checked to confirm the applicable security updates have been applied.
<br>
<h3>Further Information</h3>
For further details about these vulnerabilities and the available security updates, please refer to the official Plesk documentation:
<br>
<a href="https://support.plesk.com/hc/en-us/articles/44397729587351-Vulnerability-CVE-2026-109618-and-CVE-2026-109619-PHP2Shell-Remote-code-execution-in-PHP-shipped-with-Plesk">Plesk Security Advisory – CVE-2026-109618 and CVE-2026-109619</a>
<br>
For guidance on viewing and managing PHP versions within Plesk, please refer to:
<br>
<a href="https://docs.plesk.com/en-US/obsidian/administrator-guide/web-hosting/php-management/configuring-php-handlers.75149/">Plesk Documentation – Configuring PHP Handlers</a>
<br>
We understand that applying security updates may require additional planning, particularly for environments running older PHP versions or applications.
We appreciate your patience and cooperation as we work together to ensure the ongoing security of your services.
For further updates, please continue to monitor <a href="https://status.mysau.com.au">Servers Australia's Status Page</a>.
---
[2026-10-22T15:13:39.430+11:00] (identified) We can confirm that the latest security patches have now been deployed, and web service restarts have been issued across all MMA-managed customer environments.
These restarts were carried out to ensure the latest security updates have been applied correctly and are in effect.
While these maintenance activities have been completed, we encourage customers to continue monitoring their websites, applications and operating systems for any unexpected behaviour and to ensure their environments remain up to date with the latest security patches.
We will continue to monitor vendor security advisories and provide further updates or take additional action where required.
---
[2026-10-22T14:45:53.978+11:00] (identified) Following advice from our vendors, we are currently restarting web services for all managed MMA customers to ensure the latest security patches have been applied correctly.
Affected customers may experience a brief interruption to web services of approximately 60–90 seconds during the restart process. Services are expected to return to normal automatically once the restart is complete.
We also advise all unmanaged MMA customers to restart their Apache, LiteSpeed, PHP-FPM and Nginx services, where applicable, after applying the latest patches to ensure the updates take effect correctly.
We will provide further updates as required.
---
[2026-10-22T13:37:06.384+11:00] (identified) At this time, we are advising customers of important PHP security updates following the identification of two critical vulnerabilities: CVE-2026-109618 and CVE-2026-109619.
These vulnerabilities affect multiple PHP versions and may expose servers and hosted applications to security risks if left unpatched.
==== Customer Action Required ====
Customers without a Monitoring & Maintenance Agreement (MMA) are responsible for applying the required security updates to their servers.
Servers Australia will not automatically apply these updates to self-managed, unmanaged or other hosting services that are not covered by an MMA.
We strongly recommend reviewing your PHP installations and applying the necessary security updates as soon as possible.
==== Recommended Actions ====
=== Update PHP to a Supported Version ===
Review all installed PHP versions and update them to the latest compatible security release.
Where possible, we recommend upgrading to PHP 8.4 or PHP 8.5, provided your websites, applications and extensions support these versions.
As of 22 October 2026, the minimum upstream PHP releases addressing these vulnerabilities are:
PHP 8.2.35
PHP 8.3.36
PHP 8.4.27
PHP 8.5.12
=== Apply Updates Across All PHP Installations ===
Ensure security updates are applied to all PHP installations, including PHP-FPM, command-line PHP, web server PHP handlers and associated extensions.
For servers using cPanel or CloudLinux, apply the relevant vendor-provided security updates, including backported fixes where available.
=== Update Your Server Software ===
Apply available security updates to your operating system, hosting control panel (such as cPanel/WHM), web server and associated software.
Ensure your server is running supported software versions.
=== Review Older PHP Versions ===
PHP 8.1 and older versions no longer receive security updates from the official PHP project.
Some Linux distributions and long-term support (LTS) vendors may provide backported security fixes for these older versions. If you are using an unsupported PHP version, we recommend contacting your software vendor to confirm whether the required security fixes are available or upgrading to a currently supported PHP version.
Due to the severity of these vulnerabilities, the PHP security team has also provided minimal source-level backports for:
PHP 7.4: https://github.com/php/php-src/tree/PHP-7.4-CVE-2026-109618-109619
PHP 8.0: https://github.com/php/php-src/tree/PHP-8.0-CVE-2026-109618-109619
PHP 8.1: https://github.com/php/php-src/tree/PHP-8.1-CVE-2026-109618-109619
These fixes are intended to assist customers who build PHP from source or do not have access to security updates through an LTS vendor.
Please note that these backports do not restore official support for older PHP versions. Upgrading to a supported version remains the recommended approach wherever possible.
=== Verify Your Websites and Applications ===
After applying updates, restart any affected services, such as Apache, PHP-FPM or LiteSpeed, as required.
Confirm your websites and applications are functioning correctly and that the relevant security fixes have been applied.
We also recommend ensuring current backups are available and reviewing server and website logs for unusual activity.
==== Need Assistance? ====
If you are unable to complete these updates yourself, the Servers Australia Support Team can assist.
Please note:
Security updates for non-MMA services will not be applied automatically.
Customers are responsible for applying the updates or requesting assistance.
Support requests are subject to your existing service agreement, and additional charges may apply.
PHP upgrades may affect compatibility with older websites and applications. We recommend ensuring current backups are available before making changes.
To request assistance, please submit a support ticket through the Servers Australia Customer Portal:
https://mysau.com.au
==== Further Information ====
For additional information about these vulnerabilities, supported PHP versions and available security updates, please refer to the following official resources.
Official PHP Website:
https://www.php.net
PHP Supported Versions:
https://www.php.net/supported-versions.php
The PHP Foundation – Today's PHP Security Release, and How We're Strengthening PHP Security:
https://thephp.foundation/blog/2026/10/21/todays-php-security-release-and-how-were-strengthening-php-security/
We encourage all affected customers to review their environments and apply the necessary updates promptly to help maintain the security of their services.
---
[2026-10-22T12:39:33.794+11:00] (identified) Servers Australia is continuing to respond to two recently disclosed critical PHP security vulnerabilities, CVE-2026-109618 and CVE-2026-109619, which affect PHP installations across multiple operating systems and hosting environments.
Our teams are actively monitoring security advisories and patch releases from PHP, cPanel, CloudLinux, Ubuntu and other relevant vendors, and applying updates to customer servers covered by a Servers Australia Monitoring and Maintenance Agreement (MMA).
This status page will serve as the central point of information for customers regarding the progress of security updates, outstanding vendor patches and any potential service impacts.
==== Current Security Update Progress ====
=== cPanel – Non-CloudLinux Environments ===
Security updates have been applied to all applicable cPanel servers covered by an MMA that are not running CloudLinux OS.
PHP 8.2, 8.3, 8.4 and 8.5 – Security updates applied.
PHP 7.4, 8.0 and 8.1 – Backported security patches applied.
=== CloudLinux – ALT-PHP Environments ===
CloudLinux has now released security updates addressing the identified vulnerabilities for affected ALT-PHP versions across applicable operating systems.
Our team is actively deploying these updates across managed customer environments and validating that the appropriate security patches have been successfully installed.
=== Ubuntu and Other PHP Environments ===
Our team is continuing to review and apply applicable security updates for other managed PHP environments, including Ubuntu-based servers, as the relevant vendors release and confirm their patches.
==== Expected Service Impact ====
As part of this security maintenance, we will be restarting Apache, PHP-FPM and LiteSpeed web services, where applicable, to ensure security updates take effect.
These restarts may result in brief interruptions to website or application availability, typically lasting only a few seconds.
We are working to minimise disruption while prioritising the security of affected customer environments.
=== Customer Action Required ===
No action is required from customers whose affected servers are covered by a Servers Australia MMA. Our teams are coordinating and applying the necessary updates.
Customers who manage their own servers or PHP installations should review the applicable vendor security advisories and ensure relevant updates are applied as soon as possible.
=== Further Updates ===
We will continue to update this status page as additional security patches become available, outstanding updates are deployed, and our teams complete validation across the affected environments.
Need Assistance?
If you experience any issues with your website or hosted applications following this maintenance, please contact our Support Team by submitting a ticket through the Servers Australia Customer Portal.
We appreciate your patience and understanding as we undertake this important security maintenance.
Upcoming maintenance
Announced by Servers Australia. Planned work, not an outage.
Network Embargo Period - 26/27Scheduled for Dec 13, 2026 · 672h 0mScheduled
<p>To ensure network stability during the holiday season, Servers Australia will implement a scheduled freeze on <strong>planned core network changes</strong> from <strong>9:00 AM AEDT, 14th December 2026, to 9:00 AM AEDT, 11th January 2027.</strong></p>
<p>During this period:</p>
<ul>
<li><strong>Provisioning of new services</strong> will continue where possible, although some requests may experience extended delivery times during the holiday period.</li>
<li>Requests requiring <strong>core network changes</strong> may be deferred until the change freeze concludes.</li>
<li><strong>Emergency changes</strong> may still be undertaken where necessary to maintain network security, stability or availability.</li>
</ul>
<p>Existing services are expected to operate as normal. Routine changes and support requests will continue to be managed throughout this period, although some requests may take longer to complete.</p>
<p>To minimise potential delays, we encourage customers to submit any urgent provisioning requests or planned changes well in advance of the change freeze.</p>
<p>If you have any questions or concerns about how this may impact your services, please contact our support team.</p>
<p>Thank you for your understanding and cooperation.</p>
Servers Australia Uptime History
Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Servers Australia incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.
Uptime history3 days observed
Nov 12100.00% average · 3 days with incidentsNov 14
Live Servers Australia Outage Reports
Problems reported by engineers using Servers Australia. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.
Reports, last 24 hours0 total
24h agoNothing reportednow
No Servers Australia problems reported yet.
Are you seeing Servers Australia problems too?
Reports are anonymous, take about ten seconds, and help the next engineer who checks.
About Servers Australia
Is Servers Australia down? Its official status page at status.mysau.com.au reports on 28 components, including Equinix BR1, Equinix ME1 and Equinix PE2. PulsAPI checks it every few minutes and can alert you when Servers Australia reports an incident.
Servers Australia Status FAQ
Is Servers Australia down right now?
The verdict at the top of this page comes from the latest poll of the official Servers Australia status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.
What should I do if Servers Australia is not working?
Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Servers Australia recovers.
How do I check Servers Australia uptime history?
PulsAPI tracks Servers Australia uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Servers Australia changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.
How fast does PulsAPI detect Servers Australia outages?
PulsAPI reads the official Servers Australia status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.
Does PulsAPI track individual Servers Australia components?
Yes. PulsAPI monitors 28 individual Servers Australia components, so you can see which service or region is affected instead of a generic "service degraded" banner.
Can I get alerts when Servers Australia goes down?
Yes. Create a free account and subscribe to Servers Australia: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.
How do I report an issue with Servers Australia to the community?
Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Servers Australia problems early. Official status pages often lag real incidents by 10 to 20 minutes.
Is there a free way to monitor Servers Australia?
Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Servers Australia plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.
Track Servers Australia with the rest of your stack
4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.