GTT is back and now throttling!

This is used for general discussion that is not necessarily server-related.
Post Reply
stickz
https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA

GTT is back and now throttling!

Post by stickz »

So I noticed that GTT was back in Chicago.

It sure didn't take a long time to notice it was back, simply by the slower transfer speeds when downloading files. I honestly knew it was GTT before typing sudo mtr into my Ubuntu terminal.

So my first complain is a new transit link, which, just got prepended for load balancing. It runs to my UK2 VPS located in London. It's throttling my 1gbps transfer speeds down to 200mbps.

Posted bellow are the inbound and outbound transit routes. It would be appreciated if this issue could be fixed. Throttling is not a good thing, especially, when running between VPS's.

My traceroute [v0.85]
ssd3690 (0.0.0.0) Thu Apr 7 02:49:01 2016
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 82.163.78.1 0.0% 17 0.8 6.1 0.4 62.3 15.5
2. inx.as13213.net 0.0% 17 0.4 0.7 0.4 3.4 0.7
3. 83.170.70.237 0.0% 17 1.1 1.1 0.8 1.5 0.0
4. 92.60.249.45 0.0% 17 0.5 0.6 0.4 1.3 0.0
5. et-8-1-0.chi12.ip4.gtt.net 0.0% 17 85.0 85.0 84.9 85.0 0.0
6. gtt-1.e6.router2.chicago.nfoserv 0.0% 17 85.0 85.0 85.0 85.1 0.0
7. chicago-ventrilo.nfoservers.com 0.0% 16 85.1 85.2 85.0 87.4 0.5

C:\>tr 82.163.79.241
traceroute to 82.163.79.241 (82.163.79.241), 30 hops max, 60 byte packets
1 internal.e4.router1.chicago.nfoservers.com (72.5.195.254) 0.090 ms 0.083 ms 0.082 ms
2 border10.te7-4.nuclearfallout-65.chg.pnap.net (64.74.96.37) 0.342 ms 0.391 ms 0.455 ms
3 core3.te2-1-bbnet1.chg.pnap.net (64.94.32.3) 0.745 ms 0.846 ms 0.846 ms
4 ae-25.r05.chcgil09.us.bb.gin.ntt.net (129.250.203.177) 0.844 ms 0.965 ms 0.965 ms
5 ae11.chi11.ip4.gtt.net (199.229.229.193) 0.370 ms 0.372 ms 0.374 ms
6 et-7-1-0.lon11.ip4.gtt.net (141.136.111.9) 84.763 ms 84.919 ms 84.903 ms
7 as13213.ae4.ar1.lhr1.uk.as4436.gtt.net (69.22.139.46) 85.592 ms 85.419 ms 85.406 ms
8 83.170.70.226 (83.170.70.226) 85.221 ms 85.315 ms 85.591 ms
9 dc5.as13213.net (83.170.70.134) 85.141 ms 89.205 ms 89.313 ms
10 myhost241.websoldest.biz (82.163.79.241) 85.043 ms 85.044 ms *

And right here is the slower transfer speeds.
$ wget fastdl.us.xenogamers.com/backup.tar.gz
--2016-04-07 02:56:42-- http://fastdl.us.xenogamers.com/backup.tar.gz
Resolving fastdl.us.xenogamers.com (fastdl.us.xenogamers.com)... 216.52.148.201
Connecting to fastdl.us.xenogamers.com (fastdl.us.xenogamers.com)|216.52.148.201|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1338516949 (1.2G) [application/x-gzip]
Saving to: ‘backup.tar.gz.1’

24% [========> ] 326,335,475 25.1MB/s eta 42s
User avatar
Edge100x
Founder
Founder
Posts: 12945
Joined: Thu Apr 18, 2002 11:04 pm
Location: Seattle
Contact:

Re: GTT is back and now throttling!

Post by Edge100x »

Nod, as I have previously communicated, we added our own links to GTT in Chicago. Thank goodness, because they make a big difference in DDoS mitigation capabilities.

On the inbound to us, you'd need to talk to your other provider, as they are choosing that path.

On the outbound from us, your other provider is prepending its other transit links in order to force most traffic over GTT, which is why you see it take Internap->NTT->GTT. I should be able to force a different path, such as Cogent, but you'll need to open a support request so that we can track this concern.

That said, I do not believe that they are throttling you, if you're seeing 200 Mbps. That is quite high to be a throttle.

For routing questions, you should be opening up a support request instead of posting here. As you know, we reliably respond to them and I look at routing concerns personally.
Post Reply