bgpreport

Network · data from 2026-11-12

AS263545 BETINI NET TELECOM LTDA

Registry name: AS263545 - BETINI NET TELECOM LTDA, BR · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
7IPv6 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 AS263545, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS263545, 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.
191.6.0.0/22 Valid Other IRR onlyNTTCOM, RADB, TC 672 100% 67
2804:13ac::/33 Valid Other IRR onlyTC 635 100% 68
2804:13ac:8000::/33 Valid Other IRR onlyTC 635 100% 68
2804:13ac::/32 Valid Other IRR onlyRADB, TC 634 100% 67
2804:13ac::/34 Valid Other IRR onlyTC 634 100% 67
2804:13ac:4000::/34 Valid Other IRR onlyTC 634 100% 67
2804:13ac:8000::/34 Valid Other IRR onlyTC 634 100% 67
2804:13ac:c000::/34 Valid Other IRR onlyTC 634 100% 67
191.6.0.0/24 Valid Other IRR onlyTC 338 50% 63
191.6.1.0/24 Valid Other IRR onlyTC 338 50% 63
191.6.2.0/24 Valid Other IRR onlyTC 338 50% 63
191.6.3.0/24 Valid Other IRR onlyTC 338 50% 63
191.6.0.0/23 Valid Other IRR onlyTC 5 1%low visibility 2
191.6.2.0/23 Valid Other IRR onlyTC 5 1%low visibility 2

AS-SET

AS263545'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 14 are in fix.csv.

  • Route object: RIR14
ChangePrefix or setDetailFull-table peers
Route object: RIR191.6.0.0/22Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:13ac::/33Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:13ac:8000::/33Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:13ac::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:13ac::/34Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:13ac:4000::/34Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:13ac:8000::/34Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:13ac:c000::/34Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR191.6.0.0/24Route object only in TC. Add it in the RIR database for the space.338 of 673
Route object: RIR191.6.1.0/24Route object only in TC. Add it in the RIR database for the space.338 of 673
Route object: RIR191.6.2.0/24Route object only in TC. Add it in the RIR database for the space.338 of 673
Route object: RIR191.6.3.0/24Route object only in TC. Add it in the RIR database for the space.338 of 673
Route object: RIR191.6.0.0/23Route object only in TC. Add it in the RIR database for the space.5 of 673
Route object: RIR191.6.2.0/23Route object only in TC. Add it in the RIR database for the space.5 of 673

Route objects not announced

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