Informational communities

We set these on routes we send to you.

BGP communityDescription
48070:10:XXXXRoute learned from peer with relationship type XXXX
48070:15:XXXXRoute learned at site ID XXXX
48070:20:XXXXRoute learned from peer ASN XXXX
48070:25:XXXXRoute learned from IX ID XXXX

Action communities

These communities control how we export routes.

Global export
BGP communityDescription
48070:5000:0No export
48070:5000:1Prepend once on all exports
48070:5000:2Prepend twice on all exports
48070:5000:3Prepend thrice on all exports
Per internet exchange
BGP communityDescription
48070:6000:XXXXNo export to IX ID XXXX
48070:6001:XXXXPrepend once to IX ID XXXX
48070:6002:XXXXPrepend twice to IX ID XXXX
48070:6003:XXXXPrepend thrice to IX ID XXXX
Per ASN
BGP communityDescription
48070:7000:XXXXNo export to AS XXXX
48070:7001:XXXXPrepend once to AS XXXX
48070:7002:XXXXPrepend twice to AS XXXX
48070:7003:XXXXPrepend thrice to AS XXXX
Per site
BGP communityDescription
48070:8000:XXXXNo export from site ID XXXX
48070:8001:XXXXPrepend once from site ID XXXX
48070:8002:XXXXPrepend twice from site ID XXXX
48070:8003:XXXXPrepend thrice from site ID XXXX

BGP wiki

Reference IDs unique to AS48070 — substitute these for XXXX above.

Site IDs

We use facility IDs from PeeringDB. Example: MyHostingSpace – Peterborough is 11352.

IDDescription
11352MyHostingSpace — Peterborough
34Telehouse — London (Docklands North)
601Teledata Manchester — Delta House
Internet exchange points

We use IXP IDs from PeeringDB. Example: LINX LON1 is 18.

IDDescription
18LINX LON1
321LINX LON2
583LINX Manchester
53LONAP
Relationship types

Used in informational communities based on relationship type.

IDDescription
100Transit
200Peers
400Our customers
1000Originated routes

Setting communities and nothing changing?

Check the session is up on the looking glass first, or drop the NOC a line with your ASN and the prefix in question.