bgpreport

Network · data from 2026-11-12

AS263308 Ntweb Internet

Registry name: AS263308 - NTWEB SOLUCOES EM INTERNET LTDA ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263308, 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.7.24.0/23 No ROA Nonecovered by 191.7.24.0/22 672 100% 66
191.7.25.0/24 No ROA Nonecovered by 191.7.24.0/22 672 100% 66
191.7.26.0/23 No ROA Nonecovered by 191.7.24.0/22 672 100% 66
191.7.26.0/24 No ROA Nonecovered by 191.7.24.0/22 672 100% 66
191.7.27.0/24 No ROA Nonecovered by 191.7.24.0/22 672 100% 66
191.7.24.0/24 No ROA Other origin onlycovered by 191.7.24.0/22 663 99% 67
191.7.24.0/22 No ROA Other IRR onlyRADB, TC 672 100% 66
2804:1400::/32 No ROA Other IRR onlyRADB, TC 6 1%low visibility 6

AS-SET

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

  • ROA: none8
  • Route object: none6
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none191.7.24.0/23No ROA covers it. Add a ROA for AS263308, maxLength 23.672 of 673
Route object: none191.7.24.0/23No route object for it. A route object for 191.7.24.0/22 with origin AS263308 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263308 in the RIR database for the space.672 of 673
ROA: none191.7.25.0/24No ROA covers it. Add a ROA for AS263308, maxLength 24.672 of 673
Route object: none191.7.25.0/24No route object for it. A route object for 191.7.24.0/22 with origin AS263308 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263308 in the RIR database for the space.672 of 673
ROA: none191.7.26.0/23No ROA covers it. Add a ROA for AS263308, maxLength 23.672 of 673
Route object: none191.7.26.0/23No route object for it. A route object for 191.7.24.0/22 with origin AS263308 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263308 in the RIR database for the space.672 of 673
ROA: none191.7.26.0/24No ROA covers it. Add a ROA for AS263308, maxLength 24.672 of 673
Route object: none191.7.26.0/24No route object for it. A route object for 191.7.24.0/22 with origin AS263308 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263308 in the RIR database for the space.672 of 673
ROA: none191.7.27.0/24No ROA covers it. Add a ROA for AS263308, maxLength 24.672 of 673
Route object: none191.7.27.0/24No route object for it. A route object for 191.7.24.0/22 with origin AS263308 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263308 in the RIR database for the space.672 of 673
ROA: none191.7.24.0/24No ROA covers it. Add a ROA for AS263308, maxLength 24.663 of 673
Route object: none191.7.24.0/24Route objects for it name AS272479. A route object for 191.7.24.0/22 with origin AS263308 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263308 in the RIR database for the space.663 of 673
ROA: none191.7.24.0/22No ROA covers it. Add a ROA for AS263308, maxLength 22.672 of 673
Route object: RIR191.7.24.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none2804:1400::/32No ROA covers it. Add a ROA for AS263308, maxLength 32.6 of 636
Route object: RIR2804:1400::/32Route object only in RADB, TC. Add it in the RIR database for the space.6 of 636

Route objects not announced

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