Forum Discussion
1,031 Replies
- iEddieDean5 months agoSeasoned Newcomer
Same stuff here. Seems like Amazon blocked some clusters of IPs from eastern Europe. It is funny enough that on my inet provider some ppl can play with no problems and some don`t( Like me.
- N1ckyTr1cky5 months agoSeasoned Newcomer
i didnt find where i can send this
- Maidlife9205 months agoSeasoned Adventurer
refund declined because I played more than 2 hours........both companies are clowns.
- Maidlife9205 months agoSeasoned Adventurer
Submitted a refund request, I will let you know how it goes in case anyone else wants to get their money back.
- Vlamak_NAH5 months agoRising Scout
Today I tried to find out which external servers the PS5 connects to for the online game Battlefield 6.
A program for monitoring network traffic (an analogue of Wireshark / network sniffer) was installed on the computer. The console itself was connected via Wi-Fi, which was distributed from the computer.
The goal: to intercept packets from PS5 to see the IP addresses of the external servers it is trying to connect to.
During the program, I recorded several external IP addresses to which PS5 tried to connect:
- For example:
18.96.53.73,
13.42.14.22,
104.69.222.203,
54.197.155.195 and more….
Some addresses responded correctly, packets came without errors.
- Other addresses did not respond, and the program recorded timeout ((checked through the command line)).
- I found out that the reason for the lack of response is not in PS5, but in blocking or filtering traffic on the side of the Internet provider.
Here is a list of specific external IP addresses that I recorded today and that did not respond when trying to connect PS5:
- 104.69.222.203
- 54.197.155.195
These addresses tried to get packages from PS5, but timeout was recorded in the logs - no answers came.
At the same time, other addresses, such as 13.42.14.22, answered correctly (TCP/UDP connection was established without problems).
It was on these three IPs that I came to the conclusion that the connection is blocked or filtered on the provider's side.
—- 104.69.222.203
- Owner: Akamai Technologies
- Used for: Content delivery and cloud services
- Note: Akamai provides content delivery services and can be involved in the infrastructure of game services.
—- 54.197.155.195
- Owner: Amazon Web Services (AWS)
- Used for: Cloud computing and hosting
- Note: AWS provides cloud services, including hosting game servers.
- HullCitymad2005 months agoSeasoned Newcomer
Glad to hear someone else has realised the same thing with this error. Its such a strange one.
- Yordan19485 months agoNew Vanguard
Another day same **bleep**
- SuperSovietJesus5 months agoNew Traveler
Honestly, I doubt that would work. Even if your ISP were willing to try, they don’t have control once traffic leaves their own network. The problem seems to appear after the connection hops off your ISP’s edge and enters the wider internet, somewhere in the peering between AWS’s European edge and the backbone providers they use.
There’s no way for an ISP to “route around” that manually on a per-customer basis; those paths are automatically chosen based on BGP (Border Gateway Protocol) rules that prioritize efficiency and agreements between networks. In other words, your packets take the path the internet as a whole decides on, not one your ISP can hand-tune for you.
That’s why this issue needs to be addressed higher up the chain, through collaboration between EA and AWS to repair or reroute the broken link between them.
- amoogus735 months agoNew Hotshot
its officially been a week without a fix 🥳🥳🥳🥳 good job ea lets keep it going