The network behind your servers
Every Serverside server runs on AS55285, our own autonomous system, with open peering and DDoS protection standard, not an add-on. Every claim on this page is something you can verify yourself.
AS55285
Our own autonomous system
7
Network metros
6
Internet exchanges
9
Network facilities
IPv4 + IPv6
Dual-stack network
Open
Peering policy
AS55285 is the autonomous system Serverside operates end to end. We don't resell capacity on someone else's network: we hold our own ASN, register our own routes, and set our own peering policy. That gives us direct control over routing decisions, direct peering relationships with the networks our traffic touches, and one team accountable when something at the network layer needs attention, rather than a support ticket relayed to an upstream provider.
Everything on this page is independently checkable. Our ASN, IRR AS-SET, and peering records are public on PeeringDB and bgp.tools, and our looking glass runs live ping, traceroute, and BGP lookups from every metro we deploy servers in. You can test a path from where you sit before you order a server, not after.
Points of presence
Seven network metros across North America and Europe, with dedicated servers available in five of them today.
- Live
- Coming soon
| Metro | Facilities | Looking glass |
|---|---|---|
 | Digital Realty AMS3, Nikhef | AMS3 |
 | Netrality CH1, Digital Realty CH2 | CH1 |
| DataBank DFW1 | DFW1 |
| Digital Realty LAX10 | LAX10 |
| Digital Realty EWR20 | EWR20 |
 | Equinix FR5 | — |
 | Telehouse West | — |
| Equinix SYD5Coming soon | — |
What powers our network
Included with every dedicated server on AS55285 by default, not sold as a separate add-on.
Redundant, blended transit
Servers connect through dual uplinks on diverse paths through our fabric, blended with multiple transit providers, so a single failed link or session does not take a server offline by itself.
Settlement-free peering, open policy
We peer at 6 internet exchanges under an open policy registered on PeeringDB, keeping more traffic on direct paths instead of routed through a third party.
Always-on DDoS protection
Mitigation runs inline at the network edge on every server by default. There is nothing to buy separately and nothing to switch on before you go live.
IPv6, dual-stack by default
Every server ships with IPv4 and IPv6 enabled together, so IPv6 is not a request you file or a feature you pay extra for.
BGP sessions & BYOIP
Run your own routing: we support BGP sessions for customers who want to announce their own IP space through our network instead of using address space we assign.
Private networking
Connect your own servers to each other over our internal network instead of the public internet, keeping database replication and node-to-node traffic off a public interface.
24/7 monitoring & NOC
Our network operations team watches routing and connectivity around the clock, not just during business hours.
A growing global footprint
Seven network metros across North America and Europe today, with additional points of presence on the way.
DDoS protection
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.
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.
- Included on every server automatically, no opt-in or add-on fee
- Filtering happens inline at the network edge, ahead of your host
- No DNS change, proxy, or separate scrubbing endpoint required
Redundancy & routing
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.
When a path fails, whether an uplink, a fabric link, or an upstream session, routing reconverges onto the next available path automatically.
- Dual uplinks on separate switches
- Diverse paths across the network fabric
- Blended transit plus settlement-free peering
- Automatic reconvergence onto another path on failure
IP addressing, BGP & IPv6
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.
- Dual-stack IPv4 + IPv6 on every server by default
- BGP sessions available for customers announcing their own IP space
- Routes registered under AS55285:AS-ALL in the IRR
Test it before you buy
Our public looking glass runs ping, traceroute, and BGP lookups from each of our server metros, so you can check latency and path from where you sit before ordering a server.
Every live metro in the footprint table above links straight to its looking-glass location, or open the looking glass and pick one yourself.
Network FAQ
AS55285 is the autonomous system Serverside operates to connect its dedicated servers to the internet. It's registered on PeeringDB as a network service provider (NSP) with an open peering policy, and every server we provision uses it by default.
Further reading
DDoS Attacks Explained: Common Forms and How to Protect Against Them
DDoS attack types explained: volumetric, protocol and application-layer attacks, and the defences that stop each.
WireGuard vs Tailscale vs Headscale vs NetBird: The Self-Hosted Mesh VPN Decision
WireGuard vs Tailscale vs Headscale vs NetBird: who runs your control plane, and which mesh VPN to self-host.
How to Capture and Analyse a DDoS Attack with Wireshark (and tcpdump)
Capture and analyse a DDoS attack: safe tcpdump capture under load, then Wireshark triage and display filters.
