IPFone incident

Audio Quality / Packet Loss

Major Resolved View vendor source →

IPFone experienced a major incident on February 4, 2026 affecting Core Voice Network, lasting 3h 19m. The incident has been resolved; the full update timeline is below.

Started
Feb 04, 2026, 03:54 PM UTC
Resolved
Feb 04, 2026, 07:14 PM UTC
Duration
3h 19m
Detected by Pingoru
Feb 04, 2026, 03:54 PM UTC

Affected components

Core Voice Network

Update timeline

  1. investigating Feb 04, 2026, 03:54 PM UTC

    We’re aware of an increase in reports of audio quality issues, including choppy or intermittent audio from the Detroit (Legacy TelNet Worldwide) Network. Our voice networking team is actively investigating and working to isolate the cause. If you’re experiencing issues or would like to provide an update on an existing ticket, please call or text us at 800.508.1254, or email [email protected]. Our team is here to help. We’ll continue to share updates here as they become available. Thank you for your patience.

  2. monitoring Feb 04, 2026, 04:28 PM UTC

    The root cause of the audio quality and packet loss reports has been identified and remediated as of 10:58 AM ET. Our team is continuing to monitor closely to ensure service remains stable. If you’re still experiencing any issues, please report them by calling or texting 800.508.1254, or by emailing [email protected] so we can assist promptly. We’ll provide additional updates here, along with a Root Cause Analysis (RFO), once our review is complete.

  3. resolved Feb 04, 2026, 07:14 PM UTC

    The issue was traced to a section of legacy configuration on a device that affected how traffic was routed under normal redundancy conditions. The condition was identified during routine network maintenance. The configuration was corrected as of 10:58 AM ET, and service has since stabilized.

  4. postmortem Feb 04, 2026, 07:14 PM UTC

    The issue was traced to a section of legacy configuration on a device that affected how traffic was routed under normal redundancy conditions. The condition was identified during routine network maintenance. The configuration was corrected as of 10:58 AM ET, and service has since stabilized.