Network · data from 2026-11-12

AS264484 4u Network

Registry name: AS264484 - 4U NETWORK, BR · PeeringDB

10IPv4 routes 100.0% RPKI valid · 20.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 8 with no route object for this origin

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

0Route objects not announced registered with origin AS264484, seen from no peer

Announced routes

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


131.255.108.0/24	Valid	Nonecovered by 131.255.108.0/22	672 100%	67
131.255.109.0/24	Valid	Nonecovered by 131.255.108.0/22	672 100%	67
131.255.110.0/24	Valid	Nonecovered by 131.255.108.0/22	672 100%	67
131.255.111.0/24	Valid	Nonecovered by 131.255.108.0/22	672 100%	67
138.186.168.0/24	Valid	Nonecovered by 138.186.168.0/22	672 100%	67
138.186.169.0/24	Valid	Nonecovered by 138.186.168.0/22	672 100%	67
138.186.170.0/24	Valid	Nonecovered by 138.186.168.0/22	672 100%	67
138.186.171.0/24	Valid	Nonecovered by 138.186.168.0/22	672 100%	67
131.255.108.0/22	Valid	Other IRR onlyRADB, TC	672 100%	67
138.186.168.0/22	Valid	Other IRR onlyRADB, TC	672 100%	67
2804:204c::/32	Valid	Other IRR onlyRADB, TC	635 100%	69

AS-SET

AS264484'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 11 are in fix.csv.

Route object: none8
Route object: RIR3

Change	Prefix or set	Detail	Full-table peers
Route object: none	131.255.108.0/24	No route object for it. A route object for 131.255.108.0/22 with origin AS264484 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264484 in the RIR database for the space.	672 of 673
Route object: none	131.255.109.0/24	No route object for it. A route object for 131.255.108.0/22 with origin AS264484 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264484 in the RIR database for the space.	672 of 673
Route object: none	131.255.110.0/24	No route object for it. A route object for 131.255.108.0/22 with origin AS264484 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264484 in the RIR database for the space.	672 of 673
Route object: none	131.255.111.0/24	No route object for it. A route object for 131.255.108.0/22 with origin AS264484 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264484 in the RIR database for the space.	672 of 673
Route object: none	138.186.168.0/24	No route object for it. A route object for 138.186.168.0/22 with origin AS264484 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264484 in the RIR database for the space.	672 of 673
Route object: none	138.186.169.0/24	No route object for it. A route object for 138.186.168.0/22 with origin AS264484 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264484 in the RIR database for the space.	672 of 673
Route object: none	138.186.170.0/24	No route object for it. A route object for 138.186.168.0/22 with origin AS264484 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264484 in the RIR database for the space.	672 of 673
Route object: none	138.186.171.0/24	No route object for it. A route object for 138.186.168.0/22 with origin AS264484 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264484 in the RIR database for the space.	672 of 673
Route object: RIR	131.255.108.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	138.186.168.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	2804:204c::/32	Route object only in 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

131.255.108.0/24

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

672 of 673

Route object: none

131.255.109.0/24

672 of 673

Route object: none

131.255.110.0/24

672 of 673

Route object: none

131.255.111.0/24

672 of 673

Route object: none

138.186.168.0/24

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

672 of 673

Route object: none

138.186.169.0/24

672 of 673

Route object: none

138.186.170.0/24

672 of 673

Route object: none

138.186.171.0/24

672 of 673

Route object: RIR

131.255.108.0/22

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

672 of 673

Route object: RIR

138.186.168.0/22

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

672 of 673

Route object: RIR

2804:204c::/32

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

635 of 636

Route objects not announced

Every route object with origin AS264484 is announced.

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.