crooked-holiday-5421
04/08/2026, 7:28 AMtall-airline-16756
04/08/2026, 7:29 AMtall-airline-16756
04/08/2026, 7:29 AM*.livekit.cloud.
• Static IP blocks are provided only when you pin to a region that supports them. The current shared static blocks are:
◦ 143.223.88.0/21
◦ 161.115.160.0/19
Could you tell me which LiveKit region or deployment you’re using (for example: US, EU, India, or a self-hosted URL)? I’ll confirm whether static IPs apply for your region or if you should allow the domain wildcard.
Sources: Support data sovereignty in Saudi Arabia | LiveKit | Checklist for Regional Deployments | LiveKit | Support data sovereignty in India | LiveKit, with interactive elementscrooked-holiday-5421
04/08/2026, 7:36 AMtall-airline-16756
04/08/2026, 7:36 AMcrooked-holiday-5421
04/08/2026, 9:53 AMtall-airline-16756
04/08/2026, 9:54 AM*.livekit.cloud (or *.region.production.livekit.cloud) by domain.
1. Do you see any logs on your endpoint (incoming requests, errors, non-2xx responses)? If so, what status codes or errors appear?
2. Are you verifying webhook signatures? Note LiveKit sends Content-Type: application/webhook+json and an Authorization header with a JWT; signature verification requires access to the raw POST body (e.g., use express.raw({ type: 'application/webhook+json' }) in Express).
3. Does your endpoint respond quickly with a 2xx? Slow or non-2xx responses cause retries/backpressure and may drop events after retries/MaxAge.
If you share answers to 1–4 and any sample logs or status codes, I’ll suggest the next concrete steps to restore delivery.
Sources: Best practices for managing webhook event streams | LiveKit | Best practices for managing webhook event streams | LiveKit | examples/survey | livekit/livekit_composite | DeepWiki | server-sdk-go | livekit/livekit_composite | DeepWiki | Agents Framework | livekit/livekit_composite | DeepWiki, with interactive elements