bgpreport

Network · data from 2026-11-12

AS23780 CTB Media Inc.

Registry name: CTB - CTB Media Inc., JP · PeeringDB

6IPv4 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 AS23780, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS23780, 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.
49.128.24.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
211.15.112.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
211.19.224.0/19 Valid Other IRR onlyJPIRR, RADB 672 100% 67
49.128.96.0/22 Valid Other IRR onlyJPIRR, RADB 670 100% 67
203.201.52.0/22 Valid Other IRR onlyJPIRR, RADB 670 100% 67
2402:6c80::/32 Valid Other IRR onlyJPIRR 636 100% 69
126.52.96.0/22 Valid Other IRR onlyJPIRR 214 32% 58

AS-SET

PeeringDB's irr_as_set for AS23780: AS-23780. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS23780 isn't in the set, or no route object for AS23780 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS23780 in itNot covered
AS-23780 JPIRR 117 Yes 0

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

  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
Route object: RIR49.128.24.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR211.15.112.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR211.19.224.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR49.128.96.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR203.201.52.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2402:6c80::/32Route object only in JPIRR. Add it in the RIR database for the space.636 of 636
Route object: RIR126.52.96.0/22Route object only in JPIRR. Add it in the RIR database for the space.214 of 673

Route objects not announced

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