bgpreport

Network · data from 2026-11-12

AS18260 EHIME CATV CO.,LTD.

Registry name: e-catv - EHIME CATV CO.,LTD., JP · PeeringDB

27IPv4 routes 81.5% RPKI valid · 85.2% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
4RPKI invalid 4 origin · 0 maxLength
1No ROA 4 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS18260, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS18260, 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.

192.218.200.0/24 Invalid: origin None 2 0%low visibility 2
192.218.201.0/24 Invalid: origin None 2 0%low visibility 2
192.218.202.0/24 Invalid: origin None 2 0%low visibility 2
192.218.203.0/24 Invalid: origin None 2 0%low visibility 2
103.194.72.0/22 No ROA Other IRR onlyNTTCOM 672 100% 67
24.53.192.0/19 Valid Other IRR onlyNTTCOM 672 100% 67
27.106.208.0/21 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
27.106.224.0/19 Valid Other IRR onlyNTTCOM 672 100% 67
101.2.128.0/19 Valid Other IRR onlyNTTCOM 672 100% 67
101.55.232.0/21 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
103.2.64.0/22 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
119.30.8.0/22 Valid Other IRR onlyNTTCOM 672 100% 67
119.30.12.0/23 Valid Other IRR onlyNTTCOM 672 100% 67
202.165.48.0/21 Valid Other IRR onlyNTTCOM 672 100% 67
219.100.172.0/22 Valid Other IRR onlyNTTCOM 672 100% 67
219.109.48.0/24 Valid Other IRR onlyNTTCOM 672 100% 67
219.109.50.0/23 Valid Other IRR onlyNTTCOM 672 100% 67
219.109.56.0/21 Valid Other IRR onlyNTTCOM 672 100% 67
220.156.192.0/18 Valid Other IRR onlyNTTCOM 672 100% 67
101.1.64.0/18 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
210.87.224.0/20 Valid Other IRR onlyNTTCOM 671 100% 67
210.141.208.0/22 Valid Other IRR onlyNTTCOM 671 100% 67
210.141.214.0/23 Valid Other IRR onlyNTTCOM 671 100% 67
210.141.216.0/23 Valid Other IRR onlyNTTCOM 671 100% 67
210.141.220.0/22 Valid Other IRR onlyNTTCOM 671 100% 67
219.109.49.0/24 Valid Other IRR onlyNTTCOM 670 100% 67
210.141.219.0/24 Valid Other IRR onlyNTTCOM 669 99% 67
2400:df00::/32 Valid Other IRR onlyNTTCOM 634 100% 70

AS-SET

PeeringDB's irr_as_set for AS18260: NTTCOM::AS18260:AS-EHIME-CATV. 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 (AS18260 isn't in the set, or no route object for AS18260 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 objectsAS18260 in itNot covered
NTTCOM::AS18260:AS-EHIME-CATV In no IRR database read today.

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

  • ROA: origin4
  • ROA: none1
  • Route object: none4
  • Route object: RIR24
  • AS-SET: not found1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: origin192.218.200.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS18260 should announce it, add a ROA for AS18260.2 of 673
Route object: none192.218.200.0/24No route object for it. Add a route object with origin AS18260 in the RIR database for the space.2 of 673
ROA: origin192.218.201.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS18260 should announce it, add a ROA for AS18260.2 of 673
Route object: none192.218.201.0/24No route object for it. Add a route object with origin AS18260 in the RIR database for the space.2 of 673
ROA: origin192.218.202.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS18260 should announce it, add a ROA for AS18260.2 of 673
Route object: none192.218.202.0/24No route object for it. Add a route object with origin AS18260 in the RIR database for the space.2 of 673
ROA: origin192.218.203.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS18260 should announce it, add a ROA for AS18260.2 of 673
Route object: none192.218.203.0/24No route object for it. Add a route object with origin AS18260 in the RIR database for the space.2 of 673
ROA: none103.194.72.0/22No ROA covers it. Add a ROA for AS18260, maxLength 22.672 of 673
Route object: RIR103.194.72.0/22Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR24.53.192.0/19Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR27.106.208.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR27.106.224.0/19Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR101.2.128.0/19Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR101.55.232.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.2.64.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR119.30.8.0/22Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR119.30.12.0/23Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR202.165.48.0/21Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR219.100.172.0/22Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR219.109.48.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR219.109.50.0/23Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR219.109.56.0/21Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR220.156.192.0/18Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR101.1.64.0/18Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.87.224.0/20Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR210.141.208.0/22Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR210.141.214.0/23Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR210.141.216.0/23Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR210.141.220.0/22Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR219.109.49.0/24Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673
Route object: RIR210.141.219.0/24Route object only in NTTCOM. Add it in the RIR database for the space.669 of 673
Route object: RIR2400:df00::/32Route object only in NTTCOM. Add it in the RIR database for the space.634 of 636
AS-SET: not foundNTTCOM::AS18260:AS-EHIME-CATVPeeringDB names NTTCOM::AS18260:AS-EHIME-CATV; no IRR database read has it.

Route objects not announced

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

119.30.8.0/21NTTCOMNo ROA
210.141.208.0/20NTTCOMNo ROA
210.141.216.0/21NTTCOMValid
210.141.218.0/24NTTCOMValid
219.109.48.0/20NTTCOMValid
219.109.52.0/22NTTCOMValid

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.