just noticed that our analytics queries are timing out when we try to pull conversation data specifically for calls routed through our ap-southeast-1 byoc trunks. this is happening during peak business hours here in singapore, roughly 10am to 2pm sgt. the issue seems to be isolated to the /api/v2/analytics/conversations/queries endpoint when we filter by trunk_id for our primary and failover carriers in that region. we are using the java sdk version 1.24.3 and have verified that the network connectivity to the genesys cloud api gateway is stable. however, the requests are hanging for over 60 seconds before returning a 504 gateway timeout error. interestingly, this does not happen for our us-east-1 or eu-west-1 trunks, which suggests a regional backend issue or a specific configuration quirk with the ap-southeast-1 analytics cluster. we have checked the sip registration status and all trunks are showing as registered and healthy with no recent failover events logged in the last 24 hours. the payload we are sending is relatively simple, just requesting conversation_id, start_time, and duration for the last hour, with a limit of 1000 records. we have also tried reducing the limit to 100 records, but the timeout persists. has anyone else seen this behavior with ap-southeast-1 byoc trunks? we are concerned that we might be missing critical data for our carrier performance reports. we have already opened a support ticket with genesys, but they are asking for more details on the specific trunk configurations and the exact timestamps of the failures. any insights or workarounds would be greatly appreciated. we are considering switching to a different reporting method if this is a known limitation of the analytics api in this region. thanks in advance for any help.