Thanks — that’s very helpful to know this is happening for every number. I know that’s frustrating, and I’ll help you get this resolved.
Quick summary of what’s happening
• LiveKit’s backend is timing out when calling CarrierX’s API at https://api.carrierx.com/core/v2/phonenumber/dids, causing the "context deadline exceeded" error and preventing any number provisioning.
Next steps I can take and what I need from you Please provide the following so I can investigate and narrow down the root cause:
1. LiveKit Project ID (or the account identifier you use to order numbers).
2. Approximate time (and timezone) when this started, and whether it’s been continuous since then.
3. Confirm whether you attempted retries and, if so, how many and at what intervals.
4. Any recent changes on your side that could affect network egress (firewall rules, IP allowlists, new VPC/NAT config, etc.).
5. If possible, paste one full error instance (timestamped log line) — the snippet you already sent is helpful, but a full log entry helps match diagnostics.
What I’ll do after you share those details
• Check our backend request logs for your Project ID and time range to see whether the CarrierX requests are failing repeatedly or intermittently.
• Look for patterns (rate limits, repeated timeouts, 5xx responses) and confirm whether this is a transient network issue or something ongoing between LiveKit and CarrierX.
• Recommend immediate workarounds (retries with backoff, alternative provisioning paths) based on findings, and provide next steps to restore number ordering.
If you’d like to start immediately: share the Project ID and a recent timestamped log entry and I’ll begin checking the request traces right away.
, with interactive elements