ResearchIRR · RIPE

AS-XENONCLOUD N

An as-set registered in RIPE, maintained by LIR-DE-XENONCLOUD-1-MNT, XENONCLOUD-MNT. It names 2 ASes and 1 set directly; followed all the way down, it reaches 2 ASes through 1 nested sets.

Members

What AS-XENONCLOUD lists

2 ASes and 1 set, written in the object across every registry that holds it. Sets open their own page. 1 of the sets is not registered in any IRR we mirror, so a filter built from AS-XENONCLOUD gets nothing from it.

AS-MWSQ not registeredAS200718 ph24AS202278 XENONCLOUD
Expanded

Every AS it reaches

What a filter built from AS-XENONCLOUD would let in: 2 ASes.

Show the 2 ASes
AS200718AS202278
Prefixes

What AS-XENONCLOUD covers

Every route object in the IRR whose origin is one of the 2 ASes it reaches: the prefixes a filter built from AS-XENONCLOUD (with bgpq4, say) would allow. 1 IPv4 and 4 IPv6. Every one is in the IRR API.

1 IPv4 prefix
80.75.214.0/24
4 IPv6 prefixes
2001:67c:1168::/482a13:5680::/322a13:5680:ffff::/482a13:5682::/40
Registries

Each registry’s copy

RIPE3 membersN
Maintained byLIR-DE-XENONCLOUD-1-MNT, XENONCLOUD-MNT
Last modified2023-04-19T12:41:26Z
MembersAS202278 AS-MWSQ AS200718
mbrs-by-refN
Used by

Sets that include AS-XENONCLOUD

AS-REJECTYAS212635:AS-BGP-EXCHANGE-DUSSELDORF-RS
Tools

Check AS-XENONCLOUD live

IRR API, with prefixes