bgpreport

Network · data from 2026-11-12

AS139076 EnjoyVC Japan

Registry name: ENJOYVC-AS-AP - EnjoyVC Japan Corporation, JP · PeeringDB

21IPv4 routes 42.9% RPKI valid · 42.9% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
12No ROA 12 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS139076, seen from no peer

Announced routes

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

103.221.49.0/24 Invalid: origin Other origin only 5 1%low visibility 4
111.235.76.0/22 No ROA Other origin only 661 98% 66
111.235.76.0/24 No ROA None 661 98% 66
103.57.48.0/22 No ROA Other origin only 643 96% 66
103.246.156.0/24 No ROA Other origin only 621 92% 65
103.246.157.0/24 No ROA Other origin only 621 92% 65
103.246.158.0/24 No ROA Other origin only 621 92% 65
103.246.159.0/24 No ROA Other origin only 621 92% 65
202.66.168.0/24 No ROA Other origin only 621 92% 65
103.57.48.0/24 No ROA None 107 16% 44
133.88.76.0/24 No ROA Other origin only 107 16% 44
161.248.113.0/24 No ROA Other IRR onlyRADB 670 100% 67
2001:df0:7480::/48 No ROA Other IRR onlyRADB 635 100% 67
45.204.57.0/24 Valid None 668 99% 67
103.221.48.0/24 Valid Other IRR onlyRADB 668 99% 67
116.204.234.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
116.204.235.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.139.110.0/24 Valid RIR databaseAPNIC 671 100% 67
64.204.68.0/24 Valid RIR databaseARIN, RADB 670 100% 67
103.139.111.0/24 Valid RIR databaseAPNIC 670 100% 67
103.146.78.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
103.244.208.0/24 Valid RIR databaseAPNIC 670 100% 67

AS-SET

PeeringDB's irr_as_set for AS139076: AS-139076. 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 (AS139076 isn't in the set, or no route object for AS139076 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 objectsAS139076 in itNot covered
AS-139076 RADB1 member set in no database: AS-AGOTOZ 2014,819 Yes 12
APNIC (also)5 member sets in no database: AS-135377, AS-AGOTOZ, AS-ARESFLARE-TRANSIT, AS-IQ-TW, AS140591:AS-TESUCH 126897,502 Yes 12

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

  • ROA: origin1
  • ROA: none12
  • Route object: none12
  • Route object: RIR3
  • AS-SET: missing member1
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: origin103.221.49.0/24ROAs covering it name AS25743, AS139259, not AS139076. If AS139076 should announce it, add a ROA for AS139076.5 of 673
Route object: none103.221.49.0/24Route objects for it name AS139259. Add a route object with origin AS139076 in the RIR database for the space.5 of 673
ROA: none111.235.76.0/22No ROA covers it. Add a ROA for AS139076, maxLength 22.661 of 673
Route object: none111.235.76.0/22Route objects for it name AS131950. Add a route object with origin AS139076 in the RIR database for the space.661 of 673
ROA: none111.235.76.0/24No ROA covers it. Add a ROA for AS139076, maxLength 24.661 of 673
Route object: none111.235.76.0/24No route object for it. Add a route object with origin AS139076 in the RIR database for the space.661 of 673
ROA: none103.57.48.0/22No ROA covers it. Add a ROA for AS139076, maxLength 22.643 of 673
Route object: none103.57.48.0/22Route objects for it name AS131950. Add a route object with origin AS139076 in the RIR database for the space.643 of 673
ROA: none103.246.156.0/24No ROA covers it. Add a ROA for AS139076, maxLength 24.621 of 673
Route object: none103.246.156.0/24Route objects for it name AS58879, AS137443, AS137969. Add a route object with origin AS139076 in the RIR database for the space.621 of 673
ROA: none103.246.157.0/24No ROA covers it. Add a ROA for AS139076, maxLength 24.621 of 673
Route object: none103.246.157.0/24Route objects for it name AS58879, AS137443, AS137969. Add a route object with origin AS139076 in the RIR database for the space.621 of 673
ROA: none103.246.158.0/24No ROA covers it. Add a ROA for AS139076, maxLength 24.621 of 673
Route object: none103.246.158.0/24Route objects for it name AS58879, AS137443, AS137969. Add a route object with origin AS139076 in the RIR database for the space.621 of 673
ROA: none103.246.159.0/24No ROA covers it. Add a ROA for AS139076, maxLength 24.621 of 673
Route object: none103.246.159.0/24Route objects for it name AS58879, AS137443, AS137969. Add a route object with origin AS139076 in the RIR database for the space.621 of 673
ROA: none202.66.168.0/24No ROA covers it. Add a ROA for AS139076, maxLength 24.621 of 673
Route object: none202.66.168.0/24Route objects for it name AS58879, AS137443. Add a route object with origin AS139076 in the RIR database for the space.621 of 673
ROA: none103.57.48.0/24No ROA covers it. Add a ROA for AS139076, maxLength 24.107 of 673
Route object: none103.57.48.0/24No route object for it. Add a route object with origin AS139076 in the RIR database for the space.107 of 673
ROA: none133.88.76.0/24No ROA covers it. Add a ROA for AS139076, maxLength 24.107 of 673
Route object: none133.88.76.0/24Route objects for it name AS131950. Add a route object with origin AS139076 in the RIR database for the space.107 of 673
ROA: none161.248.113.0/24No ROA covers it. Add a ROA for AS139076, maxLength 24.670 of 673
Route object: RIR161.248.113.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2001:df0:7480::/48No ROA covers it. Add a ROA for AS139076, maxLength 48.635 of 636
Route object: RIR2001:df0:7480::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: none45.204.57.0/24No route object for it. Add a route object with origin AS139076 in the RIR database for the space.668 of 673
Route object: RIR103.221.48.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
AS-SET: missing memberAS-139076AS-139076 (RADB) lists AS-AGOTOZ; no IRR database read has it.

Route objects not announced

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

43.246.199.0/24APNIC, RADBValid
112.75.0.0/18RADBNo ROA
112.75.192.0/22RADBNo ROA
113.31.64.0/21RADBNo ROA
113.31.72.0/21RADBNo ROA
113.31.128.0/21RADBNo ROA
113.31.136.0/21RADBNo ROA
118.184.88.0/24RADBNo ROA
118.184.89.0/24RADBNo ROA

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.