Current RIS Routing Beacons
Note: IPv6 beacons and anchors are now being announced from the RRCs. See below for details.
All RRCs:
- Announcements at 00:00, 04:00, 08:00, 12:00, 16:00, 20:00 (UTC)
- Withdrawals at 02:00, 06:00, 10:00, 14:00, 18:00, 22:00 (UTC)
Comments:
The RIS Beacons were initiated to assist studies concerning unwanted
effects on convergence when applying Route Flap Damping practices.
You can read more about this at:
http://www.ripe.net/projects/ris/docs/beacon.html
All IPv4 beacon prefixes are announced with additional attributes. We now overload the BGP AGGREGATOR attribute to tag each announcement with a timestamp, a sequence number and the identifier of the RRC making the announcement. These are encoded as follows:
AGGREGATOR IP ADDRESS: 10.x.y.z, where x, y and z form a 24-bit count of the number of seconds between the start of the month and the time of the announcement.
AGGREGATOR AS NUMBER: 64512 + n, where n is a 10-bit number encoded as
MSB LSB
+---+---+---+---+---+---+---+---+---+---+
| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 |
+---+---+---+---+---+---+---+---+---+---+
| RRC ID | Sequence Number |
+---+---+---+---+---+---+---+---+---+---+
Adding 64512 brings the resulting number into the private AS number range.
A
query matrix to simplify querying the RIS database for our routing beacons can be found at:
http://www.ris.ripe.net/beacons/index.shtml
Routing Beacon Address Schema - IPv4
| Prefix: |
RRC: |
Location: |
| 84.205.64.0/24 |
RRC00 - RIPE NCC |
Amsterdam, NL |
| 84.205.65.0/24 |
RRC01 - LINX |
London, UK |
| 84.205.66.0/24 |
RRC02 - SFINX |
Paris, FR |
| 84.205.67.0/24 |
RRC03 - AMS-IX, NL-IX, GN-IX |
Amsterdam, NL |
| 84.205.68.0/24 |
RRC04 - CIXP |
Geneva, CH |
| 84.205.69.0/24 |
RRC05 - VIX |
Vienna, AT |
| 84.205.70.0/24 |
RRC06 - DIX-IE |
Otematchi, JP |
| 84.205.71.0/24 |
RRC07 - NETNOD |
Stockholm, SE |
| 84.205.74.0/24 |
RRC10 - MIX |
Milan, IT |
| 84.205.75.0/24 |
RRC11 - NYIIX |
New York , NY, US |
| 84.205.76.0/24 |
RRC12 - DE-CIX |
Frankfurt, DE |
| 84.205.77.0/24 |
RRC13 - MSK-IX |
Moscow, RU |
| 84.205.78.0/24 |
RRC14 - PAIX |
Palo Alto, CA, US |
| 84.205.79.0/24 |
RRC15 - PTTMetro-SP |
Sao Paulo, BR |
Routing Beacon Address Schema - IPv6
| Prefix: |
RRC: |
Location: |
| 2001:7FB:FE00::/48 |
RRC00 - RIPE NCC |
Amsterdam, NL |
| 2001:7FB:FE01::/48 |
RRC01 - LINX |
London, UK |
| 2001:7FB:FE02::/48 |
RRC02 - SFINX |
Paris, FR |
| 2001:7FB:FE03::/48 |
RRC03 - AMS-IX, NL-IX, GN-IX |
Amsterdam, NL |
| 2001:7FB:FE04::/48 |
RRC04 - CIXP |
Geneva, CH |
| 2001:7FB:FE05::/48 |
RRC05 - VIX |
Vienna, AT |
| 2001:7FB:FE07::/48 |
RRC07 - NETNOD |
Stockholm, SE |
| 2001:7FB:FE0A::/48 |
RRC10 - MIX |
Milan, IT |
| 2001:7FB:FE0B::/48 |
RRC11 - NYIIX |
New York , NY, US |
| 2001:7FB:FE0C::/48 |
RRC12 - DE-CIX |
Frankfurt, DE |
| 2001:7FB:FE0E::/48 |
RRC14 - PAIX |
Palo Alto, CA, US |
Additionally, we announce an anchor prefix from each RRC. These are permanently announced and can be used to differentiate between activity seen as a result of changes on the originating RRC and that seen for other reasons (it the anchor flaps, it could mean that the RRC was reloaded and activity of the corresponding beacon can be ignored when doing analysis of the RIS data).
Routing Anchor Address Schema - IPv4
| Prefix: |
RRC: |
Location: |
| 84.205.80.0/24 |
RRC00 - RIPE NCC |
Amsterdam, NL |
| 84.205.81.0/24 |
RRC01 - LINX |
London, UK |
| 84.205.82.0/24 |
RRC02 - SFINX |
Paris, FR |
| 84.205.83.0/24 |
RRC03 - AMS-IX, NL-IX, GN-IX |
Amsterdam, NL |
| 84.205.84.0/24 |
RRC04 - CIXP |
Geneva, CH |
| 84.205.85.0/24 |
RRC05 - VIX |
Vienna, AT |
| 84.205.86.0/24 |
RRC06 - DIX-IE |
Otematchi, JP |
| 84.205.87.0/24 |
RRC07 - NETNOD |
Stockholm, SE |
| 84.205.90.0/24 |
RRC10 - MIX |
Milan, IT |
| 84.205.91.0/24 |
RRC11 - NYIIX |
New York , NY, US |
| 84.205.92.0/24 |
RRC12 - DE-CIX |
Frankfurt, DE |
| 84.205.93.0/24 |
RRC13 - MSK-IX |
Moscow, RU |
| 84.205.94.0/24 |
RRC14 - PAIX |
Palo Alto, CA, US |
| 84.205.95.0/24 |
RRC15 - PTTMetro-SP |
Sao Paulo, BR |
Routing Anchor Address Schema - IPv6
| Prefix: |
RRC: |
Location: |
| 2001:7FB:FF00::/48 |
RRC00 - RIPE NCC |
Amsterdam, NL |
| 2001:7FB:FF01::/48 |
RRC01 - LINX |
London, UK |
| 2001:7FB:FF02::/48 |
RRC02 - SFINX |
Paris, FR |
| 2001:7FB:FF03::/48 |
RRC03 - AMS-IX, NL-IX, GN-IX |
Amsterdam, NL |
| 2001:7FB:FF04::/48 |
RRC04 - CIXP |
Geneva, CH |
| 2001:7FB:FF05::/48 |
RRC05 - VIX |
Vienna, AT |
| 2001:7FB:FF07::/48 |
RRC07 - NETNOD |
Stockholm, SE |
| 2001:7FB:FF0A::/48 |
RRC10 - MIX |
Milan, IT |
| 2001:7FB:FF0B::/48 |
RRC11 - NYIIX |
New York , NY, US |
| 2001:7FB:FF0C::/48 |
RRC12 - DE-CIX |
Frankfurt, DE |
| 2001:7FB:FF0E::/48 |
RRC14 - PAIX |
Palo Alto, CA, US |
RRC14 / RRC03:
- Permanent announcement from RRC14
- Announcements from RRC03 at 00:00, 04:00, 08:00, 12:00, 16:00, 20:00 (UTC)
- Withdrawals from RRC03 at 02:00, 06:00, 10:00, 14:00, 18:00, 22:00 (UTC)
- 84.205.72.1 is also configured as a "pingable address"
Comments:
Beacon initiated to simulate anycast failover from RRC14 to RRC03.
84.205.72.1 is also configured as a "pingable address".
Routing Beacon Address Schema
| Prefix: |
RRC: |
Location: |
| 84.205.72.0/24 |
RRC03 - AMS-IX, NL-IX, GN-IX |
Amsterdam, NL |
| 84.205.72.0/24 |
RRC14 - PAIX |
Palo Alto, CA, US |
Historical List of RIS Routing Beacons:
02/02/2005 - 03/09/2007:
RRC01 / RRC03:
- Permanent announcement from RRC01
- Announcements from RRC03 at 00:00, 04:00, 08:00, 12:00, 16:00, 20:00 (UTC)
- Withdrawals from RRC03 at 02:00, 06:00, 10:00, 14:00, 18:00, 22:00 (UTC)
Comments:
Beacon initiated to simulate anycast failover from RRC01 to RRC03.
Routing Beacon Address Schema
| Prefix: |
RRC: |
Location: |
| 84.205.72.0/24 |
RRC01 - LINX |
London, UK |
| 84.205.72.0/24 |
RRC03 - AMS-IX, NL-IX, GN-IX |
Amsterdam, NL |
30/09/2002 - 02/02/2005:
All RRCs:
- Announcements at 00:00h, 04:00h, 08:00h, 12:00h, 16:00h and 20:00h (UTC)
- Withdrawals at 02:00h, 06:00h, 10:00h, 14:00h, 18:00h and 22:00h (UTC)
Comments:
Beacons initiated to assist studies into unwanted effects on convergence when applying current Route Flap Damping practises.
Routing Beacon Address Schema
| Prefix: |
RRC: |
Location: |
| 195.80.224.0/24 |
RRC00 - RIPE NCC |
Amsterdam, NL |
| 195.80.225.0/24 |
RRC01 - LINX |
London, UK |
| 195.80.226.0/24 |
RRC02 - SFINX |
Paris, FR |
| 195.80.227.0/24 |
RRC03 - AMS-IX |
Amsterdam, NL |
| 195.80.228.0/24 |
RRC04 - CIXP |
Geneva, CH |
| 195.80.229.0/24 |
RRC05 - VIX |
Vienna, AT |
| 195.80.230.0/24 |
RRC06 - NSPIXP2 |
Otematchi, JP |
| 195.80.231.0/24 |
RRC07 - Netnod-IX |
Stockholm, SE |
| 195.80.232.0/24 |
RRC08 - MAE-WEST |
San Jose, CA, US |
To query the data-base for these prefixes,
click here.
10/03/2002 - 02/02/2005:
RRC01:
RRC03:
- Announcements at 00:00h, 04:00h, 08:00h, 12:00h, 16:00h and 20:00h (UTC)
- Withdrawals at 02:00h, 06:00h, 10:00h, 14:00h, 18:00h and 22:00h (UTC)
Comments:
Beacon initiated to simulate anycast failover from RRC01 to RRC03.
Routing Beacon Address Schema
| Prefix: |
RRC: |
Location: |
| 195.80.233.0/24 |
RRC01 - LINX |
London, UK |
| 195.80.233.0/24 |
RRC03 - AMS-IX |
Amsterdam, NL |
All beacon prefixes are now announced with additional attributes.
We now overload the BGP AGGREGATOR attribute to tag each announcement
with a timestamp, a sequence number and the identifier of the RRC making
the announcement. These are encoded as follows:
AGGREGATOR IP ADDRESS: 10.x.y.z, where x, y and z form a 24-bit count of the
number of seconds between the start of the month and the time of the
announcement.
AGGREGATOR AS NUMBER: 64512 + n, where n is a 10-bit number encoded as
MSB LSB
+---+---+---+---+---+---+---+---+---+---+
| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 |
+---+---+---+---+---+---+---+---+---+---+
| RRC ID | Sequence Number |
+---+---+---+---+---+---+---+---+---+---+
Adding 64512 brings the resulting number into the private AS number range.
Experimental: From 25/09/2003
an additional prefix 195.80.239.0/24
has been announced from all RRCs.
This acts as an "anchor" to help differentiate between intentional beacon-related
routing activity and other activity. The anchor prefix is announced with the Aggregator
attribute set as follows:
Aggregator IP Address: 10.255.255.255
Aggregator AS Number: 64512 + rrc-id * 64
06/11/2003 - 02/02/2005:
RRC10:
- Announcements at 00:00h, 04:00h, 08:00h, 12:00h, 16:00h and 20:00h (UTC)
- Withdrawals at 02:00h, 06:00h, 10:00h, 14:00h, 18:00h and 22:00h (UTC)
Comments:
Beacon initiated to assist studies into unwanted effects on convergence when
applying current Route Flap Damping practises.
Routing Beacon Address Schema
| Prefix: |
RRC: |
Location: |
| 195.80.234.0/24 |
RRC10 - MIX |
Milan, IT |
14/02/2004 - 02/02/2005:
RRC11:
- Announcements at 00:00h, 04:00h, 08:00h, 12:00h, 16:00h and 20:00h (UTC)
- Withdrawals at 02:00h, 06:00h, 10:00h, 14:00h, 18:00h and 22:00h (UTC)
Comments:
Beacon initiated to assist studies into unwanted effects on convergence when
applying current Route Flap Damping practises.
Routing Beacon Address Schema
| Prefix: |
RRC: |
Location: |
| 195.80.235.0/24 |
RRC11 - NYIIX |
New York, NY, USA |
06/07/2004 - 02/02/2005:
RRC12:
- Announcements at 00:00h, 04:00h, 08:00h, 12:00h, 16:00h and 20:00h
(UTC)
- Withdrawals at 02:00h, 06:00h, 10:00h, 14:00h, 18:00h and 22:00h
(UTC)
Comments:
Beacon initiated to assist studies into unwanted effects on convergence
when
applying current Route Flap Damping practises.
Routing Beacon Address Schema
| Prefix: |
RRC: |
Location: |
| 195.80.236.0/24 |
RRC12 - DE-CIX |
Frankfurt, Germany |
20/09/2004 - 02/02/2005:
Additional Beacon Prefix, 195.80.238.0/24 is announced as normal on RRC01,
RRC02,
RRC05, RRC06, RRC11. This Beacon Prefix is requested from Hitech Ballani
(hitesh@cs.cornell.edu) to work on Anycast server behaviours.
06/07/2004 - 02/02/2005:
RRC12:
- Announcements at 00:00h, 04:00h, 08:00h, 12:00h, 16:00h and 20:00h
(UTC)
- Withdrawals at 02:00h, 06:00h, 10:00h, 14:00h, 18:00h and 22:00h
(UTC)
Comments:
Beacon initiated to assist studies into unwanted effects on convergence
when
applying current Route Flap Damping practises.
Routing Beacon Address Schema
| Prefix: |
RRC: |
Location: |
| 195.80.236.0/24 |
RRC12 - DE-CIX |
Frankfurt, Germany |
07/12/2004 - 02/02/2005:
RRC14:
- Announcements at 00:00h, 04:00h, 08:00h, 12:00h, 16:00h and 20:00h
(UTC)
- Withdrawals at 02:00h, 06:00h, 10:00h, 14:00h, 18:00h and 22:00h
(UTC)
Comments:
Beacon initiated to assist studies into unwanted effects on convergence
when
applying current Route Flap Damping practises.
Routing Beacon Address Schema
| Prefix: |
RRC: |
Location: |
| 195.80.232.0/24 |
RRC14 - PAIX |
Palo Alto, US |
Prefix 195.80.232.0/24 was previously announced by RRC08. After moving
RRC08 from MAE-West to PAIX, it is announced by RRC14.
03/02/2005 - Present
RIS Beacons were re-numbered and the new list is below.
All RRCs:
- Announcements at 00:00, 04:00, 08:00, 12:00, 16:00, 20:00 (UTC)
- Withdrawals at 02:00, 06:00, 10:00, 14:00, 18:00, 22:00 (UTC)
Routing Beacon Address Schema
| Prefix: |
RRC: |
Location: |
| 84.205.64.0/24 |
RRC00 - RIPE NCC |
Amsterdam, NL |
| 84.205.65.0/24 |
RRC01 - LINX |
London, UK |
| 84.205.66.0/24 |
RRC02 - SFINX |
Paris, FR |
| 84.205.67.0/24 |
RRC03 - AMS-IX, NL-IX, GN-IX |
Amsterdam, NL |
| 84.205.68.0/24 |
RRC04 - CIXP |
Geneva, CH |
| 84.205.69.0/24 |
RRC05 - VIX |
Vienna, AT |
| 84.205.70.0/24 |
RRC06 - DIX-IE |
Otematchi, JP |
| 84.205.71.0/24 |
RRC07 - NETNOD |
Stockholm, SE |
| 84.205.74.0/24 |
RRC10 - MIX |
Milan, IT |
| 84.205.75.0/24 |
RRC11 - NYIIX |
New York , NY, US |
| 84.205.76.0/24 |
RRC12 - DE-CIX |
Frankfurt, DE |
| 84.205.78.0/24 |
RRC14 - PAIX |
Palo Alto, CA, US |
Routing Anchor Address Schema
| Prefix: |
RRC: |
Location: |
| 84.205.80.0/24 |
RRC00 - RIPE NCC |
Amsterdam, NL |
| 84.205.81.0/24 |
RRC01 - LINX |
London, UK |
| 84.205.82.0/24 |
RRC02 - SFINX |
Paris, FR |
| 84.205.83.0/24 |
RRC03 - AMS-IX, NL-IX, GN-IX |
Amsterdam, NL |
| 84.205.84.0/24 |
RRC04 - CIXP |
Geneva, CH |
| 84.205.85.0/24 |
RRC05 - VIX |
Vienna, AT |
| 84.205.86.0/24 |
RRC06 - DIX-IE |
Otematchi, JP |
| 84.205.87.0/24 |
RRC07 - NETNOD |
Stockholm, SE |
| 84.205.90.0/24 |
RRC10 - MIX |
Milan, IT |
| 84.205.91.0/24 |
RRC11 - NYIIX |
New York , NY, US |
| 84.205.92.0/24 |
RRC12 - DE-CIX |
Frankfurt, DE |
| 84.205.94.0/24 |
RRC14 - PAIX |
Palo Alto, CA, US |
RRC01 / RRC03:
- Permanent announcement from RRC01
- Announcements from RRC03 at 00:00, 04:00, 08:00, 12:00, 16:00, 20:00 (UTC)
- Withdrawals from RRC03 at 02:00, 06:00, 10:00, 14:00, 18:00, 22:00 (UTC)
Routing Beacon Address Schema
| Prefix: |
RRC: |
Location: |
| 84.205.72.0/24 |
RRC01 - LINX |
London, UK |
| 84.205.72.0/24 |
RRC03 - AMS-IX, NL-IX, GN-IX |
Amsterdam, NL |
02/06/2005 - Present
RRC13 was put online. Beacon prefix announcement schedule is the same as the other RRCs.
- Announcements at 00:00, 04:00, 08:00, 12:00, 16:00, 20:00 (UTC)
- Withdrawals at 02:00, 06:00, 10:00, 14:00, 18:00, 22:00 (UTC)
Routing Beacon Address Schema
| Prefix: |
RRC: |
Location: |
| 84.205.77.0/24 |
RRC13 - MSK-IX |
Moscow, RU |
Routing Anchor Address Schema
| Prefix: |
RRC: |
Location: |
| 84.205.93.0/24 |
RRC13 - MSK-IX |
Moscow, RU |
14/12/2005 - Present
RRC15 was put online. Beacon prefix announcement schedule is the same as the other RRCs.
- Announcements at 00:00, 04:00, 08:00, 12:00, 16:00, 20:00 (UTC)
- Withdrawals at 02:00, 06:00, 10:00, 14:00, 18:00, 22:00 (UTC)
Routing Beacon Address Schema
| Prefix: |
RRC: |
Location: |
| 84.205.79.0/24 |
RRC15 - PTTMetro-SP |
Sao Paulo, BR |
Routing Anchor Address Schema
| Prefix: |
RRC: |
Location: |
| 84.205.95.0/24 |
RRC15 - PTTMetro-SP |
Sao Paulo, BR |
How to Lease a Beacon
If you need different announcement or withdrawal patterns for a defined period of time, contact us at ris@ripe.net.
|
 |
| RELATED TOPICS |
|
|
|
|
