bgpreport

Network · data from 2026-11-12

AS199668 Bureau1440-AS Bureau 1440 LLC

Registry name: Bureau1440-AS Bureau 1440 LLC, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS199668, 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.
138.16.144.0/21 No ROA RIR databaseRIPE 672 100% 66
138.16.144.0/22 No ROA RIR databaseRIPE 672 100% 67
138.16.144.0/24 No ROA RIR databaseRIPE 672 100% 67
195.96.40.0/21 No ROA RIR databaseRIPE 666 99% 66
195.96.40.0/22 No ROA RIR databaseRIPE 666 99% 67
195.96.40.0/24 No ROA RIR databaseRIPE 666 99% 67
195.96.41.0/24 No ROA RIR databaseRIPE 666 99% 66
195.96.43.0/24 No ROA RIR databaseRIPE 666 99% 67
195.96.44.0/22 No ROA RIR databaseRIPE 666 99% 67
195.96.45.0/24 No ROA RIR databaseRIPE 666 99% 66
195.96.42.0/24 No ROA RIR databaseRIPE 665 99% 67
195.96.44.0/24 No ROA RIR databaseRIPE 1 0%low visibility 1

AS-SET

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

  • ROA: none12
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none138.16.144.0/21No ROA covers it. Add a ROA for AS199668, maxLength 21.672 of 673
ROA: none138.16.144.0/22No ROA covers it. Add a ROA for AS199668, maxLength 22.672 of 673
ROA: none138.16.144.0/24No ROA covers it. Add a ROA for AS199668, maxLength 24.672 of 673
ROA: none195.96.40.0/21No ROA covers it. Add a ROA for AS199668, maxLength 21.666 of 673
ROA: none195.96.40.0/22No ROA covers it. Add a ROA for AS199668, maxLength 22.666 of 673
ROA: none195.96.40.0/24No ROA covers it. Add a ROA for AS199668, maxLength 24.666 of 673
ROA: none195.96.41.0/24No ROA covers it. Add a ROA for AS199668, maxLength 24.666 of 673
ROA: none195.96.43.0/24No ROA covers it. Add a ROA for AS199668, maxLength 24.666 of 673
ROA: none195.96.44.0/22No ROA covers it. Add a ROA for AS199668, maxLength 22.666 of 673
ROA: none195.96.45.0/24No ROA covers it. Add a ROA for AS199668, maxLength 24.666 of 673
ROA: none195.96.42.0/24No ROA covers it. Add a ROA for AS199668, maxLength 24.665 of 673
ROA: none195.96.44.0/24No ROA covers it. Add a ROA for AS199668, maxLength 24.1 of 673

Route objects not announced

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

138.16.145.0/24RIPENo ROA
138.16.146.0/24RIPENo ROA
138.16.147.0/24RIPENo ROA
138.16.148.0/22RIPENo ROA
138.16.148.0/24RIPENo ROA
138.16.149.0/24RIPENo ROA
138.16.150.0/24RIPENo ROA
138.16.151.0/24RIPENo ROA
195.96.46.0/24RIPENo ROA
195.96.47.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.