Our application has experienced an almost complete collapse in traffic and performance metrics from Russian users. Testing through a VPN located in Russia does not reproduce the problem, but around 99% of our observed RU traffic is failing or not reaching the application as expected. Our users can still access S3-hosted files through CloudFront, so the issue may be specific to another part of the network path. Could AWS or EC2 IP ranges be restricted or filtered in Russia? Has anyone seen similar connectivity problems recently?
3 Answers
Russia has previously blocked or disrupted ranges associated with major cloud providers, including AWS and GCP. Restrictions can also change over time, so it’s possible that a new filtering rule is affecting the addresses your application uses while CloudFront remains reachable.
There have been periodic network-isolation tests and increased VPN restrictions that can affect cloud-hosted services, especially EC2 addresses commonly used for VPNs. It may be temporary, but checking route traces, connection success by provider, and whether rotating the origin IP changes the result could help identify the pattern.
I’d compare the failed requests by ASN, destination IP, and ISP before concluding that AWS itself is being blocked. If the failures are concentrated among particular Russian carriers or ASNs, that points more toward regional filtering or routing problems than an application-wide issue.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures