asn.dev

Routing security

AS25880 YURGATELEKOM-AS

Unclassified RIPE

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

Announcements

What this network originates

18 observed

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

PrefixRPKIIRRVantage points
31.170.184.0/21No ROAIRR53
31.170.184.0/24No ROAIRR53
31.170.185.0/24No ROAIRR53
31.170.186.0/24No ROAIRR53
89.145.128.0/19No ROAIRR53
89.145.128.0/22No ROAIRR53
89.145.137.0/24No ROAIRR covering53
89.145.140.0/22No ROAIRR53
89.145.144.0/22No ROAIRR53
89.145.145.0/24No ROAIRR covering53
89.145.148.0/22No ROAIRR53
89.145.152.0/22No ROAIRR53
89.145.156.0/22No ROAIRR53
185.190.184.0/22No ROAIRR53
185.190.184.0/24No ROAIRR53
185.190.185.0/24No ROAIRR53
185.190.186.0/24No ROAIRR53
185.190.187.0/24No ROAIRR53

RPKI · ROAs

Route origin authorisations

0 ROAs

Signed statements by address holders that AS25880 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

18 objects · 2 not announced

Route objects naming AS25880 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
89.145.132.0/22RIPEOAO YurgatelekomYURGATELEKOM-MNT2011-11-03Not announced
89.145.136.0/22RIPEOAO YurgatelekomYURGATELEKOM-MNT2011-11-03Not announced
31.170.184.0/21RIPEOAO YurgatelekomYURGATELEKOM-MNT2018-04-27Announced
31.170.184.0/24RIPERU-YURGATELEKOM-20180726YURGATELEKOM-MNT2018-07-26Announced
31.170.185.0/24RIPERU-YURGATELEKOM-20180726YURGATELEKOM-MNT2018-07-26Announced
31.170.186.0/24RIPERU-YURGATELEKOM-20180726YURGATELEKOM-MNT2018-07-26Announced
89.145.128.0/19RIPEOAO YurgatelekomYURGATELEKOM-MNT2011-11-03Announced
89.145.128.0/22RIPEOAO YurgatelekomYURGATELEKOM-MNT2011-11-03Announced
89.145.140.0/22RIPEOAO YurgatelekomYURGATELEKOM-MNT2011-11-03Announced
89.145.144.0/22RIPEOAO YurgatelekomYURGATELEKOM-MNT2011-11-03Announced
89.145.148.0/22RIPEOAO YurgatelekomYURGATELEKOM-MNT2011-11-03Announced
89.145.152.0/22RIPEOAO YurgatelekomYURGATELEKOM-MNT2011-11-03Announced
89.145.156.0/22RIPEOAO YurgatelekomYURGATELEKOM-MNT2011-11-03Announced
185.190.184.0/22RIPERUTELECOMYURGATELEKOM-MNT2018-04-27Announced
185.190.184.0/24RIPERU-YURGATELEKOM-20180726YURGATELEKOM-MNT2018-07-26Announced
185.190.185.0/24RIPERU-YURGATELEKOM-20180726YURGATELEKOM-MNT2018-07-26Announced
185.190.186.0/24RIPERU-YURGATELEKOM-20180726YURGATELEKOM-MNT2018-07-26Announced
185.190.187.0/24RIPERU-YURGATELEKOM-20180726YURGATELEKOM-MNT2018-07-26Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-BLOCK-SETRIPELists AS25880 as a direct member
AS-BLOCKED-RURIPELists AS25880 as a direct member
AS-MF-MGSMRIPELists AS25880 as a direct member
AS-MSVRIPELists AS25880 as a direct member
AS-SOVAMRIPELists AS25880 as a direct member
AS-TTKRIPELists AS25880 as a direct member
AS-ZSTTK-SETRIPELists AS25880 as a direct member

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