Checkout Sale ServicesExplore

Serververse · Network

Global capacity, site by site.

Total network capacity includes the full capacity of each location. Use this overview for locations, IP lease and IP transit, BYOIP and BYOAS, peering, Serververse Shield and the looking glass.

Total capacity is the sum of every site

We do not market a single invented uplink figure for the whole platform. Global capacity is the combined full capacity of each location below. Each card is that site's full contribution, not a shared fraction.

How the total is built

Noida, Mumbai, Surat Edge, Singapore, Frankfurt and the United States each bring their full site capacity into the network total. Edge, peering and transit roles differ by location, but every site's capacity still counts in full.

6 locationsFull capacity per siteSum = global capacity

Surat Edge note

Surat Edge is our Tier 3 India edge and colocation node. It includes a 1 Gbps uplink, matching what we publish on Edge. Its full site capacity still contributes to the network total like every other location.

Full capacity by location

Separate cards for each site. Role describes how the location sits on the network. Capacity notes state that the site's full capacity is included in the total.

Peering · Transit

Noida, India

Full site capacity counts toward the global total. Core India peering and transit for regional workloads.

Serververse ShieldSerververse Shield · Cloudflare Magic Transit · 3-layer DDoS for India.
Peering · Transit

Mumbai, India

Full site capacity contributes to the network total. Metro reach for western India and interconnect.

Serververse ShieldSerververse Shield · Cloudflare Magic Transit · 3-layer DDoS for India.
Edge · Colocation

Surat Edge, India

Full site capacity is included in the total. Tier 3 edge facility with a 1 Gbps uplink for colocated hardware.

Serververse ShieldSerververse Shield coverage where traffic terminates on the Serververse path.
Peering · Transit

Singapore

Full site capacity adds into global capacity. APAC transit and peering for low-latency regional routes.

Serververse ShieldSerververse Shield on OVH for Singapore.
Peering · Transit

Frankfurt, Germany

Full site capacity is part of the sum. European peering and transit for EU-facing services.

Serververse ShieldSerververse Shield · Cloudflare Magic Transit · 3-layer DDoS for Germany.
Peering · Transit

United States

Full site capacity contributes to the worldwide total. North American reach for US-facing traffic.

Serververse ShieldSerververse Shield with Cloudflare Magic Transit where the path supports it.

Choose one of two options

Network Transit has two buy paths: IP transit and IP lease. Prices and checkout sync with the store on /nt.

Option 1

IP transit

Put a public IPv4 on a Linux box through a tunnel to our edge, including gear behind NAT. Useful for developers, homelabs and game servers that need a public path without moving the machine into a DC.

  • Tunnel-based public reachability to Serververse edge
  • Same store catalog as IP lease, different use path
  • BGP sessions, VXLAN and private link on Network Transit
Option 2

IP lease

Lease clean public IPv4 for portable announcement or assignment. Blocks can be announced to any region with any provider — not bound to one territory — and geolocation can be changed.

  • Announce to any region with any provider
  • Not territory-locked · geolocation can be updated
  • Fits VPS, bare metal, colo and approved customer gear

BYOIP and BYOAS

Bring your own address space or announce your own ASN through Serververse routing. We scope sessions, tunnels and announcements with you rather than publishing a fake ASN on this page.

BYOIP

Bring your own IP

Announce or route prefixes you already hold, subject to RIR and LOA checks. Pair with IP lease or IP transit where the design needs both.

BYOAS

Bring your own ASN

Run BGP with your ASN toward Serververse. Session details, communities and policy are confirmed during onboarding, not invented in marketing copy.

Peering and ASN

Peering requests and live ASN details are handled through contact or the looking glass. We do not publish a fabricated ASN number here.

Peering

Settlement-free or paid peering depends on location, traffic balance and capacity at the site. Start with a short note on what you want to exchange and which region matters.

ASN and routes

Confirm ASN, prefixes and reachability from the looking glass or ask the network team via contact. Looking glass is the public check; contact is for peering and policy.

Serververse Shield · Cloudflare Magic Transit

DDoS protection on Serververse paths is Serververse Shield: OVH VAC and Edge Firewall, then Cloudflare Magic Transit, then Serververse in-house filtering — three layers before origin. Built for DDoS protected VPS, game servers and public APIs. Full walkthrough at docs.serververs.com/shield.

Magic Transit

Cloudflare Magic Transit

The globally distributed highlight of Shield. Prefixes are scrubbed across Cloudflare’s network so volumetric and protocol floods never land first on your uplink — the same stack people search for when they want DDoS protected VPS with real L3/L4 coverage.

3 layers

OVH + Magic Transit + Serververse

Layer one: OVH VAC. Layer two: Cloudflare Magic Transit. Layer three: Serververse ACLs, rate limits and custom policies. Spectrum available on request for SMP-style game ports.

Looking glass

Check routes, latency and reachability from Serververse vantage points. Use it before you buy transit or open a peering conversation.

lg.serververs.com

Public looking glass for traceroute, ping and BGP views from our network. Pair it with the location cards above when you plan IP lease, IP transit or BYOIP.

Need a human?

Looking glass answers reachability. Peering policy, BYOAS sessions and custom capacity still go through contact.

Support during business hours

Network tickets are handled on business days during working hours. We aim to reply within 24 to 48 hours. We cannot guarantee immediate human support on every ticket. For emergencies, use the hotline or WhatsApp listed on Contact.

Ready for addresses or a peering talk?

Buy IP lease or IP transit on Network Transit, review Shield for mitigation or open the looking glass to validate the path.

Network guide

Serververse network - capacity, transit, peering & IP services

Explore Serververse network capacity, IP transit, IP leasing, BYOIP/BYOAS, peering and Shield-backed connectivity across locations.

Whether you need internet breakout, private links or address space, the network page maps services to real operational use cases.

Homelabbers and operators can turn spare hardware into reachable servers with lease or transit options synced to the store where available.

Network: Serververse vs typical alternatives

Transparent India + global capacity with Serververse Shield.

FeatureSerververseTypical alternative
India presenceNoida & Mumbai capacityOften overseas-only POPs
ProtectionSerververse ShieldPaid add-ons or none
SupportBusiness-hours tickets · /contact hotlineOpaque chatbot-only queues
BillingINR-friendly checkoutUSD + forex

What Serververse Network covers

  • Production-ready networkGlobal capacity uplinks and regional edges tuned for real traffic.
  • Serververse ShieldAlways-on mitigation paths documented per region.
  • Clear next stepsOrder from the store, migrate via /migrate or contact for custom quotes.
  • Human support windowTickets in 24-48 hours on business days; emergencies via /contact.

Quick answers - IP transit · IP lease · BYOIP · BYOAS · Serververse ASN · network capacity.