The network behind your servers

Every server on AS55285 includes DDoS mitigation at the network edge. It is part of the network layer, not a separate product line: there is nothing to add to a cart and nothing to switch on after the server is already live.

Mitigation sits inline, in front of the server, filtering attack traffic before it reaches the host. Legitimate traffic keeps flowing without you having to repoint DNS or stand up a separate scrubbing endpoint. Every metro has its own Corero NTD1100 appliance in the path, so an attack is dropped in the metro it lands in.

Because the filter is already in the path there is no redirect to wait for: attack traffic is dropped in under a second.

Because protection is built into the network rather than layered on afterward, it covers a server from the moment it's provisioned, including during OS installs and first boot.

Servers connect through dual uplinks, each landing on a different switch, so one failed link or interface does not take a server offline on its own.

From there, traffic crosses diverse paths through our network fabric rather than a single chokepoint. We reach the rest of the internet through a blend of transit providers and settlement-free peering, so no single upstream is the only way to reach a given destination. Every one of those transit uplinks is a 100 Gbit/s port or faster.

When a path fails, whether an uplink, a fabric link, or an upstream session, routing reconverges onto the next available path automatically.

Every server ships dual-stacked, with IPv4 and IPv6 enabled together by default, so IPv6 is not a separate request or a paid add-on.

If you run your own routing, we support BGP sessions with customers who want to announce their own IP space through our network (BYOIP) instead of using address space we assign.

What we announce is registered, not just claimed: our IRR AS-SET, AS55285:AS-ALL, lists the prefixes we originate, checkable against the same public IRR and PeeringDB records any route-server lookup would use.