bgpreport

Network · data from 2026-11-12

AS141480 Haash Media

Registry name: HAASHMED-AS - Haash Media, IN · PeeringDB

8IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 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
4Route objects not announced registered with origin AS141480, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS141480, 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.139.67.0/24 Valid RIR databaseAPNIC 673 100% 66
103.155.130.0/24 Valid RIR databaseAPNIC 672 100% 67
103.155.131.0/24 Valid RIR databaseAPNIC 672 100% 67
103.160.236.0/24 Valid RIR databaseAPNIC 672 100% 66
103.160.237.0/24 Valid RIR databaseAPNIC 672 100% 67
203.109.33.0/24 Valid RIR databaseAPNIC 672 100% 67
203.109.34.0/24 Valid RIR databaseAPNIC 672 100% 67
203.109.35.0/24 Valid RIR databaseAPNIC 672 100% 67
2001:df1:a780::/48 Valid RIR databaseAPNIC 635 100% 70
2001:df1:f840::/48 Valid RIR databaseAPNIC 38 6%low visibility 28

AS-SET

PeeringDB's irr_as_set for AS141480: AS141480:AS-HAASHMED. 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 (AS141480 isn't in the set, or no route object for AS141480 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 objectsAS141480 in itNot covered
AS141480:AS-HAASHMED APNIClists itself further down5 member sets in no database: AS-6186, AS-HNSISP-TRANSIT, AS136346:AS-FASTTNET, AS137609:AS-DCSISPL, AS214174:AS-RIPE 1,262144334,505 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 9 are in fix.csv.

  • AS-SET: missing member5
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberAS141480:AS-HAASHMEDAS141480:AS-HAASHMED (APNIC) lists AS-6186; no IRR database read has it.
AS-SET: missing memberAS141480:AS-HAASHMEDAS141480:AS-HAASHMED (APNIC) lists AS-HNSISP-TRANSIT; no IRR database read has it.
AS-SET: missing memberAS141480:AS-HAASHMEDAS141480:AS-HAASHMED (APNIC) lists AS136346:AS-FASTTNET; no IRR database read has it.
AS-SET: missing memberAS141480:AS-HAASHMEDAS141480:AS-HAASHMED (APNIC) lists AS137609:AS-DCSISPL; no IRR database read has it.
AS-SET: missing memberAS141480:AS-HAASHMEDAS141480:AS-HAASHMED (APNIC) lists AS214174:AS-RIPE; no IRR database read has it.

Route objects not announced

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

103.155.130.0/23APNICValid
103.160.236.0/23APNICValid
163.227.152.0/24APNICValid
163.227.153.0/24APNICValid

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.