Visa has a selective peering policy. Peers are selected based on reciprocal benefit, and are subject to certain technical, commercial and legal requirements. Visa’s technical requirements for peering are:
- A fully redundant network with adequate capacity to exchange traffic without any congestion.
- A responsive 24x7x365 Network Operations Center (NOC), capable of assisting in the resolution of:
- Technical and performance issues.
- Security concerns, violations, denial of service attacks, or any other abuse/anomaly originating from a peer.
- Visa will accept Multi-Exit Discriminators (MEDs) values only when a mutual policy is established.
- A publicly routable ASN.
- A minimum of one publicly routable /24 network prefix.
- A current and complete peeringdb.com entry.
- No peers will advertise static routing, a route of last resort (default), or otherwise send traffic to the other party for a route not announced via BGP.
- We support only IPv4 routes at this time.
- BGP route advertisements & path selection values should be mutually agreed and, peers are expected to announce consistent routes in all locations where they peer with Visa Inc.
- For the purpose of filtering, all parties are expected to register their routes in a public Internet Routing Registry (IRR) database. Both parties should make a good faith effort to keep this information up to date.
- MD5 is preferred for public peering.
- Optimized BGP timers are preferred for public peering.