bgpreport

Network · data from 2026-11-12

AS9164 R-TEL-AS "R-TEL" LLC

Registry name: R-TEL-AS "R-TEL" LLC, UA · not in PeeringDB

0IPv4 routes
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS9164, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS9164, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
2a14:6300:6::/48 No ROA RIR databaseRIPE 631 99% 69

AS-SET

AS9164 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 2 are in fix.csv.

  • ROA: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2a14:6300:6::/48No ROA covers it. Add a ROA for AS9164, maxLength 48.631 of 636

Route objects not announced

Route objects with origin AS9164 whose prefix no peer sees AS9164 announce. Many are kept on purpose (backup routes, space announced only in some places).

194.26.0.0/24RIPENo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.