bgpreport

Network · data from 2026-11-12

AS134312 Digi Win Infotainment Mumba

Registry name: DIGIWIN-AS - Digi Win Infotainment Mumbai Pvt Ltd, IN · PeeringDB

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

Announced routes

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

202.72.225.0/24 No ROA RIR databaseAPNIC 672 100% 67
202.72.226.0/24 No ROA RIR databaseAPNIC 672 100% 67
202.72.227.0/24 No ROA RIR databaseAPNIC 672 100% 67
202.72.224.0/24 No ROA RIR databaseAPNIC 671 100% 67
103.250.37.0/24 Valid RIR databaseAPNIC 672 100% 67
103.182.216.0/24 Valid RIR databaseAPNIC 671 100% 67
103.182.217.0/24 Valid RIR databaseAPNIC 671 100% 67
103.250.36.0/24 Valid RIR databaseAPNIC 671 100% 67
103.250.38.0/24 Valid RIR databaseAPNIC 671 100% 67
103.250.39.0/24 Valid RIR databaseAPNIC 671 100% 67

AS-SET

PeeringDB's irr_as_set for AS134312: AS134312:AS-DIGIWIN. 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 (AS134312 isn't in the set, or no route object for AS134312 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 objectsAS134312 in itNot covered
AS134312:AS-DIGIWIN APNIC 811,012 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 10 are in fix.csv.

  • ROA: none4
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none202.72.225.0/24No ROA covers it. Add a ROA for AS134312, maxLength 24.672 of 673
ROA: none202.72.226.0/24No ROA covers it. Add a ROA for AS134312, maxLength 24.672 of 673
ROA: none202.72.227.0/24No ROA covers it. Add a ROA for AS134312, maxLength 24.672 of 673
ROA: none202.72.224.0/24No ROA covers it. Add a ROA for AS134312, maxLength 24.671 of 673

Route objects not announced

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

103.182.216.0/23APNICValid
103.232.22.0/24RADBNo ROA
103.250.36.0/22APNICValid
103.250.36.0/23APNICValid
103.250.38.0/23APNICValid
202.72.224.0/22APNICNo 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.