ResearchRouting table, RPKI, IRR & looking glass

AS218375

No registry name is on file for AS218375. It originates 1 prefix in the global routing table.

0
IPv4 prefixes
1
IPv6 prefixes
100%
RPKI valid

Who holds AS218375

Names from RIPE NCC’s daily list of every allocated AS number. The ASN lookup fetches the full WHOIS record live.

AS number
AS218375
Handle
n/a
Organization
n/a
Country
n/a
ASPA
None published

What AS218375 announces

Prefixes originated by AS218375 in the routing table our collectors hold (kept current as routes change), each checked against the RPKI (every ten minutes) and the IRR (daily).

IPv4 prefixes
0
IPv6 prefixes
1
RPKI valid
1 100%
RPKI invalid
0
RPKI not found
0
ROAs naming AS218375
1
With an IRR route object
1 100%

Announced prefixes

Each opens its own page: who announces it, the paths our collectors see, its ROAs and route objects.

IPv6 (1)

RPKI valid   RPKI invalid   no ROA covers it

Who AS218375 buys transit from

Inferred from the AS paths in the RouteViews tables and our own collectors’ feeds, refreshed every 4 hours, most-seen first. 2 upstreams.

Who buys transit from AS218375

None seen: AS218375 does not appear to provide transit to anyone.

Routing registry objects

From the mirrored IRR databases (RADB, the five RIRs and more). Look it up live.

Sourceas-nameMaintained by
RIPECALGANAYGUN-ASRIPE-NCC-END-MNT, CALGANAYGUN-MNT, LIR-UK-SHIKANOKO-1-MNT

Route objects with origin AS218375: RIPE 1

as-sets that list AS218375 (2)