Störungsverlauf von Secureco

1. 21. September 2026 um 04:46 UTCinvestigating

   Wir untersuchen derzeit ein problem mit einem unserer carrier, wenn anrufe verbunden sind, aber kein audio vorhanden ist.

2. 21. September 2026 um 05:09 UTCmonitoring

   Sanierungsmaßnahmen durchgeführt und wir sehen Anrufe mit normalem Audio aus dem Träger jetzt. Wir überwachen weiterhin die Leistung

3. 21. September 2026 um 05:25 UTCidentified

   Wir sehen, dass Anrufe immer noch kein richtiges Audio für einige Kunden haben. Das Team arbeitet an zusätzlichen Sanierungsmaßnahmen.

4. 21. September 2026 um 05:35 UTCmonitoring

   Das Problem ist gelöst. Wir überwachen weiterhin

5. 21. September 2026 um 05:35 UTCmonitoring

   Wir werden weiterhin auf weitere Probleme achten.

6. 21. September 2026 um 08:46 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 16. Juni 2026 um 00:28 UTCinvestigating

   We are investigating unusual errors and some performance degradation of our self-service IVP portal / API. This is related to the Portal only and has no impact on calls\payments processing.

2. 16. Juni 2026 um 03:34 UTCidentified

   Our team has identified the problem and is working on the fix

3. 17. Juni 2026 um 03:40 UTCmonitoring

   A fix has been deployed and we are monitoring the IVP portal performance

4. 18. Juni 2026 um 00:50 UTCresolved

   This incident has been resolved.

1. 28. Mai 2026 um 23:04 UTCinvestigating

   We are currently investigating an issue with certain payment types. Some payments may be impacted.

2. 28. Mai 2026 um 23:20 UTCidentified

   We have found the cause of the issue and a fix is now being prepared and implemented.

3. 29. Mai 2026 um 00:00 UTCmonitoring

   The fix has been successful and transactions should now work as expected. Will continue to monitor to ensure normal operation,

4. 29. Mai 2026 um 00:03 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 29. Mai 2026 um 01:04 UTCresolved

   Services have now returned to normal.

1. 25. Mai 2026 um 04:55 UTCresolved

   Due to the failure of an emergency change required to ensure the security, integrity and availability of the AU1, AU2 and AU3 regions, we are aware that customer experienced call failures during new call attempts for approximately 15 to 20 minutes from approximately 14h50 AEST on 18/05/2026. Active calls did not experience any impact and the issue was confirmed resolved at 15h08, with monitoring revealing all calls connecting successfully from that time onwards.

1. 22. April 2026 um 02:34 UTCinvestigating

   SecureCo has been notified by one of the carriers in AU about an issue affecting their inbound and outbound voice services across Australian carriers. The incident was identified at 22 April 2026, 11:05 (AEST) and is under investigation. Current known impact: Intermittent inbound call failures, including toll-free (1800) services Outbound calls may experience brief disruption but are generally completing via automatic rerouting. We are monitoring the situation and will provide further updates as they become available.

2. 22. April 2026 um 02:44 UTCmonitoring

   We have been notified by the carrier that the issue has been resolved.

3. 22. April 2026 um 06:11 UTCresolved

   This incident has been resolved.

1. 25. Februar 2026 um 18:19 UTCinvestigating

   We are currently investigating errors seen in Payment IVR transaction processing

2. 25. Februar 2026 um 18:41 UTCidentified

   The issue has been identified and a fix has been deployed.

3. 25. Februar 2026 um 18:42 UTCmonitoring

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

4. 25. Februar 2026 um 20:37 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 25. Februar 2026 um 21:27 UTCresolved

   This incident has been resolved.

1. 14. Dezember 2025 um 23:48 UTCinvestigating

   We are currently investigating reports of call failures affecting SecureCo AU region

2. 14. Dezember 2025 um 23:59 UTCidentified

   We have identified the problem and the team is working on the fix. ETA 10 mins

3. 15. Dezember 2025 um 00:00 UTCidentified

   We are continuing to work on a fix for this issue.

4. 15. Dezember 2025 um 00:01 UTCidentified

   The services are restored back to operational. We are continuing to monitor the situation

5. 15. Dezember 2025 um 00:04 UTCmonitoring

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

6. 15. Dezember 2025 um 00:06 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 15. Dezember 2025 um 02:49 UTCresolved

   This incident has been resolved.

1. 29. Oktober 2025 um 01:57 UTCinvestigating

   We are investigating issues with Payment IVR affecting some of our Customers

2. 29. Oktober 2025 um 02:59 UTCinvestigating

   Investigation is ongoing, some remediation steps attempted, the issue is still ongoing.

3. 29. Oktober 2025 um 03:37 UTCinvestigating

   Investigation ongoing. Root cause is still not identified.

4. 29. Oktober 2025 um 04:11 UTCmonitoring

   The issue has been identified and service has been restored. We will continue to monitor for the next hour prior to closing the incident.

5. 29. Oktober 2025 um 05:28 UTCresolved

   This incident has been resolved.

1. 16. Oktober 2025 um 19:00 UTCinvestigating

   We are currently investigating this issue.

2. 16. Oktober 2025 um 19:01 UTCinvestigating

   We are continuing to investigate this issue.

3. 16. Oktober 2025 um 19:21 UTCidentified

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

4. 16. Oktober 2025 um 19:57 UTCmonitoring

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

5. 16. Oktober 2025 um 20:48 UTCresolved

   This incident has been resolved.

