Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


OVH launches Germany Datacenter - Page 2
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

OVH launches Germany Datacenter

2»

Comments

  • CConnerCConner Member, Host Rep
    edited July 2017

    Sigh.... this DC is pretty bad. Getting 55 ms from the Netherlands. Gravelines (same distance) is 28 ms for me.

  • idrasidras Member

    waiting for USA location

  • vfusevfuse Member, Host Rep

    23 ms from amsterdam but goes through ovh RBX, leaseweb FRA about 15-16ms

  • Wow

  • @NexusH798 said:
    does anyone have bandwidth issue from germany to UK?

    and vice versa with my uk server by quadhost (clouvider). I had full 1gbit some time ago. but a few days ago I did some speed tests and no matter where the other servers are located (us-east, fr, nl, it, cz, 3x de) I just can get 6-11mbps.

  • lionlion Member

    I think you guys are judging too quickly. It just got opened, i guess they will improve networking further.

  • CConnerCConner Member, Host Rep

    They should make sure their network is /decent/ BEFORE offering it to the public. People paid for it.

  • @CConner said:
    They should make sure their network is /decent/ BEFORE offering it to the public. People paid for it.

    That's the reason why they offer the discover server's much cheaper.

    Thanked by 1MaikoB
  • @CConner said:
    They should make sure their network is /decent/ BEFORE offering it to the public. People paid for it.

    But OVH normally give a few months for free on your launch offers due problems like that.

  • ZerpyZerpy Member

    @CConner said:
    Sigh.... this DC is pretty bad. Getting 55 ms from the Netherlands. Gravelines (same distance) is 28 ms for me.

    Which provider do you use? I sit in NL and reach Gravelines in 13ms, and RBX in 10 :-D And Germany in 14ms

  • CConnerCConner Member, Host Rep
    edited July 2017

    XS4ALL - I know, it's total dog shit. Moving to Trined on the 12th #500 mbit up/down.

  • The DC is just connected of their FRA POP, so you should have access directly to all the same peers and transit as you would from one of their French DC’s just maybe slightly lower ping due to distance from DC to POP.

  • CConnerCConner Member, Host Rep

    Oh well, guess I will be stacking up on these. Currently have quite a few E3-1270v6's / 32 GB RAM for 98 EUR /month. This will allow me to buy 2x as many servers for the exact same price.

  • From Hostigation Charlotte:

    # ping 147.135.142.172
    PING 147.135.142.172 (147.135.142.172) 56(84) bytes of data.
    64 bytes from 147.135.142.172: icmp_seq=1 ttl=42 time=102 ms
    64 bytes from 147.135.142.172: icmp_seq=2 ttl=42 time=102 ms
    64 bytes from 147.135.142.172: icmp_seq=3 ttl=42 time=102 ms
    64 bytes from 147.135.142.172: icmp_seq=4 ttl=42 time=102 ms
    --- 147.135.142.172 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3978ms
    rtt min/avg/max/mdev = 102.161/102.198/102.264/0.039 ms
    


    From ColoCrossing LAX:

    ping 147.135.142.172
    PING 147.135.142.172 (147.135.142.172) 56(84) bytes of data.
    64 bytes from 147.135.142.172: icmp_seq=1 ttl=53 time=97.2 ms
    64 bytes from 147.135.142.172: icmp_seq=2 ttl=53 time=97.2 ms
    64 bytes from 147.135.142.172: icmp_seq=3 ttl=53 time=97.2 ms
    64 bytes from 147.135.142.172: icmp_seq=4 ttl=53 time=97.2 ms
    --- 147.135.142.172 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3915ms
    rtt min/avg/max/mdev = 97.235/97.246/97.258/0.008 ms
    
  • hackermanhackerman Member
    edited July 2017

    @WHT said:
    To much for germany, hetzer is still baba in de.

    The setup fees, though!!! Not much better economically unless you will have the server for at least a year

  • blackblack Member

    OVH world domination this year.

    Thanked by 1MaikoB
  • @doghouch said:
    From ColoCrossing LAX:

    > ping 147.135.142.172
    > PING 147.135.142.172 (147.135.142.172) 56(84) bytes of data.
    > 64 bytes from 147.135.142.172: icmp_seq=1 ttl=53 time=97.2 ms
    > 64 bytes from 147.135.142.172: icmp_seq=2 ttl=53 time=97.2 ms
    > 64 bytes from 147.135.142.172: icmp_seq=3 ttl=53 time=97.2 ms
    > 64 bytes from 147.135.142.172: icmp_seq=4 ttl=53 time=97.2 ms
    > --- 147.135.142.172 ping statistics ---
    > 4 packets transmitted, 4 received, 0% packet loss, time 3915ms
    > rtt min/avg/max/mdev = 97.235/97.246/97.258/0.008 ms
    > 

    Can't be LAX, has to be east coast US. It's at least 55-60ms cross country, then you have the Atlantic path to take which is going to be another 60ms+

  • @scaveney said:

    @doghouch said:
    From ColoCrossing LAX:

    > > ping 147.135.142.172
    > > PING 147.135.142.172 (147.135.142.172) 56(84) bytes of data.
    > > 64 bytes from 147.135.142.172: icmp_seq=1 ttl=53 time=97.2 ms
    > > 64 bytes from 147.135.142.172: icmp_seq=2 ttl=53 time=97.2 ms
    > > 64 bytes from 147.135.142.172: icmp_seq=3 ttl=53 time=97.2 ms
    > > 64 bytes from 147.135.142.172: icmp_seq=4 ttl=53 time=97.2 ms
    > > --- 147.135.142.172 ping statistics ---
    > > 4 packets transmitted, 4 received, 0% packet loss, time 3915ms
    > > rtt min/avg/max/mdev = 97.235/97.246/97.258/0.008 ms
    > > 

    Can't be LAX, has to be east coast US. It's at least 55-60ms cross country, then you have the Atlantic path to take which is going to be another 60ms+

    If you want, I'll PM you the IP. It's actually in Buffalo, so you're right to believe that it's wrong :)

  • Figured it was Buffalo ;)

  • So can I burst up to 1Gbps without any problems?

Sign In or Register to comment.