bgpreport

Network · data from 2026-11-12

AS140457 Ikhlas Cipta Teknologi

Registry name: IMEDIANET-AS-ID - PT Ikhlas Cipta Teknologi, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS140457, 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.183.146.0/23 Valid Nonecovered by 38.183.144.0/22 673 100% 70
38.183.144.0/23 Valid Other IRR onlyRADB 673 100% 70
38.183.144.0/24 Valid Other IRR onlyRADB 673 100% 70
38.183.145.0/24 Valid Other IRR onlyRADB 673 100% 70
103.153.62.0/23 Valid Other IRR onlyRADB 673 100% 70
103.153.62.0/24 Valid Other IRR onlyRADB 673 100% 70
103.153.63.0/24 Valid Other IRR onlyRADB 673 100% 69
45.198.20.0/23 Valid Other IRR onlyRADB 672 100% 70
45.198.21.0/24 Valid Other IRR onlyRADB 672 100% 70
45.198.22.0/23 Valid Other IRR onlyRADB 672 100% 70
45.198.22.0/24 Valid Other IRR onlyRADB 672 100% 69
45.198.23.0/24 Valid Other IRR onlyRADB 672 100% 70
38.183.146.0/24 Valid Other IRR onlyRADB 670 100% 69
45.198.20.0/24 Valid Other IRR onlyRADB 669 99% 70
2406:3fc0::/32 Valid Other IRR onlyRADB 635 100% 70
38.183.147.0/24 Valid Other IRR onlyRADB 37 5%low visibility 30
156.230.21.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 70

AS-SET

PeeringDB's irr_as_set for AS140457: AS-IMEDIANET. 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 (AS140457 isn't in the set, or no route object for AS140457 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 objectsAS140457 in itNot covered
AS-IMEDIANET RADB 7141 Yes 0

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

  • Route object: none1
  • Route object: RIR15
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none38.183.146.0/23No route object for it. A route object for 38.183.144.0/22 with origin AS140457 covers it (filters allowing more-specifics accept it). Add a route object with origin AS140457 in the RIR database for the space.673 of 673
Route object: RIR38.183.144.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR38.183.144.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR38.183.145.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.153.62.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.153.62.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.153.63.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR45.198.20.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.198.21.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.198.22.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.198.22.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.198.23.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.183.146.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR45.198.20.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2406:3fc0::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR38.183.147.0/24Route object only in RADB. Add it in the RIR database for the space.37 of 673

Route objects not announced

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

38.183.144.0/22ARIN, RADBValid
45.198.20.0/22RADBValid
103.13.136.0/24RADBValid
103.189.122.0/23RADBNo ROA
103.189.123.0/24RADBValid

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.