Rewindex

ChangesDailySIP / PSTN Disruption

Daily: Critical incident: SIP / PSTN Disruption

Major incidentcritical (vendor)Changed Detected stspg.io (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Daily removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: SIP / PSTN Disruption
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-02-18 11:31 UTC
AddedResolved time#5
Before: not present
After: 2026-02-18 15:55 UTC
AddedAffected components#6
Before: not present
After: SIP/PSTN
AddedUpdateinvestigating#7
Before: not present
After: We are currently investigating an issue affecting SIP / PSTN inbound calls. Customers may encounter 480 “Temporarily Unavailable” errors when attempting to receive calls. Our engineering team is actively working to identify the root cause and restore service.
AddedUpdateidentified#8
Before: not present
After: Our upstream carrier partner has identified the root cause of the issue impacting SIP/PSTN dial-in (inbound) calling and has implemented a fix. Service is beginning to recover, though some degradation may still be present while the fix fully propagates. We are actively monitoring and working to confirm full restoration of inbound calling. Outbound (dial-out) calling remains unaffected.
AddedUpdatemonitoring#9
Before: not present
After: The fix from our upstream carrier partner has been applied, and service has been restored for SIP/PSTN dial-in (inbound) calling. We are seeing successful inbound call connections again, and our internal testing confirms recovery. We are continuing to monitor closely to ensure stability and full recovery.
AddedUpdateresolved#10
Before: not present
After: This incident has been resolved.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

Wednesday, February 18

1 incident change

All Daily changesDaily profileMarkdownJSON