Network · data from 2026-11-12
AS150671 MANSOORAH TELECOMMUNICATIONS
Registry name: MTCL-AS-AP - Mansoorah Telecommunications Company Pvt Ltd, PK · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS150671, 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.
| 66.102.122.0/24 | No ROA | None | 44 7%low visibility |
| 66.102.124.0/24 | No ROA | None | 1 0%low visibility |
| 147.90.96.0/24 | Valid | Other origin onlycovered by 147.90.96.0/21 | 673 100% |
| 147.90.97.0/24 | Valid | Other origin onlycovered by 147.90.96.0/21 | 673 100% |
| 147.90.98.0/24 | Valid | Other origin onlycovered by 147.90.96.0/21 | 673 100% |
| 147.90.99.0/24 | Valid | Other origin onlycovered by 147.90.96.0/21 | 672 100% |
| 147.90.100.0/24 | Valid | Other origin onlycovered by 147.90.96.0/21 | 672 100% |
| 147.90.102.0/24 | Valid | Other origin onlycovered by 147.90.96.0/21 | 672 100% |
| 147.90.103.0/24 | Valid | Other origin onlycovered by 147.90.96.0/21 | 672 100% |
| 103.52.34.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 175.29.56.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 175.29.57.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 175.29.58.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.52.35.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 175.29.59.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 175.29.60.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 175.29.61.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 175.29.63.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 175.29.62.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 2001:df1:ac40::/48 | Valid | RIR databaseAPNIC | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS150671: AS150671. 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 (AS150671 isn't in the set, or no route object for AS150671 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 | AS150671 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS150671 | A single AS number, not a set: AS150671 (this network), 22 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 22 are in fix.csv.
- ROA: none2
- Route object: none9
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 66.102.122.0/24 | No ROA covers it. Add a ROA for AS150671, maxLength 24. |
| Route object: none | 66.102.122.0/24 | No route object for it. Add a route object with origin AS150671 in the RIR database for the space. |
| ROA: none | 66.102.124.0/24 | No ROA covers it. Add a ROA for AS150671, maxLength 24. |
| Route object: none | 66.102.124.0/24 | No route object for it. Add a route object with origin AS150671 in the RIR database for the space. |
| Route object: none | 147.90.96.0/24 | Route objects for it name AS149280. A route object for 147.90.96.0/21 with origin AS150671 covers it (filters allowing more-specifics accept it). Add a route object with origin AS150671 in the RIR database for the space. |
| Route object: none | 147.90.97.0/24 | Route objects for it name AS149280. A route object for 147.90.96.0/21 with origin AS150671 covers it (filters allowing more-specifics accept it). Add a route object with origin AS150671 in the RIR database for the space. |
| Route object: none | 147.90.98.0/24 | Route objects for it name AS149280. A route object for 147.90.96.0/21 with origin AS150671 covers it (filters allowing more-specifics accept it). Add a route object with origin AS150671 in the RIR database for the space. |
| Route object: none | 147.90.99.0/24 | Route objects for it name AS149280. A route object for 147.90.96.0/21 with origin AS150671 covers it (filters allowing more-specifics accept it). Add a route object with origin AS150671 in the RIR database for the space. |
| Route object: none | 147.90.100.0/24 | Route objects for it name AS149280. A route object for 147.90.96.0/21 with origin AS150671 covers it (filters allowing more-specifics accept it). Add a route object with origin AS150671 in the RIR database for the space. |
| Route object: none | 147.90.102.0/24 | Route objects for it name AS149280. A route object for 147.90.96.0/21 with origin AS150671 covers it (filters allowing more-specifics accept it). Add a route object with origin AS150671 in the RIR database for the space. |
| Route object: none | 147.90.103.0/24 | Route objects for it name AS149280. A route object for 147.90.96.0/21 with origin AS150671 covers it (filters allowing more-specifics accept it). Add a route object with origin AS150671 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS150671 whose prefix no peer sees AS150671 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.52.34.0/23 | RADB | No ROA |
| 103.174.194.0/23 | RADB | No ROA |
| 147.90.96.0/21 | RADB, RIPE | Valid |
| 175.29.56.0/21 | APNIC, RADB | Valid |
| 175.29.56.0/22 | APNIC | Valid |
| 175.29.56.0/23 | APNIC | Valid |
| 175.29.58.0/23 | APNIC | Valid |
| 175.29.60.0/22 | APNIC | Valid |
| 175.29.60.0/23 | APNIC | Valid |
| 175.29.62.0/23 | APNIC | Valid |
| 2a13:9500:159::/48 | RIPE | 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.