We launched our new location in Madrid, Spain.

GTHost · September 22

Dear LET Community,

We are excited to announce the launch of our new location in Madrid, Spain. As a result, we now offer instant dedicated servers in 20 locations and VPS in 17 locations.

We offer the best servers at the most competitive prices in Spain.

You can check ping and traceroute here: https://gthost.com/looking-glass/

zGato · September 22

Cogent in Spain = cheap and bad.

For reference, both servers are in Madrid.
Cogent does Barcelona - Paris - Bilbao - Madrid, wtf

GTHost · September 22

Your home provider probably has a link with Cogent in Paris; therefore, the trace goes through Paris.
We use GTT and Cogent in Madrid.

Pings from our POP to 5.134.118.41
PING 5.134.118.41 (5.134.118.41) 56(84) bytes of data.
64 bytes from 5.134.118.41: icmp_seq=1 ttl=61 time=0.388 ms
64 bytes from 5.134.118.41: icmp_seq=2 ttl=61 time=0.514 ms
64 bytes from 5.134.118.41: icmp_seq=3 ttl=61 time=0.437 ms
64 bytes from 5.134.118.41: icmp_seq=4 ttl=61 time=0.424 ms

--- 5.134.118.41 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3067ms
rtt min/avg/max/mdev = 0.388/0.440/0.514/0.052 ms
https://gthost.com/looking-glass

Nyr · September 22

For the big 4 Spanish eyeballs, testing from Madrid:

Telefónica: transit via GTT
Vodafone: transit via GTT
Orange: transit via Cogent
DIGI: transit via Cogent

In every tested case the transit does not leave Madrid, but indeed you can do better than Cogent in Spain.

From Catalonia and other regions, Cogent will indeed route via Paris or Valencia to reach Madrid. And then it is worse to have a server in Madrid compared to Paris, which of course makes no sense.

GTHost · September 22

@Nyr
Thank you.
We just opened this location, and of course, we will work on improving local connectivity.

zGato · September 22

@Nyr said:
For the big 4 Spanish eyeballs, testing from Madrid:

Telefónica: transit via GTT

Vodafone: transit via GTT

Orange: transit via Cogent

DIGI: transit via Cogent

In every tested case the transit does not leave Madrid, but indeed you can do better than Cogent in Spain.

From Catalonia and other regions, Cogent will indeed route via Paris or Valencia to reach Madrid. And then it is worse to have a server in Madrid compared to Paris, which of course makes no sense.

Digi does have around 9-10ms to them from Barcelona. Vodafone too, but the big players here are Movistar & Orange mainly (also cause most smaller ISPs here are just merging with Orange)

And considering I get 22ms to them, it's a way better choice for most people that are not in Madrid or with those 2 ISPs to just get a server in Paris (17-18ms) or Amsterdam (24-27ms)

Both @GTHost Paris & Amsterdam locations are impressively good from Barcelona (Orange)

My intention was not to attack @GTHost, although it may have seemed like. I'm thankful for providers expanding in Spain, considering the situation and the very low amount of providers here. But transit is something rough here. Best bet is probably peering with Movistar/Orange/DE-CIX in Madrid.

caasify · September 22

‏Congrats on the opening of your Madrid datacenter! If you're interested, we can feature your services on our marketplace. Feel free to DM me for details.

sasslik · September 22

Kinda high from Malaga, but gzz anyway.

PING 172.111.37.166 (172.111.37.166) 56(84) bytes of data.
64 bytes from 172.111.37.166: icmp_seq=1 ttl=54 time=18.6 ms
64 bytes from 172.111.37.166: icmp_seq=2 ttl=54 time=17.0 ms
64 bytes from 172.111.37.166: icmp_seq=3 ttl=54 time=16.2 ms
64 bytes from 172.111.37.166: icmp_seq=4 ttl=54 time=17.2 ms
64 bytes from 172.111.37.166: icmp_seq=5 ttl=54 time=16.7 ms

--- 172.111.37.166 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 16.164/17.115/18.609/0.818 ms

WhiteRoseG · September 22

Do you also have low end deals ?

zGato · September 22

@sasslik said:
Kinda high from Malaga, but gzz anyway.

PING 172.111.37.166 (172.111.37.166) 56(84) bytes of data.
64 bytes from 172.111.37.166: icmp_seq=1 ttl=54 time=18.6 ms
64 bytes from 172.111.37.166: icmp_seq=2 ttl=54 time=17.0 ms
64 bytes from 172.111.37.166: icmp_seq=3 ttl=54 time=16.2 ms
64 bytes from 172.111.37.166: icmp_seq=4 ttl=54 time=17.2 ms
64 bytes from 172.111.37.166: icmp_seq=5 ttl=54 time=16.7 ms

--- 172.111.37.166 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 16.164/17.115/18.609/0.818 ms

What's your ping to 5.134.118.41? just curious

sasslik · September 22

@zGato said:

@sasslik said:
Kinda high from Malaga, but gzz anyway.

PING 172.111.37.166 (172.111.37.166) 56(84) bytes of data.
64 bytes from 172.111.37.166: icmp_seq=1 ttl=54 time=18.6 ms
64 bytes from 172.111.37.166: icmp_seq=2 ttl=54 time=17.0 ms
64 bytes from 172.111.37.166: icmp_seq=3 ttl=54 time=16.2 ms
64 bytes from 172.111.37.166: icmp_seq=4 ttl=54 time=17.2 ms
64 bytes from 172.111.37.166: icmp_seq=5 ttl=54 time=16.7 ms

--- 172.111.37.166 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 16.164/17.115/18.609/0.818 ms

What's your ping to 5.134.118.41? just curious

