asn.dev

Routing security

AS50716 TELECOMRUNET

Unclassified RIPE

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

Announcements

What this network originates

8 observed

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

PrefixRPKIIRRVantage points
2a00:d8c0:100::/48RPKI validIRR21
87.76.0.0/20RPKI validIRR55
91.239.16.0/22RPKI validIRR55
93.171.72.0/22RPKI validIRR55
109.197.192.0/21RPKI validIRR55
146.158.80.0/21RPKI validIRR55
146.158.87.0/24RPKI validIRR covering53
176.116.136.0/21RPKI validIRR55

RPKI · ROAs

Route origin authorisations

8 ROAs

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

PrefixMax lengthTrust anchor
87.76.0.0/20/22RIPENCC
91.239.16.0/22/22RIPENCC
93.171.72.0/22/24RIPENCC
109.197.192.0/21/22RIPENCC
146.158.80.0/21/24RIPENCC
176.116.136.0/21/22RIPENCC
176.116.140.0/23/23RIPENCC
2a00:d8c0:100::/48/128RIPENCC

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

20 objects · 13 not announced

Route objects naming AS50716 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
87.76.0.0/21RIPEJSC Telecom.ru, UlyanovskMNT-TELECOMRU2011-07-28Not announced
87.76.0.0/22RIPEJSC Telecom.ru, UlyanovskMNT-TELECOMRU2023-03-09Not announced
87.76.3.0/24RIPE—MNT-TELECOMRU2025-04-08Not announced
87.76.4.0/22RIPEJSC Telecom.ru, UlyanovskMNT-TELECOMRU2023-03-09Not announced
87.76.8.0/21RIPEJSC Telecom.ru, UlyanovskMNT-TELECOMRU2011-08-02Not announced
87.76.8.0/22RIPEJSC Telecom.ru, UlyanovskMNT-TELECOMRU2023-03-09Not announced
87.76.12.0/22RIPEJSC Telecom.ru, UlyanovskMNT-TELECOMRU2023-03-09Not announced
109.197.192.0/22RIPEJSC Telecom.ru, UlyanovskMNT-TELECOMRU2010-08-22Not announced
109.197.196.0/22RIPEJSC Telecom.ru, UlyanovskMNT-TELECOMRU2010-08-22Not announced
176.116.136.0/22RIPEJSC Telecom.ru, UlyanovskMNT-TELECOMRU2014-12-26Not announced
176.116.139.0/24RIPE—MNT-TELECOMRU2025-04-08Not announced
176.116.140.0/22RIPEJSC Telecom.ru, UlyanovskMNT-TELECOMRU2014-12-26Not announced
176.116.143.0/24RIPE—MNT-TELECOMRU2025-04-08Not announced
87.76.0.0/20RIPETelecom.ru Ltd, UlyanovskMNT-TELECOMRU2012-06-18Announced
91.239.16.0/22RIPETelecom.ru Ltd, UlyanovskMNT-TELECOMRU2012-06-18Announced
93.171.72.0/22RIPE—RIPE-DB-MNT2025-07-03Announced
109.197.192.0/21RIPETelecom.ru Ltd, UlyanovskMNT-TELECOMRU2012-06-18Announced
146.158.80.0/21RIPE—RIPE-DB-MNT2025-09-26Announced
176.116.136.0/21RIPETelecom.ru Ltd, UlyanovskMNT-TELECOMRU2012-06-18Announced
2a00:d8c0:100::/48RIPEJSC Telecom.ru, UlyanovskMNT-TELECOMRU2014-07-17Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-HURRICANERADBLists AS50716 as a direct member
AS-MF-IXRIPELists AS50716 as a direct member
AS-MF-MGSMRIPELists AS50716 as a direct member
AS-ROSTELECOMRIPELists AS50716 as a direct member
AS-TELECOMRURIPELists AS50716 as a direct member
AS-TRANSROUTE-SPECRIPELists AS50716 as a direct member
AS-ULIANOVSK-RTCENTERRIPELists AS50716 as a direct member
AS-ULIANOVSK-RTCENTER-IPV6RIPELists AS50716 as a direct member
AS209141:AS-RUCUSTRADBLists AS50716 as a direct member

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