Higher network latency since 1st of May

0

Hi,

we are using Betfair and are monitoring the network latency from our servers to their API constantly. Since 2025-05-01 we see the network latency went from less then 1ms to 13ms. So that is at least 10 times slower. We are using the Dublin region and it is from multiple servers. We have been in contact with Betfair and Cloudfront, but they both tell us they see no issues on their side. Is there something we can do or check on the AWS side to see if the problem is located "here" ?

2 Answers
0

I understand you're experiencing increased network latency from your servers in the Dublin region to the Betfair API since May 1, 2025. While I can't comment on specific third-party services, I can provide some general guidance on troubleshooting network latency issues within AWS.

First, it's important to isolate whether the issue is within AWS or external. Here are some steps you can take:

  1. Check AWS service health dashboards for any known issues in the Dublin region that might be affecting network performance.

  2. Monitor your EC2 instances' network performance using CloudWatch metrics. Look at the NetworkIn, NetworkOut, and NetworkPacketsIn/Out metrics to see if there are any unusual patterns or if you're exceeding the baseline network bandwidth for your instance types.

  3. If you're using Elastic Load Balancers, check the TargetResponseTime metric in CloudWatch for any significant increases.

  4. Perform traceroutes from your EC2 instances to the Betfair API endpoint to identify where the latency is occurring. This can help determine if the issue is within AWS's network or outside of it.

  5. Test connectivity directly to the Betfair API from different AWS regions to see if the issue is specific to Dublin or more widespread.

  6. If you're using AWS Global Accelerator or CloudFront, review your configurations to ensure they're optimized for your use case.

  7. Enable detailed VPC flow logs and analyze them to identify any potential networking issues within your VPC.

If after these checks you still suspect the issue is within AWS, I recommend opening a support case with AWS. Provide detailed information including traceroutes, timestamps, and specific endpoint details to help diagnose the issue.

Remember, network performance can be affected by many factors, including routing changes, congestion, or issues with intermediate networks. Continuous monitoring and data collection will be crucial in identifying the root cause of the latency increase.
Sources
Troubleshoot high response times and ECS latency issues | AWS re:Post
Troubleshoot latency on calls or requests to Amazon ECS tasks | AWS re:Post

profile picture
answered 10 days ago
profile pictureAWS
EXPERT
reviewed 10 days ago
0

If the latency persists and you have internal evidence (mtr, CloudWatch, etc.), open a case with AWS Support - especially if you're on a paid support plan.

profile picture
answered 10 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions