Devices are successfully performing activation operations for Verizon Wireless SIMs. Monitoring period continues.
Posted Apr 23, 2025 - 05:51 UTC
Monitoring
We have confirmed the fix implemented was successful. Devices can now perform activation operations for Verizon Wireless SIMs.
We will consider this resolved if no further impacts are observed during our monitoring period.
Posted Apr 23, 2025 - 01:11 UTC
Update
Verizon have implemented the fix that's preventing fresh activations. We continue to confirm they are fully active on our side. Additional updates will be provide as soon as more information becomes available.
NOTE: This issue does not impact connectivity services for currently active SIMs.
Posted Apr 23, 2025 - 00:23 UTC
Identified
Verizon is currently getting the affected fresh activations pushed through, and we are working to fully confirm they are showing fully active on our side. A new update will be sent out soon once we see all lines with active lines.
Posted Apr 22, 2025 - 22:18 UTC
Update
Verizon support has come up with a permanent fix, which can be implemented within two to three days; currently, they are working on trying a temporary workaround.
We should be able to verify the results for the temporary workaround within an hour or so.
Posted Apr 22, 2025 - 21:06 UTC
Update
Verizon continues working on addressing internal issue preventing fresh activations. Their support team will be providing us an update within the next hour.
Posted Apr 22, 2025 - 19:55 UTC
Update
Verizon's internal teams are diligently working to resolve identified issue preventing fresh activations. Although, we do not have a specified ETR, we should be receiving updates from them within an hour.
NOTE: This issue does not impact connectivity services for currently active SIMs.
Posted Apr 22, 2025 - 17:57 UTC
Update
Verizon is working to resolve internal issue for fresh activations. We expect an update within an hour on where they are in producing a resolution.
Posted Apr 22, 2025 - 16:52 UTC
Update
We are continuing to investigate this issue.
Posted Apr 22, 2025 - 15:27 UTC
Investigating
Our partner has a working theory on underlying cause, but we are still coordinating with them to come up with a fix to get new activations to process completely.
NOTE: This issue does not impact connectivity services for currently active SIMs.
Posted Apr 22, 2025 - 12:45 UTC
Identified
The issue has been identified & a fix is being implemented.
We will provide more updates in next 90 minutes.
NOTE: This issue does not impact connectivity services for currently active SIMs.
Posted Apr 22, 2025 - 12:42 UTC
Update
Our partner has identified an internal issue within their backend systems impeding fresh activations, but the engineers are still working to determine a fix to get activation attempts to process successfully.
We will share additional updates as soon as more information becomes available.
NOTE: This issue does not impact connectivity services for currently active SIMs.
Posted Apr 22, 2025 - 10:41 UTC
Update
Customers may receive the following failure when performing Activate Operations for Verizon Wireless SIMs:
--- Error received from operator [UnifiedWebService REQUEST_FAILED CarrierRequestUnsuccessful -> REQUEST_FAILED Child bundle creation in progress. Please retry the request later.] ---
We are currently working with Verizon to investigate an issue affecting activation operations for Verizon Wireless SIMs. Customers may experience failures when attempting to activate SIMs.
We will provide updates as we learn more and work toward a resolution.
NOTE: This issue does not impact connectivity services for currently active SIMs.
Posted Apr 22, 2025 - 08:46 UTC
Update
We are engaged with Verizon & are continuing to investigate the issue. However Customers may receive the following failure when performing Activate Operations for Verizon Wireless SIMs:
--- Error received from operator [UnifiedWebService REQUEST_FAILED CarrierRequestUnsuccessful -> REQUEST_FAILED Child bundle creation in progress. Please retry the request later.] ---
We will share additional updates in next 90 minutes.
NOTE: This issue does not impact connectivity services for currently active SIMs.
Posted Apr 22, 2025 - 06:37 UTC
Update
Customers may receive the following failure when performing Activate Operations for Verizon Wireless SIMs:
--- Error received from operator [UnifiedWebService REQUEST_FAILED CarrierRequestUnsuccessful -> REQUEST_FAILED Child bundle creation in progress. Please retry the request later.] ---
Engagement and escalation with Verizon are ongoing. Our engineers are actively working with their team to determine the root cause and implement a resolution. We will share additional updates as more information becomes available.
NOTE: This issue does not impact connectivity services for currently active SIMs.
Posted Apr 22, 2025 - 04:42 UTC
Update
Customers may receive the following failure when performing Activate Operations for Verizon Wireless SIMs:
--- Error received from operator [UnifiedWebService REQUEST_FAILED CarrierRequestUnsuccessful -> REQUEST_FAILED Child bundle creation in progress. Please retry the request later.] ---
Engagement and escalation with Verizon continues. Engineers are actively working to determine the root cause and resolution. We will provide updates as more information is learned.
NOTE: This issue does not impact connectivity services for currently active SIMs.
Posted Apr 22, 2025 - 02:40 UTC
Investigating
Customers may receive the following failure when performing Activate Operations for Verizon Wireless SIMs:
--- Error received from operator [UnifiedWebService REQUEST_FAILED CarrierRequestUnsuccessful -> REQUEST_FAILED Child bundle creation in progress. Please retry the request later.] ---
We have engaged and escalated the issue with Verizon. Engineers are actively working to determine the root cause and resolution. We will provide updates as more information is learned.
NOTE: This issue does not impact connectivity services for currently active SIMs.
Posted Apr 22, 2025 - 00:54 UTC
This incident affected: Enhanced Carrier Connectivity (NAM) / MSO (API).