BGP Community support for AS6762 Customers


Seabone makes use of some set of communities to help our customers to better tune their traffic without requiring a manual intervention on the Sparkle network.

Communities accepted from customers

All customers are allowed to send the following communities:

The 6762:666 community allows you to block traffic directed to a single host (/32) in your network. This is especially useful during Denial of Service attacks. You may only block a single host within your network. Request assistance by our NOC if you need to null-route a larger block of IP addresses or if you need to block only certain ports/services. Misuse may lead to termination of contract and/or legal action.

Customer-controllable selective announce

This community string implementation is used to permit our customers to control their announcements towards the largest peerings/transits.

The format is 6762:20pXX where the fields are coded in the following way:
If p is 1,2 or 3 prepend network 1, 2 or 3 times to XX
XX defines the network you want to prepend this route to, according to the following table:

01

AS701

02

AS6453

03

AS1239

04

AS3561

05

AS3320

06

AS5511

07

AS1299

08

AS12956

09

AS3356

10

AS702

11

AS7132

12

AS174

13

AS7018

14

AS1257

15

AS3549

16

AS3257

17

AS1273

18

AS2914

19

AS1668

20

AS209

21

AS6461

22

AS4134

23

AS4837

24

AS7922

25

AS3491

26

AS5400

27

AS2856

28

AS9680

29

AS2516

31

AS4766

32

AS2686

33

AS2828

34

AS3292

35

AS3303

36

AS4637

37

AS6830

38

AS6939

39

AS7473

40

AS7575

41

AS17676

 

Controlling announcements to IXPs

The format is 6762:200XX where the fields are coded in the following way:
XX defines the IXP you don't want to send this route to, according to the following table:

99

LINX

98

AMSIX

97

DECIX

96

PAIX Palo Alto

94

EQUINIX Singapore

93

EQUINIX Ashburn


The standard local preferences on Seabone are defined as 100 for customer routes and 90 for peering routes.
A local preference of 50 is used for backup routes, such as when confining a route in a region.
This prevents the creation of blackholes in case a better route to destination is not learnt in other regions for any reason.
Customer can modify the local preference for their routes by sending a community 6762:1xxx. The following table shows the available values:

6762:1090

Set local preference to 90 (same as peering)

6762:1070

Set local preference to 70 (lower than peering)

6762:1050

Set local preference to 50 (backup route)

 

Communities sent to customers

All customers will receive at least one of these communities. These communities will help you to choose the routes that you receive from Seabone, if you have the need to route only to a particular area, or if you want to treat your link as a peering link.

6762:30

Route learnt in Europe

6762:31

Route learnt in North-America

6762:32

Route learnt in South-America

6762:33

Route learnt in Asia

6762:34

Route learnt in Africa

6762:40

Route learnt from a customer


In addiction to geographic area, all customers will (gradually) also receive communities to have more detailed information about prefixes received from Seabone.

6762:13100

Route learnt in Amsterdam

6762:10130

Route learnt in Ashburn

6762:13000

Route learnt in Athens

6762:19623

Route learnt in Aqaba

6762:15701

Route learnt in Bogota

6762:14000

Route learnt in Bucarest

6762:15400

Route learnt in Buenos Aires

6762:15759

Route learnt in Cartagena

6762:13930

Route learnt in Catania

6762:10120

Route learnt in Dallas

6762:12500

Route learnt in Djibouti

6762:10160

Route learnt in El Paso

6762:19640

Route learnt in Erbil

6762:15580

Route learnt in Fortaleza

6762:14900

Route learnt in Frankfurt

6762:18500

Route learnt in Hong Kong

6762:19000

Route learnt in Istanbul

6762:10110

Route learnt in Jacksonville

6762:12711

Route learnt in Johannesburg

6762:16000

Route learnt in Kuala Lumpur

6762:12341

Route learnt in Lagos

6762:15100

Route learnt in Lima

6762:13510

Route learnt in Lisbon

6762:14400

Route learnt in London

6762:10140

Route learnt in Los Angeles

6762:13400

Route learnt in Madrid

6762:13370

Route learnt in Marseille

6762:10190

Route learnt in McAllen

6762:10150

Route learnt in Miami

6762:13900

Route learnt in Milan

6762:10100

Route learnt in Newark/NYC

6762:13950

Route learnt in Palermo

6762:10180

Route learnt in Palo Alto

6762:15070

Route learnt in Panama

6762:13300

Route learnt in Paris

6762:15551

Route learnt in Porto Alegre

6762:14200

Route learnt in Prague

6762:15550

Route learnt in Rio De Janeiro

6762:13980

Route learnt in Rome

6762:15571

Route learnt in Salvador

6762:15600

Route learnt in Santiago

6762:15500

Route learnt in Sao Paulo

6762:13590

Route learnt in Sofia

6762:16500

Route learnt in Singapore

6762:14600

Route learnt in Stockolm

6762:19821

Route learnt in Teheran

6762:14800

Route learnt in Warsaw

6762:14300

Route learnt in Vienna


The distinction on geographic area is based on where the route entered Seabone's network. This means that you should not be surprised of seeing, for example, a South American customer tagged as North American.