You are right on that. They are ALMOST always. However, those comments were direct at the fact that is not an issue with MY ISP issue (either of them). I am on the east coast, florida is on the east coast. I was connecting to both east and west coast servers in the FPS game and I don't know where the streaming movie servers are. I did this to verify both close range and long range ISP stability.
I usually like our posts but this one seems more like a "I don't wanna hear what is working, it isn't what you think it is" post. So lets analyze some things shall we?
For it to be an ISP issue it would have to be an entire backbone issue, because of the distance between me and the server, Correct?
If you don't think that is the case I can explain, just like with most telephone networks Internet networks are eventually connected to these "backbones", Reason why? Cause like interstate highways it is better for sending information long distance to jump on a single long running LARGE pipeline that going down a buncha back streets. Ok so if my region network is working (verified by another ISP in my area, that would be connected by the same back bone, streaming live TV), then that means it cant be an issue in my region. Hence why I checked that and verified it was working. That means the infrastructure in my region is fine, I can access other regional service and my access to the backbones is not the issue.
Ok so I live far enough away, I would have to be accessing the server through one of these back bones. Now there aren't hundreds of backbones to choose from base on where you are going. Therefore the idea of going from my location to RoM's servers, is the same as me going from my location to any server located in the basic geographic region, wouldn't you agree? So therefore if lag exists on one server and not the other, and they are located in the same region... cant be the backbone now can it?
So now we have eliminated my regional infrastructure, and the backbone that would connect me to the RoM server's region all as working. OK!
This now leaves what? either the Servers regional network is having an issue (Not my ISP, their ISP), or their server. Aka Not on our end.
I just figured I would leave all that out cause the techs over at GF could have probably deciphered that without me explaining it. I just take issue with someone thinking that the information I provided would have no technical troubleshooting aspect when it does... regardless of whether they can see if it does or not. Hence why so many people have issues when calling to t/s over the phone. They don't want to answer the questions cause they cant understand WHY it would be relevant.. How about you let the Pros determine if it is relevant, instead of standing back and throwing smirky remarks? k?
Saito, I have had issues with Shentel ISP and Verizon ISP. Verified Shentel ISP issues through remote log in on my computers at the other house.
Traceroute for Verizon:
Tracing route to
www.runesofmagic.com [79.110.87.192]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms verizon.home [192.168.1.1]
2 9 ms 8 ms 8 ms 10.30.11.1
3 8 ms 7 ms 7 ms G2-0-0-2203.RONKVA-LCR-02.verizon-gni.net [130.8
1.195.250]
4 15 ms 14 ms 15 ms xe-1-0-2-0.RES-BB-RTR1.verizon-gni.net [130.81.1
99.48]
5 15 ms 14 ms 15 ms 0.xe-5-1-2.XL4.IAD8.ALTER.NET [152.63.8.1]
6 18 ms 15 ms 15 ms 0.TenGigE0-5-4-0.GW1.IAD8.ALTER.NET [152.63.33.4
5]
7 67 ms * 14 ms teliasonera-gw.customer.alter.net [152.179.50.23
4]
8 15 ms 15 ms 15 ms ash-bb3-link.telia.net [213.155.133.188]
9 116 ms 137 ms 116 ms hbg-bb1-link.telia.net [213.155.131.246]
10 115 ms 115 ms 115 ms ffm-bb1-link.telia.net [213.155.135.134]
11 114 ms 116 ms 134 ms ffm-b11-link.telia.net [213.155.130.227]
12 110 ms 110 ms 110 ms gameforge-ic-139736-ffm-b11.c.telia.net [80.239.
133.94]
13 111 ms 111 ms 110 ms vl13.gf-of.as47195.net [79.110.81.18]
14 112 ms 127 ms 110 ms kvm213.aixitng6.gfsrv.net [79.110.87.192]
Trace complete.
Problem is that it is not consistant, it disconnects me, 10 minutes later I can log back in, it has happened 3 times this morning, 11:45am 12:55 pm and I didn't get the time of the earliest, those are all EST times.