bgpreport

Network · data from 2026-11-12

AS47397 BASE-AS Base Ltd.

Registry name: BASE-AS Base Ltd., RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS47397, 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.
31.41.96.0/21 No ROA RIR databaseRIPE 673 100% 67
85.234.96.0/22 No ROA RIR databaseRIPE 673 100% 67
91.206.18.0/23 No ROA RIR databaseRIPE 673 100% 67
194.28.152.0/22 No ROA RIR databaseRIPE 673 100% 67
2001:67c:15d4::/48 No ROA RIR databaseRIPE 636 100% 67

AS-SET

AS47397 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 7 are in fix.csv.

  • ROA: none5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none31.41.96.0/21No ROA covers it. Add a ROA for AS47397, maxLength 21.673 of 673
ROA: none85.234.96.0/22No ROA covers it. Add a ROA for AS47397, maxLength 22.673 of 673
ROA: none91.206.18.0/23No ROA covers it. Add a ROA for AS47397, maxLength 23.673 of 673
ROA: none194.28.152.0/22No ROA covers it. Add a ROA for AS47397, maxLength 22.673 of 673
ROA: none2001:67c:15d4::/48No ROA covers it. Add a ROA for AS47397, maxLength 48.636 of 636

Route objects not announced

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

91.206.18.0/24RIPENo ROA
91.206.19.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.