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.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
OVH UK has a separate board as well and their support and network are poor to say the least.
There are none, just no one likes the pricing compared to other OVH DCs. I don't know anyone offering something comparable with new gear, unmetered bandwidth, etc on the west coast.
The main reason I'm holding off right now is because I don't think it's enough of a discount to be a guinea pig in their new DC. Would rather wait for them to iron out any network kinks and up their west coast peering before dropping $100/mo.
Regardless of pricing, bandwidth, etc., until routing is fixed just like all of the other new locations it isn't appealing. Psychz LA for example has 100ms+ lower latency to Asia last I checked.
Agreed, got a test IP from them and can confirm it's awful. 147.135.33.77 if anybody wants to test themselves.
You're right lol, I'm getting a 109ms ping avg from Virginia.
From Italy:
5 packets transmitted, 5 received, 0% packet loss, time 4217ms
rtt min/avg/max/mdev = 212.136/212.774/213.268/0.492 ms
From Czechia:
94.8ms from NJ.
Routed from Newark -> BHS -> Chicago -> Palo Alto (Silicon Valley) -> PDX1 (Oregon)
Think I'll stick with BHS for the foreseeable future.
Why would you be comparing BHS to Oregon if you're in NJ anyway? OR is 2000+ miles further than BHS.
Yes, yes it is.
I get latency of less than 80ms to AWS Oregon.
Look at the MTR. The extra stop in BHS to get to Chicago & Palo Alto to get to Oregon adds some time. Similiar to Comcast's backbone where they keep it on their network as much as possible to avoid transit costs.
Not ALL traffic is routed through BHS, however. You’d only be looking at Oregon location if you’re serving west coast/Asia.
So you're paying $1000/m for a server in Portland? Lol.
lol
This routing is terrible... I get better latency to certain Asian country and to western EU than to this OVH DC that's two states away from me. How is that even possible????
Connections goes from BC, Canada -> BHS -> Chicago -> Palo Alto -> PDX
Seems that everything has to hit either BHS or RBX before it can reach the actual datacenter...
Just wanted to say that the routing issues everyone is experiencing have been acknowledged, and a resolution that mitigates the latency and geographic bouncing around is being actively worked towards.
Source?
Do you need a source? they obviously are not going to keep it as is.
I was looking more for a road map for this. OVH is not known to be a fast mover. Hopefully they sort this soon.
Why is everyone hammering on their routing? It's going to change. You people are talking about it like you all forget that the internet is not a concrete highway.
It's been the same with all their new sites. Eventually they sort it out.
Singapore hasn't been sorted out after a year. Why would anyone trust OVH's promises? It's not like these servers are free.
any ETA on their cloud/vps offerings in virginia/oregon?
What's wrong with Singapore? There were problems at first but then they got a redundant route through Australia. East coast routing is not great because it goes through Europe. But west coast is ok.
Regularly offline, SLA is not enforced, latency to pretty much anywhere is still extremely bad compared to other providers etc. etc.
I work for OVH
Sweet. Any estimate as to when this would be complete? Also, you should ask for the provider tag here.
I am not the party responsible for fixing the issue so I can't give an estimate unfortunately, but I do know that it is currently being investigated.
As far as a provider tag goes - I am just a technician and don't really know how much I am able to say on behalf of the company on here, I don't think it would be very fitting giving me a tag
Just wanted to comment on this, but has anyone else noticed that this datacenter still routes everything on the west coast to Chicago and then back to Oregon? Every IP I try on http://lg.he.net does this.
I told support about this almost a whole year ago and it still hasn't been fixed. And lots of providers here are using this DC.
Anyone know how we could go about getting Octave to notice this or someone else that could get things done?
@bob1 what providers are using this DC?
Sorry my mistake, some providers are using the east coast vint hill dc, which also has issues but not as many.
Hi @bob1, We are working on the routing with an estimated fix in the next couple of months. Feel free to PM me for details.
Thanks,
James