bgpreport

Network · data from 2026-11-12

AS10209 Synopsys-AS-JP-AP - Japan HUB and Data Center

Registry name: Synopsys-AS-JP-AP - Japan HUB and Data Center, JP · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10209, 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.
198.182.50.0/23 No ROA Nonecovered by 198.182.48.0/22 672 100% 67
198.182.50.0/24 No ROA Nonecovered by 198.182.48.0/22 672 100% 67
198.182.51.0/24 No ROA Nonecovered by 198.182.48.0/22 672 100% 67
149.117.1.0/24 No ROA Other origin only 50 7%low visibility 18

AS-SET

AS10209 isn't in PeeringDB, where networks name their AS-SET.

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

  • ROA: none4
  • Route object: none4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none198.182.50.0/23No ROA covers it. Add a ROA for AS10209, maxLength 23.672 of 673
Route object: none198.182.50.0/23No route object for it. A route object for 198.182.48.0/22 with origin AS10209 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10209 in the RIR database for the space.672 of 673
ROA: none198.182.50.0/24No ROA covers it. Add a ROA for AS10209, maxLength 24.672 of 673
Route object: none198.182.50.0/24No route object for it. A route object for 198.182.48.0/22 with origin AS10209 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10209 in the RIR database for the space.672 of 673
ROA: none198.182.51.0/24No ROA covers it. Add a ROA for AS10209, maxLength 24.672 of 673
Route object: none198.182.51.0/24No route object for it. A route object for 198.182.48.0/22 with origin AS10209 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10209 in the RIR database for the space.672 of 673
ROA: none149.117.1.0/24No ROA covers it. Add a ROA for AS10209, maxLength 24.50 of 673
Route object: none149.117.1.0/24Route objects for it name AS7809, AS24539. Add a route object with origin AS10209 in the RIR database for the space.50 of 673

Route objects not announced

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

198.182.48.0/22RADBNo 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.