Anyone know why the /v2/analytics/conversations/query endpoint exhibits significant latency spikes specifically when our BYOC trunks failover in AP-SE-2?
Background
Managing 15 BYOC trunks across APAC regions. Primary carriers handle digital messaging routing seamlessly.
Issue
When traffic shifts to secondary carriers due to SIP registration drops, the analytics API response time increases from 200ms to over 4 seconds. This impacts real-time dashboard updates.
Troubleshooting
- Verified SIP credentials and registration status.
- Confirmed outbound routing rules are correct.
- Checked for carrier-specific quirks in digital channel handling.
- No 504 errors, just high latency.