Network · data from 2026-11-12
AS150696 Ms Online
Registry name: MS7-AS-AP - Ms Online, BD · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS150696, 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.245.96.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 123.253.96.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 103.60.204.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.60.204.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.60.205.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 144.48.249.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 163.61.138.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 2001:df5:1740::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:cf60::/32 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:cf60:fb::/48 | Valid | RIR databaseAPNIC | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS150696: AS150696:AS-IX. 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 (AS150696 isn't in the set, or no route object for AS150696 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 | AS150696 in it | Not covered |
|---|---|---|---|---|---|
| AS150696:AS-IX | APNIC | 80 | 1 | Yes | 2 |
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 4 are in fix.csv.
- ROA: origin2
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 103.245.96.0/24 | ROAs covering it name AS38031, AS58803, AS141731, not AS150696. If AS150696 should announce it, add a ROA for AS150696. |
| Route object: none | 103.245.96.0/24 | Route objects for it name AS141731. Add a route object with origin AS150696 in the RIR database for the space. |
| ROA: origin | 123.253.96.0/24 | ROAs covering it name AS141731, AS150744, not AS150696. If AS150696 should announce it, add a ROA for AS150696. |
| Route object: none | 123.253.96.0/24 | Route objects for it name AS141731, AS150744. Add a route object with origin AS150696 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS150696 is announced.
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.