Network · data from 2026-11-12
AS55453 Skytelecom Pakistan
Registry name: SKYTELECOM-AS-PK - House # 39 Street 38 F10 /4, PK · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS55453, 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.
| 180.178.168.0/24 | Invalid: maxLength | None | 54 8%low visibility |
| 180.178.169.0/24 | Invalid: maxLength | None | 54 8%low visibility |
| 180.178.170.0/24 | Invalid: maxLength | None | 54 8%low visibility |
| 180.178.171.0/24 | Invalid: maxLength | Other origin only | 54 8%low visibility |
| 202.92.22.0/24 | Valid | None | 673 100% |
| 103.20.1.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.20.3.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.151.26.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 27.54.120.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.54.121.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.54.122.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.20.0.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.20.2.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 113.203.242.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 113.203.243.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 137.59.192.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 137.59.193.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 137.59.194.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 137.59.195.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 27.54.123.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 223.29.225.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 223.29.235.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 2407:1b00::/34 | Valid | RIR databaseAPNIC | 634 100% |
| 2407:1b00:4000::/34 | Valid | RIR databaseAPNIC | 634 100% |
| 2407:1b00:8000::/34 | Valid | RIR databaseAPNIC | 634 100% |
AS-SET
AS55453's PeeringDB record names no 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 13 are in fix.csv.
- ROA: maxLength4
- Route object: none5
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 180.178.168.0/24 | ROA 180.178.168.0/22 AS55453 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 180.178.168.0/24. |
| Route object: none | 180.178.168.0/24 | No route object for it. Add a route object with origin AS55453 in the RIR database for the space. |
| ROA: maxLength | 180.178.169.0/24 | ROA 180.178.168.0/22 AS55453 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 180.178.169.0/24. |
| Route object: none | 180.178.169.0/24 | No route object for it. Add a route object with origin AS55453 in the RIR database for the space. |
| ROA: maxLength | 180.178.170.0/24 | ROA 180.178.168.0/22 AS55453 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 180.178.170.0/24. |
| Route object: none | 180.178.170.0/24 | No route object for it. Add a route object with origin AS55453 in the RIR database for the space. |
| ROA: maxLength | 180.178.171.0/24 | ROA 180.178.168.0/22 AS55453 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 180.178.171.0/24. |
| Route object: none | 180.178.171.0/24 | Route objects for it name AS136969, AS197328. Add a route object with origin AS55453 in the RIR database for the space. |
| Route object: none | 202.92.22.0/24 | No route object for it. Add a route object with origin AS55453 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS55453 whose prefix no peer sees AS55453 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 139.190.236.0/24 | RADB | No ROA |
| 139.190.238.0/24 | RADB | No ROA |
| 139.190.239.0/24 | RADB | No ROA |
| 2407:1b00: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.