Network · data from 2026-11-12
AS137083 TAJ Broadband Private Limited
Registry name: TAJBBMUM-AS-IN - TAJ BROADBAND PRIVATE LIMITED, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS137083, 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.57.96.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.57.97.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.105.228.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.105.229.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.105.230.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.105.231.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.157.8.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.157.9.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.181.6.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 160.25.180.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 160.25.181.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 2001:df5:680::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2001:df4:f40::/48 | Valid | RIR databaseAPNIC | 39 6%low visibility |
AS-SET
PeeringDB's irr_as_set for AS137083: AS137083:AS-TAJBB-PEERS. 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 (AS137083 isn't in the set, or no route object for AS137083 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 | AS137083 in it | Not covered |
|---|---|---|---|---|---|
| AS137083:AS-TAJBB-PEERS | APNIClists itself further down5 member sets in no database: AS-6186, AS-HNSISP-TRANSIT, AS136346:AS-FASTTNET, AS137609:AS-DCSISPL, AS214174:AS-RIPE | 1,262 | 144 | 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 15 are in fix.csv.
- AS-SET: missing member5
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: missing member | AS137083:AS-TAJBB-PEERS | AS137083:AS-TAJBB-PEERS (APNIC) lists AS-6186; no IRR database read has it. |
| AS-SET: missing member | AS137083:AS-TAJBB-PEERS | AS137083:AS-TAJBB-PEERS (APNIC) lists AS-HNSISP-TRANSIT; no IRR database read has it. |
| AS-SET: missing member | AS137083:AS-TAJBB-PEERS | AS137083:AS-TAJBB-PEERS (APNIC) lists AS136346:AS-FASTTNET; no IRR database read has it. |
| AS-SET: missing member | AS137083:AS-TAJBB-PEERS | AS137083:AS-TAJBB-PEERS (APNIC) lists AS137609:AS-DCSISPL; no IRR database read has it. |
| AS-SET: missing member | AS137083:AS-TAJBB-PEERS | AS137083:AS-TAJBB-PEERS (APNIC) lists AS214174:AS-RIPE; no IRR database read has it. |
Route objects not announced
Route objects with origin AS137083 whose prefix no peer sees AS137083 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.105.228.0/23 | APNIC | Valid |
| 103.105.230.0/23 | APNIC | Valid |
| 103.108.73.0/24 | APNIC | Valid |
| 103.175.116.0/23 | APNIC | Valid |
| 103.175.116.0/24 | APNIC | Valid |
| 103.175.117.0/24 | APNIC | Valid |
| 160.25.180.0/23 | APNIC | Valid |
| 165.99.132.0/23 | APNIC | Valid |
| 165.99.132.0/24 | APNIC | Valid |
| 165.99.133.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.