Serversify Network
Serversify is building a dual-stack (IPv4+IPv6) network with points of presence on 4 continents. We maintain an open peering policy at all major internet exchanges. Network registration and IP space allocation are currently in progress.
Pending
ASN
In Review
IPv4 Space
In Review
IPv6 Space
50+ Planned
BGP Peers
8 Planned
IXPs
10 Gbps
Backbone
IP Address Allocations
IP Space — Coming Soon
Our IPv4 and IPv6 prefix allocations are currently being registered with RIPE NCC and ARIN. Assigned blocks and RPKI ROA details will be published here once confirmed.
All future prefixes will be registered with RIPE NCC and ARIN. RPKI ROAs will be published for all allocations. Route filtering will be enforced on all customer-facing BGP sessions.
BGP Communities
Communities can be used by customers with BGP sessions on Dedicated plans to influence routing.
Planned — ASN assignment in progress; community values will be published once assigned.
Planned Points of Presence
Target peering locations once network registration is complete.
| Location | Facility | IPv4 Block | IPv6 Block | Route Server |
|---|---|---|---|---|
| Frankfurt, DE | Equinix FR5 | Pending | Pending | DE-CIX Frankfurt |
| Amsterdam, NL | Equinix AM5 | Pending | Pending | AMS-IX |
| London, UK | Equinix LD8 | Pending | Pending | LINX LON1 |
| New York, US | Equinix NY9 | Pending | Pending | NYIIX |
| Singapore, SG | Equinix SG1 | Pending | Pending | SGIX |
| Tokyo, JP | Equinix TY2 | Pending | Pending | JPIX |
Peering Policy
Type: Open peering
Minimum prefix size: /24 IPv4, /48 IPv6
Max prefixes: 100 IPv4, 200 IPv6 per session
RPKI validation: Enforced — invalid ROAs rejected
IRR filtering: Applied on all sessions
NOC email: [email protected]
PeeringDB: peeringdb.com/net/pending
Abuse & NOC Contacts
Abuse: [email protected]
NOC (24/7): [email protected]
Security: [email protected]
Abuse reports are reviewed 24/7. We aim to respond to all reports within 4 hours and to take action within 24 hours of a confirmed violation.