Autonomous system
AS2121 RIPE-MEETING-AS
Hosting APNIC
Summary
RIPE NCC (Meeting Network)
network legacy
The meeting and event network operated by the RIPE NCC (RIPE-MEETING-AS), the regional internet registry for Europe, the Middle East, and parts of Central Asia, based in Amsterdam.
What it's used for
- Providing connectivity and demonstrations at RIPE meetings and NCC events.
Notable
- Operated by the RIR itself for community and technical-coordination purposes, not a commercial network.
Interesting
- The low AS number fits the RIPE NCC's role at the centre of European internet coordination since the early 1990s.
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
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Transit providers
1 upstream, 0 downstream and 2 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS47697 | BIX.BG Ltd. | 95 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-14, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 1 prefixes · 2.05K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| NL | Netherlands | 2 |
Registry
Allocation record
- Registry
- APNIC
- Handle
AS2121- Registry name
- RIPE-MEETING-AS
- Registrant
- Reseaux IP Europeens Network Coordination Centre (RIPE NCC)
- Abuse contact
- abuse@ripe.net
- Registered
- 2002-09-20
- Last changed
- 2026-09-14
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- RIPE Meetings
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Website
- https://www.ripe.net
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 100% valid · 2 valid, 0 with no ROA
- ROAs
- 2 authorising AS2121
- ASPA
- 2 declared providers
- IRR
- 100% registered · 2 of 2 announcements
- Route objects
- 4 naming AS2121
Reputation
Classification and threat
Hosting Datacenter or cloud provider. Addresses are servers, not people.
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: 442 networks and 1,772 prefixes, as published 2026-10-15. 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