I am experiencing quite a bit of latency when connecting to Servint servers:

Ping statistics for 209.50.251.77:
Packets: Sent = 100, Received = 81, Lost = 19 (19% loss),
Approximate round trip times in milli-seconds:
Minimum = 211ms, Maximum = 448ms, Average = 296ms

C:\Documents and Settings\Owner>tracert servint.net

Tracing route to servint.net [209.50.251.77]
over a maximum of 30 hops:

1 14 ms 13 ms 14 ms h-69-3-206-129.SFLDMIDN.covad.net [69.3.206.129]

2 14 ms 13 ms 14 ms 192.168.7.161
3 14 ms 13 ms 14 ms ge-5-1-133.hsa1.Detroit1.Level3.net [63.211.20.1
85]
4 14 ms 14 ms 14 ms ge-6-0-0.mp1.Detroit1.Level3.net [64.159.0.201]

5 51 ms 52 ms 51 ms so-0-1-0.bbr2.NewYork1.Level3.net [64.159.1.42]

6 51 ms 51 ms 51 ms ge-5-2.core2.NewYork1.Level3.net [64.159.17.166]

7 51 ms 56 ms 60 ms gblx-level3-oc12.NewYork1.Level3.net [63.211.54.
74]
8 51 ms 52 ms 52 ms pos3-0-2488M.cr1.NYC1.gblx.net [67.17.64.149]
9 52 ms 52 ms 52 ms pos0-0-2488M.cr2.JFK1.gblx.net [67.17.72.2]
10 50 ms 53 ms 51 ms so3-0-0-2488M.ar1.JFK1.gblx.net [67.17.72.18]
11 47 ms 47 ms 47 ms Net-Access-Corporation-Net-Access-Corp.so-0-2-1.
ar1.JFK1.gblx.net [64.211.83.62]
12 * 64 ms 66 ms 0.so-1-2-0.gbr1.ash.nac.net [209.123.11.18]
13 342 ms 341 ms 343 ms ash-m20-ge0-0-0.gnaps.net [207.99.39.158]
14 337 ms * * f3-0.br1.mcl1.cent.net [199.232.56.26]
15 * 341 ms 341 ms www.servint.net [209.50.251.77]

Trace complete.


Is anyone else having problems?

Hi
I meet the same situation. It has been a while already. Problem seems still existing

These are traceroutes both to my site and the servint website taken throughout the afternoon:


1 10 ms <10 ms 10 ms 10.74.48.x
2 <10 ms <10 ms 10 ms leed-t2cam1-a-ge-wan34-110.inet.ntl.com [80.0.54.113]
3 <10 ms 10 ms 10 ms leed-t2core-a-ge-wan61.inet.ntl.com [80.0.241.33]
4 10 ms 10 ms 10 ms lee-bb-a-so-120-0.inet.ntl.com [62.253.185.17]
5 10 ms 10 ms 20 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
6 50 ms 50 ms 60 ms tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]
7 10 ms 20 ms 10 ms linx.ge-0-0-0.gbr1.ltn.nac.net [195.66.224.94]
8 80 ms 91 ms 90 ms 0.so-0-3-0.gbr2.nwr.nac.net [209.123.11.209]
9 90 ms 90 ms 80 ms 0.so-0-2-0.gbr1.ash.nac.net [209.123.11.30]
10 340 ms 341 ms 340 ms ash-m20-ge0-0-0.gnaps.net [207.99.39.158]
11 340 ms 341 ms 340 ms f3-0.br1.mcl1.cent.net [199.232.56.26]
12 * * * Request timed out.
13 341 ms 340 ms 351 ms 216.22.26.111



-----------------------------



