PLEASE READ ME FIRST
Aeria does not own, nor do they have any control over intermediate nodes. This is a problem out of anybody's control. Real-time gaming applications will be the most obviously affected services. People that are connecting through these problem nodes are also using them to connect to Aeria's website. Anybody whose connection is routed through these nodes will be experiencing issues, no matter what they're trying to do.
The nodes that are causing issues are owned by people who run the Tier 1 and Tier 2 networks that make up the Internet. I'm sure they actively monitor and strive to resolve all issues immediately, because issues with nodes can affect everyone worldwide (trying to reach a server through a slow node is slow for everyone, no matter where you live).
What does that mean?
Think of the node as a bridge that connects two main roads. Think of your packets as cars that can only travel a pre-determined path. The broken node is a faulty bridge that keeps randomly dropping cars. Any car that needs to travel across that bridge risks being dropped.
If you're trying to drive from your house to Walgreen's, and the bridge between you drops your car whenever you try to cross, Walgreen's can't do anything to fix it. The people that maintain the roads and bridges need to come to fix it.
How can I help?
- Run the command prompt (WindowsKey+R, "cmd"), or in your start menu, find "Command Prompt"
- Determine which IP you check, based on your server (not terribly important that you pick the right one, but if it's localized to one server, it will help diagnose that).
- In your command prompt, type "tracert " and the IP address that matches your server
- Take a screenshot and post it here, or copy/paste your tracert results in [ code] tags.
Tracing route to ip-174-142-117-10.static.privatedns.com [188.8.131.52]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 5 ms 5 ms 10.11.0.1
3 5 ms 7 ms 5 ms ctt191109.ceinetworks.com [184.108.40.206]
4 7 ms 6 ms 5 ms ctt191166.ceinetworks.com [220.127.116.11]
5 11 ms 11 ms 11 ms h18.104.22.168.static.ip.windstream.net [22.214.171.124]
6 11 ms 11 ms 11 ms h126.96.36.199.static.ip.windstream.net [188.8.131.52]
7 39 ms 21 ms 21 ms h184.108.40.206.static.ip.windstream.net [220.127.116.11]
8 22 ms 21 ms 21 ms h18.104.22.168.static.ip.windstream.net [22.214.171.124]
9 22 ms 21 ms 21 ms xe-10-0-0.bar2.Cleveland1.Level3.net [126.96.36.199]
10 31 ms 35 ms 31 ms ae-9-9.ebr2.Chicago1.Level3.net [188.8.131.52]
11 34 ms 31 ms 42 ms ae-1-100.ebr1.Chicago1.Level3.net [184.108.40.206]
12 51 ms 51 ms 51 ms ae-10-10.car2.Montreal2.Level3.net [220.127.116.11]
13 136 ms 55 ms 207 ms ae-11-11.car1.Montreal2.Level3.net [18.104.22.168]
14 52 ms 107 ms 74 ms te6-2.cl-core05.level3.mtl.iweb.com [22.214.171.124]
15 55 ms 64 ms 53 ms te8-2.v0708.cl-car08.mtl.iweb.com [126.96.36.199]
16 56 ms 51 ms 57 ms ip-174-142-117-10.static.privatedns.com [188.8.131.52]