bgpreport

Network · data from 2026-11-12

AS269340 BM SERVICOS EM TELECOMUNICACOES

Registry name: AS269340 - BM SERVICOS EM TELECOMUNICACOES LTDA., BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269340, 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.
2804:6320::/34 No ROA Nonecovered by 2804:6320::/32 630 99% 67
2804:6320:4000::/34 No ROA Nonecovered by 2804:6320::/32 630 99% 67
2804:6320:8000::/34 No ROA Nonecovered by 2804:6320::/32 630 99% 67
2804:6320:c000::/34 No ROA Nonecovered by 2804:6320::/32 630 99% 67
45.184.140.0/22 No ROA Other IRR onlyALTDB, RADB 667 99% 67

AS-SET

AS269340's PeeringDB record names no 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 17 are in fix.csv.

  • ROA: none5
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none2804:6320::/34No ROA covers it. Add a ROA for AS269340, maxLength 34.630 of 636
Route object: none2804:6320::/34No route object for it. A route object for 2804:6320::/32 with origin AS269340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269340 in the RIR database for the space.630 of 636
ROA: none2804:6320:4000::/34No ROA covers it. Add a ROA for AS269340, maxLength 34.630 of 636
Route object: none2804:6320:4000::/34No route object for it. A route object for 2804:6320::/32 with origin AS269340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269340 in the RIR database for the space.630 of 636
ROA: none2804:6320:8000::/34No ROA covers it. Add a ROA for AS269340, maxLength 34.630 of 636
Route object: none2804:6320:8000::/34No route object for it. A route object for 2804:6320::/32 with origin AS269340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269340 in the RIR database for the space.630 of 636
ROA: none2804:6320:c000::/34No ROA covers it. Add a ROA for AS269340, maxLength 34.630 of 636
Route object: none2804:6320:c000::/34No route object for it. A route object for 2804:6320::/32 with origin AS269340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269340 in the RIR database for the space.630 of 636
ROA: none45.184.140.0/22No ROA covers it. Add a ROA for AS269340, maxLength 22.667 of 673
Route object: RIR45.184.140.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.667 of 673

Route objects not announced

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

45.184.140.0/23ALTDBNo ROA
45.184.140.0/24ALTDBNo ROA
45.184.141.0/24ALTDBNo ROA
45.184.142.0/23ALTDBNo ROA
45.184.142.0/24ALTDBNo ROA
45.184.143.0/24ALTDBNo ROA
2804:6320::/32ALTDB, RADBNo 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.