bgpreport

Network · data from 2026-11-12

AS24201 Andalas Media Informatika

Registry name: ANDALASMEDIA-AS-ID - PT. Andalas Media Informatika, ID · PeeringDB

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

Announced routes

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

202.87.248.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 67
202.87.249.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
202.87.250.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
202.87.251.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 67
202.87.252.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 67
202.87.253.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 67
202.87.254.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
202.87.255.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 67

AS-SET

PeeringDB's irr_as_set for AS24201: AS24201. 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 (AS24201 isn't in the set, or no route object for AS24201 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 objectsAS24201 in itNot covered
AS24201 A single AS number, not a set: AS24201 (this network), 268 route objects.

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

  • Route object: RIR8
  • Route object: not announced260
ChangePrefix or setDetailFull-table peers
Route object: RIR202.87.248.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR202.87.249.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.87.250.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.87.251.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR202.87.252.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR202.87.253.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR202.87.254.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.87.255.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

103.31.32.0/19NTTCOMNo ROA
103.31.32.0/20NTTCOMNo ROA
103.31.32.0/21NTTCOMNo ROA
103.31.32.0/22NTTCOMNo ROA
103.31.36.0/22NTTCOMNo ROA
103.31.36.0/23NTTCOMNo ROA
103.31.36.0/24NTTCOMNo ROA
103.31.37.0/24NTTCOMNo ROA
103.31.40.0/21NTTCOMNo ROA
103.31.40.0/22NTTCOMNo ROA
103.31.44.0/22NTTCOMNo ROA
103.31.46.0/23NTTCOMNo ROA
103.31.48.0/20NTTCOMNo ROA
103.31.48.0/21NTTCOMNo ROA
103.31.48.0/22NTTCOMNo ROA
103.31.48.0/23NTTCOMNo ROA
103.31.48.0/24NTTCOMNo ROA
103.31.49.0/24NTTCOMNo ROA
103.31.50.0/23NTTCOMNo ROA
103.31.50.0/24NTTCOMNo ROA
103.31.51.0/24NTTCOMNo ROA
103.31.56.0/21NTTCOMNo ROA
103.31.56.0/22NTTCOMNo ROA
103.31.56.0/23NTTCOMNo ROA
103.31.56.0/24NTTCOMNo ROA
103.31.57.0/24NTTCOMNo ROA
103.31.58.0/23NTTCOMNo ROA
103.31.58.0/24NTTCOMNo ROA
103.31.59.0/24NTTCOMNo ROA
103.31.60.0/22NTTCOMNo ROA
103.31.60.0/23NTTCOMNo ROA
103.31.60.0/24NTTCOMNo ROA
103.31.61.0/24NTTCOMNo ROA
103.31.62.0/23NTTCOMNo ROA
103.31.62.0/24NTTCOMNo ROA
103.31.63.0/24NTTCOMNo ROA
103.86.140.0/24REACHInvalid: origin
103.253.86.0/23NTTCOMNo ROA
103.253.86.0/24NTTCOM, RADBNo ROA
103.253.87.0/24NTTCOM, RADBNo ROA
117.103.8.0/21NTTCOM, RADBNo ROA
117.103.8.0/22NTTCOM, RADBNo ROA
117.103.8.0/23NTTCOM, RADBNo ROA
117.103.10.0/23NTTCOM, RADBNo ROA
117.103.12.0/22NTTCOM, RADBNo ROA
117.103.12.0/23NTTCOM, RADBNo ROA
117.103.14.0/23NTTCOM, RADBNo ROA
119.2.64.0/19REACHInvalid: origin
119.2.64.0/23REACHInvalid: origin
119.2.65.0/24REACHInvalid: origin
119.2.66.0/23REACHInvalid: origin
119.2.66.0/24REACHInvalid: origin
119.2.67.0/24REACHInvalid: origin
119.2.68.0/23REACHInvalid: origin
119.2.70.0/23REACHInvalid: origin
119.2.71.0/24REACHInvalid: origin
119.2.72.0/23REACHInvalid: origin
119.2.73.0/24REACHInvalid: origin
119.2.76.0/23REACHInvalid: origin
119.2.78.0/23REACHInvalid: origin
119.2.78.0/24REACHInvalid: origin
119.2.80.0/23REACHInvalid: origin
119.2.80.0/24REACHInvalid: origin
119.2.81.0/24REACHInvalid: origin
119.2.82.0/23REACHInvalid: origin
119.2.82.0/24REACHInvalid: origin
119.2.83.0/24REACHInvalid: origin
119.2.84.0/23REACHInvalid: origin
119.2.84.0/24REACHInvalid: origin
119.2.86.0/23REACHInvalid: origin
119.2.88.0/23REACHInvalid: origin
119.2.88.0/24REACHInvalid: origin
119.2.89.0/24REACHInvalid: origin
119.2.90.0/23REACHInvalid: origin
119.2.90.0/24REACHInvalid: origin
119.2.91.0/24REACHInvalid: origin
119.2.92.0/23REACHInvalid: origin
119.2.92.0/24REACHInvalid: origin
119.2.93.0/24REACHInvalid: origin
119.2.94.0/23REACHInvalid: origin
119.2.94.0/24REACHInvalid: origin
202.67.32.0/20NTTCOM, RADBNo ROA
202.67.32.0/21NTTCOM, RADBNo ROA
202.67.32.0/22NTTCOM, RADBNo ROA
202.67.32.0/23NTTCOM, RADBNo ROA
202.67.34.0/23NTTCOM, RADBNo ROA
202.67.36.0/22NTTCOM, RADBNo ROA
202.67.36.0/23NTTCOM, RADBNo ROA
202.67.38.0/23NTTCOM, RADBNo ROA
202.67.40.0/21NTTCOM, RADBNo ROA
202.67.40.0/22NTTCOM, RADBNo ROA
202.67.40.0/23NTTCOM, RADBNo ROA
202.67.42.0/23NTTCOMNo ROA
202.67.44.0/22NTTCOM, RADBNo ROA
202.67.44.0/23NTTCOM, RADBNo ROA
202.67.46.0/23NTTCOM, RADBNo ROA
202.87.248.0/21NTTCOM, RADB, REACHValid
202.87.248.0/22NTTCOM, RADBValid
202.87.248.0/23NTTCOM, RADB, REACHValid
202.87.250.0/23NTTCOM, RADB, REACHValid
202.87.252.0/22NTTCOM, RADBValid
202.87.252.0/23NTTCOM, RADB, REACHValid
202.87.254.0/23NTTCOM, RADB, REACHValid
202.93.224.0/20NTTCOM, RADBNo ROA
202.93.232.0/21NTTCOM, RADBNo ROA
202.93.232.0/22NTTCOM, RADBNo ROA
202.93.232.0/23NTTCOM, RADBNo ROA
202.93.232.0/24NTTCOM, RADBNo ROA
202.93.233.0/24NTTCOM, RADBNo ROA
202.93.234.0/23NTTCOM, RADBNo ROA
202.93.234.0/24NTTCOM, RADBNo ROA
202.93.235.0/24NTTCOM, RADBNo ROA
202.93.236.0/22NTTCOM, RADBNo ROA
202.93.236.0/23NTTCOM, RADBNo ROA
202.93.236.0/24NTTCOM, RADBNo ROA
202.93.237.0/24NTTCOM, RADBNo ROA
202.93.238.0/23NTTCOM, RADBNo ROA
202.93.238.0/24NTTCOM, RADBNo ROA
202.93.239.0/24NTTCOM, RADBNo ROA
202.93.240.0/21NTTCOM, RADBNo ROA
202.93.240.0/22NTTCOM, RADBNo ROA
202.93.242.0/23NTTCOM, RADBNo ROA
202.123.224.0/20NTTCOM, RADBNo ROA
202.123.224.0/21NTTCOM, RADBNo ROA
202.123.224.0/22NTTCOM, RADBNo ROA
202.123.224.0/23NTTCOM, RADBNo ROA
202.123.224.0/24NTTCOM, RADBNo ROA
202.123.225.0/24NTTCOM, RADBNo ROA
202.123.226.0/23NTTCOM, RADBNo ROA
202.123.226.0/24NTTCOM, RADBNo ROA
202.123.227.0/24NTTCOM, RADBNo ROA
202.123.228.0/22NTTCOM, RADBNo ROA
202.123.228.0/23NTTCOM, RADBNo ROA
202.123.228.0/24NTTCOM, RADBNo ROA
202.123.229.0/24NTTCOM, RADBNo ROA
202.123.230.0/23NTTCOM, RADBNo ROA
202.123.230.0/24NTTCOM, RADBNo ROA
202.123.231.0/24NTTCOM, RADBNo ROA
202.123.232.0/21NTTCOM, RADBNo ROA
202.123.232.0/22NTTCOM, RADBNo ROA
202.123.232.0/23NTTCOM, RADBNo ROA
202.123.232.0/24NTTCOM, RADBNo ROA
202.123.233.0/24NTTCOM, RADBNo ROA
202.123.234.0/23NTTCOM, RADBNo ROA
202.123.234.0/24NTTCOM, RADBNo ROA
202.123.235.0/24NTTCOM, RADBNo ROA
202.123.236.0/22NTTCOM, RADBNo ROA
202.123.236.0/23NTTCOM, RADBNo ROA
202.123.236.0/24NTTCOM, RADBNo ROA
202.123.237.0/24NTTCOM, RADBNo ROA
202.123.238.0/23NTTCOM, RADBNo ROA
202.123.238.0/24NTTCOM, RADBNo ROA
202.123.239.0/24NTTCOM, RADBNo ROA
202.148.0.0/19NTTCOM, RADBNo ROA
202.148.0.0/20NTTCOM, RADBNo ROA
202.148.0.0/21NTTCOM, RADBNo ROA
202.148.0.0/22NTTCOM, RADBNo ROA
202.148.0.0/23NTTCOM, RADBNo ROA
202.148.2.0/23NTTCOM, RADBNo ROA
202.148.4.0/22NTTCOM, RADBNo ROA
202.148.4.0/23NTTCOM, RADBNo ROA
202.148.16.0/20NTTCOM, RADBNo ROA
202.148.16.0/21NTTCOM, RADBNo ROA
202.148.16.0/22NTTCOM, RADBNo ROA
202.148.16.0/23NTTCOM, RADBNo ROA
202.148.18.0/23NTTCOM, RADBNo ROA
202.148.20.0/22NTTCOM, RADBNo ROA
202.148.20.0/23NTTCOM, RADBNo ROA
202.148.22.0/23NTTCOM, RADBNo ROA
202.148.24.0/21NTTCOM, RADBNo ROA
202.148.24.0/22NTTCOM, RADBNo ROA
202.148.26.0/23NTTCOM, RADBNo ROA
202.148.28.0/22NTTCOM, RADBNo ROA
202.148.28.0/23NTTCOM, RADBNo ROA
202.159.0.0/17NTTCOM, RADBNo ROA
202.159.64.0/18NTTCOM, RADBNo ROA
202.159.64.0/19NTTCOM, RADBNo ROA
202.159.64.0/20NTTCOM, RADBNo ROA
202.159.64.0/21NTTCOM, RADBNo ROA
202.159.64.0/22NTTCOM, RADBNo ROA
202.159.64.0/23NTTCOM, RADBNo ROA
202.159.64.0/24NTTCOM, RADBNo ROA
202.159.65.0/24NTTCOM, RADBNo ROA
202.159.66.0/23NTTCOM, RADBNo ROA
202.159.66.0/24NTTCOM, RADBNo ROA
202.159.67.0/24NTTCOM, RADBNo ROA
202.159.68.0/22NTTCOM, RADBNo ROA
202.159.68.0/23NTTCOM, RADBNo ROA
202.159.68.0/24NTTCOM, RADBNo ROA
202.159.69.0/24NTTCOM, RADBNo ROA
202.159.70.0/23NTTCOM, RADBNo ROA
202.159.70.0/24NTTCOM, RADBNo ROA
202.159.71.0/24NTTCOM, RADBNo ROA
202.159.72.0/21NTTCOM, RADBNo ROA
202.159.72.0/22NTTCOM, RADBNo ROA
202.159.72.0/23NTTCOM, RADBNo ROA
202.159.72.0/24NTTCOM, RADBNo ROA
202.159.73.0/24NTTCOM, RADBNo ROA
202.159.74.0/23NTTCOM, RADBNo ROA
202.159.74.0/24NTTCOM, RADBNo ROA
202.159.75.0/24NTTCOM, RADBNo ROA
202.159.76.0/22NTTCOM, RADBNo ROA
202.159.76.0/23NTTCOM, RADBNo ROA
202.159.76.0/24NTTCOM, RADBNo ROA
202.159.77.0/24NTTCOM, RADBNo ROA
202.159.78.0/23NTTCOM, RADBNo ROA
202.159.78.0/24NTTCOM, RADBNo ROA
202.159.79.0/24NTTCOM, RADBNo ROA
202.159.80.0/20NTTCOM, RADBNo ROA
202.159.80.0/21NTTCOM, RADBNo ROA
202.159.80.0/22NTTCOM, RADBNo ROA
202.159.80.0/23NTTCOM, RADBNo ROA
202.159.80.0/24NTTCOM, RADBNo ROA
202.159.81.0/24NTTCOM, RADBNo ROA
202.159.82.0/23NTTCOM, RADBNo ROA
202.159.82.0/24NTTCOM, RADBNo ROA
202.159.83.0/24NTTCOM, RADBNo ROA
202.159.84.0/22NTTCOM, RADBNo ROA
202.159.84.0/23NTTCOM, RADBNo ROA
202.159.84.0/24NTTCOM, RADBNo ROA
202.159.85.0/24NTTCOM, RADBNo ROA
202.159.86.0/23NTTCOM, RADBNo ROA
202.159.86.0/24NTTCOM, RADBNo ROA
202.159.87.0/24NTTCOM, RADBNo ROA
202.159.88.0/21NTTCOM, RADBNo ROA
202.159.88.0/22NTTCOM, RADBNo ROA
202.159.88.0/23NTTCOM, RADBNo ROA
202.159.88.0/24NTTCOM, RADBNo ROA
202.159.89.0/24NTTCOM, RADBNo ROA
202.159.90.0/23NTTCOM, RADBNo ROA
202.159.90.0/24NTTCOM, RADBNo ROA
202.159.91.0/24NTTCOM, RADBNo ROA
202.159.92.0/22NTTCOM, RADBNo ROA
202.159.92.0/23NTTCOM, RADBNo ROA
202.159.92.0/24NTTCOM, RADBNo ROA
202.159.93.0/24NTTCOM, RADBNo ROA
202.159.94.0/23NTTCOM, RADBNo ROA
202.159.94.0/24NTTCOM, RADBNo ROA
202.159.95.0/24NTTCOM, RADBNo ROA
202.160.254.0/24NTTCOM, RADBNo ROA
202.162.204.0/22RADBNo ROA
202.162.204.0/23NTTCOM, RADBNo ROA
202.180.48.0/21RADBNo ROA
202.180.48.0/22RADBNo ROA
202.180.48.0/23RADBNo ROA
202.180.50.0/23RADBNo ROA
202.180.52.0/22RADBNo ROA
202.180.52.0/23RADBNo ROA
202.180.54.0/23RADBNo ROA
203.201.160.0/20NTTCOM, RADBNo ROA
203.201.160.0/21NTTCOM, RADBNo ROA
203.201.160.0/22NTTCOM, RADBNo ROA
203.201.160.0/23NTTCOM, RADBNo ROA
203.201.162.0/23NTTCOM, RADBNo ROA
203.201.164.0/22NTTCOM, RADBNo ROA
203.201.164.0/23NTTCOM, RADBNo ROA
203.201.166.0/23NTTCOM, RADBNo ROA
203.201.168.0/21NTTCOM, RADBNo ROA
203.201.168.0/22NTTCOM, RADBNo ROA
203.201.168.0/23NTTCOM, RADBNo 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.