100% packet loss at EA Gateway

Lusalma

Reputable
May 14, 2015
2
0
4,510
Hi, I saw that you were able to help someone who had 100% packet loss on his ISP.
I have been having an issue with EA Games where I cannot login to EA Origin at all from home.

Some of the items I have done:
1) Confirmed that my laptop is able to login to Origin at other locations (This is not related to the pc settings/software) and impacts every device in the house.
2) Spoke with my ISP who has seen similar issues from EA where people cannot access EA website or login to Origin.
3) Contacted EA help who had me run the UOTrace - which basically showed 100% packet loss at the EA Gateway.

Now the main issue is that EA is still running around in circles trying to tell me that it is my ISP or my computer when it is a loss of information at their gateway.

Do you have any suggestions on what this could be other than EA blocking my IP address? (Which seems the most likely case to me at this point, regardless of what EA claims.)

Here is the trace after it leaves internal network;

100.ge-5-0-9.mpr1.msp2.us.above.n208.185.145.233 5 4ms 4ms 0% 103 / 103 4ms / 23ms
ae2.mpr1.msp1.us.zip.zayo.com 64.125.31.157 6 5ms 6ms 0% 103 / 103 5ms / 37ms
ae5.cr1.ord2.us.zip.zayo.com 64.125.30.89 7 13ms 16ms 0% 103 / 103 13ms / 53ms
ae4.er1.ord7.us.zip.zayo.com 64.125.28.50 8 15ms 15ms 0% 102 / 102 14ms / 47ms
ix-7-0.tcore1.ct8-chicago.as6453.63.243.129.13 9 13ms 14ms 0% 102 / 102 13ms / 64ms
if-12-6.tcore2.nyy-new-york.as645216.6.99.45 10 33ms 33ms 0% 102 / 102 33ms / 86ms
if-4-4.thar2.njy-newark.as6453.ne66.198.111.17 11 34ms 34ms 0% 102 / 102 33ms / 58ms
if-11-2.tcore2.aeq-ashburn.as6453216.6.87.137 12 37ms 37ms 0% 102 / 102 37ms / 43ms
if-2-2.tcore1.aeq-ashburn.as6453.216.6.87.2 13 39ms 39ms 0% 102 / 102 39ms / 43ms
* Unknown Host * 66.198.154.186 14 45ms 41ms 0% 102 / 102 40ms / 66ms
unknown.prolexic.com 209.200.144.35 15 44ms 41ms 0% 102 / 102 39ms / 65ms
unknown.prolexic.com 209.200.168.132 16 39ms 39ms 0% 102 / 102 39ms / 42ms
* Unknown Host * 159.153.93.2 17 40ms 100% 0 / 102
* Unknown Host * 159.153.225.30 18 41ms 37ms 0% 102 / 102 35ms / 92ms
meav5-pub.pt.iad.ea.com 159.153.226.105 19 35ms 35ms 0% 102 / 102 35ms / 82ms
 
Are you talking about this line in the trace or is there some other loss at the end that you do not show.

* Unknown Host * 159.153.93.2 17 40ms 100% 0 / 102

This means absolutely nothing. It just means this device is configured to not send ICMP time to live expired messages.

Because you get responses from 159.153.226.105 traffic obviously is not being blocked by the device before it.

It gets extremely hard to troubleshoot things when there are firewalls involved. Many times you can log into sites and they work fine but traceroute and ping will completely fail because the firewall is configured to not allow ping and traceroute.

This trace shows no issues at other than a little packet jitter but that appers be being caused in the internal network since it start in the first hop.
 

Lusalma

Reputable
May 14, 2015
2
0
4,510
This was one of the tests that they had me run.
So the full issue is that from my home network, I am completely unable to login to EA. It doesn't matter what device (ipad or computer) is used to access the login page. The server rejects the request, but yes, I am commenting on the EA gateway line that shows the 100% loss.

I have no other explanation to what is going on as nothing at my ISP or home change from the time that it worked previously to now.
The only reasonable explanation I have come across is that for some reason EA decided to block a range of IP addresses that basically includes the hub of which I am a part of.
 
If it was being blocked at that IP you would never see anything past it.

Try using a public DNS server like 8.8.8.8 just to be sure you are really going to the proper address.

It would extremely unusual for them to allow ping but not web or other traffic.

You could try something like wireshark and see what comes up. If they are blocking you would see your machine send syn packets over and over with no response.