Network · data from 2026-11-12

AS133153 IPv4Superhub IPv4 Superhub Limited

Registry name: IPv4Superhub IPv4 Superhub Limited, HK · not in PeeringDB

6IPv4 routes 66.7% RPKI valid · 66.7% with a route object

0IPv6 routes

1RPKI invalid 1 origin · 0 maxLength

1No ROA 2 with no route object for this origin

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

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

Announced routes

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


82.22.39.0/24	Invalid: origin	Other origin only	20 3%low visibility	16
82.39.212.0/22	No ROA	None	673 100%	67
82.39.99.0/24	Valid	Other IRR onlyRADB	673 100%	66
213.220.62.0/24	Valid	Other IRR onlyRADB	673 100%	66
193.254.244.0/24	Valid	RIR databaseRIPE	673 100%	67
193.254.245.0/24	Valid	RIR databaseRIPE	673 100%	67

82.22.39.0/24

Invalid: origin

Other origin only

20 3%low visibility

82.39.212.0/22

No ROA

None

673 100%

82.39.99.0/24

Valid

Other IRR onlyRADB

673 100%

213.220.62.0/24

Valid

Other IRR onlyRADB

673 100%

193.254.244.0/24

Valid

RIR databaseRIPE

673 100%

193.254.245.0/24

Valid

RIR databaseRIPE

673 100%

AS-SET

AS133153 isn't in PeeringDB, where networks name their 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.

ROA: origin1
ROA: none1
Route object: none2
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
ROA: origin	82.22.39.0/24	ROAs covering it name AS398547, not AS133153. If AS133153 should announce it, add a ROA for AS133153.	20 of 673
Route object: none	82.22.39.0/24	Route objects for it name AS398547. Add a route object with origin AS133153 in the RIR database for the space.	20 of 673
ROA: none	82.39.212.0/22	No ROA covers it. Add a ROA for AS133153, maxLength 22.	673 of 673
Route object: none	82.39.212.0/22	No route object for it. Add a route object with origin AS133153 in the RIR database for the space.	673 of 673
Route object: RIR	82.39.99.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	213.220.62.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

82.22.39.0/24

ROAs covering it name AS398547, not AS133153. If AS133153 should announce it, add a ROA for AS133153.

20 of 673

Route object: none

82.22.39.0/24

Route objects for it name AS398547. Add a route object with origin AS133153 in the RIR database for the space.

20 of 673

ROA: none

82.39.212.0/22

No ROA covers it. Add a ROA for AS133153, maxLength 22.

673 of 673

Route object: none

82.39.212.0/22

No route object for it. Add a route object with origin AS133153 in the RIR database for the space.

673 of 673

Route object: RIR

82.39.99.0/24

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

673 of 673

Route object: RIR

213.220.62.0/24

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

673 of 673

Route objects not announced

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