bgpreport

Network · data from 2026-11-12

AS271496 AS271496 - BNET RIO PROVEDOR DE ACESSO A INTERNET LTDA

Registry name: AS271496 - BNET RIO PROVEDOR DE ACESSO A INTERNET LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271496, 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:7c70:ff00::/40 No ROA Nonecovered by 2804:7c70::/32 635 100% 67
181.224.50.0/23 Valid Other IRR onlyRADB, TC 672 100% 66
181.224.50.0/24 Valid Other IRR onlyTC 672 100% 66
181.224.49.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
181.224.51.0/24 Valid Other IRR onlyTC 671 100% 66
181.224.48.0/24 Valid Other IRR onlyTC 670 100% 66

AS-SET

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

  • ROA: none1
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2804:7c70:ff00::/40No ROA covers it. Add a ROA for AS271496, maxLength 40.635 of 636
Route object: none2804:7c70:ff00::/40No route object for it. A route object for 2804:7c70::/32 with origin AS271496 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271496 in the RIR database for the space.635 of 636
Route object: RIR181.224.50.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR181.224.50.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR181.224.49.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR181.224.51.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR181.224.48.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

181.224.48.0/22RADB, TCNo ROA
181.224.48.0/23RADB, TCValid
2804:7c70::/32RADB, TCNo 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.