bgpreport

Network · data from 2026-11-12

AS142307 CYB Media Group

Registry name: CYB-AS-ID - PT CYB Media Group, ID · PeeringDB

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

Announced routes

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

38.191.164.0/23 No ROA None 200 30% 53
38.226.45.0/24 No ROA None 75 11% 37
38.226.47.0/24 No ROA None 67 10%low visibility 36
38.226.46.0/24 No ROA None 66 10%low visibility 36
38.188.207.0/24 No ROA None 64 10%low visibility 35
38.46.232.0/24 No ROA Other IRR onlyRADB 484 72% 67
38.46.234.0/24 No ROA Other IRR onlyRADB 484 72% 67
38.46.235.0/24 No ROA Other IRR onlyRADB 484 72% 67
38.191.164.0/24 No ROA Other IRR onlyRADB 484 72% 67
38.191.165.0/24 No ROA Other IRR onlyRADB 484 72% 67
38.46.233.0/24 No ROA Other IRR onlyRADB 483 72% 67
103.179.84.0/24 Valid None 672 100% 67
103.168.44.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69

AS-SET

PeeringDB's irr_as_set for AS142307: AS142307:AS-PEERS. 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 (AS142307 isn't in the set, or no route object for AS142307 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 objectsAS142307 in itNot covered
AS142307:AS-PEERS APNIC 219 Yes 6

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

  • ROA: none11
  • Route object: none6
  • Route object: RIR7
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none38.191.164.0/23No ROA covers it. Add a ROA for AS142307, maxLength 23.200 of 673
Route object: none38.191.164.0/23No route object for it. Add a route object with origin AS142307 in the RIR database for the space.200 of 673
ROA: none38.226.45.0/24No ROA covers it. Add a ROA for AS142307, maxLength 24.75 of 673
Route object: none38.226.45.0/24No route object for it. Add a route object with origin AS142307 in the RIR database for the space.75 of 673
ROA: none38.226.47.0/24No ROA covers it. Add a ROA for AS142307, maxLength 24.67 of 673
Route object: none38.226.47.0/24No route object for it. Add a route object with origin AS142307 in the RIR database for the space.67 of 673
ROA: none38.226.46.0/24No ROA covers it. Add a ROA for AS142307, maxLength 24.66 of 673
Route object: none38.226.46.0/24No route object for it. Add a route object with origin AS142307 in the RIR database for the space.66 of 673
ROA: none38.188.207.0/24No ROA covers it. Add a ROA for AS142307, maxLength 24.64 of 673
Route object: none38.188.207.0/24No route object for it. Add a route object with origin AS142307 in the RIR database for the space.64 of 673
ROA: none38.46.232.0/24No ROA covers it. Add a ROA for AS142307, maxLength 24.484 of 673
Route object: RIR38.46.232.0/24Route object only in RADB. Add it in the RIR database for the space.484 of 673
ROA: none38.46.234.0/24No ROA covers it. Add a ROA for AS142307, maxLength 24.484 of 673
Route object: RIR38.46.234.0/24Route object only in RADB. Add it in the RIR database for the space.484 of 673
ROA: none38.46.235.0/24No ROA covers it. Add a ROA for AS142307, maxLength 24.484 of 673
Route object: RIR38.46.235.0/24Route object only in RADB. Add it in the RIR database for the space.484 of 673
ROA: none38.191.164.0/24No ROA covers it. Add a ROA for AS142307, maxLength 24.484 of 673
Route object: RIR38.191.164.0/24Route object only in RADB. Add it in the RIR database for the space.484 of 673
ROA: none38.191.165.0/24No ROA covers it. Add a ROA for AS142307, maxLength 24.484 of 673
Route object: RIR38.191.165.0/24Route object only in RADB. Add it in the RIR database for the space.484 of 673
ROA: none38.46.233.0/24No ROA covers it. Add a ROA for AS142307, maxLength 24.483 of 673
Route object: RIR38.46.233.0/24Route object only in RADB. Add it in the RIR database for the space.483 of 673
Route object: none103.179.84.0/24No route object for it. Add a route object with origin AS142307 in the RIR database for the space.672 of 673
Route object: RIR103.168.44.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

38.46.232.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.