Network

Locations

48 IX is currently available in the following locations:

Facility NameFacility IDMetro IDAddress
EdgeConneX ECDPHX0101013011 S. 52nd St., Tempe, AZ, 85282

The Facility ID is used throughout 48 IX for identification and locational purposes.

Peering Network

48 IX utilizes unique IPv4 and IPv6 addresses assigned by ARIN for the peering LAN:

PrefixDescription
149.112.3.0/24Peering LAN IPv4 1
2001:504:14::/64Peering LAN IPv6 1

Routing

48 IX utilizes AS62484 for all multilateral BGP adjacencies. AS62484 Should never appear in the AS_PATH of routes received from the route servers.

Looking Glass

Route Servers

Route ServerIPv4 AddressIPv6 AddressPlatform
rs1.48ix.net149.112.3.12001:504:14::1FRRouting
rs2.48ix.net149.112.3.22001:504:14::2FRRouting

Forwarding

48 IX route servers are not in the forwarding path, and have IPv4 & IPv6 forward explicitly disabled.

Route Filtering

The following BGP updates are automatically rejected:

  • Routes to a bogon network
  • Routes with a bogon ASN in the AS_PATH
  • RPKI-invalid routes

The following actions are performed upon receiving a valid BGP update from a multilateral peer:

  • Strip all BGP communities in the AS62484 namespace except those allowed for participant use
  • Set Local Preference to 200
  • Set informational BGP communities

BGP Communities

48 IX leverages BGP Communities to provide participants with the ability to control how their routes are announced to other multilateral participants.

Well Known Communities

The following well-known BGP communities are supported:

CommunityNameAction
65535:1NO_EXPORTExport the route to all participants, with the NO_EXPORT community attached
65535:2NO_ADVERTISEExport the route to all participants, with the NO_ADVERTISE community attached
65535:666BLACKHOLEExport the route to all participants, with the BLACKHOLE community attached

Informational Communities

The following communities will be appended to any route received on a 48-IX route server, and may be used for granular route filtering or other informational purposes:

CommunityName
62484:0Any: Any route that has traversed AS62484
62484:64810:xRoute Server ID: x is equal to the Route Server ID on which the route was received
62484:64820:xLocation: x is equal to the Facility ID
62484:64830:xMetro ID: x is equal to the Metro ID
62484:64840:xParticipant ID: x is equal to the Participant ID
62484:62484:xParticipant ASN: x is equal to the Participant ASN

Announcement Control Communities

Standard Communities
CommunityAction
0:xDon't export to participant with ASN x
62484:xOnly export to participant with ASN x
62484:64801Prepend advertising ASN 1 times to all participants
62484:64802Prepend advertising ASN 2 times to all participants
62484:64803Prepend advertising ASN 3 times to all participants
Extended Communities
Ext. CommunityAction
rt:0:yDon't export to participant with ASN y
rt:62484:yOnly export to participant with ASN y
rt:64801:yPrepend advertising ASN 1 times to participant with ASN y
rt:64802:yPrepend advertising ASN 2 times to participant with ASN y
rt:64803:yPrepend advertising ASN 3 times to participant with ASN y
Large Communities
Large CommunityAction
62484:0:zDon't export to participant with ASN z
62484:1:zOnly export to participant with ASN z
62484:64801:zPrepend advertising ASN 1 times to participant with ASN z
62484:64802:zPrepend advertising ASN 2 times to participant with ASN z
62484:64803:zPrepend advertising ASN 3 times to participant with ASN z

Community Filtering

To mitigate community "noise", all BGP communities not specified in this document are deleted from inbound BGP updates, and only communities in the Informational Communities section are exported.

The only exception to this are Well Known Communities — all supported well-known BGP communities are maintained on outbound updates.