Network · data from 2026-11-12

AS266643 NETFY TELECOMUNICACOES

Registry name: AS266643 - NETFY TELECOMUNICACOES, BR · PeeringDB

6IPv4 routes 100.0% RPKI valid · 100.0% with a route object

3IPv6 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

0Low visibility seen by under 10% of full-table peers

3Route objects not announced registered with origin AS266643, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS266643, 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.


128.201.174.0/24	Valid	Other IRR onlyRADB, TC	669 99%	66
128.201.172.0/23	Valid	Other IRR onlyTC	665 99%	67
128.201.172.0/24	Valid	Other IRR onlyTC	665 99%	67
128.201.173.0/24	Valid	Other IRR onlyTC	665 99%	67
128.201.175.0/24	Valid	Other IRR onlyTC	665 99%	67
2804:3f28:ff00::/40	Valid	Other IRR onlyRADB	633 100%	67
2804:3f28:7800::/38	Valid	Other IRR onlyRADB	631 99%	67
2804:3f28::/32	Valid	Other IRR onlyRADB, TC	630 99%	67
128.201.172.0/22	Valid	Other IRR onlyRADB, TC	135 20%	45

AS-SET

AS266643'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 12 are in fix.csv.

Route object: RIR9
Route object: not announced3

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	128.201.174.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	669 of 673
Route object: RIR	128.201.172.0/23	Route object only in TC. Add it in the RIR database for the space.	665 of 673
Route object: RIR	128.201.172.0/24	Route object only in TC. Add it in the RIR database for the space.	665 of 673
Route object: RIR	128.201.173.0/24	Route object only in TC. Add it in the RIR database for the space.	665 of 673
Route object: RIR	128.201.175.0/24	Route object only in TC. Add it in the RIR database for the space.	665 of 673
Route object: RIR	2804:3f28:ff00::/40	Route object only in RADB. Add it in the RIR database for the space.	633 of 636
Route object: RIR	2804:3f28:7800::/38	Route object only in RADB. Add it in the RIR database for the space.	631 of 636
Route object: RIR	2804:3f28::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	630 of 636
Route object: RIR	128.201.172.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	135 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

128.201.174.0/24

Route object only in RADB, TC. Add it in the RIR database for the space.

669 of 673

Route object: RIR

128.201.172.0/23

Route object only in TC. Add it in the RIR database for the space.

665 of 673

Route object: RIR

128.201.172.0/24

Route object only in TC. Add it in the RIR database for the space.

665 of 673

Route object: RIR

128.201.173.0/24

Route object only in TC. Add it in the RIR database for the space.

665 of 673

Route object: RIR

128.201.175.0/24

Route object only in TC. Add it in the RIR database for the space.

665 of 673

Route object: RIR

2804:3f28:ff00::/40

Route object only in RADB. Add it in the RIR database for the space.

633 of 636

Route object: RIR

2804:3f28:7800::/38

Route object only in RADB. Add it in the RIR database for the space.

631 of 636

Route object: RIR

2804:3f28::/32

Route object only in RADB, TC. Add it in the RIR database for the space.

630 of 636

Route object: RIR

128.201.172.0/22

Route object only in RADB, TC. Add it in the RIR database for the space.

135 of 673

Route objects not announced

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


128.201.174.0/23	TC	Valid
2804:3f28::/33	TC	Valid
2804:3f28:8000::/33	TC	Valid

128.201.174.0/23

Valid

2804:3f28::/33

Valid

2804:3f28:8000::/33

Valid

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.