Autonomous system
AS56554 IETF-MEETING IETF Meeting Network
Unclassified RIPE NSP
Summary
IETF Meeting Network
ietf meeting temporary infrastructure
IETF-MEETING is the dedicated network for IETF meetings, operated by the Internet Society.
What it's used for
- The space carries the temporary network infrastructure for IETF meetings, as indicated by the netname
ietf-meeting-networkand registrants including theIETF Executive DirectorandIETF NOC. - The AS announces 4096 IPv4 addresses and 2 IPv6 prefixes, with only 1 observed neighbour, reflecting a self-contained, event-specific network rather than a transit or access provider.
- Traffic consists of attendees, presenters, and staff connecting to the venue's Wi-Fi and wired infrastructure during IETF meetings, which are held three times per year globally.
Notable
- Registrants align with the announcer, listing the
IETF Executive Director,IETF NOC,Internet Society, andAbuse-C Role. - The address inventory is a single /20 block (31.130.224.0/20) and two IPv6 prefixes, sized for a large conference venue rather than a permanent ISP footprint.
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 1 exchange in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| San Francisco Metropolitan Internet Exchange | San Francisco, United States | 206.197.187.110 |
Transit providers
1 upstream, 0 downstream and 2 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS400517 | Linespeed | 129 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-10, 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 · 4.10K addresses IPv6 2 prefixes
| Country | Name | Prefixes |
|---|---|---|
| CH | Switzerland | 3 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS56554- Registry name
- IETF-MEETING
- Registrant
- IETF-MNT
- Abuse contact
- abuse@noc.ietf.org
- Registered
- 2011-03-16
- Last changed
- 2019-03-26
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- IETF-MEETING
- Also known as
- ... where it all began ...
- Network type
- NSP
- Scope
- Global
- Traffic ratio
- Mostly Inbound
- Peering policy
- Open
- IRR as-set
RIPE::AS56554:AS-IETF-MEETING- Website
- https://www.ietf.org/meeting/
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 · 3 valid, 0 with no ROA
- ROAs
- 4 authorising AS56554
- ASPA
- no ASPA record
- IRR
- 100% registered · 3 of 3 announcements
- Route objects
- 158 naming AS56554
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: 431 networks and 1,775 prefixes, as published 2026-10-11. 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