bgpreport

Network · data from 2026-11-12

AS138089 Global Media Data Prima

Registry name: GMDP-AS-ID - PT.Global Media Data Prima, ID · PeeringDB

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

Announced routes

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

2403:e0c0:1::/48 Valid Nonecovered by 2403:e0c0::/32 636 100% 70
2403:e0c0:2::/48 Valid Nonecovered by 2403:e0c0::/32 636 100% 70
2403:e0c0:3::/48 Valid Nonecovered by 2403:e0c0::/32 636 100% 70
2403:e0c0:4::/48 Valid Nonecovered by 2403:e0c0::/32 636 100% 70
2403:e0c0:13::/48 Valid Nonecovered by 2403:e0c0::/32 636 100% 70
2403:e0c0:5::/48 Valid Nonecovered by 2403:e0c0::/32 634 100% 69
103.131.16.0/23 Valid Other IRR onlyRADB 673 100% 69
103.124.136.0/23 Valid Other IRR onlyNTTCOM, RADB 671 100% 68
103.124.138.0/23 Valid Other IRR onlyRADB 671 100% 68
103.158.13.0/24 Valid Other IRR onlyRADB 671 100% 68
157.20.244.0/24 Valid Other IRR onlyRADB 671 100% 68
157.20.252.0/23 Valid Other IRR onlyRADB 671 100% 68
160.191.180.0/24 Valid Other IRR onlyRADB 671 100% 68
113.192.48.0/24 Valid Other IRR onlyRADB 670 100% 68
165.99.225.0/24 Valid Other IRR onlyRADB 670 100% 68
103.124.138.0/24 Valid Other IRR onlyRADB 212 32% 56
103.124.139.0/24 Valid Other IRR onlyRADB 212 32% 56
103.131.16.0/24 Valid Other IRR onlyRADB 212 32% 56
103.131.17.0/24 Valid Other IRR onlyRADB 212 32% 56
157.20.252.0/24 Valid Other IRR onlyRADB 212 32% 56
157.20.253.0/24 Valid Other IRR onlyRADB 212 32% 56
103.63.26.0/24 Valid RIR databaseAPNIC 671 100% 68
103.131.18.0/23 Valid RIR databaseAPNIC 671 100% 68
210.87.74.0/24 Valid RIR databaseAPNIC, RADB 670 100% 68
45.198.32.0/23 Valid RIR databaseAFRINIC, RADB 669 99% 68
45.198.34.0/23 Valid RIR databaseAFRINIC, RADB 669 99% 68
2403:e0c0::/32 Valid RIR databaseAPNIC, RADB 636 100% 70
103.124.137.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 212 32% 56
103.131.18.0/24 Valid RIR databaseAPNIC 212 32% 56
103.131.19.0/24 Valid RIR databaseAPNIC 212 32% 56
45.198.32.0/24 Valid RIR databaseAFRINIC, RADB 211 31% 56
45.198.33.0/24 Valid RIR databaseAFRINIC, RADB 211 31% 56
45.198.34.0/24 Valid RIR databaseAFRINIC, RADB 211 31% 56
45.198.35.0/24 Valid RIR databaseAFRINIC, RADB 211 31% 56
103.124.136.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 211 31% 56

AS-SET

