asn.dev

Routing security

AS41718 VITRINATV-AS

Unclassified RIPE

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

Announcements

What this network originates

7 observed

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

PrefixRPKIIRRVantage points
193.27.224.0/24No ROAIRR52
193.27.225.0/24No ROAIRR52
191.44.34.0/24RPKI validIRR57
191.44.35.0/24RPKI validIRR53
194.156.120.0/24RPKI validIRR57
194.156.121.0/24RPKI validIRR52
195.216.153.0/24RPKI validIRR52

RPKI · ROAs

Route origin authorisations

5 ROAs

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

PrefixMax lengthTrust anchor
191.44.34.0/24/24RIPENCC
191.44.35.0/24/24RIPENCC
194.156.120.0/24/24RIPENCC
194.156.121.0/24/24RIPENCC
195.216.153.0/24/24RIPENCC

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

7 objects · 0 not announced

Route objects naming AS41718 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
191.44.34.0/24RIPE—IP-RIPE2026-06-11Announced
191.44.35.0/24RIPE—IP-RIPE2026-06-11Announced
193.27.224.0/24RIPE—IP-RIPE2019-12-12Announced
193.27.225.0/24RIPE—IP-RIPE2024-04-09Announced
194.156.120.0/24RIPE—IP-RIPE2025-02-04Announced
194.156.121.0/24RIPE—IP-RIPE2025-02-04Announced
195.216.153.0/24RIPE—IP-RIPE2023-07-26Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-DATAIXRIPELists AS41718 as a direct member
AS-DDOS-GUARDRIPELists AS41718 as a direct member
AS-GFWRIPELists AS41718 as a direct member
AS-GLOBAL-NETRIPELists AS41718 as a direct member
AS-HURRICANERADBLists AS41718 as a direct member
AS-ICNETRIPELists AS41718 as a direct member
AS-MF-MGSMRIPELists AS41718 as a direct member
AS-MISAKA-CUSTOMERSRIPELists AS41718 as a direct member
AS-MSKROUTESERVERRIPELists AS41718 as a direct member
AS-MSVRIPELists AS41718 as a direct member
AS-PIG-NETWORKRIPELists AS41718 as a direct member
AS-PIGNETWORKRADBLists AS41718 as a direct member
AS-PITER-IX-MSKRIPELists AS41718 as a direct member
AS-SOVAMRIPELists AS41718 as a direct member
AS-STORMWALL-SETRADBLists AS41718 as a direct member
AS-STORMWALL-SETRIPELists AS41718 as a direct member
AS-TEAM-HOSTRIPELists AS41718 as a direct member
AS-TRANSROUTE-SPECRIPELists AS41718 as a direct member
AS-TURKTELEKOMRIPELists AS41718 as a direct member
AS197068:AS-CUSTRIPELists AS41718 as a direct member
AS59692:AS-IQWEBRIPELists AS41718 as a direct member

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