bgpreport

Network · data from 2026-11-12

AS59179 MINS-AS - MINS Technologies Private Limited

Registry name: MINS-AS - MINS Technologies Private Limited, IN · not in PeeringDB

14IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 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
0Low visibility seen by under 10% of full-table peers
23Route objects not announced registered with origin AS59179, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS59179, 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.44.99.0/24 Valid RIR databaseAPNIC 673 100% 67
203.112.155.0/24 Valid RIR databaseAPNIC 673 100% 67
103.44.96.0/24 Valid RIR databaseAPNIC 672 100% 66
103.44.97.0/24 Valid RIR databaseAPNIC 672 100% 66
103.44.98.0/24 Valid RIR databaseAPNIC 672 100% 66
103.188.46.0/24 Valid RIR databaseAPNIC 672 100% 66
103.188.47.0/24 Valid RIR databaseAPNIC 672 100% 66
203.112.152.0/24 Valid RIR databaseAPNIC 672 100% 66
203.112.153.0/24 Valid RIR databaseAPNIC 672 100% 66
203.112.154.0/24 Valid RIR databaseAPNIC 672 100% 66
27.100.24.0/24 Valid RIR databaseAPNIC 671 100% 66
27.100.25.0/24 Valid RIR databaseAPNIC 671 100% 66
27.100.26.0/24 Valid RIR databaseAPNIC 671 100% 67
27.100.27.0/24 Valid RIR databaseAPNIC 671 100% 67
2407:8e80::/48 Valid RIR databaseAPNIC 636 100% 69
2407:8e80:1::/48 Valid RIR databaseAPNIC 636 100% 69
2407:8e80:2::/48 Valid RIR databaseAPNIC 636 100% 69

AS-SET

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

  • Route object: not announced23

Route objects not announced

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

27.100.24.0/22APNICValid
27.100.24.0/23APNICValid
27.100.26.0/23APNICValid
103.44.96.0/22APNICValid
103.44.96.0/23APNICValid
103.44.98.0/23APNICValid
103.71.167.0/24APNICValid
103.188.46.0/23APNICValid
203.112.152.0/22APNICValid
203.112.152.0/23APNICValid
203.112.154.0/23APNICValid
2407:8e80:3::/48APNICValid
2407:8e80:4::/48APNICValid
2407:8e80:5::/48APNICValid
2407:8e80:6::/48APNICValid
2407:8e80:7::/48APNICValid
2407:8e80:8::/48APNICValid
2407:8e80:9::/48APNICValid
2407:8e80:a::/48APNICValid
2407:8e80:b::/48APNICValid
2407:8e80:c::/48APNICValid
2407:8e80:d::/48APNICValid
2407:8e80:e::/48APNICValid

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.