1 10 ms <10 ms 10 ms 10.74.48.x
2 10 ms <10 ms 10 ms leed-t2cam1-a-ge-wan34-110.inet.ntl.com [80.0.54.113]
3 <10 ms 10 ms 10 ms leed-t2core-a-ge-wan61.inet.ntl.com [80.0.241.33]
4 10 ms <10 ms 10 ms lee-bb-a-so-120-0.inet.ntl.com [62.253.185.17]
5 10 ms 10 ms 20 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
6 50 ms 60 ms 60 ms tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]
7 10 ms 20 ms 10 ms linx.ge-0-0-0.gbr1.ltn.nac.net [195.66.224.94]
8 80 ms 90 ms 90 ms 0.so-0-3-0.gbr2.nwr.nac.net [209.123.11.209]
9 90 ms 90 ms 90 ms 0.so-0-2-0.gbr1.ash.nac.net [209.123.11.30]
10 340 ms 341 ms 340 ms ash-m20-ge0-0-0.gnaps.net [207.99.39.158]
11 350 ms 351 ms 340 ms f3-0.br1.mcl1.cent.net [199.232.56.26]
12 * * * Request timed out.
13 351 ms 340 ms 351 ms 216.22.26.111




-----------------------------




1 10 ms 10 ms 10 ms 10.74.48.x
2 10 ms <10 ms 10 ms leed-t2cam1-a-ge-wan34-110.inet.ntl.com [80.0.54.113]
3 10 ms 10 ms 10 ms leed-t2core-a-ge-wan61.inet.ntl.com [80.0.241.33]
4 <10 ms 10 ms 10 ms lee-bb-a-so-120-0.inet.ntl.com [62.253.185.17]
5 20 ms 10 ms 11 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
6 60 ms 60 ms 60 ms tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]
7 20 ms 10 ms 20 ms linx.ge-0-0-0.gbr1.ltn.nac.net [195.66.224.94]
8 90 ms 80 ms 90 ms 0.so-0-3-0.gbr2.nwr.nac.net [209.123.11.209]
9 90 ms 80 ms 80 ms 0.so-0-2-0.gbr1.ash.nac.net [209.123.11.30]
10 351 ms 350 ms 341 ms ash-m20-ge0-0-0.gnaps.net [207.99.39.158]
11 350 ms 371 ms 340 ms f3-0.br1.mcl1.cent.net [199.232.56.26]
12 351 ms 360 ms 371 ms www .servint.net [209.50.251.77]




-----------------------------




1 10 ms <10 ms 10 ms 10.74.48.1
2 <10 ms 10 ms 10 ms leed-t2cam1-a-ge-wan34-110.inet.ntl.com [80.0.54.113]
3 10 ms 10 ms 10 ms leed-t2core-a-ge-wan61.inet.ntl.com [80.0.241.33]
4 10 ms 10 ms 10 ms lee-bb-a-so-120-0.inet.ntl.com [62.253.185.17]
5 10 ms 10 ms 20 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
6 40 ms 40 ms 50 ms tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]
7 10 ms 20 ms 20 ms linx.ge-0-0-0.gbr1.ltn.nac.net [195.66.224.94]
8 80 ms 90 ms 130 ms 0.so-0-3-0.gbr2.nwr.nac.net [209.123.11.209]
9 81 ms 90 ms 90 ms 0.so-0-2-0.gbr1.ash.nac.net [209.123.11.30]
10 361 ms 360 ms * ash-m20-ge0-0-0.gnaps.net [207.99.39.158]
11 371 ms 370 ms 371 ms f3-0.br1.mcl1.cent.net [199.232.56.26]
12 361 ms 360 ms 371 ms www .servint.net [209.50.251.77]



------------------------------


Every single time I've had problems connecting to anything at servint, it has always been the same thing:

ash-m20-ge0-0-0.gnaps.net


Also, when I did a search of the forum for "gnaps", quite a lot of the posts it brought up were people mentioning the same problem, going back for months!


Why do they keep using gnaps when it causes problems so frequently???

I've been really happy with everything else at servint, and it's a real shame that they let this one problem just fester and tarnish both their service and reputation.

Servint - Please resolve this gnaps issue. And not just now, I mean a long term solution so we won't have to put up with it again and again and again as usual.

