Network · data from 2026-11-12

AS9609 BBIX CDN

Registry name: BBIX-CDN - BBIX, Inc., JP · PeeringDB

1IPv4 routes 100.0% RPKI valid · 100.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 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 AS9609, seen from no peer

Announced routes

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


61.245.110.0/24	Valid	Other IRR onlyJPIRR	668 99%	67
2403:c780:a991::/48	Valid	Other IRR onlyJPIRR	614 97%	66

AS-SET

AS9609'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 2 are in fix.csv.

Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	61.245.110.0/24	Route object only in JPIRR. Add it in the RIR database for the space.	668 of 673
Route object: RIR	2403:c780:a991::/48	Route object only in JPIRR. Add it in the RIR database for the space.	614 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

61.245.110.0/24

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

668 of 673

Route object: RIR

2403:c780:a991::/48

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

614 of 636

Route objects not announced

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