Network · data from 2026-11-12
AS7530 Cloud and SDN Laboratory
Registry name: BBTower-Lab - BroadBand Tower, Inc., JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS7530, 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.
| 210.231.212.0/22 | Valid | Other IRR onlyRADB | 669 99% |
| 210.231.220.0/22 | Valid | Other IRR onlyRADB | 669 99% |
| 2405:f000::/32 | Valid | Other IRR onlyRADB | 634 100% |
| 210.231.222.0/23 | Valid | Other IRR onlyRADB | 188 28% |
AS-SET
PeeringDB's irr_as_set for AS7530: AS-IRI. 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 (AS7530 isn't in the set, or no route object for AS7530 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.
| Name | Database | ASNs | Sets | AS7530 in it | Not covered |
|---|---|---|---|---|---|
| AS-IRI | RADB | 2 | 1 | Yes | 0 |
| RIPE (also) | 0 | 1 | No | 4 |
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: RIR4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 210.231.212.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.231.220.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2405:f000::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.231.222.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS7530 whose prefix no peer sees AS7530 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 210.231.208.0/20 | RADB | Valid |
| 210.231.208.0/21 | RADB | Valid |
| 210.231.216.0/21 | RADB | Valid |
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.