Network · data from 2026-11-12
AS149268 ROARNET
Registry name: ROARNET-AS-IN - Roarnet Broadband Pvt Ltd, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS149268, 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.75.41.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.75.43.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.144.193.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.151.38.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.163.178.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.163.179.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.181.2.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.182.82.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.182.83.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.75.40.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.163.56.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.163.57.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.181.3.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 2001:df0:b840::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df6:2e80::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df6:2280::/48 | Valid | RIR databaseAPNIC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS149268: AS149268:AS-ROARNET. 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 (AS149268 isn't in the set, or no route object for AS149268 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 | AS149268 in it | Not covered |
|---|---|---|---|---|---|
| AS149268:AS-ROARNET | 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 | 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 16 are in fix.csv.
- AS-SET: missing member5
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: missing member | AS149268:AS-ROARNET | AS149268:AS-ROARNET (APNIC) lists AS-6186; no IRR database read has it. |
| AS-SET: missing member | AS149268:AS-ROARNET | AS149268:AS-ROARNET (APNIC) lists AS-HNSISP-TRANSIT; no IRR database read has it. |
| AS-SET: missing member | AS149268:AS-ROARNET | AS149268:AS-ROARNET (APNIC) lists AS136346:AS-FASTTNET; no IRR database read has it. |
| AS-SET: missing member | AS149268:AS-ROARNET | AS149268:AS-ROARNET (APNIC) lists AS137609:AS-DCSISPL; no IRR database read has it. |
| AS-SET: missing member | AS149268:AS-ROARNET | AS149268:AS-ROARNET (APNIC) lists AS214174:AS-RIPE; no IRR database read has it. |
Route objects not announced
Route objects with origin AS149268 whose prefix no peer sees AS149268 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.75.40.0/22 | APNIC | Valid |
| 103.75.40.0/23 | APNIC | Valid |
| 103.75.42.0/23 | APNIC | Valid |
| 103.75.42.0/24 | APNIC | Valid |
| 103.154.58.0/23 | APNIC | Valid |
| 103.154.58.0/24 | APNIC | Valid |
| 103.154.59.0/24 | APNIC | Valid |
| 103.163.56.0/23 | APNIC | Valid |
| 103.163.178.0/23 | APNIC | Valid |
| 103.181.2.0/23 | APNIC | Valid |
| 103.182.82.0/23 | 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.