YourCloudTelco Outage History

YourCloudTelco is up right now

Pingoru has recorded 49 incidents for YourCloudTelco: 8 in the last 12 months and 1 in the last 90 days.

Source: status.yourcloudtelco.com.au

49incidents recorded
8last 12 months
1last 90 days
5 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking YourCloudTelco in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202611 of 720 (0%)
May 202600 of 744 (0%)
June 202624 of 720 (1%)
July 202610 of 744 (0%)
August 202614 of 744 (1%)
September 202600 of 720 (0%)
October 202600 of 536 (0%)

Incidents, newest first

Critical August 9, 2026 Fax issues 3h 53m Faxing

Started Aug 09, 2026, 11:50 PM UTC· resolved Aug 10, 2026, 03:43 AM UTC

  1. investigating Aug 09, 2026, 11:50 PM UTC

    We are currently investigating this issue.

  2. monitoring Aug 10, 2026, 02:29 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 10, 2026, 03:43 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 16, 2026 Calling outgage 13m YourCloudTelco Calling Platform (Network), Arena

Started Jul 16, 2026, 04:50 AM UTC· resolved Jul 16, 2026, 05:04 AM UTC

  1. investigating Jul 16, 2026, 04:50 AM UTC

    We are currently investigating this issue.

  2. resolved Jul 16, 2026, 05:04 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 11, 2026 Arena access down 1h 30m Arena

Started Jun 11, 2026, 11:56 PM UTC· resolved Jun 12, 2026, 01:27 AM UTC

  1. identified Jun 11, 2026, 11:56 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Jun 12, 2026, 01:25 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 12, 2026, 01:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 1, 2026 Network Outage 2h 27m YourCloudTelco Calling Platform (Network)

Started Jun 01, 2026, 11:05 PM UTC· resolved Jun 02, 2026, 01:32 AM UTC

  1. identified Jun 01, 2026, 11:05 PM UTC

    The issue has been identified and a fix is being implemented.

  2. resolved Jun 02, 2026, 01:32 AM UTC

    This incident has been resolved.

  3. postmortem Jun 02, 2026, 01:32 AM UTC

    Earlier today we experienced a brief service interruption affecting parts of our voice platform. The issue was caused by an unexpected interaction between **OpenSIPS**, the platform that manages and routes phone calls across our network, and **Homer**, a monitoring system used by our engineers for call analysis and troubleshooting. This interaction resulted in OpenSIPS consuming excessive server resources, causing call processing services to become unavailable. Unfortunately, diagnosing the root cause took longer than expected because the symptoms initially appeared to be a general OpenSIPS performance issue rather than a fault related to the monitoring platform. ### **What customers experienced** * Outbound and inbound calling services were unavailable during the incident period. * Some call attempts may have failed or been unable to connect. ### **Resolution** * The Homer integration was isolated from the OpenSIPS platform. * OpenSIPS services were restored and normal call processing resumed. * Additional monitoring and safeguards are being reviewed to help prevent a recurrence. We apologise for any inconvenience caused and appreciate your patience while the issue was investigated and resolved

Read the full incident report →

Minor April 21, 2026 Newtowrk issues 1h 23m YourCloudTelco Calling Platform (Network)

Started Apr 21, 2026, 03:42 AM UTC· resolved Apr 21, 2026, 05:05 AM UTC

  1. investigating Apr 21, 2026, 03:42 AM UTC

    We are currently investigating this issue.

  2. monitoring Apr 21, 2026, 03:57 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 21, 2026, 05:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 20, 2025 Calls not connecting inbound and outbonud 1h 17m YourCloudTelco Calling Platform (Network)

Started Nov 20, 2025, 04:20 AM UTC· resolved Nov 20, 2025, 05:38 AM UTC

  1. identified Nov 20, 2025, 04:20 AM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Nov 20, 2025, 04:54 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Nov 20, 2025, 05:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 10, 2025 Arena access 1d 1h Arena

Started Nov 10, 2025, 11:07 PM UTC· resolved Nov 12, 2025, 12:10 AM UTC

  1. identified Nov 10, 2025, 11:07 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Nov 10, 2025, 11:20 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Nov 12, 2025, 12:10 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 10, 2025 Inbound calling issue 59m YourCloudTelco Calling Platform (Network)

Started Nov 10, 2025, 03:46 AM UTC· resolved Nov 10, 2025, 04:46 AM UTC

  1. identified Nov 10, 2025, 03:46 AM UTC

    We have identified an issue with some of our numbers being unable to receive calls, we are currently working on a fix.

  2. resolved Nov 10, 2025, 04:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 11, 2025 Outage 2d 7h YourCloudTelco Calling Platform (Network), Arena

Started Jul 11, 2025, 09:54 PM UTC· resolved Jul 14, 2025, 05:20 AM UTC

  1. investigating Jul 11, 2025, 09:54 PM UTC

    We are currently investigating this issue.

  2. identified Jul 11, 2025, 10:13 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jul 11, 2025, 11:27 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jul 14, 2025, 05:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 10, 2025 Registration issue 19h 15m YourCloudTelco Calling Platform (Network)

Started Jun 10, 2025, 04:04 AM UTC· resolved Jun 10, 2025, 11:20 PM UTC

  1. investigating Jun 10, 2025, 04:04 AM UTC

    We are currently investigating this issue.

  2. monitoring Jun 10, 2025, 04:19 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 10, 2025, 11:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 12, 2025 Degraded voice network – YourCloudTelco Calling Platform (Network)

Started Mar 12, 2025, 02:34 AM UTC· resolved Mar 12, 2025, 02:34 AM UTC

  1. resolved Mar 12, 2025, 02:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 17, 2025 Outbound calls to mobiles 3h 31m YourCloudTelco Calling Platform (Network)

Started Feb 17, 2025, 09:00 PM UTC· resolved Feb 18, 2025, 12:32 AM UTC

  1. investigating Feb 17, 2025, 09:00 PM UTC

    We are currently investigating an issue with outbound calls to mobiles.

  2. monitoring Feb 17, 2025, 09:30 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 18, 2025, 12:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 27, 2025 Degraded calling 3h

Started Jan 27, 2025, 10:00 AM UTC· resolved Jan 27, 2025, 01:00 PM UTC

  1. resolved Jan 31, 2025, 12:02 AM UTC

    Incident Summary: On January 31, 2025, a voice server (OpenSIPS) experienced severe performance degradation due to excessive CPU utilisation, resulting in impaired call handling capabilities. The incident was resolved through a service restart. Timeline: 9:30 PM: Initial spike in outbound calls observed 10:00 AM: Beginning of a significant decrease in call volume 11:45 AM: Continued service degradation 12:00 AM: Service restored following OpenSIPS restart Impact: Reduced capacity to handle inbound and outbound calls Noticeable decrease in successful call completions No complete service interruption, but severely degraded performance Root Cause: The OpenSIPS server experienced CPU utilisation reaching 99%, severely impacting its ability to process calls efficiently. While the service remained running, it was effectively non-responsive due to the excessive load. Resolution: The immediate issue was resolved by restarting the OpenSIPS service at 12:00 AM AEDT. Following the restart, normal service operation resumed with CPU usage returning to expected levels.

Read the full incident report →