Network · data from 2026-11-12
AS138298 A2j Data Services
Registry name: A2JDATA-AS-IN - A2j Data Services Pvt. Ltd., IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS138298, 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.87.46.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 103.116.86.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 103.174.104.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 103.87.44.0/24 | Valid | Other origin only | 672 100% |
| 103.153.227.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.158.230.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.158.231.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.165.165.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.215.201.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.215.203.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 2001:df1:37c0::/48 | Valid | RIR databaseAPNIC | 2 0%low visibility |
| 2001:df1:5e40::/48 | Valid | RIR databaseAPNIC | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS138298: AS138298. 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 (AS138298 isn't in the set, or no route object for AS138298 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 | AS138298 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS138298 | A single AS number, not a set: AS138298 (this network), 15 route objects. | |||||
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 8 are in fix.csv.
- ROA: none3
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.87.46.0/24 | No ROA covers it. Add a ROA for AS138298, maxLength 24. |
| ROA: none | 103.116.86.0/24 | No ROA covers it. Add a ROA for AS138298, maxLength 24. |
| ROA: none | 103.174.104.0/24 | No ROA covers it. Add a ROA for AS138298, maxLength 24. |
| Route object: none | 103.87.44.0/24 | Route objects for it name AS134316, AS153953. Add a route object with origin AS138298 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS138298 whose prefix no peer sees AS138298 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.158.230.0/23 | APNIC | Valid |
| 103.174.105.0/24 | APNIC | Invalid: origin |
| 103.215.200.0/24 | APNIC | Invalid: origin |
| 2001:df1:5ec0::/48 | 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.