asn.dev

Routing security

AS20870 KAVKAZ-TRANSTELECOM-AS

Unclassified RIPE

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

Announcements

What this network originates

16 observed

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

PrefixRPKIIRRVantage points
2a03:5b80::/32No ROAIRR31
80.72.224.0/20No ROAIRR53
80.72.224.0/23No ROAIRR covering53
80.72.229.0/24No ROAIRR53
80.72.230.0/24No ROAIRR covering53
80.72.233.0/24No ROAIRR covering53
80.72.237.0/24No ROAIRR53
80.72.239.0/24No ROAIRR covering53
83.69.64.0/19No ROAIRR53
83.69.64.0/24No ROAIRR53
83.69.68.0/23No ROAIRR covering53
83.69.70.0/24No ROAIRR covering53
83.69.85.0/24No ROAIRR covering53
89.16.96.0/19No ROAIRR53
89.16.96.0/24No ROAIRR covering53
89.16.111.0/24No ROAIRR covering53

RPKI · ROAs

Route origin authorisations

0 ROAs

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

17 objects · 10 not announced

Route objects naming AS20870 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
80.72.227.0/24RADBProxy-registered route objectMAINT-AS34912025-03-28Not announced
80.72.228.0/24RADBProxy-registered route objectMAINT-AS34912025-03-28Not announced
80.72.232.0/24RADBProxy-registered route objectMAINT-AS34912025-03-28Not announced
83.69.65.0/24RIPEKavkaz TransTeleComKTTKNET-MNT2021-04-05Not announced
83.69.66.0/24RADBProxy-registered route objectMAINT-AS34912025-03-28Not announced
83.69.67.0/24RADBProxy-registered route objectMAINT-AS34912025-03-28Not announced
83.69.71.0/24RADBProxy-registered route objectMAINT-AS34912025-03-28Not announced
83.69.72.0/24RADBProxy-registered route objectMAINT-AS34912025-03-28Not announced
83.69.74.0/24RADBProxy-registered route objectMAINT-AS34912025-03-28Not announced
83.69.75.0/24RADBProxy-registered route objectMAINT-AS34912025-03-28Not announced
80.72.224.0/20RIPEKavkaz TransTeleComKTTKNET-MNT2015-04-08Announced
80.72.229.0/24RADBProxy-registered route objectMAINT-AS34912025-03-28Announced
80.72.237.0/24RADBProxy-registered route objectMAINT-AS34912025-03-28Announced
83.69.64.0/19RIPEKavkaz TransTeleComKTTKNET-MNT2015-04-08Announced
83.69.64.0/24RADBProxy-registered route objectMAINT-AS34912025-03-28Announced
89.16.96.0/19RIPEKavkaz TransTeleComKTTKNET-MNT2015-04-08Announced
2a03:5b80::/32RIPECJSC "Caucasus - Transtelekom"KTTKNET-MNT2015-04-08Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-BLOCK-SETRIPELists AS20870 as a direct member
AS-BLOCKED-RURIPELists AS20870 as a direct member
AS-BTN-CUSTOMERSRADBLists AS20870 as a direct member
AS-KTTKRIPELists AS20870 as a direct member
AS-MIRTELECOMRNDRIPELists AS20870 as a direct member
AS3491:AS-CUSTOMERS-EURADBLists AS20870 as a direct member

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