bgpreport

Network · data from 2026-11-12

AS9607 BroadBand Tower

Registry name: BBTower - BroadBand Tower, Inc., JP · PeeringDB

20IPv4 routes 100.0% RPKI valid · 100.0% with a route object
5IPv6 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 AS9607, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS9607, 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.
124.147.16.0/21 Valid Other IRR onlyRADB 669 99% 67
202.183.80.0/21 Valid Other IRR onlyRADB 669 99% 67
203.141.56.0/21 Valid Other IRR onlyRADB 669 99% 67
203.216.192.0/19 Valid Other IRR onlyRADB 669 99% 67
208.111.48.0/21 Valid Other IRR onlyRADB 669 99% 67
211.14.0.0/21 Valid Other IRR onlyRADB 669 99% 67
103.96.112.0/22 Valid Other IRR onlyRADB 667 99% 67
124.147.24.0/22 Valid Other IRR onlyRADB 667 99% 67
124.147.28.0/22 Valid Other IRR onlyRADB 667 99% 67
203.141.48.0/22 Valid Other IRR onlyRADB 667 99% 67
203.141.52.0/23 Valid Other IRR onlyRADB 667 99% 67
203.141.55.0/24 Valid Other IRR onlyRADB 667 99% 67
211.14.9.0/24 Valid Other IRR onlyRADB 667 99% 67
211.14.10.0/23 Valid Other IRR onlyRADB 667 99% 67
211.14.16.0/22 Valid Other IRR onlyRADB 667 99% 67
211.14.24.0/23 Valid Other IRR onlyRADB 667 99% 67
211.14.30.0/23 Valid Other IRR onlyRADB 667 99% 67
124.147.0.0/20 Valid Other IRR onlyRADB 666 99% 67
210.231.208.0/22 Valid Other IRR onlyRADB 666 99% 67
218.231.252.0/23 Valid Other IRR onlyRADB 666 99% 67
2001:370::/32 Valid Other IRR onlyRADB 635 100% 69
2001:370::/40 Valid Other IRR onlyRADB 635 100% 69
2001:370:a::/48 Valid Other IRR onlyRADB 635 100% 69
2001:370:6000::/38 Valid Other IRR onlyRADB 635 100% 69
2404:c700::/32 Valid Other IRR onlyRADB 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS9607: AS-GCTR-JP. 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 (AS9607 isn't in the set, or no route object for AS9607 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 objectsAS9607 in itNot covered
AS-GCTR-JP RADB 6411,116 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 25 are in fix.csv.

  • Route object: RIR25
ChangePrefix or setDetailFull-table peers
Route object: RIR124.147.16.0/21Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR202.183.80.0/21Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR203.141.56.0/21Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR203.216.192.0/19Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR208.111.48.0/21Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR211.14.0.0/21Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR103.96.112.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR124.147.24.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR124.147.28.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR203.141.48.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR203.141.52.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR203.141.55.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR211.14.9.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR211.14.10.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR211.14.16.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR211.14.24.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR211.14.30.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR124.147.0.0/20Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR210.231.208.0/22Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR218.231.252.0/23Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR2001:370::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2001:370::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2001:370:a::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2001:370:6000::/38Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2404:c700::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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