Network · data from 2026-11-12

AS266010 AS266010 - BOA VISTA NET SERVICOS DE COMUNICACAO LTDA

Registry name: AS266010 - BOA VISTA NET SERVICOS DE COMUNICACAO LTDA, BR · not in PeeringDB

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

3IPv6 routes 100.0% RPKI valid · 33.3% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 2 with no route object for this origin

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

9Route objects not announced registered with origin AS266010, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS266010, 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:4134:8030::/44	Valid	Nonecovered by 2804:4134:8000::/34	636 100%	67
2804:4134:8010::/44	Valid	Nonecovered by 2804:4134:8000::/34	634 100%	67
181.191.112.0/24	Valid	Other IRR onlyTC	672 100%	66
181.191.114.0/24	Valid	Other IRR onlyRADB, TC	671 100%	67
181.191.115.0/24	Valid	Other IRR onlyRADB, TC	670 100%	67
181.191.112.0/22	Valid	Other IRR onlyRADB, TC	665 99%	66
2804:4134::/32	Valid	Other IRR onlyRADB, TC	630 99%	67

AS-SET

AS266010 isn't in PeeringDB, where networks name their 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.

Route object: none2
Route object: RIR5
Route object: not announced9

Change	Prefix or set	Detail	Full-table peers
Route object: none	2804:4134:8030::/44	No route object for it. A route object for 2804:4134:8000::/34 with origin AS266010 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266010 in the RIR database for the space.	636 of 636
Route object: none	2804:4134:8010::/44	No route object for it. A route object for 2804:4134:8000::/34 with origin AS266010 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266010 in the RIR database for the space.	634 of 636
Route object: RIR	181.191.112.0/24	Route object only in TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	181.191.114.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	181.191.115.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	181.191.112.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	665 of 673
Route object: RIR	2804:4134::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	630 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2804:4134:8030::/44

No route object for it. A route object for 2804:4134:8000::/34 with origin AS266010 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266010 in the RIR database for the space.

636 of 636

Route object: none

2804:4134:8010::/44

634 of 636

Route object: RIR

181.191.112.0/24

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

672 of 673

Route object: RIR

181.191.114.0/24

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

671 of 673

Route object: RIR

181.191.115.0/24

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

670 of 673

Route object: RIR

181.191.112.0/22

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

665 of 673

Route object: RIR

2804:4134::/32

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

630 of 636

Route objects not announced

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


181.191.112.0/23	RADB, TC	Valid
181.191.113.0/24	TC	Valid
181.191.114.0/23	RADB, TC	Valid
2804:4134::/33	TC	Valid
2804:4134::/34	TC	Valid
2804:4134:4000::/34	TC	Valid
2804:4134:8000::/33	TC	Valid
2804:4134:8000::/34	TC	Valid
2804:4134:c000::/34	TC	Valid

181.191.112.0/23

RADB, TC

Valid

181.191.113.0/24

Valid

181.191.114.0/23

RADB, TC

Valid

2804:4134::/33

Valid

2804:4134::/34

Valid

2804:4134:4000::/34

Valid

2804:4134:8000::/33

Valid

2804:4134:8000::/34

Valid

2804:4134:c000::/34

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.