Network · data from 2026-11-12
AS135003 Multan Cable & Internet Services
Registry name: MULTAN-AS-AP - Multan Cable & Internet Services (Pvt) Ltd, PK · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135003, 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.
| 2400:bf40:4::/48 | No ROA | Nonecovered by 2400:bf40::/32 | 629 99% |
| 2400:bf40::/32 | No ROA | Other IRR onlyRADB | 630 99% |
| 103.86.133.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.86.135.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.86.132.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.86.134.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.6.208.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.6.209.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.6.210.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.6.211.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS135003: APNIC::AS135003:AS-MISPL. 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 (AS135003 isn't in the set, or no route object for AS135003 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 | AS135003 in it | Not covered |
|---|---|---|---|---|---|
| APNIC::AS135003:AS-MISPL | APNIC | 0 | 1 | No | 10 |
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 13 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: RIR1
- AS-SET: own ASN1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2400:bf40:4::/48 | No ROA covers it. Add a ROA for AS135003, maxLength 48. |
| Route object: none | 2400:bf40:4::/48 | No route object for it. A route object for 2400:bf40::/32 with origin AS135003 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135003 in the RIR database for the space. |
| ROA: none | 2400:bf40::/32 | No ROA covers it. Add a ROA for AS135003, maxLength 32. |
| Route object: RIR | 2400:bf40::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: own ASN | APNIC::AS135003:AS-MISPL | AS135003 isn't in AS135003:AS-MISPL (APNIC) once expanded. Add AS135003 to it. |
Route objects not announced
Route objects with origin AS135003 whose prefix no peer sees AS135003 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.86.132.0/22 | APNIC, RADB | Valid |
| 103.86.132.0/23 | APNIC | Valid |
| 103.86.134.0/23 | APNIC | Valid |
| 203.6.208.0/22 | APNIC, RADB | Valid |
| 203.6.208.0/23 | APNIC | Valid |
| 203.6.210.0/23 | APNIC | Valid |
| 2400:bf40:1::/48 | APNIC | Valid |
| 2400:bf40:2::/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.