bgpreport

Network · data from 2026-11-12

AS34567 NEXT-AS Next Limited

Registry name: NEXT-AS Next Limited, HK · not in PeeringDB

0IPv4 routes
68IPv6 routes 86.8% RPKI valid · 97.1% with a route object
0RPKI invalid 0 origin · 0 maxLength
9No ROA 2 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS34567, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS34567, 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.
2a11:d880::/29 No ROA None 1 0%low visibility 1
2a12:b400::/29 No ROA None 1 0%low visibility 2
2a07:f600:4058::/48 No ROA RIR databaseRIPE 636 100% 69
2a0f:500::/29 No ROA RIR databaseRIPE 634 100% 67
2a11:a240::/29 No ROA RIR databaseRIPE 631 99% 67
2a11:ea80::/29 No ROA RIR databaseRIPE 631 99% 67
2a12:1040::/29 No ROA RIR databaseRIPE 631 99% 67
2a12:2d80::/29 No ROA RIR databaseRIPE 631 99% 67
2a12:9300::/29 No ROA RIR databaseRIPE 631 99% 67
2a0d:8cc0::/29 Valid RIR databaseRIPE 633 100% 67
2a0e:af40::/29 Valid RIR databaseRIPE 633 100% 67
2a0e:e9c0::/29 Valid RIR databaseRIPE 633 100% 67
2a0f:e180::/29 Valid RIR databaseRIPE 633 100% 67
2a11:17c0::/29 Valid RIR databaseRIPE 631 99% 67
2a11:1c80::/29 Valid RIR databaseRIPE 631 99% 67
2a11:2d00::/29 Valid RIR databaseRIPE 631 99% 67
2a11:4540::/29 Valid RIR databaseRIPE 631 99% 67
2a11:4f00::/29 Valid RIR databaseRIPE 631 99% 67
2a11:64c0::/29 Valid RIR databaseRIPE 631 99% 67
2a11:6b80::/29 Valid RIR databaseRIPE 631 99% 67
2a11:81c0::/29 Valid RIR databaseRIPE 631 99% 67
2a11:86c0::/29 Valid RIR databaseRIPE 631 99% 67
2a11:8740::/29 Valid RIR databaseRIPE 631 99% 67
2a11:8980::/29 Valid RIR databaseRIPE 631 99% 67
2a11:9580::/29 Valid RIR databaseRIPE 631 99% 67
2a11:9f00::/29 Valid RIR databaseRIPE 631 99% 67
2a11:a040::/29 Valid RIR databaseRIPE 631 99% 67
2a11:a140::/29 Valid RIR databaseRIPE 631 99% 67
2a11:b0c0::/29 Valid RIR databaseRIPE 631 99% 67
2a11:b700::/29 Valid RIR databaseRIPE 631 99% 67
2a11:bb00::/29 Valid RIR databaseRIPE 631 99% 67
2a11:bbc0::/29 Valid RIR databaseRIPE 631 99% 67
2a11:be40::/29 Valid RIR databaseRIPE 631 99% 67
2a11:bf80::/29 Valid RIR databaseRIPE 631 99% 67
2a11:c240::/29 Valid RIR databaseRIPE 631 99% 67
2a11:c580::/29 Valid RIR databaseRIPE 631 99% 67
2a11:c680::/29 Valid RIR databaseRIPE 631 99% 67
2a11:cec0::/29 Valid RIR databaseRIPE 631 99% 67
2a11:d340::/29 Valid RIR databaseRIPE 631 99% 67
2a11:dac0::/29 Valid RIR databaseRIPE 631 99% 67
2a11:df00::/29 Valid RIR databaseRIPE 631 99% 67
2a11:e640::/29 Valid RIR databaseRIPE 631 99% 67
2a11:e6c0::/29 Valid RIR databaseRIPE 631 99% 67
2a11:e8c0::/29 Valid RIR databaseRIPE 631 99% 67
2a11:fa40::/29 Valid RIR databaseRIPE 631 99% 67
2a11:fc40::/29 Valid RIR databaseRIPE 631 99% 67
2a11:ff40::/29 Valid RIR databaseRIPE 631 99% 67
2a12:580::/29 Valid RIR databaseRIPE 631 99% 67
2a12:900::/29 Valid RIR databaseRIPE 631 99% 67
2a12:dc0::/29 Valid RIR databaseRIPE 631 99% 67
2a12:e40::/29 Valid RIR databaseRIPE 631 99% 67
2a12:11c0::/29 Valid RIR databaseRIPE 631 99% 67
2a12:12c0::/29 Valid RIR databaseRIPE 631 99% 67
2a12:1a80::/29 Valid RIR databaseRIPE 631 99% 67
2a12:2b80::/29 Valid RIR databaseRIPE 631 99% 67
2a12:2e80::/29 Valid RIR databaseRIPE 631 99% 67
2a12:3c00::/29 Valid RIR databaseRIPE 631 99% 67
2a12:8380::/29 Valid RIR databaseRIPE 631 99% 67
2a12:8480::/29 Valid RIR databaseRIPE 631 99% 67
2a12:8a00::/29 Valid RIR databaseRIPE 631 99% 67
2a12:9200::/29 Valid RIR databaseRIPE 631 99% 67
2a12:aa00::/29 Valid RIR databaseRIPE 631 99% 67
2a12:af00::/29 Valid RIR databaseRIPE 631 99% 67
2a12:b700::/29 Valid RIR databaseRIPE 631 99% 67
2a12:bb00::/29 Valid RIR databaseRIPE 631 99% 67
2a12:c980::/29 Valid RIR databaseRIPE 631 99% 67
2a12:d080::/29 Valid RIR databaseRIPE 631 99% 67
2a12:d200::/29 Valid RIR databaseRIPE 631 99% 67

AS-SET

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

  • ROA: none9
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none2a11:d880::/29No ROA covers it. Add a ROA for AS34567, maxLength 29.1 of 636
Route object: none2a11:d880::/29No route object for it. Add a route object with origin AS34567 in the RIR database for the space.1 of 636
ROA: none2a12:b400::/29No ROA covers it. Add a ROA for AS34567, maxLength 29.1 of 636
Route object: none2a12:b400::/29No route object for it. Add a route object with origin AS34567 in the RIR database for the space.1 of 636
ROA: none2a07:f600:4058::/48No ROA covers it. Add a ROA for AS34567, maxLength 48.636 of 636
ROA: none2a0f:500::/29No ROA covers it. Add a ROA for AS34567, maxLength 29.634 of 636
ROA: none2a11:a240::/29No ROA covers it. Add a ROA for AS34567, maxLength 29.631 of 636
ROA: none2a11:ea80::/29No ROA covers it. Add a ROA for AS34567, maxLength 29.631 of 636
ROA: none2a12:1040::/29No ROA covers it. Add a ROA for AS34567, maxLength 29.631 of 636
ROA: none2a12:2d80::/29No ROA covers it. Add a ROA for AS34567, maxLength 29.631 of 636
ROA: none2a12:9300::/29No ROA covers it. Add a ROA for AS34567, maxLength 29.631 of 636

Route objects not announced

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