Network · data from 2026-11-12
AS45150 MPHASIS-BGM-AS - Mphasis Ltd,
Registry name: MPHASIS-BGM-AS - Mphasis Ltd,, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS45150, 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.
| 203.12.223.0/24 | Invalid: maxLength | RIR databaseAPNIC | 18 3%low visibility |
| 103.9.225.0/24 | No ROA | RIR databaseAPNIC | 673 100% |
| 103.7.3.0/24 | No ROA | RIR databaseAPNIC, RADB | 670 100% |
| 103.246.49.0/24 | Valid | RIR databaseAPNIC | 673 100% |
AS-SET
AS45150 isn't in PeeringDB, where networks name their 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 5 are in fix.csv.
- ROA: maxLength1
- ROA: none2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 203.12.223.0/24 | ROA 203.12.222.0/23 AS45150 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 203.12.223.0/24. |
| ROA: none | 103.9.225.0/24 | No ROA covers it. Add a ROA for AS45150, maxLength 24. |
| ROA: none | 103.7.3.0/24 | No ROA covers it. Add a ROA for AS45150, maxLength 24. |
Route objects not announced
Route objects with origin AS45150 whose prefix no peer sees AS45150 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.246.48.0/23 | APNIC | Valid |
| 203.12.222.0/23 | 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.