asn.dev

Routing security

AS209367 HAPOTELE

Unclassified RIPE

RPKI valid 0% 0 of 23 announcements
RPKI invalid 0 none
No ROA 23 not covered by any ROA
IRR registered 100% 0 missing · 0 other origin
ROAs 0 authorising this AS

Announcements

What this network originates

23 observed

Every prefix observed with AS209367 as its origin, checked against RPKI and the IRR. Problems sort first.

PrefixRPKIIRRVantage points
62.76.146.0/23No ROAIRR53
62.76.194.0/23No ROAIRR53
62.76.196.0/22No ROAIRR53
91.196.4.0/24No ROAIRR53
193.232.0.0/23No ROAIRR53
193.232.14.0/23No ROAIRR53
193.232.116.0/24No ROAIRR53
193.232.118.0/24No ROAIRR53
193.232.144.0/23No ROAIRR53
193.232.209.0/24No ROAIRR53
194.85.200.0/23No ROAIRR53
194.190.44.0/23No ROAIRR53
194.190.47.0/24No ROAIRR53
194.190.88.0/24No ROAIRR53
194.190.94.0/23No ROAIRR53
194.226.161.0/24No ROAIRR53
194.226.184.0/23No ROAIRR53
194.226.242.0/24No ROAIRR53
194.226.252.0/24No ROAIRR53
195.19.131.0/24No ROAIRR53
195.19.141.0/24No ROAIRR53
195.19.156.0/24No ROAIRR53
195.208.198.0/23No ROAIRR53

RPKI · ROAs

Route origin authorisations

0 ROAs

Signed statements by address holders that AS209367 may originate these prefixes, up to the maximum length shown.

No ROA names this AS as an authorised origin.

ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.

RPKI · ASPA

Declared transit providers

No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.

IRR

Registered route objects

24 objects · 1 not announced

Route objects naming AS209367 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.

PrefixSourceDescriptionMaintainerChangedRouting
2a07:fc80::/29RIPE—LIR-RU-HAPOTELE-1-MNT2022-04-21Not announced
62.76.146.0/23RIPEHAPOTELEROSNIIROS-MNT2026-07-29Announced
62.76.194.0/23RIPEHAPOTELEROSNIIROS-MNT2025-04-14Announced
62.76.196.0/22RIPEHAPOTELEROSNIIROS-MNT2025-04-14Announced
91.196.4.0/24RIPE—LIR-RU-HAPOTELE-1-MNT2022-09-12Announced
193.232.0.0/23RIPEHAPOTELEROSNIIROS-MNT2025-10-16Announced
193.232.14.0/23RIPEHAPOTELEROSNIIROS-MNT2025-07-21Announced
193.232.116.0/24RIPEHAPOTELEROSNIIROS-MNT2024-08-05Announced
193.232.118.0/24RIPEHAPOTELEROSNIIROS-MNT2022-04-26Announced
193.232.144.0/23RIPEHAPOTELEROSNIIROS-MNT2026-06-24Announced
193.232.209.0/24RIPEHAPOTELEROSNIIROS-MNT2025-03-24Announced
194.85.200.0/23RIPEHAPOTELEROSNIIROS-MNT2025-12-30Announced
194.190.44.0/23RIPEHAPOTELEROSNIIROS-MNT2025-05-22Announced
194.190.47.0/24RIPEHAPOTELEROSNIIROS-MNT2025-01-16Announced
194.190.88.0/24RIPEHAPOTELEROSNIIROS-MNT2026-08-17Announced
194.190.94.0/23RIPEHAPOTELEROSNIIROS-MNT2025-04-14Announced
194.226.161.0/24RIPEHAPOTELEROSNIIROS-MNT2024-09-03Announced
194.226.184.0/23RIPEHAPOTELEROSNIIROS-MNT2026-02-12Announced
194.226.242.0/24RIPEHAPOTELEROSNIIROS-MNT2024-11-02Announced
194.226.252.0/24RIPEHAPOTELEROSNIIROS-MNT2024-09-24Announced
195.19.131.0/24RIPEHAPOTELEROSNIIROS-MNT2025-02-27Announced
195.19.141.0/24RIPEHAPOTELEROSNIIROS-MNT2025-02-13Announced
195.19.156.0/24RIPEHAPOTELEROSNIIROS-MNT2025-04-02Announced
195.208.198.0/23RIPEHAPOTELEROSNIIROS-MNT2025-11-24Announced

IRR

AS-sets

The as-set is what upstreams expand to build this network's customer filter. Sets that list AS209367 directly show who expects to carry it.

AS-setWhereRelationship
AS-HAPOTELERIPELists AS209367 as a direct member
AS-HAPOTELE-IPV6RIPELists AS209367 as a direct member
AS-RETN-ACTUAL-V4RIPELists AS209367 as a direct member
AS41194:AS-RASCOMRIPELists AS209367 as a direct member

RPKI from rpki-client, validated 2026-10-12 12:10 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-12. Cross-check on bgp.he.net.