asn.dev

Routing security

AS50825 UVT

Unclassified RIPE

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

Announcements

What this network originates

7 observed

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

PrefixRPKIIRRVantage points
2a03:c20::/29RPKI validIRR29
5.181.92.0/22RPKI validIRR53
78.24.96.0/22RPKI validIRR53
178.17.0.0/20RPKI validIRR53
178.17.14.0/24RPKI validIRR52
185.63.96.0/22RPKI validIRR53
185.160.20.0/22RPKI validIRR53

RPKI · ROAs

Route origin authorisations

6 ROAs

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

PrefixMax lengthTrust anchor
5.181.92.0/22/24RIPENCC
78.24.96.0/22/24RIPENCC
178.17.0.0/20/24RIPENCC
185.63.96.0/22/24RIPENCC
185.160.20.0/22/24RIPENCC
2a03:c20::/29/48RIPENCC

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

63 objects · 56 not announced

Route objects naming AS50825 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
5.181.92.0/24RIPE—MNT-2CONNECT2019-04-08Not announced
5.181.93.0/24RIPE—MNT-2CONNECT2019-04-08Not announced
5.181.94.0/24RIPE—MNT-2CONNECT2019-04-08Not announced
5.181.95.0/24RIPE—MNT-2CONNECT2019-04-08Not announced
78.24.96.0/24RIPE—MNT-2CONNECT2019-05-13Not announced
78.24.97.0/24RIPE—MNT-2CONNECT2019-05-13Not announced
78.24.98.0/24RIPE—MNT-2CONNECT2019-05-13Not announced
78.24.99.0/24RIPE—MNT-2CONNECT2019-05-13Not announced
178.17.0.0/24RIPE—MNT-2CONNECT2016-04-07Not announced
178.17.1.0/24RIPE—MNT-2CONNECT2016-04-07Not announced
178.17.2.0/24RIPE—MNT-2CONNECT2016-04-07Not announced
178.17.3.0/24RIPE—MNT-2CONNECT2016-04-07Not announced
178.17.4.0/24RIPE—MNT-2CONNECT2016-04-07Not announced
178.17.5.0/24RIPE—MNT-2CONNECT2016-04-07Not announced
178.17.6.0/24RIPE—MNT-2CONNECT2016-04-07Not announced
178.17.7.0/24RIPE—MNT-2CONNECT2016-04-07Not announced
178.17.8.0/24RIPE—MNT-2CONNECT2016-04-07Not announced
178.17.9.0/24RIPE—MNT-2CONNECT2016-04-07Not announced
178.17.10.0/24RIPE—MNT-2CONNECT2016-04-07Not announced
178.17.11.0/24RIPE—MNT-2CONNECT2016-04-07Not announced
178.17.12.0/24RIPE—MNT-2CONNECT2016-04-07Not announced
178.17.13.0/24RIPE—MNT-2CONNECT2016-04-07Not announced
178.17.15.0/24RIPE—MNT-2CONNECT2016-04-07Not announced
185.63.96.0/24RIPE—MNT-UVT2016-04-07Not announced
185.63.97.0/24RIPE—MNT-UVT2016-04-07Not announced
185.63.98.0/24RIPE—MNT-UVT2016-04-07Not announced
185.63.99.0/24RIPE—MNT-UVT2016-04-07Not announced
185.160.20.0/24RIPE—MNT-UVT2026-02-04Not announced
185.160.21.0/24RIPE—MNT-UVT2026-02-04Not announced
185.160.22.0/24RIPE—MNT-UVT2026-02-04Not announced
185.160.23.0/24RIPE—MNT-UVT2026-02-04Not announced
2a03:c20::/32RIPEUVT InternetMNT-UVT2014-07-10Not announced
2a03:c22::/36RIPE—MNT-UVT2024-01-04Not announced
2a03:c22:1000::/36RIPE—MNT-UVT2024-01-04Not announced
2a03:c22:2000::/36RIPE—MNT-UVT2024-01-04Not announced
2a03:c22:3000::/36RIPE—MNT-UVT2024-01-04Not announced
2a03:c22:4000::/36RIPE—MNT-UVT2024-01-04Not announced
2a03:c22:5000::/36RIPE—MNT-UVT2024-01-04Not announced
2a03:c22:6000::/36RIPE—MNT-UVT2024-01-04Not announced
2a03:c22:7000::/36RIPE—MNT-UVT2024-01-04Not announced
2a03:c22:8000::/36RIPE—MNT-UVT2024-01-04Not announced
2a03:c22:9000::/36RIPE—MNT-UVT2024-01-04Not announced
2a03:c22:a000::/36RIPE—MNT-UVT2024-01-04Not announced
2a03:c22:b000::/36RIPE—MNT-UVT2024-01-04Not announced
2a03:c22:c000::/36RIPE—MNT-UVT2024-01-04Not announced
2a03:c22:d000::/36RIPE—MNT-UVT2024-01-04Not announced
2a03:c22:e000::/36RIPE—MNT-UVT2024-01-04Not announced
2a03:c22:f000::/36RIPE—MNT-UVT2024-01-04Not announced
2a03:c23:8000::/36RIPE—MNT-UVT2023-12-18Not announced
2a03:c23:9000::/36RIPE—MNT-UVT2023-12-18Not announced
2a03:c23:a000::/36RIPE—MNT-UVT2023-12-18Not announced
2a03:c23:b000::/36RIPE—MNT-UVT2023-12-18Not announced
2a03:c23:c000::/36RIPE—MNT-UVT2023-12-18Not announced
2a03:c23:d000::/36RIPE—MNT-UVT2023-12-18Not announced
2a03:c23:e000::/36RIPE—MNT-UVT2023-12-18Not announced
2a03:c23:f000::/36RIPE—MNT-UVT2023-12-18Not announced
5.181.92.0/22RIPE—MNT-2CONNECT2019-04-08Announced
78.24.96.0/22RIPE—MNT-UVT2018-06-25Announced
178.17.0.0/20RIPEUVT internet networkMNT-2CONNECT2010-03-31Announced
178.17.14.0/24RIPE—MNT-2CONNECT2016-04-07Announced
185.63.96.0/22RIPEUVT InternetMNT-UVT2014-07-10Announced
185.160.20.0/22RIPE—MNT-UVT2026-02-03Announced
2a03:c20::/29RIPE—MNT-2CONNECT2021-10-12Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-2CONNECTRIPELists AS50825 as a direct member
AS-2CONNECT-FENIXRIPELists AS50825 as a direct member
AS-2CONNECT-NIXRIPELists AS50825 as a direct member

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