Autonomous system
AS12654 RIPE-NCC-RIS-AS Reseaux IP Europeens Network Coordination Centre RIPE NCC
Unclassified RIPE
Summary
RIPE NCC Routing Information Service
research infrastructure measurement
The beacon network: prefixes announced and withdrawn on a schedule so the rest of the Internet can be measured against them.
What it's used for
- Routing measurement. 5,776 addresses in 16 IPv4 prefixes, 28 IPv6 prefixes, and 153 observed BGP neighbours.
Notable
- Every block carries the netname
RIPE-NCC-RIS-BEACON. - The IPv4 announcements include a
/25at93.175.154.0and a/28at93.175.154.128, both far longer than the/24most operators will accept. - The IPv6 announcements range from
/46down to a single/64at2001:7fb:fb01:200::/64. - First seen in routing data in October 2002.
- Eighteen sampled addresses were queried and none returned a name.
Interesting
- A beacon is a prefix that is announced and withdrawn on a fixed, published timetable. Because the schedule is known in advance, anyone watching BGP can measure exactly how long an update takes to propagate, which paths it takes, and where it is filtered. The prefix carries no traffic; the announcement itself is the payload.
- That is why the sizes look wrong. A
/28and a bare/64exist to find out who accepts them, and the answer maps the filtering policies of the whole Internet without asking anyone. - This is the system that produces the first-seen dates in every other entry of this kind. Records only start where the collectors started, so the earliest date the archive can show is a property of this network's history rather than of the networks it observes.
- 153 neighbours for a network that serves no users is a measurement platform peering as widely as it can, because each additional peer is another vantage point.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
Recorded at 25 exchanges in 17 countries, largest first.
| Exchange | Location | Their address |
|---|---|---|
| IX.br (PTT.br) São Paulo | São Paulo, Brazil | 187.16.216.23 |
| DE-CIX Frankfurt | Frankfurt, Germany | 80.81.192.152 |
| LINX LON1 | London, United Kingdom | 195.66.225.241 |
| AMS-IX Amsterdam | Amsterdam, Netherlands | 80.249.208.69 |
| Neutral Internet Exchange | Amsterdam, Netherlands | 193.239.116.45 |
| NAPAfrica IX Johannesburg | Johannesburg, South Africa | 196.60.8.86 |
| France-IX Paris | Paris, France | 2001:7f8:54::1:99 |
| MSK-IX Moscow | Moscow, Russia | 195.208.208.114 |
Transit providers
86 upstream, 0 downstream and 129 adjacent networks observed; most-used upstreams first.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-13, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 19 prefixes · 5.78K addresses IPv6 16 prefixes
| Country | Name | Prefixes |
|---|---|---|
| NL | Netherlands | 35 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS12654- Registry name
- RIPE-NCC-RIS-AS
- Registrant
- Reseaux IP Europeens Network Coordination Centre (RIPE NCC)
- Abuse contact
- abuse@ripe.net
- Registered
- 1970-01-01
- Last changed
- 2026-10-09
- Allocation
- allocated
Routing security
RPKI and IRR
- RPKI
- 94% valid · 75 valid, 2 with no ROA 3 RPKI-invalid
- ROAs
- 84 authorising AS12654
- ASPA
- no ASPA record
- IRR
- 99% registered · 79 of 80 announcements 1 other origin
- Route objects
- 105 naming AS12654
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 436 networks and 1,771 prefixes, as published 2026-10-13. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere