IntelePeer incident

Outage affecting Inbound/Oubound Calls. It looks like CHI, DEN and DAL are affected.

Critical Resolved View vendor source →

IntelePeer experienced a critical incident on August 15, 2022 affecting Chicago Switch and Dallas Switch and 1 more component, lasting 4h 18m. The incident has been resolved; the full update timeline is below.

Started
Aug 15, 2022, 07:19 PM UTC
Resolved
Aug 15, 2022, 11:37 PM UTC
Duration
4h 18m
Detected by Pingoru
Aug 15, 2022, 07:19 PM UTC

Affected components

Chicago SwitchDallas SwitchDenver Switch

Update timeline

  1. investigating Aug 15, 2022, 04:47 PM UTC

    We are currently investigating this issue.

  2. investigating Aug 15, 2022, 04:47 PM UTC

    We are continuing to investigate this issue.

  3. investigating Aug 15, 2022, 04:49 PM UTC

    We are continuing to investigate this issue.

  4. investigating Aug 15, 2022, 04:50 PM UTC

    We are continuing to investigate this issue.

  5. investigating Aug 15, 2022, 04:53 PM UTC

    We are continuing to investigate this issue.

  6. identified Aug 15, 2022, 06:22 PM UTC

    Intelepeer is aware of the impairment issue. Some nodes have been restored and call processing is slowly returning to normal. We will continue to provide updates as they become available.

  7. identified Aug 15, 2022, 07:19 PM UTC

    The latest update. Unfortunately, IntelePeer is still running in an impaired stated. We are restoring our routing engine, but we still have impairment on some of the nodes as we are seeing conflicts with external services (external feeds attributed to Stir Shaken affective stability) which we are trying to disassociate. . As of this juncture, we expect that we will be running in an impaired state until 5 pm ET. Currently inbound and outbound call processing is returning to normal completion levels as we have partial restoral of our routing engine. More updates to come.

  8. identified Aug 15, 2022, 07:53 PM UTC

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

  9. identified Aug 15, 2022, 07:54 PM UTC

    The latest update. Unfortunately, IntelePeer is still running in an impaired stated. We are restoring our routing engine, but we still have impairment on some of the nodes as we are seeing conflicts with external services (external feeds attributed to Stir Shaken affective stability) which we are trying to disassociate. . As of this juncture, we expect that we will be running in an impaired state until 5 pm ET. Currently inbound and outbound call processing is returning to normal completion levels as we have partial restoral of our routing engine. More updates to come.

  10. identified Aug 15, 2022, 07:54 PM UTC

    The latest update. Unfortunately, IntelePeer is still running in an impaired stated. We are restoring our routing engine, but we still have impairment on some of the nodes as we are seeing conflicts with external services (external feeds attributed to Stir Shaken affective stability) which we are trying to disassociate. . As of this juncture, we expect that we will be running in an impaired state until 5 pm ET. Currently inbound and outbound call processing is returning to normal completion levels as we have partial restoral of our routing engine. More updates to come.

  11. identified Aug 15, 2022, 07:55 PM UTC

    The latest update. Unfortunately, IntelePeer is still running in an impaired stated. We are restoring our routing engine, but we still have impairment on some of the nodes as we are seeing conflicts with external services (external feeds attributed to Stir Shaken affective stability) which we are trying to disassociate. . As of this juncture, we expect that we will be running in an impaired state until 5 pm ET. Currently inbound and outbound call processing is returning to normal completion levels as we have partial restoral of our routing engine. More updates to come.

  12. monitoring Aug 15, 2022, 08:39 PM UTC

    Inbound and outbound call processing is returning to normal completion levels. No other issues are anticipated at this time as we work to analyze impact. More updates to come. We are restoring our routing engine, but we still have impairment on some of the nodes as we are seeing conflicts with external services (external feeds attributed to Stir Shaken affective stability) which we are trying to disassociate.. Thank you for your patience. IntelePeer Operations Team

  13. monitoring Aug 15, 2022, 09:27 PM UTC

    Inbound and outbound call processing has been restored to normal levels. No other issues are anticipated at this time. Stir/Shaken capabilities are disabled at this moment due to the issues that were created which caused today’s impairment. Intelepeer will continue to work with its stir/shaken vendor to validate and restore services once all potential issues are identified and addressed. A full root cause analysis will be provided to every customer. Thank you for your patience. IntelePeer Operations Team

  14. resolved Aug 15, 2022, 11:37 PM UTC

    This incident has been resolved.