bgpreport

Network · data from 2026-11-12

AS264991 BOMFIM E SOUSA

Registry name: AS264991 - BOMFIM E SOUSA LTDA, BR · PeeringDB

7IPv4 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
8No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS264991, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS264991, 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.

170.84.92.0/22 No ROA Other IRR onlyRADB, TC 671 100% 67
170.84.92.0/23 No ROA Other IRR onlyRADB 671 100% 67
170.84.93.0/24 No ROA Other IRR onlyRADB, TC 671 100% 67
170.84.94.0/23 No ROA Other IRR onlyRADB 671 100% 67
170.84.94.0/24 No ROA Other IRR onlyRADB, TC 671 100% 67
170.84.92.0/24 No ROA Other IRR onlyRADB, TC 669 99% 67
170.84.95.0/24 No ROA Other IRR onlyRADB, TC 669 99% 67
2804:3114::/32 No ROA Other IRR onlyRADB, TC 357 56% 65

AS-SET

PeeringDB's irr_as_set for AS264991: AS264991. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS264991 isn't in the set, or no route object for AS264991 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS264991 in itNot covered
AS264991 A single AS number, not a set: AS264991 (this network), 8 route objects.

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

  • ROA: none8
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none170.84.92.0/22No ROA covers it. Add a ROA for AS264991, maxLength 22.671 of 673
Route object: RIR170.84.92.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none170.84.92.0/23No ROA covers it. Add a ROA for AS264991, maxLength 23.671 of 673
Route object: RIR170.84.92.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none170.84.93.0/24No ROA covers it. Add a ROA for AS264991, maxLength 24.671 of 673
Route object: RIR170.84.93.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none170.84.94.0/23No ROA covers it. Add a ROA for AS264991, maxLength 23.671 of 673
Route object: RIR170.84.94.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none170.84.94.0/24No ROA covers it. Add a ROA for AS264991, maxLength 24.671 of 673
Route object: RIR170.84.94.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none170.84.92.0/24No ROA covers it. Add a ROA for AS264991, maxLength 24.669 of 673
Route object: RIR170.84.92.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none170.84.95.0/24No ROA covers it. Add a ROA for AS264991, maxLength 24.669 of 673
Route object: RIR170.84.95.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:3114::/32No ROA covers it. Add a ROA for AS264991, maxLength 32.357 of 636
Route object: RIR2804:3114::/32Route object only in RADB, TC. Add it in the RIR database for the space.357 of 636

Route objects not announced

Every route object with origin AS264991 is announced.

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.