Network · data from 2026-11-12
AS151704 Bharat Datacenter
Registry name: BHARATDC-AS - BHARAT DATACENTER, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS151704, 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.
| 81.29.148.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 95.135.161.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 178.92.73.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 91.236.119.0/24 | No ROA | None | 2 0%low visibility |
| 103.72.102.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 103.204.22.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 31.42.125.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 31.56.59.0/24 | Valid | RIR databaseRADB, RIPE | 668 99% |
| 85.209.161.0/24 | Valid | RIR databaseRADB, RIPE | 668 99% |
| 87.76.217.0/24 | Valid | RIR databaseRADB, RIPE | 668 99% |
| 87.232.72.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 89.251.16.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 95.134.165.0/24 | Valid | RIR databaseRADB, RIPE | 668 99% |
| 103.144.36.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 103.190.92.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 103.190.93.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 103.243.119.0/24 | Valid | RIR databaseAPNIC, RADB | 668 99% |
| 109.122.56.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 151.242.176.0/24 | Valid | RIR databaseRADB, RIPE | 668 99% |
| 151.242.178.0/24 | Valid | RIR databaseRADB, RIPE | 668 99% |
| 151.242.184.0/24 | Valid | RIR databaseRADB, RIPE | 668 99% |
| 151.242.187.0/24 | Valid | RIR databaseRADB, RIPE | 668 99% |
| 157.10.98.0/24 | Valid | RIR databaseALTDB, APNIC | 668 99% |
| 157.10.99.0/24 | Valid | RIR databaseALTDB, APNIC | 668 99% |
| 167.104.222.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 178.92.122.0/24 | Valid | RIR databaseRADB, RIPE | 668 99% |
| 178.94.176.0/24 | Valid | RIR databaseRADB, RIPE | 668 99% |
| 185.67.20.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 191.219.28.0/24 | Valid | RIR databaseRADB, RIPE | 668 99% |
| 222.167.207.0/24 | Valid | RIR databaseRADB, RIPE | 668 99% |
| 168.222.105.0/24 | Valid | RIR databaseRADB, RIPE | 667 99% |
| 194.31.164.0/24 | Valid | RIR databaseRIPE | 667 99% |
| 2001:df3:5cc0::/48 | Valid | RIR databaseALTDB, APNIC | 629 99% |
| 2a0b:4e07:1c00::/48 | Valid | RIR databaseRIPE | 629 99% |
| 2a0b:4e07:1c01::/48 | Valid | RIR databaseRIPE | 629 99% |
| 2a0b:4e07:1c02::/48 | Valid | RIR databaseRIPE | 629 99% |
| 2a0b:4e07:1c04::/48 | Valid | RIR databaseRIPE | 629 99% |
| 2a0b:4e07:1c05::/48 | Valid | RIR databaseRIPE | 629 99% |
| 87.76.149.0/24 | Valid | RIR databaseRADB, RIPE | 400 59% |
AS-SET
PeeringDB's irr_as_set for AS151704: AS151704:AS-CUSTOMERS. 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 (AS151704 isn't in the set, or no route object for AS151704 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 | AS151704 in it | Not covered |
|---|---|---|---|---|---|
| AS151704:AS-CUSTOMERS | APNIC | 11 | 1 | Yes | 4 |
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 19 are in fix.csv.
- ROA: origin3
- ROA: none1
- Route object: none4
- Route object: RIR2
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 81.29.148.0/24 | ROAs covering it name AS198566, not AS151704. If AS151704 should announce it, add a ROA for AS151704. |
| Route object: none | 81.29.148.0/24 | Route objects for it name AS198566. Add a route object with origin AS151704 in the RIR database for the space. |
| ROA: origin | 95.135.161.0/24 | ROAs covering it name AS834, AS20473, not AS151704. If AS151704 should announce it, add a ROA for AS151704. |
| Route object: none | 95.135.161.0/24 | Route objects for it name AS834. Add a route object with origin AS151704 in the RIR database for the space. |
| ROA: origin | 178.92.73.0/24 | ROAs covering it name AS20473, AS215228, not AS151704. If AS151704 should announce it, add a ROA for AS151704. |
| Route object: none | 178.92.73.0/24 | Route objects for it name AS215228. Add a route object with origin AS151704 in the RIR database for the space. |
| ROA: none | 91.236.119.0/24 | No ROA covers it. Add a ROA for AS151704, maxLength 24. |
| Route object: none | 91.236.119.0/24 | No route object for it. Add a route object with origin AS151704 in the RIR database for the space. |
| Route object: RIR | 103.72.102.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.204.22.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS151704 whose prefix no peer sees AS151704 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.170.58.0/23 | APNIC | Invalid: origin |
| 103.170.58.0/24 | APNIC | Valid |
| 103.170.59.0/24 | APNIC | Valid |
| 103.190.92.0/23 | APNIC | Valid |
| 103.200.75.0/24 | APNIC | Valid |
| 157.10.98.0/23 | APNIC | Valid |
| 191.44.86.0/24 | RADB, RIPE | Valid |
| 2a0b:4e07:1c00::/38 | RIPE | No ROA |
| 2a14:7583:d003::/48 | RIPE | 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.