bgpreport

Network · data from 2026-11-12

AS18135 BTV Co.,Ltd.

Registry name: BTV - BTV CO.,LTD., JP · PeeringDB

10IPv4 routes 80.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
2No 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 AS18135, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS18135, 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.
163.131.104.0/22 No ROA Other IRR onlyJPIRR, RADB 669 99% 67
163.131.108.0/22 No ROA Other IRR onlyJPIRR, RADB 669 99% 67
42.83.0.0/18 Valid Other IRR onlyJPIRR 671 100% 67
153.124.224.0/21 Valid Other IRR onlyJPIRR 671 100% 67
182.23.216.0/21 Valid Other IRR onlyJPIRR 671 100% 67
203.211.32.0/20 Valid Other IRR onlyJPIRR 671 100% 67
203.211.48.0/21 Valid Other IRR onlyJPIRR 671 100% 67
219.103.0.0/19 Valid Other IRR onlyJPIRR 671 100% 67
103.205.48.0/22 Valid Other IRR onlyJPIRR 669 99% 67
219.100.88.0/22 Valid Other IRR onlyJPIRR 669 99% 67
2401:d500::/32 Valid Other IRR onlyJPIRR 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS18135: AS-BTVの. 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 (AS18135 isn't in the set, or no route object for AS18135 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 objectsAS18135 in itNot covered
AS-BTVの Not an AS-SET name.

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

  • ROA: none2
  • Route object: RIR11
ChangePrefix or setDetailFull-table peers
ROA: none163.131.104.0/22No ROA covers it. Add a ROA for AS18135, maxLength 22.669 of 673
Route object: RIR163.131.104.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.669 of 673
ROA: none163.131.108.0/22No ROA covers it. Add a ROA for AS18135, maxLength 22.669 of 673
Route object: RIR163.131.108.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR42.83.0.0/18Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR153.124.224.0/21Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR182.23.216.0/21Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR203.211.32.0/20Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR203.211.48.0/21Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR219.103.0.0/19Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR103.205.48.0/22Route object only in JPIRR. Add it in the RIR database for the space.669 of 673
Route object: RIR219.100.88.0/22Route object only in JPIRR. Add it in the RIR database for the space.669 of 673
Route object: RIR2401:d500::/32Route object only in JPIRR. Add it in the RIR database for the space.636 of 636

Route objects not announced

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