About Us

Why we run our own stack

Most hosts resell capacity on a network they do not control. We hold our own ASN, register the prefixes we announce under the IRR AS-SET AS55285:AS-ALL, and set our own peering policy, which PeeringDB lists as open. When a route needs changing, the person who changes it works here.

The footprint is seven metros: Amsterdam, Chicago, Dallas, Los Angeles, New Jersey, Frankfurt and London. Dedicated servers ship from five of them today, with Sydney being built out. Peering runs across six internet exchanges and nine facilities, all of it on public record at PeeringDB and bgp.tools. Our looking glass will run a ping, traceroute or BGP lookup from any live metro before you order.

Downtime that is our direct fault is credited at 5% of the monthly fee per hour, up to the full month.

What that means for your server

Dual uplinks, diverse paths

Servers connect through two uplinks on separate paths across our fabric, blended across multiple transit providers, so one failed link or BGP session does not take a server offline.

24/7 monitoring and support

The NOC watches the network around the clock. Tickets reach the team that runs the routers and the racks, not a queue that escalates them elsewhere.

100% uptime SLA

Service downtime that is our direct fault is credited at 5% of the monthly fee per hour, up to the full month. Attacks and hardware or software failures are excluded.

Open peering at six exchanges

We peer openly across six internet exchanges and nine facilities, so traffic to the networks your users sit on hands off directly instead of crossing a third party first.

DDoS filtering included

Mitigation runs at the network edge on every server. There is nothing to add to the cart and nothing to switch on after the server is live.

Console and API

Provision, rebuild and manage servers from the cloud console, or programmatically over the API.