bgpreport

Network · data from 2026-11-12

AS55666 PT Media Sarana Data (GMEDIA)

Registry name: GMEDIA-AS-ID - PT Media Sarana Data, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55666, 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.99.164.0/24 Invalid: origin Other origin only 130 19% 52
2401:1700:7c17::/48 Valid Nonecovered by 2401:1700::/32 636 100% 70
2401:1700:7c1f::/48 Valid Nonecovered by 2401:1700::/32 636 100% 70
2401:1700:23::/48 Valid Nonecovered by 2401:1700::/32 634 100% 70
2401:1700:7c0f::/48 Valid Nonecovered by 2401:1700::/32 1 0%low visibility 1
2401:1700:7c2f::/48 Valid Nonecovered by 2401:1700::/32 1 0%low visibility 1
103.4.52.0/24 Valid Other IRR onlyALTDB, RADB 673 100% 69
103.4.54.0/24 Valid Other IRR onlyALTDB, RADB 673 100% 69
202.46.148.0/22 Valid Other IRR onlyALTDB, RADB 673 100% 69
202.46.150.0/24 Valid Other IRR onlyALTDB, RADB 673 100% 69
202.46.151.0/24 Valid Other IRR onlyALTDB, RADB 673 100% 69
103.4.53.0/24 Valid Other IRR onlyALTDB, RADB 672 100% 69
103.140.76.0/24 Valid Other IRR onlyALTDB, RADB 672 100% 69
202.145.6.0/24 Valid Other IRR onlyALTDB, RADB 672 100% 69
202.145.7.0/24 Valid Other IRR onlyALTDB, RADB 672 100% 69
43.245.184.0/24 Valid Other IRR onlyALTDB, RADB 671 100% 69
202.46.148.0/24 Valid Other IRR onlyALTDB, RADB 671 100% 69
202.46.149.0/24 Valid Other IRR onlyALTDB, RADB 671 100% 69
2401:1700::/48 Valid Other IRR onlyALTDB, NTTCOM, RADB 636 100% 70
2401:1700:5::/48 Valid Other IRR onlyALTDB, NTTCOM 636 100% 70
2401:1700:9::/48 Valid Other IRR onlyALTDB, NTTCOM, RADB 636 100% 70
2401:1700:f::/48 Valid Other IRR onlyALTDB 636 100% 70
2401:1700:19::/48 Valid Other IRR onlyALTDB 636 100% 70
2401:1700:20::/48 Valid Other IRR onlyALTDB 636 100% 70
2401:1700:4::/48 Valid Other IRR onlyALTDB, NTTCOM 635 100% 70
2401:1700:d::/48 Valid Other IRR onlyALTDB, NTTCOM 635 100% 70
2401:1700:1a::/48 Valid Other IRR onlyALTDB 635 100% 70
2401:1700:1d::/48 Valid Other IRR onlyALTDB 635 100% 70
2401:1700:1e::/48 Valid Other IRR onlyALTDB, RADB 635 100% 67
2401:1700:1::/48 Valid Other IRR onlyALTDB, NTTCOM, RADB 634 100% 70
2401:1700:3::/48 Valid Other IRR onlyALTDB, NTTCOM 634 100% 70
2401:1700:c::/48 Valid Other IRR onlyALTDB, NTTCOM 634 100% 70
2401:1700:10::/48 Valid Other IRR onlyALTDB, RADB 634 100% 70
2401:1700:11::/48 Valid Other IRR onlyALTDB, NTTCOM, RADB 634 100% 70
2401:1700:12::/48 Valid Other IRR onlyALTDB, NTTCOM, RADB 634 100% 70
2401:1700:13::/48 Valid Other IRR onlyALTDB, NTTCOM, RADB 634 100% 70
2401:1700:14::/48 Valid Other IRR onlyALTDB, NTTCOM, RADB 634 100% 70
2401:1700:15::/48 Valid Other IRR onlyALTDB, RADB 634 100% 70
2401:1700:16::/48 Valid Other IRR onlyALTDB, RADB 634 100% 70
2401:1700:17::/48 Valid Other IRR onlyALTDB 634 100% 70
2401:1700:18::/48 Valid Other IRR onlyALTDB 634 100% 70
2401:1700:1b::/48 Valid Other IRR onlyALTDB 634 100% 70
2401:1700:1c::/48 Valid Other IRR onlyALTDB 634 100% 70
2401:1700:22::/48 Valid Other IRR onlyALTDB 634 100% 70
2401:1700:1f::/48 Valid Other IRR onlyALTDB 1 0%low visibility 1
43.245.184.0/22 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
43.245.186.0/24 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
43.252.156.0/22 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 673 100% 69
49.128.176.0/21 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
49.128.176.0/23 Valid RIR databaseAPNIC, RADB 673 100% 69
49.128.178.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
49.128.180.0/24 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
49.128.182.0/24 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
49.128.183.0/24 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
103.17.244.0/22 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 673 100% 69
103.17.244.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
103.17.244.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 673 100% 69
103.17.246.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
103.31.224.0/22 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
103.247.120.0/22 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
103.247.122.0/24 Valid RIR databaseALTDB, APNIC, RADB 673 100% 70
103.249.65.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
103.255.240.0/22 Valid RIR databaseALTDB, APNIC, RADB, REACH 673 100% 69
103.255.240.0/24 Valid RIR databaseALTDB, APNIC, RADB, REACH 673 100% 69
103.255.243.0/24 Valid RIR databaseALTDB, APNIC, RADB, REACH 673 100% 69
111.68.24.0/21 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
111.68.29.0/24 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
111.68.30.0/24 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
111.68.31.0/24 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
112.78.32.0/21 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 673 100% 69
112.78.34.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 673 100% 69
112.78.37.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 673 100% 69
116.254.113.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 673 100% 70
116.254.117.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 673 100% 69
116.254.118.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 673 100% 69
119.2.48.0/21 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
119.2.50.0/24 Valid RIR databaseALTDB, APNIC, RADB 673 100% 68
119.2.53.0/24 Valid RIR databaseALTDB, APNIC, RADB 673 100% 70
119.2.55.0/24 Valid RIR databaseALTDB, APNIC, RADB 673 100% 68
202.145.6.0/23 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
203.30.236.0/23 Valid RIR databaseALTDB, APNIC, RADB 673 100% 69
43.245.185.0/24 Valid RIR databaseALTDB, APNIC, RADB 672 100% 69
43.245.187.0/24 Valid RIR databaseALTDB, APNIC, RADB 672 100% 69
49.128.176.0/24 Valid RIR databaseALTDB, APNIC, RADB 672 100% 69
49.128.177.0/24 Valid RIR databaseALTDB, APNIC, RADB 672 100% 69
49.128.179.0/24 Valid RIR databaseALTDB, APNIC, RADB 672 100% 69
49.128.181.0/24 Valid RIR databaseALTDB, APNIC, RADB 672 100% 69
103.31.224.0/24 Valid RIR databaseALTDB, APNIC, RADB 672 100% 67
103.31.225.0/24 Valid RIR databaseALTDB, APNIC, RADB 672 100% 67
103.247.123.0/24 Valid RIR databaseALTDB, APNIC, RADB 672 100% 68
103.255.241.0/24 Valid RIR databaseALTDB, APNIC, RADB, REACH 672 100% 69
111.68.26.0/24 Valid RIR databaseALTDB, APNIC, RADB 672 100% 69
111.68.27.0/24 Valid RIR databaseALTDB, APNIC, RADB 672 100% 69
112.78.32.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 672 100% 69
112.78.36.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 672 100% 69
112.78.39.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 672 100% 68
116.254.112.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 672 100% 69
116.254.114.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 672 100% 69
116.254.116.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 672 100% 69
119.2.54.0/24 Valid RIR databaseALTDB, APNIC, RADB 672 100% 69
203.30.236.0/24 Valid RIR databaseALTDB, APNIC, RADB 672 100% 69
203.30.237.0/24 Valid RIR databaseALTDB, APNIC, RADB 672 100% 69
103.247.120.0/24 Valid RIR databaseALTDB, APNIC, RADB 671 100% 69
111.68.24.0/24 Valid RIR databaseALTDB, APNIC, RADB 671 100% 69
111.68.25.0/24 Valid RIR databaseALTDB, APNIC, RADB 671 100% 69
112.78.33.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 671 100% 69
112.78.35.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 671 100% 69
116.254.119.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 671 100% 69
119.2.52.0/24 Valid RIR databaseALTDB, APNIC, RADB 671 100% 69
2401:1700::/32 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 635 100% 69
103.31.226.0/24 Valid RIR databaseALTDB, APNIC, RADB 2 0%low visibility 2
103.31.227.0/24 Valid RIR databaseALTDB, APNIC, RADB 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS55666: ALTDB::AS55666:AS-GMEDIA. 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 (AS55666 isn't in the set, or no route object for AS55666 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 objectsAS55666 in itNot covered
ALTDB::AS55666:AS-GMEDIA ALTDB 3611,969 Yes 1

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

  • ROA: origin1
  • Route object: none6
  • Route object: RIR39
  • Route object: not announced76
ChangePrefix or setDetailFull-table peers
ROA: origin103.99.164.0/24ROAs covering it name AS38760, not AS55666. If AS55666 should announce it, add a ROA for AS55666.130 of 673
Route object: none103.99.164.0/24Route objects for it name AS38760. Add a route object with origin AS55666 in the RIR database for the space.130 of 673
Route object: none2401:1700:7c17::/48No route object for it. A route object for 2401:1700::/32 with origin AS55666 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55666 in the RIR database for the space.636 of 636
Route object: none2401:1700:7c1f::/48No route object for it. A route object for 2401:1700::/32 with origin AS55666 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55666 in the RIR database for the space.636 of 636
Route object: none2401:1700:23::/48No route object for it. A route object for 2401:1700::/32 with origin AS55666 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55666 in the RIR database for the space.634 of 636
Route object: none2401:1700:7c0f::/48No route object for it. A route object for 2401:1700::/32 with origin AS55666 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55666 in the RIR database for the space.1 of 636
Route object: none2401:1700:7c2f::/48No route object for it. A route object for 2401:1700::/32 with origin AS55666 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55666 in the RIR database for the space.1 of 636
Route object: RIR103.4.52.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.4.54.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.46.148.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.46.150.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.46.151.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.4.53.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.140.76.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.145.6.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.145.7.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR43.245.184.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR202.46.148.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR202.46.149.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2401:1700::/48Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2401:1700:5::/48Route object only in ALTDB, NTTCOM. Add it in the RIR database for the space.636 of 636
Route object: RIR2401:1700:9::/48Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2401:1700:f::/48Route object only in ALTDB. Add it in the RIR database for the space.636 of 636
Route object: RIR2401:1700:19::/48Route object only in ALTDB. Add it in the RIR database for the space.636 of 636
Route object: RIR2401:1700:20::/48Route object only in ALTDB. Add it in the RIR database for the space.636 of 636
Route object: RIR2401:1700:4::/48Route object only in ALTDB, NTTCOM. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:1700:d::/48Route object only in ALTDB, NTTCOM. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:1700:1a::/48Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:1700:1d::/48Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:1700:1e::/48Route object only in ALTDB, RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:1700:1::/48Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2401:1700:3::/48Route object only in ALTDB, NTTCOM. Add it in the RIR database for the space.634 of 636
Route object: RIR2401:1700:c::/48Route object only in ALTDB, NTTCOM. Add it in the RIR database for the space.634 of 636
Route object: RIR2401:1700:10::/48Route object only in ALTDB, RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2401:1700:11::/48Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2401:1700:12::/48Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2401:1700:13::/48Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2401:1700:14::/48Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2401:1700:15::/48Route object only in ALTDB, RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2401:1700:16::/48Route object only in ALTDB, RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2401:1700:17::/48Route object only in ALTDB. Add it in the RIR database for the space.634 of 636
Route object: RIR2401:1700:18::/48Route object only in ALTDB. Add it in the RIR database for the space.634 of 636
Route object: RIR2401:1700:1b::/48Route object only in ALTDB. Add it in the RIR database for the space.634 of 636
Route object: RIR2401:1700:1c::/48Route object only in ALTDB. Add it in the RIR database for the space.634 of 636
Route object: RIR2401:1700:22::/48Route object only in ALTDB. Add it in the RIR database for the space.634 of 636
Route object: RIR2401:1700:1f::/48Route object only in ALTDB. Add it in the RIR database for the space.1 of 636

Route objects not announced

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

43.252.156.0/23APNIC, NTTCOM, RADBValid
43.252.156.0/24APNIC, NTTCOM, RADBValid
43.252.157.0/24APNIC, NTTCOM, RADBValid
43.252.158.0/23APNIC, NTTCOM, RADBValid
43.252.158.0/24APNIC, NTTCOM, RADBValid
43.252.159.0/24APNIC, NTTCOM, RADBValid
49.128.176.0/22APNIC, RADBValid
49.128.178.0/24APNIC, RADBValid
49.128.180.0/22APNIC, NTTCOM, RADBValid
49.128.180.0/23APNIC, NTTCOM, RADBValid
49.128.182.0/23APNIC, NTTCOM, RADBValid
103.4.52.0/23ALTDBValid
103.17.245.0/24APNIC, NTTCOM, RADBValid
103.17.246.0/24APNIC, NTTCOM, RADBValid
103.17.247.0/24APNIC, NTTCOM, RADBValid
103.21.206.0/24APNICInvalid: origin
103.140.76.0/23ALTDB, RADBValid
103.140.77.0/24ALTDB, RADBValid
103.247.120.0/23APNIC, RADBValid
103.247.121.0/24APNIC, RADBValid
103.247.122.0/23APNIC, NTTCOM, RADBValid
103.248.198.0/23APNICInvalid: origin
103.248.198.0/24APNICInvalid: origin
103.248.199.0/24APNICInvalid: origin
103.255.240.0/23APNIC, RADBValid
103.255.242.0/23APNIC, RADBValid
103.255.242.0/24APNIC, RADB, REACHValid
111.68.24.0/22APNIC, RADBValid
111.68.24.0/23APNIC, RADBValid
111.68.26.0/23APNIC, NTTCOM, RADBValid
111.68.28.0/22APNIC, NTTCOM, RADBValid
111.68.28.0/23APNIC, NTTCOM, RADBValid
111.68.28.0/24APNIC, RADBValid
111.68.30.0/23APNIC, NTTCOM, RADBValid
112.78.32.0/22APNIC, NTTCOM, RADBValid
112.78.32.0/23APNIC, NTTCOM, RADBValid
112.78.34.0/23APNIC, NTTCOM, RADBValid
112.78.36.0/22APNIC, NTTCOM, RADBValid
112.78.36.0/23APNIC, NTTCOM, RADBValid
112.78.38.0/23APNIC, NTTCOM, RADBValid
112.78.38.0/24APNIC, NTTCOM, RADBValid
116.254.112.0/21ALTDB, APNIC, NTTCOM, RADBValid
116.254.112.0/22APNIC, NTTCOM, RADBValid
116.254.112.0/23APNIC, NTTCOM, RADBValid
116.254.114.0/23APNIC, NTTCOM, RADBValid
116.254.115.0/24APNIC, NTTCOM, RADBValid
116.254.116.0/22APNIC, NTTCOM, RADBValid
116.254.116.0/23APNIC, NTTCOM, RADBValid
116.254.118.0/23APNIC, NTTCOM, RADBValid
119.2.48.0/22APNIC, RADBValid
119.2.48.0/23APNIC, RADBValid
119.2.48.0/24APNIC, RADBValid
119.2.49.0/24APNIC, RADBValid
119.2.50.0/23APNIC, NTTCOM, RADBValid
119.2.51.0/24APNIC, RADBValid
119.2.52.0/22APNIC, NTTCOM, RADBValid
119.2.52.0/23APNIC, NTTCOM, RADBValid
119.2.54.0/23APNIC, NTTCOM, RADBValid
202.46.144.0/20RADBNo ROA
202.46.144.0/21RADBNo ROA
202.46.148.0/23RADBValid
202.46.150.0/23RADBValid
202.46.152.0/21RADBNo ROA
2001:df0:fa00::/48RADBNo ROA
2001:df1:2600::/48RADBNo ROA
2001:df1:e000::/48NTTCOM, RADBValid
2401:1700:2::/48ALTDB, NTTCOM, RADBValid
2401:1700:6::/48ALTDB, NTTCOM, RADBValid
2401:1700:7::/48ALTDB, NTTCOM, RADBValid
2401:1700:8::/48ALTDB, NTTCOM, RADBValid
2401:1700:a::/48ALTDB, NTTCOMValid
2401:1700:b::/48ALTDB, NTTCOMValid
2401:1700:e::/48ALTDB, NTTCOMValid
2401:1700:21::/48ALTDBValid
2401:1700:a1::/48RADBValid
2401:1700:b0b0::/48NTTCOMValid

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.