<?xml version="1.0" encoding="UTF-8" ?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title type="text">Vonex Status</title>
    <subtitle type="html"><![CDATA[Status Feed]]></subtitle>
    <link href="https://status.vonex.net/atom"></link>
    <id>https://status.vonex.net/</id>
    <link rel="alternate" type="text/html" href="https://status.vonex.net/atom" ></link>
    <link rel="self" type="application/atom+xml" href="https://status.vonex.net/" ></link>
        <updated>2026-04-21T19:47:49+00:00</updated>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Significant Local Outage affecting Multiple Technologies in Tropical North Coast, QLD]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/123/"></link>
            <id>https://status.vonex.net/incident/123/</id>
            <summary type="html"><![CDATA[<p>NBN and Optus have advised service outage that have been caused by ex-Tropical Cyclone Koji, which resulted in widespread power outages in its path. Due to rainfall, there is a risk of flooding and road closures. These conditions are likely to delay network and service restoration activities. The recovery efforts will be coordinated by nbn and Optus with guidance from the power providers and Emergency Services. Technicians will be dispatched to sites only when it is safe to do so.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2026-01-11T22:42:02+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[NBN - Victoria Severe Weather - 09/01/2026]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/122/"></link>
            <id>https://status.vonex.net/incident/122/</id>
            <summary type="html"><![CDATA[<p>There are currently multiple significant bushfires burning across Victoria, driven by persistent high temperatures and elevated fire danger ratings in several regions. At this time, there is no confirmed damage to NBN or Mobile network assets; however, impacts will continue to be monitored closely throughout the day. The elevated bushfire risk may result in service disruptions, access constraints, and potential safety‑related delays to any restoration activities.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2026-01-09T06:04:42+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex - Softphone Outage - 08/12/2025]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/121/"></link>
            <id>https://status.vonex.net/incident/121/</id>
            <summary type="html"><![CDATA[<p>Outage impacting Ringotel/Softphone platform has been resolved</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-12-08T02:55:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex - NBN - Tamworth NSW Unplanned Outage 27/11/2025]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/120/"></link>
            <id>https://status.vonex.net/incident/120/</id>
            <summary type="html"><![CDATA[<p>NBN have reported a critical NBN fault impacting services in Tamworth and surrounds with 64,448 NBN services across all retail service providers has been resolved 27/11/2025 16:42 AEDT</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-11-27T01:11:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex - NBN and Mobility - NSW Severe Storms 26/11/2025]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/119/"></link>
            <id>https://status.vonex.net/incident/119/</id>
            <summary type="html"><![CDATA[<p>Severe weather across Central &amp; Northern New South Wales (NSW) is impacting the commercial power supply, resulting in disruptions on the NBN and Optus Mobility networks. These conditions are likely to delay network and service restoration activities. The recovery efforts will be coordinated by NBN and Optus with guidance from the commercial power providers. Technicians will be dispatched to sites only when it is safe to do so.</p>
<p>Since the last update, 9 nbn services have been restored. As at 07:30 AEDT on 02/12/2025, 48 nbn services across all providers are currently unable to access the nbn® network across the following technologies: Fibre to the Node (FTTN) and Fibre to the Building (FTTB).
Locations Impacted</p>
<p>Regional Australia – NSW: Terrigal and Blacktown.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-11-26T10:42:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex - NBN and Mobility - SE QLD Severe Storms 24/11/2025]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/118/"></link>
            <id>https://status.vonex.net/incident/118/</id>
            <summary type="html"><![CDATA[<p>Severe storms that swept through South East Queensland afternoon 24/11/2025 caused multiple local power outages with impact to individual NBN services and mobile towers in the region. Carriers and Energex are worked to restore power as a priority when weather permitted.</p>
<p>As at 21:01 AEDT on 01/12/2025, all affected nbn services have been restored. Please continue to report faults as normal if further issues are experienced.</p>
<p>Locations Impacted</p>
<p>Regional Australia – Southeast Coast region of QLD.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-11-24T08:31:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex - Optus Mobile Outage - Remote Outage in Eyre Peninsula and South West, SA]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/117/"></link>
            <id>https://status.vonex.net/incident/117/</id>
            <summary type="html"><![CDATA[<p>Optus has advised Vonex of an outage affecting mobile services in Eyre Peninsula and South West, SA has been resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-11-07T01:49:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Optus Mobile - Regional Outage in Coffs Harbour, Dural - Wisemans Ferry, Lower Hunter, Maitland, Upper Hunter, NSW]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/116/"></link>
            <id>https://status.vonex.net/incident/116/</id>
            <summary type="html"><![CDATA[<p>Optus have advised Vonex of an outage impacting mobile voice and mobile broadband services in Coffs Harbour, Dural - Wisemans Ferry, Lower Hunter, Maitland, Upper Hunter, NSW has been resolved as of 19:40</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-11-05T01:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex - NBN - Maitland NSW Unplanned Outage - 05/11/2025]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/115/"></link>
            <id>https://status.vonex.net/incident/115/</id>
            <summary type="html"><![CDATA[<p>Services in Maitland and surrounds were restored and stable 05/11/2025 following repairs to fibre infrastructure</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-11-04T23:26:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Important Service Notice - Potential delays due to Tropical Cyclone Tino]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/113/"></link>
            <id>https://status.vonex.net/incident/113/</id>
            <summary type="html"><![CDATA[<p>We’d like to advise that Tropical Cyclone Tino is intensifying and is expected to impact Vonex's offshore operations as of 04/11/2025. As a result, our support and service provisioning teams may experience disruptions.</p>
<p>To minimise any delays, we’ve activated additional teams to assist with overflow. While these team members may not have full context on existing cases, they will be working closely with our support leaders to ensure continuity and timely responses wherever possible.</p>
<p>We appreciate your patience and understanding during this time, and we’ll continue to keep you updated as the situation evolves.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-11-03T20:09:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Optus Mobile Voice - Regional Outage in Port Douglas - Daintree, QLD 29/10/2025 Resolved]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/112/"></link>
            <id>https://status.vonex.net/incident/112/</id>
            <summary type="html"><![CDATA[<p>Optus indicate outage impacting mobile service in Port Douglas - Daintree, QLD has been resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-10-28T20:15:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Ongoing Impacts from Severe Weather Event in Brisbane QLD 26/10/2025 Resolved]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/111/"></link>
            <id>https://status.vonex.net/incident/111/</id>
            <summary type="html"><![CDATA[<p>Outage stemming from severe weather from weekend of 26/10/2026 has been closed following large scale power outage restoration in Brisbane.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-10-26T05:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Unplanned Voice Service Disruption 16/09/2025]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/110/"></link>
            <id>https://status.vonex.net/incident/110/</id>
            <summary type="html"><![CDATA[<p>Voice platform outage caused by third party supplier update, this was rolled back to restore functionality 16/09/2025 18:53 AEST, service has remained stable since.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-09-16T08:27:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex PBX Maintenance]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/109/"></link>
            <id>https://status.vonex.net/incident/109/</id>
            <summary type="html"><![CDATA[<p>Vonex wishes to advise that we will be performing scheduled maintenance on 08/09/2025 from 22:00 to 22:10 AEST.</p>
<p>Maintenance Details:
• Service(s) affected: Vonex Hosted PBX
• Purpose: PBX Maintenance
• Expected downtime: 10 minutes</p>
<p>During this time, you may experience a brief service disruption.
We apologize for any inconvenience and appreciate your patience.
If you have any questions or concerns, please contact our support team at business-support@vonex.com.au.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-09-08T07:01:17+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Legacy NBN outage in NSW 29/08/2025]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/107/"></link>
            <id>https://status.vonex.net/incident/107/</id>
            <summary type="html"><![CDATA[<p>Upstream provider has repaired fibre break impacting legacy NBN services in NSW, please report any further NSW faults as normal to Vonex Helpdesk once basic troubleshooting has been performed.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-08-28T22:27:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[NBN - Matiland NSW - Unplanned Outage 18/08/2025 Restored]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/106/"></link>
            <id>https://status.vonex.net/incident/106/</id>
            <summary type="html"><![CDATA[<p>Fibre break impacting backhaul to Vonex's Maitland NSW POI of interconnect has been restored following completion of fibre splicing.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-08-17T23:18:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[NBN and Mobile - Severe Weather Conditions in NSW]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/105/"></link>
            <id>https://status.vonex.net/incident/105/</id>
            <summary type="html"><![CDATA[<p>NBN and Mobile Network outage in NSW Northern Rivers, Mid North Coast area &amp; Surrounds as a result of commercial power outages caused by severe weather and significant flooding has now been formally flagged as resolved by NBN and Optus.</p>
<p>Any individual services in these regions still reporting issues should be raised with Vonex support staff to investigate once basic troubleshooting including a powercycle has been performed.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-08-03T08:01:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[NBN and Mobile Outage - Regional Northern QLD 31/07/025 - Restored]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/104/"></link>
            <id>https://status.vonex.net/incident/104/</id>
            <summary type="html"><![CDATA[<p>NBN and Optus Mobile networks have reported NBN fibre break impacting services in Bayview Heights, Bentley Park, Bungalow, Earlville, Manoora, Manunda, Mooroobool, Mount Sheridan, Westcourt and Woree QLD 4868, 4869, 4870 has been restored and services have recovered. Any faults to Vonex services should be reported as normal.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-07-31T13:06:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex PBX Maintenance]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/103/"></link>
            <id>https://status.vonex.net/incident/103/</id>
            <summary type="html"><![CDATA[<p>Vonex wishes to advise that we will be performing scheduled maintenance on 28/07/2025 from 22:00 to 23:30 AEST.</p>
<p>Maintenance Details:
• Service(s) affected: Vonex Hosted PBX
• Purpose: PBX Upgrade to v68.0.42.
• Expected downtime: 90 minutes</p>
<p>During this time, you may experience a brief service disruption.</p>
<p>We apologize for any inconvenience and appreciate your patience.</p>
<p>If you have any questions or concerns, please contact our support team at business-support@vonex.com.au.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-07-28T06:46:12+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex PBX Maintenance]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/102/"></link>
            <id>https://status.vonex.net/incident/102/</id>
            <summary type="html"><![CDATA[<p>Vonex wishes to advise that we will be performing scheduled maintenance on 24/07/2025 from 21:00 to 22:00 AEST.</p>
<p>Maintenance Details:
• Service(s) affected: Vonex Hosted PBX
• Purpose: PBX Upgrade to v68.0.42.
• Expected downtime: 60 minutes</p>
<p>During this time, you may experience a brief service disruption.</p>
<p>We apologize for any inconvenience and appreciate your patience.</p>
<p>If you have any questions or concerns, please contact our support team at business-support@vonex.com.au.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-07-24T05:00:43+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex PBX Maintenance]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/101/"></link>
            <id>https://status.vonex.net/incident/101/</id>
            <summary type="html"><![CDATA[<p>Vonex wishes to advise that we will be performing scheduled maintenance on 23/07/2025 from 22:00 to 23:00 AEST.</p>
<p>Maintenance Details:
• Service(s) affected: Vonex Hosted PBX
• Purpose: PBX Upgrade to v68.0.42.
• Expected downtime: 60 minutes</p>
<p>During this time, you may experience a brief service disruption.</p>
<p>We apologize for any inconvenience and appreciate your patience.</p>
<p>If you have any questions or concerns, please contact our support team at business-support@vonex.com.au.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-07-23T06:19:57+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[NBN - Gold Coast QLD and Northern NSW]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/100/"></link>
            <id>https://status.vonex.net/incident/100/</id>
            <summary type="html"><![CDATA[<p>Outage briefly impacting Legacy Gold Coast NBN services has been resolved, any further issues should be raised with Vonex Support Desk as normal.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-07-22T06:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex PBX Maintenance]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/99/"></link>
            <id>https://status.vonex.net/incident/99/</id>
            <summary type="html"><![CDATA[<p>Vonex wishes to advise that we will be performing scheduled maintenance on 22/07/2025 from 22:30 to 23:00 AEST.</p>
<p>Maintenance Details:
• Service(s) affected: Vonex Hosted PBX
• Purpose: PBX Upgrade to v68.0.42.
• Expected downtime: 30 minutes</p>
<p>During this time, you may experience a brief service disruption.</p>
<p>We apologize for any inconvenience and appreciate your patience.</p>
<p>If you have any questions or concerns, please contact our support team at business-support@vonex.com.au.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-07-22T05:26:36+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex PBX Maintenance]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/98/"></link>
            <id>https://status.vonex.net/incident/98/</id>
            <summary type="html"><![CDATA[<p>Vonex wishes to advise that we will be performing scheduled maintenance on 21/07/2025 from 22:00 to 23:00 AEST.</p>
<p>Maintenance Details:
• Service(s) affected: Vonex Hosted PBX
• Purpose: PBX Upgrade to v68.0.42.
• Expected downtime: 60 minutes</p>
<p>During this time, you may experience a brief service disruption.</p>
<p>We apologize for any inconvenience and appreciate your patience.</p>
<p>If you have any questions or concerns, please contact our support team at business-support@vonex.com.au.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-07-21T07:29:51+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex PBX Maintenance]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/97/"></link>
            <id>https://status.vonex.net/incident/97/</id>
            <summary type="html"><![CDATA[<p>Vonex wishes to advise that we will be performing scheduled maintenance on 17/07/2025 from 22:30 to 23:30 AEST.</p>
<p>Maintenance Details:
• Service(s) affected: Vonex Hosted PBX
• Purpose: PBX Upgrade to v68.0.42.
• Expected downtime: 60 minutes</p>
<p>During this time, you may experience a brief service disruption.</p>
<p>We apologize for any inconvenience and appreciate your patience.</p>
<p>If you have any questions or concerns, please contact our support team at business-support@vonex.com.au.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-07-17T06:31:03+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex PBX Maintenance]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/96/"></link>
            <id>https://status.vonex.net/incident/96/</id>
            <summary type="html"><![CDATA[<p>Vonex wishes to advise that we will be performing scheduled maintenance on 16/07/2025 from 22:30 to 23:00 AEST.</p>
<p>Maintenance Details:
• Service(s) affected: Vonex Hosted PBX
• Purpose: PBX Upgrade to v68.0.42.
• Expected downtime: 30 minutes</p>
<p>During this time, you may experience a brief service disruption.</p>
<p>We apologize for any inconvenience and appreciate your patience.</p>
<p>If you have any questions or concerns, please contact our support team at business-support@vonex.com.au.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-07-16T07:10:20+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex PBX Maintenance]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/95/"></link>
            <id>https://status.vonex.net/incident/95/</id>
            <summary type="html"><![CDATA[<p>Vonex wishes to advise that we will be performing scheduled maintenance on 15/07/2025 from 22:30 to 23:00 AEST.</p>
<p>Maintenance Details:
• Service(s) affected: Vonex Hosted PBX
• Purpose: PBX Upgrade to v68.0.42.
• Expected downtime: 30 minutes</p>
<p>During this time, you may experience a brief service disruption.</p>
<p>We apologize for any inconvenience and appreciate your patience.</p>
<p>If you have any questions or concerns, please contact our support team at business-support@vonex.com.au.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-07-15T07:09:34+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex PBX Maintenance]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/94/"></link>
            <id>https://status.vonex.net/incident/94/</id>
            <summary type="html"><![CDATA[<p>Vonex wishes to advise that we will be performing scheduled maintenance on 14/07/2025 from 22:00 to 23:00 AEST.</p>
<p>Maintenance Details:
• Service(s) affected: Vonex Hosted PBX
• Purpose: PBX Upgrade to v68.0.42.
• Expected downtime: 60 minutes</p>
<p>During this time, you may experience a brief service disruption.</p>
<p>We apologize for any inconvenience and appreciate your patience.</p>
<p>If you have any questions or concerns, please contact our support team at business-support@vonex.com.au.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-07-14T05:43:01+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex PBX Maintenance]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/93/"></link>
            <id>https://status.vonex.net/incident/93/</id>
            <summary type="html"><![CDATA[<p>Vonex wishes to advise that we will be performing scheduled maintenance on 10/07/2025 from 22:30 to 23:30 AEST.</p>
<p>Maintenance Details:
• Service(s) affected: Vonex Hosted PBX
• Purpose: PBX Upgrade to v68.0.42.
• Expected downtime: 30 minutes</p>
<p>During this time, you may experience a brief service disruption.</p>
<p>We apologize for any inconvenience and appreciate your patience.</p>
<p>If you have any questions or concerns, please contact our support team at business-support@vonex.com.au.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-07-10T04:44:51+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex PBX Maintenance]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/92/"></link>
            <id>https://status.vonex.net/incident/92/</id>
            <summary type="html"><![CDATA[<p>Vonex wishes to advise that we will be performing scheduled maintenance on 09/07/2025 from 22:30 to 23:00 AEST.</p>
<p>Maintenance Details:
• Service(s) affected: Vonex Hosted PBX
• Purpose: PBX Upgrade to v68.0.42.
• Expected downtime: 30 minutes</p>
<p>During this time, you may experience a brief service disruption.</p>
<p>We apologize for any inconvenience and appreciate your patience.</p>
<p>If you have any questions or concerns, please contact our support team at business-support@vonex.com.au.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-07-09T06:32:41+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex PBX Maintenance]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/91/"></link>
            <id>https://status.vonex.net/incident/91/</id>
            <summary type="html"><![CDATA[<p>Vonex wishes to advise that we will be performing scheduled maintenance on 08/07/2025 from 22:30 to 23:00 AEST.</p>
<p>Maintenance Details:
• Service(s) affected: Vonex Hosted PBX
• Purpose: PBX Upgrade to v68.0.42.
• Expected downtime: 30 minutes</p>
<p>During this time, you may experience a brief service disruption.</p>
<p>We apologize for any inconvenience and appreciate your patience.</p>
<p>If you have any questions or concerns, please contact our support team at business-support@vonex.com.au.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-07-08T04:35:14+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex PBX Maintenance]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/90/"></link>
            <id>https://status.vonex.net/incident/90/</id>
            <summary type="html"><![CDATA[<p>Vonex wishes to advise that we will be performing scheduled maintenance on 07/07/2025 from 22:00 to 22:30 AEST.</p>
<p>Maintenance Details:
• Service(s) affected: Vonex Hosted PBX
• Purpose: PBX Upgrade to v68.0.42.
• Expected downtime: 30 minutes</p>
<p>During this time, you may experience a brief service disruption.</p>
<p>We apologize for any inconvenience and appreciate your patience.</p>
<p>If you have any questions or concerns, please contact our support team at business-support@vonex.com.au.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-07-07T04:29:39+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex PBX Maintenance]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/89/"></link>
            <id>https://status.vonex.net/incident/89/</id>
            <summary type="html"><![CDATA[<p>Vonex wishes to advise that we will be performing scheduled maintenance on 03/07/2025 from 22:30 to 22:50 AEST.</p>
<p>Maintenance Details:
• Service(s) affected: Vonex Hosted PBX
• Purpose: PBX Upgrade to v68.0.42.
• Expected downtime: 20 minutes</p>
<p>During this time, you may experience a brief service disruption.</p>
<p>We apologize for any inconvenience and appreciate your patience.</p>
<p>If you have any questions or concerns, please contact our support team at business-support@vonex.com.au.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-07-03T05:27:26+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex PBX Maintenance]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/88/"></link>
            <id>https://status.vonex.net/incident/88/</id>
            <summary type="html"><![CDATA[<p>Vonex wishes to advise that we will be performing scheduled maintenance on 02/07/2025 from 22:00 to 22:30 AEST.</p>
<p>Maintenance Details:
• Service(s) affected: Vonex Hosted PBX
• Purpose: PBX Upgrade to v68.0.42.
• Expected downtime: 30 minutes</p>
<p>During this time, you may experience a brief service disruption.</p>
<p>We apologize for any inconvenience and appreciate your patience.</p>
<p>If you have any questions or concerns, please contact our support team at business-support@vonex.com.au.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-07-02T06:12:58+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Severe Weather Event - East Coast NSW - 02/07/2025]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/87/"></link>
            <id>https://status.vonex.net/incident/87/</id>
            <summary type="html"><![CDATA[<p>Both Optus and NBN have confirmed outages caused by severe weather across the East Coast of NSW that impacted commercial power supply to carrier infrastructure has been resolved and all services should be back online. Any services that have not recovered should be treated as normal faults and raised with Vonex support teams if necessary.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-07-01T21:56:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Port Augusta South Australia - Unplanned Outage 06/06/2025]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/86/"></link>
            <id>https://status.vonex.net/incident/86/</id>
            <summary type="html"><![CDATA[<p>Vonex's NBN Port Augusta POI in South Australia was impacted by a inland fibre break between Adelaide and Perth at a railway intersection, splicing was completed 07/06/2025 and services have remained stable since.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-06-06T08:39:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[NBN - Northern NSW Severe Weather Event - 20/05/2025]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/85/"></link>
            <id>https://status.vonex.net/incident/85/</id>
            <summary type="html"><![CDATA[<p>With impacts of weather event being resolved and clear and safe path to restoration for remainder, NBN have flagged return to BAU in Nth NSW.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-05-20T05:29:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Ex-Tropical Cyclone Alfred - Ongoing Impacts to NBN and Mobile Services in SE QLD and NTH NSW]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/84/"></link>
            <id>https://status.vonex.net/incident/84/</id>
            <summary type="html"><![CDATA[<p>Ex-Tropical Cyclone Alfred continues to cause significant impact to Southeast Queensland and Northern New South Wales, bringing strong winds, heavy rainfall, and flooding that has 280 mobile tower site and many individual Vonex services on the NBN networks in these regions offline due to power outages, largest impact being major NBN outage in Nerang on the Gold Coast.</p>
<p>NBN and Optus Mobile have activated emergency management teams and deployed additional local resources throughout the region to manage power outages and work with emergency services to restore services weather conditions permitting.</p>
<p>Further updates will be provided by normal communication channels as situation progresses.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-03-06T22:54:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[NBN Systems - Unplanned Outage 19/02/2025]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/83/"></link>
            <id>https://status.vonex.net/incident/83/</id>
            <summary type="html"><![CDATA[<p>NBN has restored the outage impacting the Service Portal, Diagnostics/Service Health, Appointments, Orders and Assurance Fault Tickets. Any faults or orders delayed by this outage will be cleared as promptly as possible by Vonex Support Staff.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-02-19T01:23:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[AAPT Major Outage]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/82/"></link>
            <id>https://status.vonex.net/incident/82/</id>
            <summary type="html"><![CDATA[<p>AAPT delivered services were impacted by a major nationwide outage within the AAPT/TPG network this evening 10th Feb 2025, this has now been resolved and majorirty of services have recovered. Any services still impacted should complete standard troubleshooting and equipment powercycle prior to raising to Vonex Support. NBN services on the Vonex direct network and via other legacy providers were not impacted and should be treated as normal.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2025-02-10T09:05:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Vonex Wholesale - NBN - Unplanned Outage VIC 15/10/2024]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/81/"></link>
            <id>https://status.vonex.net/incident/81/</id>
            <summary type="html"><![CDATA[<p>NBN - Unplanned Outage VIC 15/10/2024
Vonex has become aware of an unplanned outage impacting NBN services in some areas in VIC, investigation is presently ongoing with upstream provider.
Current locations impacted are:
Karingal;
Cheltenham;
Keysborough;
Dandenong.</p>
<p>UPDATE:</p>
<p>Services in South-East Melbourne have been restored following two separate, unrelated fibre breaks yesterday afternoon.
The fibre breaks occurred after trucks hit aerial cables at two different sites in Melbourne's suburbs. Our upstream carrier teams worked throughout the night to resolve the fibre breaks which were restored at 1am in Tottenham and 4.30am in Mulgrave.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-10-15T03:48:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Issue with Calling DID's hosted with Symbio from the Optus mobile network]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/80/"></link>
            <id>https://status.vonex.net/incident/80/</id>
            <summary type="html"><![CDATA[<p>Issue with calls to Vonex DID's hosted with Symbio from mobile voice services on the Optus mobile network on 12/10/2024 has been formally resolved with stable platform and calls since late 12/10/2024.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-10-12T02:33:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[NBN Outage Broadbeach QLD]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/79/"></link>
            <id>https://status.vonex.net/incident/79/</id>
            <summary type="html"><![CDATA[<p>NBN services in Broadbeach have remained online stable since power was restored by carrier.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2024-09-11T10:26:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[NBN Disruption(QLD)]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/75/"></link>
            <id>https://status.vonex.net/incident/75/</id>
            <summary type="html"><![CDATA[<p>The reported issue has been fixed. If you are still experiencing this issue, please let us know as soon as possible</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-11-27T07:51:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[NBN Disruption(QLD)]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/74/"></link>
            <id>https://status.vonex.net/incident/74/</id>
            <summary type="html"><![CDATA[<p>Carrier field technicians have confirmed that fibres were damaged by a third party. Fibre contractors are currently on site preparing the damaged area for the installation of a new cable. No ETR available. Further updates will be provided in approximately 2 hours.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-11-27T00:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[NBN Disruption(QLD)]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/73/"></link>
            <id>https://status.vonex.net/incident/73/</id>
            <summary type="html"><![CDATA[<p>Please be advised that some customers in or around Nerang, Eight Mile, &amp; Southport, are experiencing network difficulties.</p>
<p>There is currently no ETR, but carrier engineers are current investigating and working on this.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-11-26T17:17:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[NBN Fixed Wireless NSW Unplanned Outage]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/72/"></link>
            <id>https://status.vonex.net/incident/72/</id>
            <summary type="html"><![CDATA[<p>Vonex has become aware of an unplanned outage on the NBN Fixed Wireless network in Northern NSW with impact to services around Coffs Harbour and surrounds stretching out west towards Tamworth, NBN has now restored outage and services in the region have been seen to recover.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-11-24T01:18:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[UPDATE 1]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/71/"></link>
            <id>https://status.vonex.net/incident/71/</id>
            <summary type="html"><![CDATA[<p>Small area impacted and actively being restored</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-11-21T23:23:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[NBN Service Disruption]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/70/"></link>
            <id>https://status.vonex.net/incident/70/</id>
            <summary type="html"><![CDATA[<p>Due to an upstream change, some NBN services may be affected. Updates to follow</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-11-21T19:01:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Mobile Outage Resolved]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/69/"></link>
            <id>https://status.vonex.net/incident/69/</id>
            <summary type="html"><![CDATA[<p>The reported issue has been fixed. If you are still experiencing this issue, please let us know as soon as possible</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-11-08T06:06:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[UPDATE 1]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/64/"></link>
            <id>https://status.vonex.net/incident/64/</id>
            <summary type="html"><![CDATA[<p>Engineers are continuing to work through rectifying. Some phone services are gradually being restored.</p>
<p>This may take a few hours for all services to come back on line and different services may restore at different sites over that time. No action is required and services will be automatically restored.</p>
<p>We will provide further update once available.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-11-08T03:12:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Major Mobile Outage]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/63/"></link>
            <id>https://status.vonex.net/incident/63/</id>
            <summary type="html"><![CDATA[<p>Optus have reported a nationwide outage impacting mobile voice and mobile broadband services for all Optus brands and resellers including Vonex This major outage is being investigated with the highest priority and no workaround is available.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2023-11-07T17:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Voice service disruption]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/62/"></link>
            <id>https://status.vonex.net/incident/62/</id>
            <summary type="html"><![CDATA[<h2>UPDATE 1</h2>
<p>Vonex Engineers were aware of some issues ongoing with our voice service platform due to a hardware failure
This has been fixed</p>
<p>Symptom:</p>
<p>Date Started: 05 Dec 2022</p>
<p>Time Started: 13:30 AEDT</p>
<p>Date Ended: 05 Dec 2022</p>
<p>Time Ended: 15:15 AEDT</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-12-04T13:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Voice service disruption ( MNF Legacy Voice Services)]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/61/"></link>
            <id>https://status.vonex.net/incident/61/</id>
            <summary type="html"><![CDATA[<h2>UPDATE 1</h2>
<p>Vonex Engineers are aware of some issues ongoing with Legacy MNF voice services</p>
<p>Symptom: inbound and outbound call quality issues</p>
<p>Date Started: 5/09/22</p>
<p>Time Started: (.30 am AEST</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-09-04T23:30:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Voice service disruption]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/60/"></link>
            <id>https://status.vonex.net/incident/60/</id>
            <summary type="html"><![CDATA[<h2>UPDATE 1</h2>
<p>Vonex Engineers are aware of some intermittent connectivity issues ongoing with our voice service platform</p>
<p>We are currently working on it to get it resolved as soon as possible.</p>
<p>Symptom: Inbound calls via some Telstra networks are not reaching the Vonex Network</p>
<p>Date Started: 13 July 2022</p>
<p>Time Started: Approximately 11:15am AEST</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-07-13T01:58:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[MNF Legacy Service Outage]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/59/"></link>
            <id>https://status.vonex.net/incident/59/</id>
            <summary type="html"><![CDATA[<p>Customers who are on the MNF Legacy system will experience service difficulties resulting in</p>
<p>Inbound and Outbound call issues</p>
<p>Making Payments</p>
<p>Service changes</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2022-03-29T05:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Voice service disruption]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/57/"></link>
            <id>https://status.vonex.net/incident/57/</id>
            <summary type="html"><![CDATA[<p>Vonex Engineers are aware of some issues ongoing with MNF Legacy Voice Services. MNF engineers are currently working on the issue</p>
<p>Symptoms reported : intermittent outbound and inbound call failures and loss of features such cli overstamping.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-11-29T00:50:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[MNF Legacy Customer Portal]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/56/"></link>
            <id>https://status.vonex.net/incident/56/</id>
            <summary type="html"><![CDATA[<p>We have identified  issues with MNF's Legacy Customer Portal and  MNF engineers are working on it.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-11-29T00:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Voice service disruption]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/55/"></link>
            <id>https://status.vonex.net/incident/55/</id>
            <summary type="html"><![CDATA[<p>Issue has been fixed as of 11:15 AEDT</p>
<p>Vonex Engineers are aware of some issues ongoing with our voice service platform
We are currently working on it to get it resolved as soon as possible.</p>
<p>Symptom: Inbound and outbound calls failure</p>
<p>Date Started: 29 Nov 2021</p>
<p>Time Started: Approximately 10:45 AEDT</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2021-11-28T23:45:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[MAINTENANCE]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/54/"></link>
            <id>https://status.vonex.net/incident/54/</id>
            <summary type="html"><![CDATA[<p>Dear Valued Customers,</p>
<p>This is to notify you that our upstream data engineers will be conducting two maintenance events to standardize the configuration across the network.</p>
<p>Planned Activities Details:</p>
<p>Impacts:</p>
<p>Inbound calls from Telstra to Symbio Western Australia (WA) DIDs will be affected for up to 20 minutes during the maintenance period.</p>
<p>Outbound from Symbio call termination services (CTS) will not be affected.</p>
<p>Activity Start Time: Friday, 2020-11-27 @ 00:01 AEDT (GMT+11)</p>
<p>Activity End Time: Friday, 2020-11-27 @ 05:00 AEDT (GMT+11)</p>
<p>Activity Start Time: Wednesday, 2020-12-02 @ 00:01 AEDT (GMT+11)</p>
<p>Activity End Time: Wednesday, 2020-12-02 @ 05:00 AEDT (GMT+11)</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-11-23T05:38:17+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[MAINTENANCE]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/52/"></link>
            <id>https://status.vonex.net/incident/52/</id>
            <summary type="html"><![CDATA[<p>Dear Valued Customers,</p>
<p>This is to notify you that our upstream data engineers will be conducting two maintenance events to standardize the configuration across the network.</p>
<p>Planned Activities Details:</p>
<p>Impacts:</p>
<p>Inbound calls from Telstra to Symbio Western Australia (WA) DIDs will be affected for up to 20 minutes during the maintenance period.</p>
<p>Outbound from Symbio call termination services (CTS) will not be affected.</p>
<p>Activity Start Time: Friday, 2020-11-27 @ 00:01 AEDT (GMT+11)</p>
<p>Activity End Time: Friday, 2020-11-27 @ 05:00 AEDT (GMT+11)</p>
<p>Activity Start Time: Wednesday, 2020-12-02 @ 00:01 AEDT (GMT+11)</p>
<p>Activity End Time: Wednesday, 2020-12-02 @ 05:00 AEDT (GMT+11)</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-11-23T05:35:25+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[MAINTENANCE]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/51/"></link>
            <id>https://status.vonex.net/incident/51/</id>
            <summary type="html"><![CDATA[<p>Dear Customers,</p>
<p>One of our Data center operators will be conducting some works at the mentioned times. This only affects a select list of wholesalers with PBXs hosted in international locations. All PBXs within Australia will not be affected. We will keep a lookout on the progress of this event</p>
<p>Start Date: Friday 31-Oct-2020 03:00 AEDT</p>
<p>End Date: Friday 31-Oct-2020 07:00 AEDT</p>
<p>Duration: 4 hours</p>
<p>Event Type: Planned Maintenance</p>
<p>Subject: Event 121951828 - Component Replacement fcr01.sng01</p>
<p>Severity: High</p>
<p>Network Engineers will be replacing a faulty component in fcr01.sng01 to normalize component redundancy. The Front End Customer router (FCR) provides public front-end network connectivity to hosts in the Singapore datacenter POD 1.</p>
<p>During this 4 hour window, traffic will be shifted away from the component being replaced to limit impact to customer traffic. When this shifts occur, some clients may notice a brief period of degradation or a loss to packets-in-flight.</p>
<p>Private connectivity will NOT be affected during this work.</p>
<p>The maintenance procedure is designed to avoid down time, however there is risk of hardware failure. If this occurs customer may experience a disruption of up to 30 minutes.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-10-01T03:42:31+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[MAINTENANCE]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/50/"></link>
            <id>https://status.vonex.net/incident/50/</id>
            <summary type="html"><![CDATA[<p>This is to notify you that our upstream data engineers will be conducting a maintenance event to standardize the configuration across the network.</p>
<p>Planned Activities Details:</p>
<p>Impacts:</p>
<p>We don't foresee any service impacts. However, there may be a downtime for inbound services for up to 15 mins if a rollback is required to be performed by our upstream engineers.</p>
<p>Activity Start Time: Wednesday, 2020-09-23 @ 23:00 AEST (GMT+10)</p>
<p>Activity End Time: Thursday, 2020-09-24 @ 03:00 AEST (GMT+10)</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-09-17T02:23:20+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[MAINTENENCE]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/49/"></link>
            <id>https://status.vonex.net/incident/49/</id>
            <summary type="html"><![CDATA[<p>This is to notify you that our upstream engineers will be conducting a maintenance event to standardize the configuration across the network.</p>
<p>Planned Activities Details:</p>
<p>Impacts:</p>
<p>No impacts expected</p>
<p>Activity Start Time: Wednesday, 2020-09-16 @ 23:00 AEST (GMT+10)</p>
<p>Activity End Time: Thursday, 2020-09-17 @ 04:00 AEST (GMT+10)</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-09-10T02:11:39+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[MAINTENENCE]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/48/"></link>
            <id>https://status.vonex.net/incident/48/</id>
            <summary type="html"><![CDATA[<p>We wish to advise the following Planned Outage has been scheduled by our upstream provider</p>
<p>Work Start Date/Time:  15-09-2020 00:01:00 AEST</p>
<p>Work End Date/Time:     15-09-2020 06:00:00 AEST</p>
<p>Location:            Sydney, NSW</p>
<p>Impact:                   Outage</p>
<p>Expected Outage:              Up to 1 Hour</p>
<p>Description of Work:  Planned router software upgrade works by upstream provider</p>
<p>Impact to Vonex:        We do not expect to have any downtime due to our redundancy setup.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-09-03T03:09:30+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[MAINTENENCE]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/47/"></link>
            <id>https://status.vonex.net/incident/47/</id>
            <summary type="html"><![CDATA[<p>This is to notify you that our data engineers will be conducting a maintenance event to standardize the configuration across the network.</p>
<p>Planned Activities Details:</p>
<p>Impacts:</p>
<p>No impacts expected</p>
<p>Activity Start Time: Wednesday, 2020-09-09 @ 23:00 AEST (GMT+10)</p>
<p>Activity End Time: Thursday, 2020-09-10 @ 04:00 AEST (GMT+10)</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-09-03T02:42:33+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Voice service disruption]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/46/"></link>
            <id>https://status.vonex.net/incident/46/</id>
            <summary type="html"><![CDATA[<p>Vonex Engineers are aware of some issues ongoing with our voice service platform
We are currently working on it to get it resolved as soon as possible.</p>
<p>Symptom: Intermittent loss of voice services</p>
<p>Date Started: 17 August 2020</p>
<p>Time Started: 09:30 AEST</p>
<p>** UPDATE **</p>
<p>Date Started:           17 August 2020</p>
<p>Time Started:           09:30 AEST</p>
<p>Date Fixed:               17 August 2020</p>
<p>Time Fixed                11:00 AEST</p>
<p>Impact:</p>
<p>Intermittent loss / degraded voice services</p>
<p>Event Log:</p>
<p>At around 09:30, Vonex Engineers got alerts from our monitoring system about intermittent failed connectivity and degraded voice quality across our network. This issue lasted about 5 minutes and resolved by itself. Vonex identified the offending carrier and a fault ticket was logged with the internet carrier. A subset of services that was dependent on this carrier was affected
At about 10:10 a second wave of intermittent failed connectivity and degraded voice quality occurred. This lasted another 5 minutes before getting resolved on its own
At about 11:00, the third wave of intermittent failed connectivity and degraded voice quality occurred. At this point, Vonex made the decision to remove the offending carrier from our network and the issue was resolved</p>
<p>Findings:</p>
<p>Upon Investigation, Our Upstream network providers had reported that there had been a DDoS attack across some of the major data carriers in Australia. This affected network connectivity and voice quality across multiple carriers. Action was taken to mitigate the attack and the issue was resolved.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-08-17T00:25:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[MAINTENENCE]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/45/"></link>
            <id>https://status.vonex.net/incident/45/</id>
            <summary type="html"><![CDATA[<p>Our Upstream will be performing a scheduled maintenance to standardize the configuration across the network</p>
<p>Planned Activities Details:</p>
<p>Impacts:
No impacts expected</p>
<p>Activity Start Time: Wednesday, 2020-08-19 @ 23:00 AEST (GMT+10)
Activity End Time: Thursday, 2020-08-20 @ 06:00 AEST (GMT+10)</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-08-05T02:05:07+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[MAINTENENCE]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/44/"></link>
            <id>https://status.vonex.net/incident/44/</id>
            <summary type="html"><![CDATA[<p>Vonex Engineers will be performing a scheduled maintenence to improve performance and scalability of our infrastructure</p>
<p>Start Date: 26 July 2020</p>
<p>Start Time: 00:30 AEST</p>
<p>End Date: 26 July 2020</p>
<p>End Time: 01:30 AEST</p>
<p>Description of Works:</p>
<p>Vonex will be adding some additional resources for our infrastructures. Engineers will be required to restart some servers as a result of this. We expect services to be intermittently unavailable within this 1-hour window.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-07-21T03:56:28+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Maintenance Notice ( Upstream Carrier)]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/43/"></link>
            <id>https://status.vonex.net/incident/43/</id>
            <summary type="html"><![CDATA[<p>This is a notice from our upstream carrier. Please note that outbound calls will route through our secondary upstream carrier during this maintenance window.</p>
<p>Planned Activities Details:</p>
<p>data engineers will be conducting two maintenance events to standardize the configuration across the network.</p>
<p>Impacts:</p>
<p>Inbound/Outbound calls may experience the following symptoms intermittently between 10 - 20 minutes.</p>
<p>Audio issues (Dead air)
Call drop for already established calls
Inability to make or receive calls
Activity Start Time: Thursday, 2020-07-23 @ 23:00 AEST (GMT+10)
Activity End Time: Friday, 2020-07-24 @ 03:00 AEST (GMT+10)</p>
<p>Activity Start Time: Monday, 2020-07-27 @ 23:00 AEST (GMT+10)
Activity End Time: Tuesday, 2020-07-28 @ 03:00 AEST (GMT+10)</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-07-09T13:21:28+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[notice from our upstream carrier]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/42/"></link>
            <id>https://status.vonex.net/incident/42/</id>
            <summary type="html"><![CDATA[<p>Impacts:
Inbound/Outbound calls may experience the following symptoms intermittently between 10 - 20 minutes.
Audio issues (Dead air)
Call drop for already established calls
Inability to make or receive calls
Activity Start Time: Tuesday, 2020-07-07 @ 04:30 AEST (GMT+10)
Activity End Time: Tuesday, 2020-07-07 @ 07:00 AEST (GMT+10)</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-06-29T08:28:46+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[notice from our upstream carrier]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/41/"></link>
            <id>https://status.vonex.net/incident/41/</id>
            <summary type="html"><![CDATA[<p>Planned Activities Details For 1st July:
Impacts:
Outbound calls to Queensland (QLD) numbers and inbound calls to Symbio Queensland (QLD) numbers may experience an intermittent connection failure for up to 10 minutes during the maintenance window.
Activity Start Time: Wednesday, 2020-07-01 @ 01:00 AEST (GMT+10)
Activity End Time: Wednesday, 2020-07-01@ 04:00 AEST (GMT+10)</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-06-29T08:26:52+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Emergency Maintenance Notice]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/40/"></link>
            <id>https://status.vonex.net/incident/40/</id>
            <summary type="html"><![CDATA[<p>Maintenance
This is a notice for emergency maintenance scheduled for 23rd June.</p>
<p>CUSTOMER IMPACT:
Vonex engineers will take all the necessary steps to ensure no impact on services. However due to the nature of the works involved, please be advised that ALL services hosted in the Sydney Data center could be impacted for short intermittent intervals of time.</p>
<p>MAINTENANCE ACTION:
Vonex engineers were alerted to a failed router in the High Availability Cluster in Sydney Data Centre on 20th June 2020. Engineers will be replacing the failed unit and adding this router to the High Availability Cluster.</p>
<p>DATE/TIME WINDOW:
6 hour window during:</p>
<p>23rd June @ 2100 to 0300 (NEXT DAY) AEST</p>
<p>Should you have any questions regarding this emergency maintenance, please open a support request with the Vonex Helpdesk, support@vonex.com.au.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-06-22T07:03:04+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[emergency maintenance scheduled for tonight]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/39/"></link>
            <id>https://status.vonex.net/incident/39/</id>
            <summary type="html"><![CDATA[<p>Maintenance
This is a notice for emergency maintenance scheduled for tonight.</p>
<p>CUSTOMER IMPACT:
We expect no impact on services hosted in Sydney Data Centre.</p>
<p>MAINTENANCE ACTION:
Vonex engineers were alerted to a failed router in the High Availability Cluster in Sydney Data Centre on 20th June 2020. Engineers will continue their works tonight to bring this device online.</p>
<p>DATE/TIME WINDOW:
6 hour window during:</p>
<p>21st June @ 2100 to 0300 (NEXT DAY) AEST</p>
<p>Should you have any questions regarding this emergency maintenance, please open a support request with the Vonex Helpdesk, support@vonex.com.au.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-06-21T03:02:59+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Emergency Maintenance Notice]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/38/"></link>
            <id>https://status.vonex.net/incident/38/</id>
            <summary type="html"><![CDATA[<p>Maintenance
This is a notice for emergency maintenance scheduled for tonight.</p>
<p>CUSTOMER IMPACT:
We expect no impact on services hosted in Sydney Data Centre.</p>
<p>MAINTENANCE ACTION:
Vonex engineers were alerted to a failed router in the High Availability Cluster in Sydney Data Centre.</p>
<p>DATE/TIME WINDOW:
1-hour window during:</p>
<p>21st June @ 0000 to 0100. AEST</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-06-20T11:20:09+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[MAINTENENCE]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/37/"></link>
            <id>https://status.vonex.net/incident/37/</id>
            <summary type="html"><![CDATA[<p>This is to notify you that our upstream data engineers will be conducting three emergency maintenance events in our Queensland data centre to standardize the configuration across the network.</p>
<p>Planned Activities Details:</p>
<p>Impacts:</p>
<p>Some outbound calls to Telstra Queensland (QLD) numbers may be dropped mid-call.</p>
<p>Some inbound calls from Telstra customer calling to Symbio Queensland (QLD) DIDs may experience intermittent connection failure for up to 8 minutes during the maintenance window. Reattempting will connect.</p>
<p>Activity Start Time: Friday, 2020-05-22 @ 00:01 AEST (GMT+10)</p>
<p>Activity End Time: Friday, 2020-05-22 @ 03:30 AEST (GMT+10)</p>
<p>Activity Start Time: Tuesday, 2020-05-26 @ 00:01 AEST (GMT+10)</p>
<p>Activity End Time: Tuesday, 2020-05-26 @ 03:30 AEST (GMT+10)</p>
<p>Activity Start Time: Wednesday, 2020-05-27 @ 00:01 AEST (GMT+10)</p>
<p>Activity End Time: Wednesday, 2020-05-27 @ 03:30 AEST (GMT+10)</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-05-25T00:47:45+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[FIXED]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/36/"></link>
            <id>https://status.vonex.net/incident/36/</id>
            <summary type="html"><![CDATA[<p>The reported issue has been fixed. If you are still experiencing this issue, please let us know as soon as possible</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-04-19T10:00:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[UPDATE 1]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/35/"></link>
            <id>https://status.vonex.net/incident/35/</id>
            <summary type="html"><![CDATA[<p>Service is currently affected by Fibre Repair planned maintenance</p>
<p>Planned Start [Sydney Time]: 19/Apr/20 6:00 AM</p>
<p>Planned Finish [Sydney Time]: 19/Apr/20 6:00 PM</p>
<p>Further updates will be provide once available.</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-04-18T21:05:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Voice service disruption]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/34/"></link>
            <id>https://status.vonex.net/incident/34/</id>
            <summary type="html"><![CDATA[<p>Vonex Engineers are aware of some issues ongoing with our voice service platform
We are currently working on it to get it resolved as soon as possible.</p>
<p>Symptom: Intermittent loss of Registrations and calls</p>
<p>Date Started: 19/04/2020</p>
<p>Time Started: 06:20 AEST</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-04-18T20:37:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[FIXED]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/33/"></link>
            <id>https://status.vonex.net/incident/33/</id>
            <summary type="html"><![CDATA[<p>The reported issue has been fixed. If you are still experiencing this issue, please let us know as soon as possible</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-04-16T03:47:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[UPDATE 2]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/32/"></link>
            <id>https://status.vonex.net/incident/32/</id>
            <summary type="html"><![CDATA[<p>Engineers have completed the works and replaced the faulty hardware. We are now monitoring the fix</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-04-16T03:40:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[UPDATE 1]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/31/"></link>
            <id>https://status.vonex.net/incident/31/</id>
            <summary type="html"><![CDATA[<p>Engineers are onsite to replace faulty hardware</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-04-16T03:15:00+00:00</updated>
        </entry>
        <entry>
            <author>
                <name>Vonex Status</name>
            </author>
            <title type="text"><![CDATA[Voice service disruption]]></title>
            <link rel="alternate" type="text/html" href="https://status.vonex.net/incident/30/"></link>
            <id>https://status.vonex.net/incident/30/</id>
            <summary type="html"><![CDATA[<p>Vonex Engineers are aware of some issues ongoing with our voice service platform
We are currently working on it to get it resolved as soon as possible.</p>
<p>Symptom: Poor voice quality</p>
<p>Date Started: 16/04/2020</p>
<p>Time Started: 13:05</p>
]]></summary>
            <content type="html"><![CDATA[]]></content>
            <updated>2020-04-16T03:14:00+00:00</updated>
        </entry>
</feed>
