bgpreport

Network · data from 2026-11-12

AS136841 MITRA TELEMEDIA MANUNGGAL

Registry name: MTMBALI-AS-ID - PT MITRA TELEMEDIA MANUNGGAL, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS136841, 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.
67.216.24.0/24 Valid Other IRR onlyRADB 673 100% 69
67.216.25.0/24 Valid Other IRR onlyRADB 673 100% 69
67.216.26.0/24 Valid Other IRR onlyRADB 673 100% 69
67.216.27.0/24 Valid Other IRR onlyRADB 672 100% 69
103.79.238.0/24 Valid Other IRR onlyRADB 672 100% 69
103.79.239.0/24 Valid Other IRR onlyRADB 672 100% 69
2401:be40:100::/48 Valid Other IRR onlyRADB 635 100% 70
2401:be40:666::/48 Valid Other IRR onlyRADB 635 100% 70
2401:be40:888::/48 Valid Other IRR onlyRADB 635 100% 70
2401:be40:1f2a::/48 Valid Other IRR onlyRADB 635 100% 70
2401:be40:2013::/48 Valid Other IRR onlyRADB 635 100% 70
2401:be40:4000::/48 Valid Other IRR onlyRADB 635 100% 70
2401:be40:7312::/48 Valid Other IRR onlyRADB 635 100% 70
2401:be40:b15a::/48 Valid Other IRR onlyRADB 635 100% 70
2401:be40:b602::/48 Valid Other IRR onlyRADB 635 100% 70
2401:be40:be57::/48 Valid Other IRR onlyRADB 635 100% 70
38.86.221.0/24 Valid RIR databaseARIN, RADB 673 100% 69
103.41.248.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
103.100.172.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
103.151.36.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
103.175.212.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
103.175.214.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
45.198.80.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 69
103.100.173.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
103.100.174.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
103.100.175.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
103.151.37.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
103.175.213.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
103.175.215.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
206.85.25.0/24 Valid RIR databaseARIN, RADB 672 100% 69
2401:be40::/32 Valid RIR databaseAPNIC, RADB 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS136841: AS136841:AS-MTMBALI. 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 (AS136841 isn't in the set, or no route object for AS136841 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 objectsAS136841 in itNot covered
AS136841:AS-MTMBALI 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 25 are in fix.csv.

  • Route object: RIR16
  • AS-SET: not found1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: RIR67.216.24.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR67.216.25.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR67.216.26.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR67.216.27.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.79.238.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.79.239.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2401:be40:100::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:be40:666::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:be40:888::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:be40:1f2a::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:be40:2013::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:be40:4000::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:be40:7312::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:be40:b15a::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:be40:b602::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:be40:be57::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
AS-SET: not foundAS136841:AS-MTMBALIPeeringDB names AS136841:AS-MTMBALI; no IRR database read has it.

Route objects not announced

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

103.41.248.0/23APNICValid
103.41.249.0/24APNIC, RADBValid
103.79.238.0/23RADBNo ROA
103.100.27.0/24APNICValid
103.100.172.0/22APNICNo ROA
103.175.212.0/22RADBNo ROA
103.175.212.0/23APNICValid
103.175.214.0/23APNICValid

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.