bgpreport

Network · data from 2026-11-12

AS7590 COMSATS - Commission on Science and Technology for

Registry name: COMSATS - Commission on Science and Technology for, PK · not in PeeringDB

48IPv4 routes 89.6% RPKI valid · 97.9% with a route object
4IPv6 routes 25.0% RPKI valid · 50.0% with a route object
4RPKI invalid 4 origin · 0 maxLength
4No ROA 3 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
93Route objects not announced registered with origin AS7590, seen from no peer

Announced routes

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

203.124.59.0/24 Invalid: origin Other origin onlycovered by 203.124.58.0/23 2 0%low visibility 2
203.124.56.0/24 Invalid: origin RIR databaseAPNIC 2 0%low visibility 2
203.124.57.0/24 Invalid: origin RIR databaseAPNIC 2 0%low visibility 2
210.56.19.0/24 Invalid: origin RIR databaseAPNIC 1 0%low visibility 1
2402:1680:2::/48 No ROA Other origin onlycovered by 2402:1680::/32 636 100% 69
2402:1680:3::/48 No ROA Other origin onlycovered by 2402:1680::/32 636 100% 69
103.152.254.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 68
2400:1760::/32 No ROA RIR databaseAPNIC, RADB 636 100% 69
203.124.52.0/24 Valid Other IRR onlyRADB 673 100% 68
203.124.53.0/24 Valid Other IRR onlyRADB 673 100% 68
203.124.32.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.124.33.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
203.124.35.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.124.36.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.124.37.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.124.39.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
203.124.40.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
203.124.41.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.124.42.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.124.43.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
203.124.44.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
203.124.45.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.124.46.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.124.47.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.124.48.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
203.124.50.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.124.51.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
203.124.54.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.124.63.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
210.56.2.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
210.56.8.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
210.56.9.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
210.56.11.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
210.56.12.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
210.56.13.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
210.56.14.0/24 Valid RIR databaseAPNIC 673 100% 68
210.56.15.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
210.56.20.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
210.56.24.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
210.56.27.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
210.56.28.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
210.56.30.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
210.56.31.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
210.56.1.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
210.56.10.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
210.56.16.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
210.56.17.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
210.56.21.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
210.56.23.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
210.56.25.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
210.56.29.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
2402:1680:1::/48 Valid RIR databaseAPNIC, RADB 635 100% 69

AS-SET

AS7590 isn't in PeeringDB, where networks name their AS-SET.

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

  • ROA: origin4
  • ROA: none4
  • Route object: none3
  • Route object: RIR2
  • Route object: not announced93
ChangePrefix or setDetailFull-table peers
ROA: origin203.124.59.0/24ROAs covering it name AS55501, not AS7590. If AS7590 should announce it, add a ROA for AS7590.2 of 673
Route object: none203.124.59.0/24Route objects for it name AS55501. A route object for 203.124.58.0/23 with origin AS7590 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7590 in the RIR database for the space.2 of 673
ROA: origin203.124.56.0/24ROAs covering it name AS55501, not AS7590. If AS7590 should announce it, add a ROA for AS7590.2 of 673
ROA: origin203.124.57.0/24ROAs covering it name AS55501, not AS7590. If AS7590 should announce it, add a ROA for AS7590.2 of 673
ROA: origin210.56.19.0/24ROAs covering it name AS137561, not AS7590. If AS7590 should announce it, add a ROA for AS7590.1 of 673
ROA: none2402:1680:2::/48No ROA covers it. Add a ROA for AS7590, maxLength 48.636 of 636
Route object: none2402:1680:2::/48Route objects for it name AS17557. A route object for 2402:1680::/32 with origin AS7590 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7590 in the RIR database for the space.636 of 636
ROA: none2402:1680:3::/48No ROA covers it. Add a ROA for AS7590, maxLength 48.636 of 636
Route object: none2402:1680:3::/48Route objects for it name AS17557. A route object for 2402:1680::/32 with origin AS7590 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7590 in the RIR database for the space.636 of 636
ROA: none103.152.254.0/24No ROA covers it. Add a ROA for AS7590, maxLength 24.673 of 673
ROA: none2400:1760::/32No ROA covers it. Add a ROA for AS7590, maxLength 32.636 of 636
Route object: RIR203.124.52.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR203.124.53.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

