Network · data from 2026-11-12
AS149617 DIGIANA SPEED NET
Registry name: DIGIANA-AS-IN - Digiana Speed Net Private Limited, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS149617, 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.160.28.0/24 | Invalid: origin | None | 1 0%low visibility |
| 103.160.29.0/24 | Invalid: origin | None | 1 0%low visibility |
| 103.185.242.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.185.243.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 119.160.208.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 45.248.188.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 45.248.189.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 2001:df1:1640::/48 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS149617: AS149617:AS-DIGIANA. 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 (AS149617 isn't in the set, or no route object for AS149617 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.
| Name | Database | ASNs | Sets | AS149617 in it | Not covered |
|---|---|---|---|---|---|
| AS149617:AS-DIGIANA | APNIClists itself further down5 member sets in no database: AS-6186, AS-HNSISP-TRANSIT, AS136346:AS-FASTTNET, AS137609:AS-DCSISPL, AS214174:AS-RIPE | 714 | 73 | Yes | 2 |
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: origin2
- Route object: none2
- AS-SET: missing member5
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 103.160.28.0/24 | ROAs covering it name AS147224, not AS149617. If AS149617 should announce it, add a ROA for AS149617. |
| Route object: none | 103.160.28.0/24 | No route object for it. Add a route object with origin AS149617 in the RIR database for the space. |
| ROA: origin | 103.160.29.0/24 | ROAs covering it name AS147224, not AS149617. If AS149617 should announce it, add a ROA for AS149617. |
| Route object: none | 103.160.29.0/24 | No route object for it. Add a route object with origin AS149617 in the RIR database for the space. |
| AS-SET: missing member | AS149617:AS-DIGIANA | AS149617:AS-DIGIANA (APNIC) lists AS-6186; no IRR database read has it. |
| AS-SET: missing member | AS149617:AS-DIGIANA | AS149617:AS-DIGIANA (APNIC) lists AS-HNSISP-TRANSIT; no IRR database read has it. |
| AS-SET: missing member | AS149617:AS-DIGIANA | AS149617:AS-DIGIANA (APNIC) lists AS136346:AS-FASTTNET; no IRR database read has it. |
| AS-SET: missing member | AS149617:AS-DIGIANA | AS149617:AS-DIGIANA (APNIC) lists AS137609:AS-DCSISPL; no IRR database read has it. |
| AS-SET: missing member | AS149617:AS-DIGIANA | AS149617:AS-DIGIANA (APNIC) lists AS214174:AS-RIPE; no IRR database read has it. |
Route objects not announced
Route objects with origin AS149617 whose prefix no peer sees AS149617 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.157.164.0/23 | APNIC | Valid |
| 103.185.242.0/23 | APNIC | Valid |
| 119.160.209.0/24 | APNIC | Valid |
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.