Network · data from 2026-11-12

AS265271 PLAYBOX INFORMATICA LTDA - ME

Registry name: AS265271 - PLAYBOX INFORMATICA LTDA - ME, BR · PeeringDB

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

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

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

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

Announced routes

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


168.90.16.0/24	Valid	Nonecovered by 168.90.16.0/23	669 99%	67
168.90.18.0/24	Valid	Other IRR onlyALTDB, RADB	673 100%	66
168.90.16.0/23	Valid	Other IRR onlyALTDB, RADB	670 100%	67
168.90.19.0/24	Valid	Other IRR onlyALTDB, RADB	670 100%	67
2804:2d48::/32	Valid	Other IRR onlyALTDB, RADB, TC	635 100%	67

AS-SET

AS265271'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 6 are in fix.csv.

Route object: none1
Route object: RIR4
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
Route object: none	168.90.16.0/24	No route object for it. A route object for 168.90.16.0/23 with origin AS265271 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265271 in the RIR database for the space.	669 of 673
Route object: RIR	168.90.18.0/24	Route object only in ALTDB, RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	168.90.16.0/23	Route object only in ALTDB, RADB. Add it in the RIR database for the space.	670 of 673
Route object: RIR	168.90.19.0/24	Route object only in ALTDB, RADB. Add it in the RIR database for the space.	670 of 673
Route object: RIR	2804:2d48::/32	Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

168.90.16.0/24

No route object for it. A route object for 168.90.16.0/23 with origin AS265271 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265271 in the RIR database for the space.

669 of 673

Route object: RIR

168.90.18.0/24

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

673 of 673

Route object: RIR

168.90.16.0/23

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

670 of 673

Route object: RIR

168.90.19.0/24

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

670 of 673

Route object: RIR

2804:2d48::/32

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

635 of 636

Route objects not announced

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


168.90.16.0/22	ALTDB, RADB, TC	Valid

168.90.16.0/22

ALTDB, 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.