bgpreport

Network · data from 2026-11-12

AS269202 BRASNET MULTIINFORMATICA

Registry name: AS269202 - BRASNET MULTIINFORMATICA LTDA ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269202, 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.
45.181.212.0/23 Valid Other IRR onlyRADB, TC 665 99% 67
45.181.212.0/24 Valid Other IRR onlyRADB, TC 665 99% 67
45.181.213.0/24 Valid Other IRR onlyRADB, TC 665 99% 67
45.181.214.0/23 Valid Other IRR onlyRADB, TC 665 99% 67
45.181.214.0/24 Valid Other IRR onlyRADB, TC 665 99% 67
45.181.215.0/24 Valid Other IRR onlyRADB, TC 665 99% 67
2804:60f4::/32 Valid Other IRR onlyTC 636 100% 67
2804:60f4::/33 Valid Other IRR onlyTC 636 100% 67
2804:60f4::/36 Valid Other IRR onlyTC 636 100% 67
2804:60f4:8000::/33 Valid Other IRR onlyTC 636 100% 67
2804:60f4:8000::/40 Valid Other IRR onlyTC 636 100% 67
2804:60f4:8100::/40 Valid Other IRR onlyTC 636 100% 67
2804:60f4:8800::/40 Valid Other IRR onlyTC 636 100% 67
2804:60f4:8700::/40 Valid Other IRR onlyTC 3 0%low visibility 3
45.181.212.0/22 Valid Other IRR onlyTC 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS269202: AS-BMI. 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 (AS269202 isn't in the set, or no route object for AS269202 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 objectsAS269202 in itNot covered
AS-BMI In no IRR database read today.

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.

  • Route object: RIR15
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: RIR45.181.212.0/23Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR45.181.212.0/24Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR45.181.213.0/24Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR45.181.214.0/23Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR45.181.214.0/24Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR45.181.215.0/24Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:60f4::/32Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:60f4::/33Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:60f4::/36Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:60f4:8000::/33Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:60f4:8000::/40Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:60f4:8100::/40Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:60f4:8800::/40Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:60f4:8700::/40Route object only in TC. Add it in the RIR database for the space.3 of 636
Route object: RIR45.181.212.0/22Route object only in TC. Add it in the RIR database for the space.2 of 673
AS-SET: not foundAS-BMIPeeringDB names AS-BMI; no IRR database read has it.

Route objects not announced

Every route object with origin AS269202 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.