bgpreport

Network · data from 2026-11-12

AS263675 JAIR APARECIDO CASAROTTE - EPP

Registry name: AS263675 - NETWEB TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263675, 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.241.169.0/24 No ROA Other IRR onlyRADB 671 100% 67
191.241.170.0/24 No ROA Other IRR onlyRADB 671 100% 67
191.241.173.0/24 No ROA Other IRR onlyRADB 671 100% 67
191.241.168.0/24 No ROA Other IRR onlyRADB 670 100% 67
191.241.174.0/24 No ROA Other IRR onlyRADB 670 100% 67
191.241.175.0/24 No ROA Other IRR onlyRADB 670 100% 67
191.241.168.0/21 No ROA Other IRR onlyRADB 669 99% 67
2804:116c::/32 No ROA Other IRR onlyRADB 632 99% 67
191.241.171.0/24 No ROA Other IRR onlyRADB 4 1%low visibility 3
191.241.172.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 1

AS-SET

AS263675'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 23 are in fix.csv.

  • ROA: none10
  • Route object: RIR10
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none191.241.169.0/24No ROA covers it. Add a ROA for AS263675, maxLength 24.671 of 673
Route object: RIR191.241.169.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none191.241.170.0/24No ROA covers it. Add a ROA for AS263675, maxLength 24.671 of 673
Route object: RIR191.241.170.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none191.241.173.0/24No ROA covers it. Add a ROA for AS263675, maxLength 24.671 of 673
Route object: RIR191.241.173.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none191.241.168.0/24No ROA covers it. Add a ROA for AS263675, maxLength 24.670 of 673
Route object: RIR191.241.168.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none191.241.174.0/24No ROA covers it. Add a ROA for AS263675, maxLength 24.670 of 673
Route object: RIR191.241.174.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none191.241.175.0/24No ROA covers it. Add a ROA for AS263675, maxLength 24.670 of 673
Route object: RIR191.241.175.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none191.241.168.0/21No ROA covers it. Add a ROA for AS263675, maxLength 21.669 of 673
Route object: RIR191.241.168.0/21Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2804:116c::/32No ROA covers it. Add a ROA for AS263675, maxLength 32.632 of 636
Route object: RIR2804:116c::/32Route object only in RADB. Add it in the RIR database for the space.632 of 636
ROA: none191.241.171.0/24No ROA covers it. Add a ROA for AS263675, maxLength 24.4 of 673
Route object: RIR191.241.171.0/24Route object only in RADB. Add it in the RIR database for the space.4 of 673
ROA: none191.241.172.0/24No ROA covers it. Add a ROA for AS263675, maxLength 24.2 of 673
Route object: RIR191.241.172.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

191.241.168.0/22RADBNo ROA
191.241.168.0/29RADBNo ROA
191.241.172.0/22RADBNo 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.