This 90000 thing needs to STOP

[Nukocafe]

Hello, please check out the internet health report to see where some of the connectivity issues in the vast interwebs are taking place.

Uh I'm on time warner, and I don't see that on this list (；´∀｀)

[Saccharin]

Uh I'm on time warner, and I don't see that on this list (；´∀｀)

Imagine you are driving between two cities. There's unlikely to be a straight road to the city so you have go via other town and cities. The nodes between Time Warner and SE are those other towns and cities. There's an issue in the journey at a node owned by level 3, let's call it a traffic incident.

[Garnetiferous]

Imagine you are driving between two cities. There's unlikely to be a straight road to the city so you have go via other town and cities. The nodes between Time Warner and SE are those other towns and cities. There's an issue in the journey at a node owned by level 3, let's call it a traffic incident.

My internet does not go through a level 3 node and I am still having connectivity issues. However, I ran a tracert and a node called te7-4.dr9.mtl.iweb.com seems to be taking an abnormally long time to respond whenever i run it during a lag spike.

[Nukocafe]

Imagine you are driving between two cities. There's unlikely to be a straight road to the city so you have go via other town and cities. The nodes between Time Warner and SE are those other towns and cities. There's an issue in the journey at a node owned by level 3, let's call it a traffic incident.

Well the weird part is - I was fine - until yesterday! So if it really was an issue with my ISP wouldn't I have been affected with everyone else from the start? That's why it seems strange. This only began happening after patch 2.28 was implemented btw.