bgpreport

Network · data from 2026-11-12

AS45148 DIGIVISION-ENTERTAINMENT-AS-IN - Digivision Entertainment Private Limited

Registry name: DIGIVISION-ENTERTAINMENT-AS-IN - Digivision Entertainment Private Limited, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45148, 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.
119.252.212.0/24 Invalid: origin RIR databaseAPNIC 2 0%low visibility 2
2403:2200::/48 No ROA RIR databaseAPNIC 636 100% 69
119.252.208.0/24 Valid RIR databaseAPNIC 673 100% 67
119.252.209.0/24 Valid RIR databaseAPNIC 673 100% 67
119.252.214.0/24 Valid RIR databaseAPNIC 672 100% 67
119.252.214.0/23 Valid RIR databaseAPNIC 671 100% 67
119.252.215.0/24 Valid RIR databaseAPNIC 671 100% 67

AS-SET

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

  • ROA: origin1
  • ROA: none1
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: origin119.252.212.0/24ROAs covering it name AS134375, not AS45148. If AS45148 should announce it, add a ROA for AS45148.2 of 673
ROA: none2403:2200::/48No ROA covers it. Add a ROA for AS45148, maxLength 48.636 of 636

Route objects not announced

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

119.252.192.0/19APNICNo ROA
119.252.208.0/21APNICNo ROA
119.252.208.0/22APNICNo ROA
119.252.208.0/23APNICValid
119.252.210.0/23APNICInvalid: origin
119.252.210.0/24APNICInvalid: origin
119.252.211.0/24APNICInvalid: origin
119.252.212.0/22APNICNo ROA
119.252.212.0/23APNICInvalid: origin
119.252.213.0/24APNICInvalid: origin

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.