Could someone clarify why the /api/v2/telephony/providers/edges/{edgeId}/trunks/{trunkId}/health endpoint reports a 150ms variance in SIP OPTIONS probe latency between our Singapore and Tokyo BYOC trunks during off-peak hours? The underlying network infrastructure is identical, using the same carrier backbone, yet the analytics dashboard shows consistent jitter spikes on the Singapore edge. This discrepancy complicates our failover logic validation, as the health checks are triggering unnecessary state changes despite stable voice quality metrics.
We have verified that the SIP registration credentials are current and that no firewall rules are blocking the diagnostic traffic. The issue persists across all 15 trunks in the region, suggesting a platform-level telemetry aggregation error rather than a carrier-specific quirk. Is there a known limitation in how the Platform API calculates health scores for BYOC endpoints in the Asia/Singapore timezone? We need to determine if this latency skew is a false positive before adjusting our outbound routing priorities.