SecureCo incident

Intermittent Quality Issues IVP SYD2

Notice Resolved View vendor source →

SecureCo experienced a notice incident on February 17, 2025 affecting Enterprise Voice for Genesys Cloud, lasting 19h 2m. The incident has been resolved; the full update timeline is below.

Started
Feb 17, 2025, 08:35 AM UTC
Resolved
Feb 18, 2025, 03:38 AM UTC
Duration
19h 2m
Detected by Pingoru
Feb 17, 2025, 08:35 AM UTC

Affected components

Enterprise Voice for Genesys Cloud

Update timeline

  1. investigating Feb 17, 2025, 08:31 AM UTC

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

  2. investigating Feb 17, 2025, 08:35 AM UTC

    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. identified Feb 17, 2025, 09:43 AM UTC

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

  4. identified Feb 17, 2025, 11:14 AM UTC

    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. identified Feb 17, 2025, 11:15 AM UTC

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

  6. identified Feb 17, 2025, 12:33 PM UTC

    Emergency works has commenced at SYD2 POP

  7. identified Feb 17, 2025, 01:17 PM UTC

    POP Maintenance on SY2 Completed

  8. monitoring Feb 17, 2025, 06:16 PM UTC

    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. monitoring Feb 18, 2025, 12:15 AM UTC

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

  10. resolved Feb 18, 2025, 03:38 AM UTC

    This incident has been resolved.