PING 5.134.118.41 (5.134.118.41) 56(84) bytes of data.
64 bytes from 5.134.118.41: icmp_seq=1 ttl=58 time=16.7 ms
64 bytes from 5.134.118.41: icmp_seq=2 ttl=58 time=22.0 ms
64 bytes from 5.134.118.41: icmp_seq=3 ttl=58 time=16.1 ms
64 bytes from 5.134.118.41: icmp_seq=4 ttl=58 time=19.7 ms
64 bytes from 5.134.118.41: icmp_seq=5 ttl=58 time=16.5 ms

--- 5.134.118.41 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 16.062/18.219/22.009/2.295 ms

qtwrk · September 22

[~] # ping 5.134.118.41   
PING 5.134.118.41 (5.134.118.41): 56 data bytes
64 bytes from 5.134.118.41: seq=0 ttl=57 time=10.175 ms
64 bytes from 5.134.118.41: seq=1 ttl=57 time=9.629 ms
64 bytes from 5.134.118.41: seq=2 ttl=57 time=9.955 ms
64 bytes from 5.134.118.41: seq=3 ttl=57 time=9.626 ms
64 bytes from 5.134.118.41: seq=4 ttl=57 time=9.622 ms
[~] # ping 172.111.37.166        #GTHost Madrid
PING 172.111.37.166 (172.111.37.166): 56 data bytes
64 bytes from 172.111.37.166: seq=0 ttl=56 time=14.160 ms
64 bytes from 172.111.37.166: seq=1 ttl=56 time=13.768 ms
64 bytes from 172.111.37.166: seq=2 ttl=56 time=14.067 ms
64 bytes from 172.111.37.166: seq=3 ttl=56 time=13.441 ms
64 bytes from 172.111.37.166: seq=4 ttl=56 time=13.836 ms
[~] # ping 139.64.166.166        #GHTost Amsterdam
PING 139.64.166.166 (139.64.166.166): 56 data bytes
64 bytes from 139.64.166.166: seq=0 ttl=53 time=29.911 ms
64 bytes from 139.64.166.166: seq=1 ttl=53 time=29.576 ms
64 bytes from 139.64.166.166: seq=2 ttl=53 time=29.346 ms
^C
--- 139.64.166.166 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 29.346/29.611/29.911 ms
[~] # ping 139.64.167.166        #GTHost Paris
PING 139.64.167.166 (139.64.167.166): 56 data bytes
64 bytes from 139.64.167.166: seq=0 ttl=53 time=32.564 ms
64 bytes from 139.64.167.166: seq=1 ttl=53 time=32.484 ms
64 bytes from 139.64.167.166: seq=2 ttl=53 time=32.441 ms
^C
--- 139.64.167.166 ping statistics ---

ping from BCN Digi

sorry for the newbie question , why Cogent bad ? as a normal user with Digi , it seems doing fine over all for Internet connection...

WhiteRoseG · September 22

@qtwrk said:
[~] # ping 5.134.118.41
PING 5.134.118.41 (5.134.118.41): 56 data bytes
64 bytes from 5.134.118.41: seq=0 ttl=57 time=10.175 ms
64 bytes from 5.134.118.41: seq=1 ttl=57 time=9.629 ms
64 bytes from 5.134.118.41: seq=2 ttl=57 time=9.955 ms
64 bytes from 5.134.118.41: seq=3 ttl=57 time=9.626 ms
64 bytes from 5.134.118.41: seq=4 ttl=57 time=9.622 ms
[~] # ping 172.111.37.166 #GTHost Madrid
PING 172.111.37.166 (172.111.37.166): 56 data bytes
64 bytes from 172.111.37.166: seq=0 ttl=56 time=14.160 ms
64 bytes from 172.111.37.166: seq=1 ttl=56 time=13.768 ms
64 bytes from 172.111.37.166: seq=2 ttl=56 time=14.067 ms
64 bytes from 172.111.37.166: seq=3 ttl=56 time=13.441 ms
64 bytes from 172.111.37.166: seq=4 ttl=56 time=13.836 ms
[~] # ping 139.64.166.166 #GHTost Amsterdam
PING 139.64.166.166 (139.64.166.166): 56 data bytes
64 bytes from 139.64.166.166: seq=0 ttl=53 time=29.911 ms
64 bytes from 139.64.166.166: seq=1 ttl=53 time=29.576 ms
64 bytes from 139.64.166.166: seq=2 ttl=53 time=29.346 ms
^C
--- 139.64.166.166 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 29.346/29.611/29.911 ms
[~] # ping 139.64.167.166 #GTHost Paris
PING 139.64.167.166 (139.64.167.166): 56 data bytes
64 bytes from 139.64.167.166: seq=0 ttl=53 time=32.564 ms
64 bytes from 139.64.167.166: seq=1 ttl=53 time=32.484 ms
64 bytes from 139.64.167.166: seq=2 ttl=53 time=32.441 ms
^C
--- 139.64.167.166 ping statistics ---

ping from BCN Digi

sorry for the newbie question , why Cogent bad ? as a normal user with Digi , it seems doing fine over all for Internet connection...

What is normal user Digi ?

qtwrk · September 22

@WhiteRoseG said:
What is normal user Digi ?

as people who just use Internet connection from Digi that don't have extensive knowledge about networking, routing ...etc

GTHost · September 22

From our POP to www.digimobil.es is 9ms via Cogent.

Via Telia the same 9ms.
https://lg.twelve99.net/?type=traceroute&router=mad-b3&address=188.26.192.1

Howdy, Stranger!

Categories

In this Discussion

We launched our new location in Madrid, Spain.

Comments

Howdy, Stranger!

Quick Links

Categories

In this Discussion

We launched our new location in Madrid, Spain.

Comments