Open the game you were having trouble with. Go grab the Windscribe VPN software, set it to Switzerland, and turn it on. If anyone's got a friend there, please let them know what's going on.ĮDIT4: I'm impatient so here's a temporary workaround that I ended up using. I tweeted them with as much info as I could fit in a tweet. New plan: try to get EA to notice this issue. I don't think the people at Comcast had any idea what I was talking about. If anyone else can do the same for their path that might help since we can give them a list of all affected circuits (or maybe we're all on the same one).ĮDIT3: Well that didn't help at all. Gonna call my ISP and see if they can get me the circuit number connecting Spokane to LA. We'll see what they say.ĮDIT2: CenturyLink says they need a circuit number to diagnose the issue.
If anyone knows how to contact a network engineer there, please let us know!ĮDIT: Contacting CenturyLink (now owns Level3 I guess) support about it. It looks like a Level3 router is blocking traffic to .com. My output: Tracing route to .com ģ 18 ms 12 ms 16 ms. Ĥ 22 ms 22 ms 19 ms. ĥ * 34 ms 29 ms 3.net On the other hand if it shows some hops before timing out then something between you and the EA server is blocking traffic. If the hops past your computer or router don't show then you've got a local problem. If anyone else has this issue, try opening a cmd prompt and typing "tracert .com".