Autonomous system
AS27500 ICANN-MEETINGS
Unclassified ARIN Non-Profit
Summary
ICANN
non-profit meetings infrastructure icann
The AS handle ICANN-MEETINGS is held by ICANN.
What it's used for
- The address space carries ICANN meeting infrastructure, evidenced by the netname
ICANN-MEETINGSand reverse DNS entries such as0-194.icannmeeting.org. - The AS announces 2048 IPv4 addresses and 1 IPv6 prefix, with only 2 observed neighbours, indicating a dedicated, low-transit network for specific organizational events rather than general internet access.
Notable
- The RDAP registrant
ICANNmatches the AS holder, confirming direct ownership of the199.91.192.0/21block. - The inventory consists of a single contiguous IPv4 /21 and a single IPv6 /48, representing a compact, self-contained estate for conference and meeting operations.
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.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-15, 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 |
|---|---|---|
| US | United States of America | 2 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS27500- Registry name
- ICANN-MEETINGS
- Registrant
- ICANN
- Abuse contact
- ops@icann.org
- Registered
- 2011-02-18
- Last changed
- 2025-06-10
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- ICANN Meetings
- Network type
- Non-Profit
- Scope
- Not Disclosed
- Traffic ratio
- Balanced
- Peering policy
- Restrictive
- Website
- https://www.icann.org
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 AS27500
- ASPA
- no ASPA record
- IRR
- 100% registered · 2 of 2 announcements
- Route objects
- 15 naming AS27500
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: 442 networks and 1,782 prefixes, as published 2026-10-16. 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