Network · data from 2026-11-12

AS269038 IDX DATA CENTERS & IT SERVICES

Registry name: AS269038 - IDX DATA CENTERS & IT SERVICES S.A., BR · PeeringDB

11IPv4 routes 100.0% RPKI valid · 90.9% with a route object

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

2Route objects not announced registered with origin AS269038, seen from no peer

Announced routes

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


170.245.214.0/24	Valid	Nonecovered by 170.245.212.0/22	672 100%	66
170.245.213.0/24	Valid	Other IRR onlyRADB	672 100%	66
45.177.172.0/22	Valid	Other IRR onlyALTDB, NTTCOM, RADB, TC	667 99%	67
45.177.174.0/24	Valid	Other IRR onlyRADB	667 99%	67
45.177.174.0/23	Valid	Other IRR onlyRADB	666 99%	67
170.245.215.0/24	Valid	Other IRR onlyRADB	666 99%	67
45.177.172.0/23	Valid	Other IRR onlyRADB	665 99%	67
170.245.212.0/24	Valid	Other IRR onlyRADB	664 99%	67
2804:5e84:ffff::/48	Valid	Other IRR onlyRADB	635 100%	67
2804:5e84::/33	Valid	Other IRR onlyRADB	630 99%	69
45.177.172.0/24	Valid	Other IRR onlyRADB	187 28%	53
45.177.173.0/24	Valid	Other IRR onlyRADB	187 28%	53
45.177.175.0/24	Valid	Other IRR onlyRADB	187 28%	53

AS-SET

AS269038'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 15 are in fix.csv.

Route object: none1
Route object: RIR12
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
Route object: none	170.245.214.0/24	No route object for it. A route object for 170.245.212.0/22 with origin AS269038 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269038 in the RIR database for the space.	672 of 673
Route object: RIR	170.245.213.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	45.177.172.0/22	Route object only in ALTDB, NTTCOM, RADB, TC. Add it in the RIR database for the space.	667 of 673
Route object: RIR	45.177.174.0/24	Route object only in RADB. Add it in the RIR database for the space.	667 of 673
Route object: RIR	45.177.174.0/23	Route object only in RADB. Add it in the RIR database for the space.	666 of 673
Route object: RIR	170.245.215.0/24	Route object only in RADB. Add it in the RIR database for the space.	666 of 673
Route object: RIR	45.177.172.0/23	Route object only in RADB. Add it in the RIR database for the space.	665 of 673
Route object: RIR	170.245.212.0/24	Route object only in RADB. Add it in the RIR database for the space.	664 of 673
Route object: RIR	2804:5e84:ffff::/48	Route object only in RADB. Add it in the RIR database for the space.	635 of 636
Route object: RIR	2804:5e84::/33	Route object only in RADB. Add it in the RIR database for the space.	630 of 636
Route object: RIR	45.177.172.0/24	Route object only in RADB. Add it in the RIR database for the space.	187 of 673
Route object: RIR	45.177.173.0/24	Route object only in RADB. Add it in the RIR database for the space.	187 of 673
Route object: RIR	45.177.175.0/24	Route object only in RADB. Add it in the RIR database for the space.	187 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

170.245.214.0/24

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

672 of 673

Route object: RIR

170.245.213.0/24

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

672 of 673

Route object: RIR

45.177.172.0/22

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

667 of 673

Route object: RIR

45.177.174.0/24

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

667 of 673

Route object: RIR

45.177.174.0/23

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

666 of 673

Route object: RIR

170.245.215.0/24

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

666 of 673

Route object: RIR

45.177.172.0/23

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

665 of 673

Route object: RIR

170.245.212.0/24

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

664 of 673

Route object: RIR

2804:5e84:ffff::/48

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

635 of 636

Route object: RIR

2804:5e84::/33

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

630 of 636

Route object: RIR

45.177.172.0/24

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

187 of 673

Route object: RIR

45.177.173.0/24

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

187 of 673

Route object: RIR

45.177.175.0/24

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

187 of 673

Route objects not announced

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


170.245.212.0/22	ALTDB, NTTCOM, RADB	Valid
2804:5e84::/32	ALTDB, NTTCOM, RADB, TC	Valid

170.245.212.0/22

ALTDB, NTTCOM, RADB

Valid

2804:5e84::/32

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