Public peering

Guidelines and general information

The following are guidelines and some general information for public peering with IBM Cloud®.

• Potential and current peers must have and maintain a valid PeeringDB.com record.
• Use of the Internet Routing Registry (IRR) is required for prefix filtering.
• Peers must supply a contact with 24x7 availability, such as a Network Operations Center.
• Peers must not use any form of gateway of last resort or default route that is directed at IBM Cloud.
• Peers must provide access to a looking glass or traceroute server to facilitate troubleshooting.
• Peer announcements must be consistent across all Interconnect locations.
• IBM Cloud sends and accepts MED attributes by request only.

IBM Cloud reserves the right to suspend peering for an indefinite period if any form of network abuse is detected and verified to be taking place through the peering interconnect. This suspension includes setting a default route to IBM Cloud. IBM Cloud doesn't accept any IPv4 announcements smaller than /24 or IPv6 announcements smaller than /48. An MD5 password is preferred but not required.

For more information, see the PeeringDB record.

If IBM Cloud's operational needs cause a peering arrangement to conflict with the best interest of IBM Cloud, IBM Cloud reserves the right to end the peering agreement with reasonable advance notice.

Public peer exchanges

The following table shows the current public peer exchanges.