bgpreport

Network · data from 2026-11-12

AS23808 TOSHIMA CABLE NETWORK

Registry name: TOSHIMA-NET - TOSHIMA CABLE NETWORK CO.,LTD, JP · PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
8Route objects not announced registered with origin AS23808, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS23808, 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.
202.140.192.0/19 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
220.152.96.0/20 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
103.40.128.0/22 Valid Other IRR onlyNTTCOM, RADB 669 99% 67
219.100.132.0/22 Valid Other IRR onlyNTTCOM, RADB 669 99% 67

AS-SET

PeeringDB's irr_as_set for AS23808: NTTCOM::AS23808:AS-TOSHIMA. 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 (AS23808 isn't in the set, or no route object for AS23808 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 objectsAS23808 in itNot covered
NTTCOM::AS23808:AS-TOSHIMA NTTCOM 1112 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 12 are in fix.csv.

  • Route object: RIR4
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: RIR202.140.192.0/19Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR220.152.96.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.40.128.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR219.100.132.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

Route objects with origin AS23808 whose prefix no peer sees AS23808 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.40.128.0/23NTTCOMValid
103.40.130.0/23NTTCOMValid
202.140.192.0/20NTTCOMValid
202.140.208.0/20NTTCOMValid
219.100.132.0/23NTTCOMValid
219.100.134.0/23NTTCOMValid
220.152.96.0/21NTTCOMValid
220.152.104.0/21NTTCOMValid

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.