TPG Telecom Outage History

Started Aug 18, 2026, 02:23 PM UTC· resolved Aug 18, 2026, 03:30 PM UTC

1. investigating Aug 18, 2026, 02:23 PM UTC

   We are currently investigating an issue in which an end user will receive an error while navigating their settings in the UI stating "There was an error retrieving some data. Please refresh the page or contact support if the issue persists."

2. investigating Aug 18, 2026, 02:57 PM UTC

   We are continuing to investigate this issue.

3. monitoring Aug 18, 2026, 03:26 PM UTC

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

4. resolved Aug 18, 2026, 03:30 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 25, 2026, 05:59 AM UTC· resolved Jun 26, 2026, 04:47 AM UTC

1. investigating Jun 25, 2026, 05:59 AM UTC

   We are currently investigating an issue causing message delivery degradation. Customers may experience delays in message processing, with some message statuses remaining in "Enroute" for longer than expected. Our engineering teams are actively investigating the root cause and working to restore normal service as quickly as possible. We will provide further updates as more information becomes available.

2. investigating Jun 25, 2026, 06:46 AM UTC

   We are investigating an issue impacting outbound message delivery across all regions. Customers will experience delays in message processing and delivery, with message statuses remaining in "Enroute" for longer than expected. This issue is affecting outbound message sending across our platform. Our engineering teams are actively investigating the root cause and working to restore normal service as quickly as possible. We will provide further updates as more information becomes available.

3. investigating Jun 25, 2026, 08:10 AM UTC

   We are still investigating an issue impacting outbound message delivery and engaging additional resources to help restore normal service as quickly as possible. Further updates will be provided as more information becomes available.

4. investigating Jun 25, 2026, 08:42 AM UTC

   We have identified an issue within the internal systems responsible for routing messages to downstream mobile network operators. Since approximately 14:30 AEST, messages within our platform have been intermittently becoming stuck in a router worker process, resulting in delays to outbound message delivery. While the issue is ongoing, small batches of queued messages are continuing to be processed and delivered approximately every few minutes. Customers may also observe duplicate message deliveries in some cases as a result of this issue. Our engineering teams are actively investigating the root cause and working to restore normal service as quickly as possible. Once the issue has been resolved, we expect queued messages to resume processing and be delivered automatically. We will provide further updates as more information becomes available.

5. investigating Jun 25, 2026, 09:52 AM UTC

   Our investigation is ongoing, and we have not yet been able to definitively identify the root cause of the issue affecting outbound message delivery within the platform. To prevent further message backlog growth and reduce the risk of additional duplicate deliveries, we have implemented the following mitigation measures: Message submissions are being temporarily blocked and will return Failed responses. Message workers have been stopped to prevent further processing of impacted traffic. Queued messages are being redirected to a new queue for post-incident analysis and recovery efforts. Customers using SMPP may still be able to submit messages during this period. As a result, some message duplication may continue to occur until the incident is fully resolved. As part of our recovery strategy, messages queued from the start of the incident will not be automatically reprocessed. While some of these messages may already have been successfully delivered after experiencing delays, others may not have been sent. Customers should be aware that message reconciliation and potential resubmission may be required once service has been restored. Our engineering teams remain actively engaged in identifying the root cause and restoring normal service. We will continue to provide updates as new information becomes available.

6. investigating Jun 25, 2026, 10:36 AM UTC

   We are continuing to investigate an issue affecting outbound message delivery. As a precaution, new message submissions are currently paused while we stabilise the system. Our engineering teams are actively working to restore normal service. Further updates will follow as more information becomes available.

7. investigating Jun 25, 2026, 11:12 AM UTC

   We are continuing to investigate this issue.

8. investigating Jun 25, 2026, 11:44 AM UTC

   We are continuing to investigate the issue. Our engineering teams are actively working to restore normal service as quickly as possible.

9. investigating Jun 25, 2026, 12:17 PM UTC

   We are continuing to investigate this issue.

10. investigating Jun 25, 2026, 12:53 PM UTC

    We are continuing to investigate this issue.

11. investigating Jun 25, 2026, 01:54 PM UTC

    We are continuing to investigate this issue. We are working on high priority together with external resources to restore service. Further updates will follow as more information becomes available.

12. investigating Jun 25, 2026, 03:04 PM UTC

    We are continuing to investigate this issue. We are actively working on restoring service through mitigation steps, including redirecting traffic to a stable alternative messaging setup. External support is also engaged and working in parallel on recovery efforts. We will provide further updates as progress is made or as new information becomes available.

13. investigating Jun 25, 2026, 03:45 PM UTC

    We are continuing to investigate this issue. We are actively working on restoring service through mitigation steps, including redirecting traffic to a stable alternative messaging setup. External support is also engaged and working in parallel on recovery efforts. We will provide further updates as progress is made or as new information becomes available.

14. monitoring Jun 25, 2026, 04:00 PM UTC

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

15. monitoring Jun 25, 2026, 05:26 PM UTC

    A fix has been implemented and messaging services have recovered. We have completed validation testing and confirmed message sending and delivery are functioning as expected. Our teams will continue to closely monitor platform performance to ensure stability. We are not currently observing any further issues related to this incident.