Same here :(

pings are around 400ms from Europe (The Netherlands), normally around 100ms

They refer to it on their network status page :

02/02/04 1:50 PM EST

ServInt Network Status Update

A ServInt upstream is experiencing capacity isues, which may cause sporadic latency on some parts of Servint's network. The capacity issue will be resolved within the hour.

"The capacity issue will be resolved within the hour."

I have no doubt that it will. But I also have no doubt that it will happen time and time again in the future (as it has in the past) unless a perminent solution is found.

Originally posted by CheeseWeasel

Why do they keep using gnaps when it causes problems so frequently???


gnaps purchased servint's network (servint was an actual carrier at that point), thus gnaps is servint's network infrastructure. not using it would be hard, if not impossible.

paul

Originally posted by CheeseWeasel
"The capacity issue will be resolved within the hour."

I have no doubt that it will. But I also have no doubt that it will happen time and time again in the future (as it has in the past) unless a perminent solution is found.

the problems you are seeing now are different from the ones you have read about. i would expect the current measures to be successful for the long term.

paul

Seems like they're constantly having network issues...which is quite a shame, considering their excellent support/managment reputation and tempting VPS plans.

I don't know where you're getting constant issues from. Williams was a problem and they apparently dumped it. The changeover which caused us a total of 4-1/2 minutes of recorded downtime is the only recorded downtime attributed to their network that I've had in 6 months....

This problem has been existing for a long time!!!
:angry:

Yeap, totalchoice has once posted servint network problem.

We never really saw much latency, when the network was up it was good.

Our problem was with WCG Transit. IMHO the issue with we had with Servint centered around WCG.

I have read that Servint has replaced WCG with NAC.

While thats a great move on Servint's part they moved a little to late for us. We cancelled with them and moved to Rackspace.

Originally posted by Watcher_TVI
I don't know where you're getting constant issues from. Williams was a problem and they apparently dumped it. The repeated issue with ash-m20-ge0-0-0.gnaps.net isn't something I have just read about - it is something I experience on an almost weekly basis. About once per week, sometimes more, sometimes less, connection to any servint related sites slows to a crawl. And every time it happens I always run a traceroute, and every time it is always that ash-m20-ge0-0-0.gnaps.net hop where the problem occurs (see my example traceroutes above). It remains this slow for at least a few hours at a time, then returns to normal.

This is coming from Leeds, England and is a consistant reocurring issue.

that wasn't the only overloaded peering/transit session or router yesterday... so apparently this router doesn't seem to be the problem, but rather the whole GNAPS network, which i'm though still pretty confident in.

seems to have been fine for me all day, pings circa 95-100 from the uk (ntl).

Originally posted by TotalChoice
We never really saw much latency, when the network was up it was good.

Our problem was with WCG Transit. IMHO the issue with we had with Servint centered around WCG.

I have read that Servint has replaced WCG with NAC.

While thats a great move on Servint's part they moved a little to late for us. We cancelled with them and moved to Rackspace. I agree that WCG was the weakest link and ServInt did take steps to replace it. I'm also pretty sure that the NAC replacement for WCG was not an agreement that couild be made in short order.


The repeated issue with ash-m20-ge0-0-0.gnaps.net isn't something I have just read about - it is something I experience on an almost weekly basis. I'm not sure why you have these issues, I'm not a ServInt engineer. All I can say is that I host a couple of active UK based sites and these people have been ecstatic with the level of uptime and speed they have experienced. If everyone was experiencing this issue I feel pretty sure I would have had at least a couple complaints from some of my UK clients by now.

I am not saying you are not having an issue, I just don't think it's as widespread as you're saying...

I'm not sure why you haven't had these issues, I'm not a ServInt engineer. All I can say is that I host a couple of active US based sites and have been saddened by the repeated speed decreases I have experienced. If no-one else was experiencing this issue I feel pretty sure I wouldn't be able to ask friends to test the speed and notice the slowness at the same time.

I am not saying you are also having an issue, I just don't think it's as narrow as you're saying...

:)

[perhaps your customers don't complain because we are talking about a few sporadic hours of slowness, not frequent down time]

They have some pretty active forums, if it was slow fo 20 minutes I would likely hear about it and rightly so, I would want to know about it and encourage the feedback about such things.

I think that you would do better trying to resolve this with ServInt rather than here. It seems that there are not a lot of other people (here at least) that share the same issues you are experiencing.

Out of curiosity, do you and your friends all share the same ISP?

I can confirm that the ping from Europe has significantly increased yesterday for most of the day, but now it is back to normal. And no, that issue is not recurring, happened only once.