PeeringDB's irr_as_set for AS138089: RADB::AS138089:AS-SET-GMDP-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 (AS138089 isn't in the set, or no route object for AS138089 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 objectsAS138089 in itNot covered
RADB::AS138089:AS-SET-GMDP-ID RADBlists itself further down19 member sets in no database: AS-DETELNETWORKS-ID, AS-RAPDODGE:AS-TERADATA, AS-TLINK-CUSTOMERS, AS-TNC, AS138915:AS-CUSTOMER … 3452115,762 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 43 are in fix.csv.

  • Route object: none6
  • Route object: RIR15
  • AS-SET: missing member19
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none2403:e0c0:1::/48No route object for it. A route object for 2403:e0c0::/32 with origin AS138089 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138089 in the RIR database for the space.636 of 636
Route object: none2403:e0c0:2::/48No route object for it. A route object for 2403:e0c0::/32 with origin AS138089 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138089 in the RIR database for the space.636 of 636
Route object: none2403:e0c0:3::/48No route object for it. A route object for 2403:e0c0::/32 with origin AS138089 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138089 in the RIR database for the space.636 of 636
Route object: none2403:e0c0:4::/48No route object for it. A route object for 2403:e0c0::/32 with origin AS138089 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138089 in the RIR database for the space.636 of 636
Route object: none2403:e0c0:13::/48No route object for it. A route object for 2403:e0c0::/32 with origin AS138089 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138089 in the RIR database for the space.636 of 636
Route object: none2403:e0c0:5::/48No route object for it. A route object for 2403:e0c0::/32 with origin AS138089 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138089 in the RIR database for the space.634 of 636
Route object: RIR103.131.16.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.124.136.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.124.138.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.158.13.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR157.20.244.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR157.20.252.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR160.191.180.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR113.192.48.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR165.99.225.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR103.124.138.0/24Route object only in RADB. Add it in the RIR database for the space.212 of 673
Route object: RIR103.124.139.0/24Route object only in RADB. Add it in the RIR database for the space.212 of 673
Route object: RIR103.131.16.0/24Route object only in RADB. Add it in the RIR database for the space.212 of 673
Route object: RIR103.131.17.0/24Route object only in RADB. Add it in the RIR database for the space.212 of 673
Route object: RIR157.20.252.0/24Route object only in RADB. Add it in the RIR database for the space.212 of 673
Route object: RIR157.20.253.0/24Route object only in RADB. Add it in the RIR database for the space.212 of 673
AS-SET: missing memberRADB::AS138089:AS-SET-GMDP-IDAS138089:AS-SET-GMDP-ID (RADB) lists AS-DETELNETWORKS-ID; no IRR database read has it.
AS-SET: missing memberRADB::AS138089:AS-SET-GMDP-IDAS138089:AS-SET-GMDP-ID (RADB) lists AS-RAPDODGE:AS-TERADATA; no IRR database read has it.
AS-SET: missing memberRADB::AS138089:AS-SET-GMDP-IDAS138089:AS-SET-GMDP-ID (RADB) lists AS-TLINK-CUSTOMERS; no IRR database read has it.
AS-SET: missing memberRADB::AS138089:AS-SET-GMDP-IDAS138089:AS-SET-GMDP-ID (RADB) lists AS-TNC; no IRR database read has it.
AS-SET: missing memberRADB::AS138089:AS-SET-GMDP-IDAS138089:AS-SET-GMDP-ID (RADB) lists AS138915:AS-CUSTOMER; no IRR database read has it.
AS-SET: missing memberRADB::AS138089:AS-SET-GMDP-IDAS138089:AS-SET-GMDP-ID (RADB) lists AS142347:AS-JAGONET; no IRR database read has it.
AS-SET: missing memberRADB::AS138089:AS-SET-GMDP-IDAS138089:AS-SET-GMDP-ID (RADB) lists AS142373:AS-MNI-CUST; no IRR database read has it.
AS-SET: missing memberRADB::AS138089:AS-SET-GMDP-IDAS138089:AS-SET-GMDP-ID (RADB) lists AS149409:AS-CDNIX; no IRR database read has it.
AS-SET: missing memberRADB::AS138089:AS-SET-GMDP-IDAS138089:AS-SET-GMDP-ID (RADB) lists AS149662:AS-HOSTNET; no IRR database read has it.
AS-SET: missing memberRADB::AS138089:AS-SET-GMDP-IDAS138089:AS-SET-GMDP-ID (RADB) lists AS149746:AS-BLIP; no IRR database read has it.
AS-SET: missing memberRADB::AS138089:AS-SET-GMDP-IDAS138089:AS-SET-GMDP-ID (RADB) lists AS150279:AS-LNS; no IRR database read has it.
AS-SET: missing memberRADB::AS138089:AS-SET-GMDP-IDAS138089:AS-SET-GMDP-ID (RADB) lists AS150279:AS-LNSNET; no IRR database read has it.
AS-SET: missing memberRADB::AS138089:AS-SET-GMDP-IDAS138089:AS-SET-GMDP-ID (RADB) lists AS150501:AS-HCI; no IRR database read has it.
AS-SET: missing memberRADB::AS138089:AS-SET-GMDP-IDAS138089:AS-SET-GMDP-ID (RADB) lists AS150552:AS-BAROKAHNET; no IRR database read has it.
AS-SET: missing memberRADB::AS138089:AS-SET-GMDP-IDAS138089:AS-SET-GMDP-ID (RADB) lists AS152005:AS-SOULTAN; no IRR database read has it.
AS-SET: missing memberRADB::AS138089:AS-SET-GMDP-IDAS138089:AS-SET-GMDP-ID (RADB) lists AS152394:AS-ATT; no IRR database read has it.
AS-SET: missing memberRADB::AS138089:AS-SET-GMDP-IDAS138089:AS-SET-GMDP-ID (RADB) lists AS153480:AS-ACS-ID; no IRR database read has it.
AS-SET: missing memberRADB::AS138089:AS-SET-GMDP-IDAS138089:AS-SET-GMDP-ID (RADB) lists AS45723:AS-OMADATA; no IRR database read has it.
AS-SET: missing memberRADB::AS138089:AS-SET-GMDP-IDAS138089:AS-SET-GMDP-ID (RADB) lists AS47311:AS-ATHARVA; no IRR database read has it.

Route objects not announced

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

103.124.136.0/22NTTCOM, RADBValid
103.131.16.0/22RADBValid
103.153.127.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.