asn.dev

Routing security

AS8570 LES OJSC Lipetskelectrosvyaz

Unclassified RIPE

RPKI valid 100% 21 of 21 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

21 observed

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

PrefixRPKIIRRVantage points
95.179.0.0/18RPKI validIRR54
95.179.0.0/19RPKI validIRR54
95.179.32.0/19RPKI validIRR54
95.179.64.0/19RPKI validIRR54
95.179.80.0/20RPKI validIRR54
95.179.96.0/19RPKI validIRR54
109.172.32.0/22RPKI validIRR54
109.172.40.0/22RPKI validIRR54
178.234.0.0/16RPKI validIRR54
178.234.0.0/17RPKI validIRR54
178.234.0.0/18RPKI validIRR54
178.234.64.0/18RPKI validIRR54
178.234.128.0/17RPKI validIRR54
178.234.128.0/18RPKI validIRR54
178.234.192.0/18RPKI validIRR54
195.34.224.0/19RPKI validIRR54
195.34.224.0/20RPKI validIRR54
195.34.232.0/21RPKI validIRR54
195.34.240.0/20RPKI validIRR54
195.34.247.0/24RPKI validIRR54
195.34.248.0/21RPKI validIRR54

RPKI · ROAs

Route origin authorisations

8 ROAs

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

PrefixMax lengthTrust anchor
95.179.0.0/18/22RIPENCC
95.179.64.0/19/20RIPENCC
95.179.80.0/20/24RIPENCC
95.179.96.0/19/22RIPENCC
109.172.32.0/22/22RIPENCC
109.172.40.0/22/22RIPENCC
178.234.0.0/16/18RIPENCC
195.34.224.0/19/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

21 objects · 0 not announced

Route objects naming AS8570 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
95.179.0.0/18RIPELipetsk Regional Public Network Route BBN-2/0 GeneralROSTELECOM-MNT2024-12-23Announced
95.179.0.0/19RIPEAddress block for point-to-poiLipetsk Regional Public Network Route BBN-2/10 GeneralROSTELECOM-MNT2024-12-23Announced
95.179.32.0/19RIPEAddress block for point-to-poiLipetsk Regional Public Network Route BBN-2/11 GeneralROSTELECOM-MNT2024-12-23Announced
95.179.64.0/19RIPEAddress block for point-to-poiLipetsk Regional Public Network Route BBN-2/12 GeneralROSTELECOM-MNT2024-12-23Announced
95.179.80.0/20RIPE—ROSTELECOM-MNT2024-12-23Announced
95.179.96.0/19RIPEAddress block for point-to-poiLipetsk Regional Public Network Route BBN-2/13 GeneralROSTELECOM-MNT2024-12-23Announced
109.172.32.0/22RIPE—ROSTELECOM-MNT2024-12-23Announced
109.172.40.0/22RIPE—ROSTELECOM-MNT2024-12-23Announced
178.234.0.0/16RIPEAddress block for point-to-point Lipetsk Regional Public Network Route BBN-3 GeneralROSTELECOM-MNT2024-12-23Announced
178.234.0.0/17RIPEAddress block for point-to-point Lipetsk Regional Public Network Route BBN-3/1ROSTELECOM-MNT2024-12-23Announced
178.234.0.0/18RIPEAddress block for point-to-point Lipetsk Regional Public Network Route BBN-3/1/1 GeneralROSTELECOM-MNT2024-12-23Announced
178.234.64.0/18RIPEAddress block for point-to-point Lipetsk Regional Public Network Route BBN-3/1/2 GeneralROSTELECOM-MNT2024-12-23Announced
178.234.128.0/17RIPEAddress block for point-to-point Lipetsk Regional Public Network Route BBN-3/2ROSTELECOM-MNT2024-12-23Announced
178.234.128.0/18RIPEAddress block for point-to-point Lipetsk Regional Public Network Route BBN-3/2/1 GeneralROSTELECOM-MNT2024-12-23Announced
178.234.192.0/18RIPEAddress block for point-to-point Lipetsk Regional Public Network Route BBN-3/2/2 GeneralROSTELECOM-MNT2024-12-23Announced
195.34.224.0/19RIPELipetsk Regional Public NetworkROSTELECOM-MNT2024-12-23Announced
195.34.224.0/20RIPELipetsk Regional Public Network Route N1ROSTELECOM-MNT2024-12-23Announced
195.34.232.0/21RIPELipetsk Regional Public Network Route N4ROSTELECOM-MNT2024-12-23Announced
195.34.240.0/20RIPELipetsk Regional Public Network Route N2ROSTELECOM-MNT2024-12-23Announced
195.34.247.0/24RIPE—ROSTELECOM-MNT2024-12-23Announced
195.34.248.0/21RIPELipetsk Regional Public Network Route N6ROSTELECOM-MNT2024-12-23Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-AXTELRADBLists AS8570 as a direct member
AS-BLOCK-SETRIPELists AS8570 as a direct member
AS-BLOCKED-RURIPELists AS8570 as a direct member
AS-BTN-CUSTOMERSRADBLists AS8570 as a direct member
AS-HURRICANERADBLists AS8570 as a direct member
AS-LESRIPELists AS8570 as a direct member
AS-ROSTELECOMRIPELists AS8570 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.