Network · data from 2026-11-12

AS263335 Alternativa Telecom

Registry name: AS263335 - Alternativa Telecom, BR · PeeringDB

7IPv4 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

8Route objects not announced registered with origin AS263335, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS263335, 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.36.136.0/21	Valid	Other IRR onlyRADB, TC	672 100%	66
191.36.136.0/22	Valid	Other IRR onlyRADB	672 100%	66
191.36.140.0/22	Valid	Other IRR onlyRADB	672 100%	66
191.36.136.0/23	Valid	Other IRR onlyRADB	671 100%	67
191.36.138.0/23	Valid	Other IRR onlyRADB	670 100%	66
191.36.140.0/23	Valid	Other IRR onlyRADB	670 100%	66
191.36.142.0/23	Valid	Other IRR onlyRADB	669 99%	67
2804:1484::/32	Valid	Other IRR onlyRADB, TC	631 99%	67
2804:1484:8000::/41	Valid	Other IRR onlyRADB	631 99%	67
2804:1484:8080::/41	Valid	Other IRR onlyRADB	631 99%	67

AS-SET

AS263335'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 18 are in fix.csv.

Route object: RIR10
Route object: not announced8

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	191.36.136.0/21	Route object only in RADB, TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	191.36.136.0/22	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	191.36.140.0/22	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	191.36.136.0/23	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	191.36.138.0/23	Route object only in RADB. Add it in the RIR database for the space.	670 of 673
Route object: RIR	191.36.140.0/23	Route object only in RADB. Add it in the RIR database for the space.	670 of 673
Route object: RIR	191.36.142.0/23	Route object only in RADB. Add it in the RIR database for the space.	669 of 673
Route object: RIR	2804:1484::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	631 of 636
Route object: RIR	2804:1484:8000::/41	Route object only in RADB. Add it in the RIR database for the space.	631 of 636
Route object: RIR	2804:1484:8080::/41	Route object only in RADB. Add it in the RIR database for the space.	631 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

191.36.136.0/21

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

672 of 673

Route object: RIR

191.36.136.0/22

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

672 of 673

Route object: RIR

191.36.140.0/22

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

672 of 673

Route object: RIR

191.36.136.0/23

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

671 of 673

Route object: RIR

191.36.138.0/23

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

670 of 673

Route object: RIR

191.36.140.0/23

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

670 of 673

Route object: RIR

191.36.142.0/23

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

669 of 673

Route object: RIR

2804:1484::/32

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

631 of 636

Route object: RIR

2804:1484:8000::/41

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

631 of 636

Route object: RIR

2804:1484:8080::/41

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

631 of 636

Route objects not announced

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


191.36.136.0/24	RADB, TC	Valid
191.36.137.0/24	RADB, TC	Valid
191.36.138.0/24	RADB, TC	Valid
191.36.139.0/24	RADB, TC	Valid
191.36.140.0/24	RADB, TC	Valid
191.36.141.0/24	RADB, TC	Valid
191.36.142.0/24	RADB, TC	Valid
191.36.143.0/24	RADB, TC	Valid

191.36.136.0/24

RADB, TC

Valid

191.36.137.0/24

RADB, TC

Valid

191.36.138.0/24

RADB, TC

Valid

191.36.139.0/24

RADB, TC

Valid

191.36.140.0/24

RADB, TC

Valid

191.36.141.0/24

RADB, TC

Valid

191.36.142.0/24

RADB, TC

Valid

191.36.143.0/24

RADB, TC

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.