Network · data from 2026-11-12
AS148000 1.10.10.10 - Indian Public DNS (AS148000)
Registry name: BHARAT-PUBLIC-DNS - BHARAT PUBLIC DNS (1.10.10.10), IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS148000, 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.
| 160.202.195.0/24 | Invalid: origin | Other origin only | 137 20% |
| 160.202.197.0/24 | Invalid: origin | Other origin only | 6 1%low visibility |
| 240a:eff3::/32 | Invalid: maxLength | Other origin onlycovered by 240a:e000::/20 | 92 14% |
| 240a:eabc:d00d::/48 | Valid | Other origin onlycovered by 240a:eabc::/32 | 636 100% |
| 160.202.194.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 1.10.10.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 36.50.50.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.68.48.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.68.49.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 160.202.196.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 160.202.200.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 160.202.201.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 36.50.36.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 45.249.126.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 2001:de2::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2409::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2409:1::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2409:e:eb::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240a:eabc:abcd::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 240a:eff2::/32 | Valid | RIR databaseAPNIC | 636 100% |
| 240a:eff8::/32 | Valid | RIR databaseAPNIC | 636 100% |
| 240a:eff9::/32 | Valid | RIR databaseAPNIC | 636 100% |
| 240a:eff4::/32 | Valid | RIR databaseAPNIC | 635 100% |
| 240a:eff5::/32 | Valid | RIR databaseAPNIC | 635 100% |
| 240a:e000::/20 | Valid | RIR databaseAPNIC | 634 100% |
AS-SET
AS148000's PeeringDB record names no 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 35 are in fix.csv.
- ROA: origin2
- ROA: maxLength1
- Route object: none4
- Route object: not announced28
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 160.202.195.0/24 | ROAs covering it name AS142501, AS148001, not AS148000. If AS148000 should announce it, add a ROA for AS148000. |
| Route object: none | 160.202.195.0/24 | Route objects for it name AS142501, AS148001. Add a route object with origin AS148000 in the RIR database for the space. |
| ROA: origin | 160.202.197.0/24 | ROAs covering it name AS142501, AS148001, AS148002, not AS148000. If AS148000 should announce it, add a ROA for AS148000. |
| Route object: none | 160.202.197.0/24 | Route objects for it name AS142501, AS148001, AS148002. Add a route object with origin AS148000 in the RIR database for the space. |
| ROA: maxLength | 240a:eff3::/32 | ROA 240a:e000::/20 AS148000 has maxLength 20; the route is a /32. Raise the maxLength, or add a ROA for 240a:eff3::/32. |
| Route object: none | 240a:eff3::/32 | Route objects for it name AS148001. A route object for 240a:e000::/20 with origin AS148000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS148000 in the RIR database for the space. |
| Route object: none | 240a:eabc:d00d::/48 | Route objects for it name AS9885. A route object for 240a:eabc::/32 with origin AS148000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS148000 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS148000 whose prefix no peer sees AS148000 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 27.0.252.0/22 | APNIC | Valid |
| 43.246.104.0/22 | APNIC | Invalid: origin |
| 45.124.224.0/22 | APNIC | Invalid: origin |
| 45.124.228.0/22 | APNIC | Invalid: origin |
| 45.124.232.0/22 | APNIC | Invalid: origin |
| 45.124.236.0/22 | APNIC | Invalid: origin |
| 45.249.127.0/24 | APNIC | Valid |
| 45.250.52.0/22 | APNIC | Valid |
| 45.250.52.0/23 | APNIC | Valid |
| 45.250.52.0/24 | APNIC | Valid |
| 45.250.53.0/24 | APNIC | Valid |
| 45.250.54.0/23 | APNIC | Valid |
| 45.250.54.0/24 | APNIC | Valid |
| 45.250.55.0/24 | APNIC | Valid |
| 103.193.48.0/22 | APNIC | No ROA |
| 103.193.52.0/22 | APNIC | No ROA |
| 103.193.56.0/22 | APNIC | No ROA |
| 103.193.60.0/22 | APNIC | No ROA |
| 160.202.192.0/24 | APNIC | Valid |
| 160.202.193.0/24 | APNIC | Valid |
| 160.202.198.0/24 | APNIC | Valid |
| 2409::/32 | APNIC | Valid |
| 2409::/40 | APNIC | Valid |
| 2409:e:ed::/48 | APNIC | Valid |
| 240a:eabc::/32 | APNIC | Valid |
| 240a:eff0::/32 | APNIC | Valid |
| 240a:eff1::/32 | APNIC | Valid |
| 240a:eff6::/32 | 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.