Incident Summary
On July 10, 2026, Peerlogic Voice experienced a network-wide service interruption affecting inbound and outbound calling, as well as certain administrative services.
This was the first network-wide outage Peerlogic has experienced in more than five years of service.
Root Cause
The interruption resulted from an incomplete configuration update within the administrative service layer of a critical infrastructure provider.
This caused the provider’s automated controls to place affected services into a restricted operating state. The incident was not caused by a failure of the Peerlogic Voice application, telecommunications platform, hardware, or underlying network architecture.
Response and Recovery
Once the configuration state was identified and corrected, service restoration began within approximately five minutes. Systems recovered normally, and no residual service impact was identified.
Preventive Actions
Peerlogic’s infrastructure includes geographic redundancy and failover protections designed to maintain service through hardware, network, and regional infrastructure failures.
Because this incident occurred within a provider-managed administrative control layer shared by the underlying services, it fell outside the normal scope of those technical failover mechanisms.
To reduce the risk of a similar provider-side configuration event, Peerlogic has implemented the following additional operational controls:
Configuration Verification Controls: Added secondary verification for changes affecting critical provider-managed service configurations, including confirmation that updates have been fully applied across all associated services.
Expanded Monitoring and Alert Routing: Updated alert distribution so that critical configuration and service-state notifications are routed immediately to shared DevOps and Operations channels.
Shared Administrative Coverage: Expanded administrative coverage for critical infrastructure platforms to ensure that configuration status and provider-originated events are visible to multiple members of the operational team.
Secondary Escalation Procedures: Established additional escalation paths for provider-originated configuration or service-state events requiring immediate operational response.
Post-Change Validation: Added explicit validation steps following administrative configuration changes to verify that all dependent services remain active and operating normally.
These controls complement our existing geographic redundancy and infrastructure safeguards and are intended to prevent a similar administrative configuration event from affecting service in the future.
Closing
We recognize the importance of uninterrupted phone service to our customers and their patients. While this was an exceptional event in more than five years of operation, we take the interruption seriously and have strengthened our configuration-management, monitoring, and operational controls as a result.