Weservcloud is a part of Weservit. The company stands for a high quality service, so that optimal performance of your server(s) or website(s) is guaranteed. We address everything within our power, so that our customers can be sure of an excellent service and in order to prevent unexpected...
I did some BGP lookups to COLO@
Telia:
AS path: 5580 46562 40426
Cogent:
AS path: 3257 46562 40426
As you can see the AS length is the same, when one of these had a shorter AS path you probably wouldn't have a multipath route.
Another advantage of multipath BGP is that you won't have a...
Actually when you use multiple TIER1 carriers most paths will have the same length. Example:
When you do a BGP lookup for this IP 194.25.0.125 (an IP from Deutsche Telekom) at all TIER1 carriers you will get a direct path to AS3320. So when you use multiple TIER1 carriers like they do (Cogent...
You are right. We have multiple Gbit trunks to Proserve, but in case of a DDOS attack sent by a single mac address the loadbalancing protocols don't work correctly. It happened that one of the Gbit/s links went full and this caused problems. Like you say we got it managed very quickly because we...
I believe that when you have your own AS, have multiple carriers (multihomed) and do your own BGP routing you can call it your own network. We have a trunk with multiple Gbit/s links to Proserve as we can get redundant links from them. Next to that we have Jointtransit with a 10Gbit/s connection...
TrueVPS was a child company from WeservIT (like we have WeservCloud and RouteLabel) managed by another family member that's right. (WeservIT is a family business). With RamNode as our customer we saw an opportunity we couldn't resist, especially because RamNode belongs to the top VPS Hosters...
TrueVPS was part of WeservIT that's right. We worked out a good deal with RamNode for their NL location. One of the terms for this deal was that we had to stop offering activities from TrueVPS. All TrueVPS customers will be transfered to RamNode hardware as you can read in the email Nick sent. ...
Received from Solus:
Yes, We are working on this. Patch will be ready within couple of minutes
I would suggest to disable the API from solusvm until our senior admin confirmation about the patch.