Giganet incident

Inbound & outbound call failures

Minor Resolved View vendor source →

Giganet experienced a minor incident on May 4, 2023 affecting Giganet DBX - TelcoSwitch, lasting 2h 10m. The incident has been resolved; the full update timeline is below.

Started
May 04, 2023, 09:29 AM UTC
Resolved
May 04, 2023, 11:39 AM UTC
Duration
2h 10m
Detected by Pingoru
May 04, 2023, 09:29 AM UTC

Affected components

Giganet DBX - TelcoSwitch

Update timeline

  1. investigating May 04, 2023, 09:29 AM UTC

    Investigating - We are investigating reports of inbound & outbound call failures. We have no further information at this time. Update will be posted once our teams establish cause and impact. May 04, 2023 - 10:29 BST

  2. investigating May 04, 2023, 09:39 AM UTC

    Update - The team continue to investigate and we have no further information of substance at this time. We are evaluating carrier routing and upstream supplier status in tandem to our own systems. May 04, 2023 - 10:39 BST

  3. identified May 04, 2023, 09:45 AM UTC

    Identified - Our team have identified the root cause and traffic is returning to normal levels - customers may experience intermittent service while we do that. We expect all traffic to have returned to normal within the next 10-15 minutes. Further updates will be posted as necessary and a debrief will be published to this incident in due course once we are satisfied of its complete resolution and all teams involved have debriefed their investigations and actions during this incident. May 04, 2023 - 10:36 BST

  4. monitoring May 04, 2023, 10:09 AM UTC

    Monitoring - All traffic is returning to normal. Where devices are unable to dial out (Internally or externally) we would encourage end users to re-register their handset by restarting that device. Todays incident is particularly involved with 3rd party suppliers to our infrastructure. As a result we need to debrief with both internal teams and those suppliers before we can provide further detail. It is unrelated to the incident on 3rd May 23. We will publish a transparent debrief in due course, but cannot do so until we have given those suppliers reasonable time to conclude their investigations in detail.

  5. resolved May 04, 2023, 11:39 AM UTC

    Resolved - We are satisfied this incident can be considered closed as of 10:52. We will publish a transparent debrief once we have detailed information from our suppliers and this has been discussed with the relevant internal teams. May 04, 2023 - 12:00 BST