1. 4. Oktober 2025 um 02:20 UTCinvestigating

   We are investigating the issue that seems to affect both outbound and inbound calls

2. 4. Oktober 2025 um 02:25 UTCmonitoring

   A fix has been deployed and all services seem to be back to normal. We continue monitoring the situation

3. 4. Oktober 2025 um 06:48 UTCresolved

   This incident has been resolved.

1. 29. September 2025 um 22:33 UTCinvestigating

   We are investigating reports of some intermittent issues with our Payments API

2. 29. September 2025 um 23:05 UTCresolved

   All services are back to normal

1. 16. September 2025 um 09:05 UTCinvestigating

   We have been notified by one of our carriage suppliers of an incident affecting Australia and New Zealand. We will provide further information when available.

2. 16. September 2025 um 09:09 UTCmonitoring

   Our carriage partner has notified us that the issue has been resolved now. We have validated that the service has been restored via test calls from our side and will continue to monitor the situation.

3. 16. September 2025 um 09:44 UTCresolved

   This incident has been resolved.

1. 8. September 2025 um 08:29 UTCinvestigating

   We are currently investigating voice call quality issues experienced by customers connecting to the Payments service in Australia

2. 8. September 2025 um 09:03 UTCidentified

   The issue has been identified and fix is being deployed

3. 8. September 2025 um 09:07 UTCmonitoring

   A fix has been applied and we are monitoring the results

4. 8. September 2025 um 22:43 UTCresolved

   This incident has been resolved.

1. 4. August 2025 um 00:02 UTCinvestigating

   We are currently investigating an issue with completing payments using Payment IVR

2. 4. August 2025 um 00:40 UTCresolved

   This incident has been resolved now

1. 30. Juli 2025 um 02:19 UTCinvestigating

   We are currently investigating a potential issue with our Hosted Payments Page This may impact some payment captures via the HPP

2. 30. Juli 2025 um 02:58 UTCidentified

   We have identified the issue and are currently implementing a fix.

3. 30. Juli 2025 um 03:55 UTCmonitoring

   Fixes have been implemented and services have returned to normal operation. We will monitor for the next 60 minutes to confirm.

4. 30. Juli 2025 um 05:16 UTCresolved

   Issue has been resolved, all services have returned to normal.

1. 2. Juni 2025 um 19:32 UTCresolved

   We are aware of ongoing issues with the Cloud Provider hosting our AU1 region since approximately 01:30 AEST 03/06/25 and have taken action to mitigate the issue until it is fully resolved, at this stage we are monitoring to ensure there is no further impact to customers. Update 07:20 AEST: We are continuing to monitor the resolution activities by our cloud provider and monitor for customer impact, with no known customer impact at this time.

1. 4. Mai 2025 um 23:24 UTCidentified

   We are experiencing a logon issue with our public service desk portal. We are still receiving support emails and phone calls, though you may not be able to view current and past cases via the web portal

2. 5. Mai 2025 um 07:15 UTCresolved

   The public service desk web portal is now available.

1. 6. April 2025 um 22:18 UTCinvestigating

   We are are currently investigating issues relating to our payment services.

2. 6. April 2025 um 22:33 UTCidentified

   The team have identified the cause of the issue and are currently remediating. Payment services should resume shortly.

3. 6. April 2025 um 22:53 UTCmonitoring

   Services have resumed and transactions are now being observed since 8:37am (AEST). The team currently monitoring services.

4. 6. April 2025 um 23:09 UTCresolved

   This incident has been resolved.

1. 4. März 2025 um 22:47 UTCinvestigating

   We are currently investigating some reported call issues / failures & degraded service.

2. 4. März 2025 um 23:04 UTCmonitoring

   Issue has been identified and service has now stablised. Engineers are currently monitoring.

3. 4. März 2025 um 23:05 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 5. März 2025 um 00:45 UTCresolved

   Monitoring has confirmed that the issue has been successfully resolved and no further action is required.

1. 17. Februar 2025 um 08:31 UTCinvestigating

   We are currently investigating ongoing reports with traffic instability between our Sydney POPs and our IVP AU1 Cloud Environment.

2. 17. Februar 2025 um 08:35 UTCinvestigating

   Earlier today we observed traffic instability isolated to a few services and customers. The issue was resolved and isolated by failing over to our HA SBC. Unfortunately as the day progressed, additional reported cases had been observed. Investigations are ongoing with our connectivity partners and cloud partners to understand the cause of the issue.

3. 17. Februar 2025 um 09:43 UTCidentified

   The issue observed has been identified as a BGP flapping issue. Investigations as to root cause are ongoing.

4. 17. Februar 2025 um 11:14 UTCidentified

   Investigations have led to a BGP flap occuring on all megaport services. An Engineer has been dispatched to the POPs for further investgation works.

5. 17. Februar 2025 um 11:15 UTCidentified

   We are continuing to work on a fix for this issue.

6. 17. Februar 2025 um 12:33 UTCidentified

   Emergency works has commenced at SYD2 POP

7. 17. Februar 2025 um 13:17 UTCidentified

   POP Maintenance on SY2 Completed

8. 17. Februar 2025 um 18:16 UTCmonitoring

   Our team has implemented a fix with the support of our routing vendor and we are monitoring to ensure there are no remaining issues.

9. 18. Februar 2025 um 00:15 UTCmonitoring

   We have identified a final routing issue and resolved it, at this time we will continue to monitor to ensure no issues remain.

10. 18. Februar 2025 um 03:38 UTCresolved

    This incident has been resolved.