16. monitoring Jun 26, 2026, 02:03 AM UTC

    Messaging services within our platform continue to operate at normal capacity, with message sending and delivery performing as expected. Our engineering teams are not observing any further issues related to this incident and continue to closely monitor platform performance to ensure ongoing stability. Work is now focused on a comprehensive investigation into the outage that occurred yesterday. Our engineering teams are collaborating with all relevant parties to determine the root cause and will provide further information as it becomes available.

17. resolved Jun 26, 2026, 04:47 AM UTC

    This incident has now been resolved, and our platform messaging services is operating normally. Message flow has returned to regular capacity, and no further issues are being observed. As part of the recovery process, messages submitted between 2:40 PM AEST on 25 June 2026 and 1:00 AM AEST on 26 June 2026 may remain in an ENROUTE status but will not be delivered. If these messages are still required, they will need to be resent. Our engineering teams are continuing to work with all relevant parties to complete a thorough root cause investigation. A Root Cause Analysis (RCA) will be shared once the investigation has concluded. We apologise for the disruption this incident caused and thank you for your patience and understanding throughout the recovery process.

Read the full incident report →

Started Jun 18, 2026, 12:03 AM UTC· resolved Jun 18, 2026, 02:35 AM UTC

1. investigating Jun 18, 2026, 12:03 AM UTC

   Delays in message deliverability have been recorded for Australian/APAC carriers . We are currently investigating the cause of this issue.

2. investigating Jun 18, 2026, 12:04 AM UTC

   We are continuing to investigate this issue.

3. investigating Jun 18, 2026, 12:04 AM UTC

   We are continuing to investigate this issue.

4. monitoring Jun 18, 2026, 01:15 AM UTC

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

5. resolved Jun 18, 2026, 02:35 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 28, 2026, 01:21 AM UTC· resolved May 28, 2026, 06:17 AM UTC

1. investigating May 28, 2026, 01:21 AM UTC

   We are currently investigating an issue with the Web Portal UI impacting the processing of new Australian Alpha Tag registration requests. Requests are timing out and users are unable to proceed to the next step of the registration process. This issue is limited to the registration interface only. There is no impact to existing Alpha Tags or current message sending services.

2. monitoring May 28, 2026, 01:49 AM UTC

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

3. resolved May 28, 2026, 06:17 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 25, 2026, 11:57 PM UTC· resolved Mar 26, 2026, 04:08 AM UTC

1. resolved Mar 26, 2026, 05:43 AM UTC

   Between 10:57 and 15:08 AEDT, customers experienced issues/delays with message delivery affecting both inbound and outbound messaging. During this time, messages were queued within the platform and processed once connectivity was restored. The incident was caused by changes to underlying network routing and connectivity, which disrupted message traffic paths. Connectivity was restored by establishing a new, direct, and stable network path. Following this, all queued messages were successfully delivered. All services are now fully operational, and connectivity has remained stable since 15:08 AEDT.

Read the full incident report →

Started Mar 02, 2026, 12:22 AM UTC· resolved Mar 02, 2026, 03:50 AM UTC

1. investigating Mar 02, 2026, 12:22 AM UTC

   We are currently experiencing issues with emails sent to all support addresses. In the meantime, please contact Support via Live Chat until the issue is resolved. Our IT team is working on this as a priority and will provide updates as soon as they become available.

2. investigating Mar 02, 2026, 02:24 AM UTC

   We are continuing to investigate this issue.

3. resolved Mar 02, 2026, 03:50 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 11, 2026, 12:17 AM UTC· resolved Feb 11, 2026, 02:24 AM UTC

1. investigating Feb 11, 2026, 12:17 AM UTC

   We are currently investigating an issue where end users are unable to add or edit contacts within the platform. No error message appears, but updates are not being saved. Our engineers are actively working to resolve this issue and will provide updates as soon as possible.

2. monitoring Feb 11, 2026, 01:31 AM UTC

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

3. monitoring Feb 11, 2026, 01:32 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Feb 11, 2026, 02:24 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 09, 2026, 02:23 AM UTC· resolved Feb 09, 2026, 03:51 AM UTC

1. investigating Feb 09, 2026, 02:23 AM UTC

   Dear Customer, We are currently investigating an issue with messages not being sent and stuck in Enroute status. Our engineers are reviewing this and working to resolve it as quickly as possible.

2. identified Feb 09, 2026, 02:44 AM UTC

   Telstra has confirmed the issue on their end and they currently working to resolve it. SMS delivery and sending may be impacted.

3. monitoring Feb 09, 2026, 03:42 AM UTC

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

4. resolved Feb 09, 2026, 03:51 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 22, 2025, 10:46 PM UTC· resolved Jan 23, 2025, 03:48 AM UTC

1. investigating Jan 22, 2025, 10:46 PM UTC

   We are currently investigating a subset of customers experiencing errors on our web portal. This is impacting some users when a web page is loaded in the portal. We will update as soon as we have more information.

2. monitoring Jan 22, 2025, 10:46 PM UTC

   We have actioned a rollback and are currently monitoring the results.

3. resolved Jan 23, 2025, 03:48 AM UTC

   This incident has been resolved.

Read the full incident report →