asn.dev

Routing security

AS12683 STATEL-AS PJSC Rostelecom

Unclassified RIPE

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

Announcements

What this network originates

10 observed

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

PrefixRPKIIRRVantage points
46.45.192.0/18RPKI validIRR53
46.63.128.0/17RPKI validIRR53
77.39.0.0/17RPKI validIRR53
82.119.128.0/19RPKI validIRR53
84.54.192.0/18RPKI validIRR53
85.159.32.0/21RPKI validIRR53
88.215.128.0/18RPKI validIRR53
94.255.0.0/17RPKI validIRR53
109.168.128.0/17RPKI validIRR53
212.96.96.0/19RPKI validIRR53

RPKI · ROAs

Route origin authorisations

10 ROAs

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

PrefixMax lengthTrust anchor
46.45.192.0/18/18RIPENCC
46.63.128.0/17/17RIPENCC
77.39.0.0/17/17RIPENCC
82.119.128.0/19/19RIPENCC
84.54.192.0/18/18RIPENCC
85.159.32.0/21/21RIPENCC
88.215.128.0/18/18RIPENCC
94.255.0.0/17/17RIPENCC
109.168.128.0/17/17RIPENCC
212.96.96.0/19/19RIPENCC

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

10 objects · 0 not announced

Route objects naming AS12683 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
46.45.192.0/18RIPEPJSC "Southern Telecommunications Company"ROSTELECOM-MNT2024-12-10Announced
46.63.128.0/17RIPEStavropol branch of OJSC RostelecomROSTELECOM-MNT2024-12-10Announced
77.39.0.0/17RIPEIP block routed by Stavropol branch of OJSC RostelecomROSTELECOM-MNT2024-12-10Announced
82.119.128.0/19RIPEMultihomed AS talking to AS8342 and AS8263ROSTELECOM-MNT2024-12-10Announced
84.54.192.0/18RIPEIP block routed by Stavropol branch of OJSC RostelecomROSTELECOM-MNT2024-12-10Announced
85.159.32.0/21RIPE—ROSTELECOM-MNT2019-03-04Announced
88.215.128.0/18RIPEMultihomed AS talking to AS8342 and AS20485ROSTELECOM-MNT2024-12-10Announced
94.255.0.0/17RIPEStavropol branch of PJSC "STC"ROSTELECOM-MNT2024-12-10Announced
109.168.128.0/17RIPEIP block routed by Stavropol branch of OJSC RostelecomROSTELECOM-MNT2024-12-10Announced
212.96.96.0/19RIPEStavropol branch of PJSC "STC"ROSTELECOM-MNT2024-12-10Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-BLOCK-SETRIPELists AS12683 as a direct member
AS-BLOCKED-RURIPELists AS12683 as a direct member
AS-HURRICANERADBLists AS12683 as a direct member
AS-ROSTELECOMRIPELists AS12683 as a direct member
AS-STATELRIPELists AS12683 as a direct member

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