103.26.184.0/24RADBNo ROA
103.26.185.0/24RADBNo ROA
103.152.254.0/23RADBNo ROA
203.124.32.0/19APNIC, RADBNo ROA
203.124.32.0/20RADBNo ROA
203.124.32.0/21RADBNo ROA
203.124.32.0/22RADBNo ROA
203.124.32.0/23RADBNo ROA
203.124.34.0/23RADBNo ROA
203.124.36.0/22RADBNo ROA
203.124.36.0/23RADBNo ROA
203.124.38.0/23RADBNo ROA
203.124.38.0/24APNICInvalid: origin
203.124.40.0/21RADBNo ROA
203.124.40.0/22RADBNo ROA
203.124.40.0/23RADBNo ROA
203.124.42.0/23RADBNo ROA
203.124.44.0/22RADBNo ROA
203.124.44.0/23RADBNo ROA
203.124.46.0/23RADBNo ROA
203.124.48.0/20RADBNo ROA
203.124.48.0/21RADBNo ROA
203.124.48.0/22RADBNo ROA
203.124.48.0/23RADBNo ROA
203.124.50.0/23RADBNo ROA
203.124.52.0/22RADBNo ROA
203.124.52.0/23RADBNo ROA
203.124.54.0/23RADBNo ROA
203.124.56.0/21RADBNo ROA
203.124.56.0/22RADBNo ROA
203.124.56.0/23RADBNo ROA
203.124.58.0/23RADBNo ROA
203.124.58.0/24APNICInvalid: origin
203.124.60.0/22RADBNo ROA
203.124.60.0/23RADBNo ROA
203.124.60.0/24APNICInvalid: origin
203.124.61.0/24APNICInvalid: origin
203.124.62.0/23RADBNo ROA
203.124.62.0/24APNICInvalid: origin
210.56.0.0/21RADBNo ROA
210.56.0.0/22RADBNo ROA
210.56.0.0/23RADBNo ROA
210.56.0.0/24APNIC, RADBValid
210.56.2.0/23RADBNo ROA
210.56.4.0/22RADBNo ROA
210.56.4.0/23RADBNo ROA
210.56.6.0/23RADBNo ROA
210.56.7.0/24APNICInvalid: origin
210.56.8.0/21APNIC, RADBNo ROA
210.56.8.0/22RADBNo ROA
210.56.8.0/23RADBNo ROA
210.56.10.0/23RADBNo ROA
210.56.12.0/22APNIC, RADBNo ROA
210.56.12.0/23RADBNo ROA
210.56.14.0/23RADBNo ROA
210.56.16.0/20RADBNo ROA
210.56.16.0/21RADBNo ROA
210.56.16.0/22RADBNo ROA
210.56.16.0/23RADBNo ROA
210.56.18.0/23RADBNo ROA
210.56.18.0/24APNICInvalid: origin
210.56.20.0/22RADBNo ROA
210.56.20.0/23RADBNo ROA
210.56.22.0/23RADBNo ROA
210.56.22.0/24APNICInvalid: origin
210.56.24.0/21RADBNo ROA
210.56.24.0/22RADBNo ROA
210.56.24.0/23RADBNo ROA
210.56.26.0/23RADBNo ROA
210.56.26.0/24APNICInvalid: origin
210.56.28.0/22RADBNo ROA
210.56.28.0/23RADBNo ROA
210.56.30.0/23RADBNo ROA
2401:0:4000::/34RADBNo ROA
2401:0:8000::/34RADBNo ROA
2401:0:c000::/34RADBNo ROA
2402:1680::/32RADBNo ROA
2402:1680:a::/48APNICNo ROA
2402:1680:b::/48APNICNo ROA
2402:1680:c::/48APNICNo ROA
2402:1680:d::/48APNICNo ROA
2402:1680:e::/48APNICNo ROA
2402:1680:f::/48APNICNo ROA
2402:1680:10::/48APNICNo ROA
2402:1680:11::/48APNICNo ROA
2402:1680:12::/48APNICNo ROA
2402:1680:13::/48APNICNo ROA
2402:1680:14::/48APNICNo ROA
2402:1680:15::/48APNICNo ROA
2402:1680:16::/48APNICNo ROA
2402:1680:17::/48APNICNo ROA
2402:1680:18::/48APNICNo ROA
2402:1680:19::/48APNICNo 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.