Network · data from 2026-11-12

AS265307 PLANETY INTERNET

Registry name: AS265307 - PLANETY INTERNET SERVICOS E COMUNICACOES LTDA - ME, BR · PeeringDB

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

2IPv6 routes 50.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

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

1Route objects not announced registered with origin AS265307, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS265307, 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:2dd8::/32	No ROA	Other IRR onlyRADB, TC	629 99%	67
168.90.101.0/24	Valid	Other IRR onlyTC	669 99%	66
168.90.102.0/24	Valid	Other IRR onlyRADB, TC	669 99%	67
168.90.100.0/24	Valid	Other IRR onlyRADB	667 99%	67
168.90.103.0/24	Valid	Other IRR onlyRADB, TC	667 99%	66
2804:2dd8:ff80::/44	Valid	Other IRR onlyTC	632 99%	67

AS-SET

AS265307'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 8 are in fix.csv.

ROA: none1
Route object: RIR6
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: none	2804:2dd8::/32	No ROA covers it. Add a ROA for AS265307, maxLength 32.	629 of 636
Route object: RIR	2804:2dd8::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	629 of 636
Route object: RIR	168.90.101.0/24	Route object only in TC. Add it in the RIR database for the space.	669 of 673
Route object: RIR	168.90.102.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	669 of 673
Route object: RIR	168.90.100.0/24	Route object only in RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	168.90.103.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	667 of 673
Route object: RIR	2804:2dd8:ff80::/44	Route object only in TC. Add it in the RIR database for the space.	632 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

2804:2dd8::/32

No ROA covers it. Add a ROA for AS265307, maxLength 32.

629 of 636

Route object: RIR

2804:2dd8::/32

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

629 of 636

Route object: RIR

168.90.101.0/24

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

669 of 673

Route object: RIR

168.90.102.0/24

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

669 of 673

Route object: RIR

168.90.100.0/24

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

667 of 673

Route object: RIR

168.90.103.0/24

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

667 of 673

Route object: RIR

2804:2dd8:ff80::/44

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

632 of 636

Route objects not announced

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


168.90.100.0/22	TC	No ROA

168.90.100.0/22

No 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.