bgpreport

Network · data from 2026-11-12

AS219153 ProjectX NETAXIS GROUP LTD

Registry name: ProjectX NETAXIS GROUP LTD, CY · not in PeeringDB

39IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
0Route objects not announced registered with origin AS219153, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS219153, 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.
13.143.204.0/23 Valid RIR databaseRIPE 673 100% 67
13.143.224.0/23 Valid RIR databaseRIPE 673 100% 67
13.143.228.0/23 Valid RIR databaseRIPE 673 100% 67
31.77.36.0/23 Valid RIR databaseRIPE 673 100% 67
78.17.218.0/23 Valid RIR databaseRIPE 673 100% 67
78.17.238.0/23 Valid RIR databaseRIPE 673 100% 67
78.17.248.0/23 Valid RIR databaseRIPE 673 100% 67
78.17.250.0/23 Valid RIR databaseRIPE 673 100% 67
89.125.190.0/23 Valid RIR databaseRIPE 673 100% 67
89.125.230.0/23 Valid RIR databaseRIPE 673 100% 67
104.143.196.0/23 Valid RIR databaseRIPE 673 100% 67
104.143.198.0/23 Valid RIR databaseRIPE 673 100% 67
104.143.220.0/23 Valid RIR databaseRIPE 673 100% 67
153.76.228.0/23 Valid RIR databaseRIPE 673 100% 67
153.76.252.0/23 Valid RIR databaseRIPE 673 100% 67
153.76.254.0/23 Valid RIR databaseRIPE 673 100% 67
162.35.232.0/23 Valid RIR databaseRIPE 673 100% 67
162.35.234.0/23 Valid RIR databaseRIPE 673 100% 67
162.35.236.0/23 Valid RIR databaseRIPE 673 100% 67
162.35.238.0/23 Valid RIR databaseRIPE 673 100% 67
162.35.240.0/23 Valid RIR databaseRIPE 673 100% 67
162.35.250.0/23 Valid RIR databaseRIPE 673 100% 67
162.35.254.0/23 Valid RIR databaseRIPE 673 100% 67
179.254.116.0/23 Valid RIR databaseRIPE 673 100% 67
179.254.118.0/23 Valid RIR databaseRIPE 673 100% 67
179.254.120.0/23 Valid RIR databaseRIPE 673 100% 67
179.254.122.0/23 Valid RIR databaseRIPE 673 100% 67
201.10.82.0/23 Valid RIR databaseRIPE 673 100% 67
201.10.88.0/23 Valid RIR databaseRIPE 673 100% 67
212.87.160.0/23 Valid RIR databaseRIPE 673 100% 67
212.87.162.0/23 Valid RIR databaseRIPE 673 100% 67
212.87.164.0/23 Valid RIR databaseRIPE 673 100% 67
212.87.166.0/23 Valid RIR databaseRIPE 673 100% 67
212.87.176.0/23 Valid RIR databaseRIPE 673 100% 67
212.87.180.0/23 Valid RIR databaseRIPE 673 100% 67
212.87.184.0/23 Valid RIR databaseRIPE 673 100% 67
13.143.212.0/23 Valid RIR databaseRIPE 671 100% 67
104.143.208.0/23 Valid RIR databaseRIPE 671 100% 68
104.143.210.0/23 Valid RIR databaseRIPE 671 100% 68

AS-SET

AS219153 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS219153 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.