VoIP.ms incident
losangeles4.voip.ms delayed CDR
Ongoing since 06:59 PM UTC, affecting VoIP.ms Platform (Call Detail Records) and Point of Presence: United States (Los Angeles 4, CA).
We are continuing to work on a fix for this incident. Please note that changes made in the customer portal regarding [losangeles4.voip.ms](http://losangeles4.voip.ms) (DID POP changes, voicemail recordings, etc.) will not be reflected during this time however please note that the voice service remains undisrupted. Thank you for your comprehension.
Affected components
Update timeline
- investigating Nov 06, 2026, 06:59 PM UTC
We are currently investigating delay in the call records and call recordings for calls made from within the [losangeles4.voip.ms](http://losangeles4.voip.ms) POP server. Our team is working to solve this as soon as possible. Apologies for the inconveniences this cause you.
- identified Nov 06, 2026, 07:22 PM UTC
We are continuing to work on a fix for this incident. Please note that changes made in the customer portal regarding [losangeles4.voip.ms](http://losangeles4.voip.ms) (DID POP changes, voicemail recordings, etc.) will not be reflected during this time however please note that the voice service remains undisrupted. Thank you for your comprehension.
Your product runs on more than VoIP.ms
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services