bgpreport

Network · data from 2026-11-12

AS141673 Mamura Inter Media

Registry name: IDNIC-MAMURA-AS-ID - PT Mamura Inter Media, ID · PeeringDB

17IPv4 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
10Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS141673, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS141673, 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.163.102.0/23 Valid Other IRR onlyRADB 673 100% 69
103.210.52.0/23 Valid Other IRR onlyRADB 673 100% 69
202.58.64.0/22 Valid Other IRR onlyRADB 673 100% 69
202.58.64.0/23 Valid Other IRR onlyRADB 673 100% 67
202.58.66.0/23 Valid Other IRR onlyRADB 673 100% 69
202.58.68.0/23 Valid Other IRR onlyRADB 673 100% 69
202.58.70.0/24 Valid Other IRR onlyRADB 673 100% 69
103.163.102.0/24 Valid Other IRR onlyRADB 35 5%low visibility 28
103.163.103.0/24 Valid Other IRR onlyRADB 35 5%low visibility 28
103.210.52.0/24 Valid Other IRR onlyRADB 35 5%low visibility 28
103.210.53.0/24 Valid Other IRR onlyRADB 35 5%low visibility 28
202.58.64.0/24 Valid Other IRR onlyRADB 35 5%low visibility 28
202.58.65.0/24 Valid Other IRR onlyRADB 35 5%low visibility 28
202.58.66.0/24 Valid Other IRR onlyRADB 35 5%low visibility 28
202.58.67.0/24 Valid Other IRR onlyRADB 35 5%low visibility 28
202.58.68.0/24 Valid Other IRR onlyRADB 35 5%low visibility 28
202.58.69.0/24 Valid Other IRR onlyRADB 35 5%low visibility 28

AS-SET

PeeringDB's irr_as_set for AS141673: AS-AS141673-MIM-ID. 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 (AS141673 isn't in the set, or no route object for AS141673 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 objectsAS141673 in itNot covered
AS-AS141673-MIM-ID In no IRR database read today.

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

  • Route object: RIR17
  • AS-SET: not found1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: RIR103.163.102.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.210.52.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.64.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.64.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.66.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.68.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.70.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.163.102.0/24Route object only in RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR103.163.103.0/24Route object only in RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR103.210.52.0/24Route object only in RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR103.210.53.0/24Route object only in RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR202.58.64.0/24Route object only in RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR202.58.65.0/24Route object only in RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR202.58.66.0/24Route object only in RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR202.58.67.0/24Route object only in RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR202.58.68.0/24Route object only in RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR202.58.69.0/24Route object only in RADB. Add it in the RIR database for the space.35 of 673
AS-SET: not foundAS-AS141673-MIM-IDPeeringDB names AS-AS141673-MIM-ID; no IRR database read has it.

Route objects not announced

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

202.58.64.0/21RADBValid
202.58.68.0/22RADBValid
202.58.70.0/23RADBValid
202.58.71.0/24RADBValid
2001:df2:3ec0::/48RADBValid

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.