SIP 408 Timeout on AP-SE-2 BYOC Trunks During Failover

Trying to make sense of why the Analytics API returns empty sets for SIP 408 errors when our AP-SE-2 BYOC trunks trigger carrier failover. The SIP registration logs show successful re-registration with the backup carrier, yet the outbound routing metrics indicate a complete loss of connectivity for 15 trunks simultaneously. Is there a known lag in the Analytics data pipeline for failover events in this region, or should I be querying a different endpoint for real-time SIP status?