Network · data from 2026-11-12
AS136902 Alegra Communication
Registry name: ALEGRA-AS-IN - Alegra Communication Private Limited, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS136902, 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.175.54.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 103.175.55.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 43.231.205.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.98.85.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.119.208.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.119.209.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.142.120.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.142.121.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.150.52.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.150.53.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.157.182.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.157.183.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.167.128.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.167.129.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 2401:24a0::/34 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:24a0:4000::/34 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS136902: AS136902:AS-ALEGRA-IN. 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 (AS136902 isn't in the set, or no route object for AS136902 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 | AS136902 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS136902:AS-ALEGRA-IN | In no IRR database read today. | |||||
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 7 are in fix.csv.
- ROA: none2
- AS-SET: not found1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.175.54.0/24 | No ROA covers it. Add a ROA for AS136902, maxLength 24. |
| ROA: none | 103.175.55.0/24 | No ROA covers it. Add a ROA for AS136902, maxLength 24. |
| AS-SET: not found | AS136902:AS-ALEGRA-IN | PeeringDB names AS136902:AS-ALEGRA-IN; no IRR database read has it. |
Route objects not announced
Route objects with origin AS136902 whose prefix no peer sees AS136902 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.167.128.0/23 | APNIC | Valid |
| 2001:df1:4080::/48 | APNIC | Valid |
| 2401:24a0:8000::/34 | APNIC | Valid |
| 2401:24a0:c000::/34 | 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.