seattle server question...
-
greuju
- New to forums
- Posts: 3
- https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
- Joined: Mon Apr 11, 2005 9:18 pm
seattle server question...
all the nuclear fallout servers get extremely high ping right now and the ones i asked said they were from seattle...why is this? i wouldnt care much but i have a seattle nfo server and its pissing me off...yesterday around 12am about 8 servers on my fav including mine hit around 220+ and right now 7pm my time they are at 70. these are pings obviously... the rest of my servers are fine, its just the block of nuclearfallout servers...i reset my server and nothing changed...
hey genius...its happening on at least 8 seattle servers...i just said that...now if our 8 servers are all on the same machine or something...
the ping is back to 20 where it should be.but when i join the game i get 40 and everyone else is in the 100's. this is not my server. in my server it says 17 and i get 42...i usually get around 15-25 in both. somethings wrong with seattles servers...
the ping is back to 20 where it should be.but when i join the game i get 40 and everyone else is in the 100's. this is not my server. in my server it says 17 and i get 42...i usually get around 15-25 in both. somethings wrong with seattles servers...
Over the past couple of days (mainly today and yesterday) there have been reports of these higher pings. We looked into it and found many similar occurences all over the web. We found a couple of trouble spots and contacted InterNAP and Level3 (most of the ping issues were through L3) but to our dismay they told us there isnt much they could do because in almost every case it was incoming traffic that had the high ping.
It appears that a lot of the high pings tonight in seattle are coming from the AT&T/Comcast backbone. I have comcast as well, so I can relate.
It appears that a lot of the high pings tonight in seattle are coming from the AT&T/Comcast backbone. I have comcast as well, so I can relate.
I can't comment on your specific routing problem without seeing your traceroutes to and from the server.
However, I can say that there have been a lot of problems in Seattle over the past few days, as bOoya said. These problems are with Comcast, and between overloaded UUnet-AT&T peering points. There was also some fiber cut on another backbone in northern California that is affecting Seattle traffic indirectly. These problems are not on our end or InterNAP's end, although sometimes they can be manually mitigated by InterNAP.
For targeted help with a server- or client-specific problem, you need to email us or visit us in IRC, as TimeX said.
However, I can say that there have been a lot of problems in Seattle over the past few days, as bOoya said. These problems are with Comcast, and between overloaded UUnet-AT&T peering points. There was also some fiber cut on another backbone in northern California that is affecting Seattle traffic indirectly. These problems are not on our end or InterNAP's end, although sometimes they can be manually mitigated by InterNAP.
For targeted help with a server- or client-specific problem, you need to email us or visit us in IRC, as TimeX said.
It sounds like you're having the issue I described above and also on the Events tab.
Again, we can't help you through the forums with your client-specific issue. You need to take action by emailing us your IP address.
Note also that you're having the same problem with servers that aren't ours. This tells you that the issue isn't on our side. Luckily, InterNAP can likely still manually improve the routing in this case.
Again, we can't help you through the forums with your client-specific issue. You need to take action by emailing us your IP address.
Note also that you're having the same problem with servers that aren't ours. This tells you that the issue isn't on our side. Luckily, InterNAP can likely still manually improve the routing in this case.