Peering with ServerSP, AS214456

ServerSP is a hosting and cloud provider with data centers in São Paulo and Miami. Our traffic flows mostly from our servers to end users, and we peer openly with any network that wants a shorter path to them.

PolicyOpen
IX.br route serversConnected
Bilateral sessionsWelcome
ContractsNot required

Our peering policy

We announce all of our prefixes to the IX.br São Paulo route servers. If your network already peers with the route servers, you are receiving our routes today and there is nothing else to do.

If your network does not use the route servers, or you simply prefer a direct session, we will set up bilateral IPv4 and IPv6 sessions with you. Every network is welcome, regardless of size or traffic volume.

General policy
Open
Route servers
All prefixes announced to the IX.br São Paulo route servers
Bilateral peering
Available to any network present at our locations
Traffic ratio
Not required
Multiple locations
Not required
Contracts
Not required

Where to peer with us

IX.br São Paulo

Ascenty SPO02, São Paulo. Dual stack, connected to the route servers.

RouterIPv4IPv6Speed
Router 1187.16.220.2512001:12f8::220:25110 Gbps
Router 2187.16.217.1422001:12f8::217:14210 Gbps

We prefer sessions on both routers, for a total of two IPv4 and two IPv6 sessions.

Miami

Our Miami data center is part of the same network, AS214456. If you would like to interconnect with us in Miami, write to us and we will find the best option.

Routing details

ASN
AS214456
IRR AS-SET
RIPE::AS214456:AS-SERVERSP
RPKI
All prefixes covered by valid ROAs
Max prefixes
IPv4: 100  /  IPv6: 20
Address families
IPv4 and IPv6

How to request a session

  1. Check that your PeeringDB record is up to date with your IX addresses and max prefixes.
  2. Email peering@serversp.com with your ASN, your IX.br São Paulo addresses and your AS-SET.
  3. We configure both of our routers and reply with confirmation, usually within a few business days.
  4. You bring up your side and the sessions come online.

What we ask from our peers

  • Keep your PeeringDB record and IRR objects current.
  • Announce only your own routes and your customers' routes.
  • Do not point a default route or send traffic to us for destinations we do not announce to you.
  • Keep a working NOC contact so we can reach you if something goes wrong.

Tools

Looking Glass São Paulo
lgsp1.serversp.net
Looking Glass Miami
lg.serversp.com
PeeringDB
peeringdb.com/asn/214456
Network status
status.serversp.net

Contacts

ServerSP may update this policy as the network grows. The most current technical data is always on our PeeringDB record.