bgpreport

Network · data from 2026-11-12

AS263473 Networld Telecom

Registry name: AS263473 - SILVANIA ALVES SANTOS ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263473, 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:1260::/33 No ROA Nonecovered by 2804:1260::/32 5 1%low visibility 3
2804:1260:8000::/33 No ROA Nonecovered by 2804:1260::/32 5 1%low visibility 3
191.242.64.0/21 No ROA Other IRR onlyRADB, TC 671 100% 67
191.242.64.0/22 No ROA Other IRR onlyRADB 671 100% 67
191.242.68.0/22 No ROA Other IRR onlyRADB 671 100% 67
2804:1260::/32 No ROA Other IRR onlyRADB, TC 636 100% 70

AS-SET

AS263473'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 24 are in fix.csv.

  • ROA: none6
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none2804:1260::/33No ROA covers it. Add a ROA for AS263473, maxLength 33.5 of 636
Route object: none2804:1260::/33No route object for it. A route object for 2804:1260::/32 with origin AS263473 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263473 in the RIR database for the space.5 of 636
ROA: none2804:1260:8000::/33No ROA covers it. Add a ROA for AS263473, maxLength 33.5 of 636
Route object: none2804:1260:8000::/33No route object for it. A route object for 2804:1260::/32 with origin AS263473 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263473 in the RIR database for the space.5 of 636
ROA: none191.242.64.0/21No ROA covers it. Add a ROA for AS263473, maxLength 21.671 of 673
Route object: RIR191.242.64.0/21Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none191.242.64.0/22No ROA covers it. Add a ROA for AS263473, maxLength 22.671 of 673
Route object: RIR191.242.64.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none191.242.68.0/22No ROA covers it. Add a ROA for AS263473, maxLength 22.671 of 673
Route object: RIR191.242.68.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:1260::/32No ROA covers it. Add a ROA for AS263473, maxLength 32.636 of 636
Route object: RIR2804:1260::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

191.242.64.0/23RADBNo ROA
191.242.64.0/24RADBNo ROA
191.242.65.0/24RADBNo ROA
191.242.66.0/23RADBNo ROA
191.242.66.0/24RADBNo ROA
191.242.67.0/24RADBNo ROA
191.242.68.0/23RADBNo ROA
191.242.68.0/24RADBNo ROA
191.242.69.0/24RADBNo ROA
191.242.70.0/23RADBNo ROA
191.242.70.0/24RADBNo ROA
191.242.71.0/24RADBNo 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.