Maxo Telecommunications Outage History

Maxo Telecommunications is up right now

Maxo Telecommunications had 5 outages in the last 2 years totaling 788h 51m of downtime — averaging 0.2 incidents per month.

There were 5 Maxo Telecommunications outages since July 6, 2025 totaling 788h 51m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.maxo.com.au

Minor December 8, 2025

Unplanned Inbound SMS Interruption

Detected by Pingoru
Dec 08, 2025, 04:42 AM UTC
Resolved
Dec 08, 2025, 05:45 AM UTC
Duration
1h 3m
Affected: SMS Messaging
Timeline · 2 updates
  1. identified Dec 08, 2025, 04:42 AM UTC

    Dear Customers and Partners, We are aware of an upstream issue affecting some inbound SMS messages to virtual mobile numbers. Outbound SMS messaging and MaxoSIM services are not affected. The upstream carrier’s engineers are working to correct the issue, however we do not have an ETA on resolution. We will supply any updates or ETAs as soon as we receive them. We thank you for your patience while the upstream issue is resolved. Kind regards, MaxoTel

  2. resolved Dec 08, 2025, 05:45 AM UTC

    Dear Customers and Partners, The outage affecting inbound SMS messages has now been resolved and new messages are being received as normal. Any messages received during the interruption were queued and are currently being processed for delivery. Kind regards, MaxoTel

Read the full incident report →

Minor September 18, 2025

Inbound Connectivity Issue - Virtual Mobile Numbers

Detected by Pingoru
Sep 18, 2025, 01:39 AM UTC
Resolved
Sep 18, 2025, 02:20 AM UTC
Duration
40m
Affected: Inbound Calling
Timeline · 2 updates
  1. investigating Sep 18, 2025, 01:39 AM UTC

    Dear MaxoTel Customers and Partners, MaxoTel engineers have observed an upstream issue with some incoming calls towards virtual mobile numbers where affected calls will ring but are unable to be answered. Returning an affected call will connect as normal. Incoming SMS and calls to geographic, 13/1300/1800 and international DIDs are not affected. Investigations are ongoing with the affected upstream provider’s senior engineers and we will provide an update as soon as possible. Kind regards, MaxoTel

  2. resolved Sep 18, 2025, 02:20 AM UTC

    Dear MaxoTel Customers and Partners, The upstream provider has completed changes to their routing and inbound calls toward virtual mobile numbers are now connecting as normal. Kind regards, MaxoTel

Read the full incident report →

Minor September 16, 2025

Unplanned Outage - Inbound Connectivity Issue - Symbio Networks

Detected by Pingoru
Sep 16, 2025, 08:41 AM UTC
Resolved
Sep 16, 2025, 09:46 AM UTC
Duration
1h 5m
Affected: Inbound Calling
Timeline · 3 updates
  1. investigating Sep 16, 2025, 08:41 AM UTC

    MaxoTel engineers have observed an issue with incoming calls from our primary carrier, Symbio Networks. Investigations are ongoing and a further update will be provided as soon as possible.

  2. monitoring Sep 16, 2025, 08:58 AM UTC

    MaxoTel engineers have observed incoming calls returning to normal. MaxoTel understands that the unplanned outage has occurred during routine maintenance conducted by upstream carrier Symbio Networks.

  3. resolved Sep 16, 2025, 09:46 AM UTC

    MaxoTel Engineers have not observed any further issues with incoming calls on Symbio hosted numbers.

Read the full incident report →

Minor July 6, 2025

Hardware failure - Core Switch Component - Equinix SY 1

Detected by Pingoru
Jul 06, 2025, 04:20 PM UTC
Resolved
Jul 06, 2025, 05:02 PM UTC
Duration
41m
Affected: Outbound CallingPBX FeaturesCloud SoftphoneWeb PortalManagement APIBilling and PaymentsTechnical SupportAustralian Capital TerritoryNorthern TerritoryQueenslandSouth AustraliaTasmaniaVictoriaWestern AustraliaNew South WalesInternational AccessFaxing ServicesSMS MessagingMaxoTel Website
Timeline · 2 updates
  1. identified Jul 06, 2025, 04:20 PM UTC

    Engineers have identified a core switch component as the cause of a failure and are currently working with on-site staff to have it replaced. We apologise for the inconvenience, and estimate a restore time in the next 30 minutes.

  2. resolved Jul 06, 2025, 05:02 PM UTC

    On-site engineers have replaced affected components, and services have returned to normal. A problem was identified with the fail-over system, which has been addressed and tested.

Read the full incident report →