Quote:
Originally Posted by TheBlackSheep
[You must be logged in to view images. Log in or Register.]
Chances are Charter isn't going to tell you anything, unfortunately. It's not Charter's routers that are the problem. It's GTT's. It was dying after it jumped from a Charter router in Atlanta to:
ae10-69.cr1-nyc3.ip4.gtt.net
That's a Global Telecom router in NYC. The issue is with GTT's routing. It has to go through GTT's routers in NYC before it can get to the data center the server is hosted in, in New Jersey. Currently it seems there are still some issues on that router. It hasn't dropped any packets, but it has a higher latency than Rogean's server.
Glad you guys got it sorted out. Hopefully GTT will get their act together.
|
I agree with your points.
Additionally though, charter's systems tell it's users what dynamic route to take to get from point A to point z. They can see a problem with another's hub point, and temp/perm remove it from the options of hubs.
That was /is my hope of what happened. OR they contacted GTT and said fix yo sheet.
KRey