Network · data from 2026-11-12
AS55501 Web Concepts
Registry name: CONNECTEL-PK - 141-143 Maulana Shaukat Ali Road, PK · PeeringDB
42IPv4 routes
100.0% RPKI valid · 97.6% with a route object
19IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
1 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
17Route objects not announced
registered with origin AS55501, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS55501, 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.
| 202.166.170.0/24 | Valid | Nonecovered by 202.166.170.0/23 | 673 100% |
| 103.105.208.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.105.209.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.105.210.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.105.210.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.105.211.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.155.4.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.155.4.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.155.5.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.155.63.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.174.99.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.178.26.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.225.220.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.225.221.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.225.222.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.225.223.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 160.250.96.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.166.160.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.166.161.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.166.162.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.166.162.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.166.163.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.166.164.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.166.164.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.166.166.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.166.166.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.166.167.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.166.168.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.166.169.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.166.170.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 202.166.171.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.166.172.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.166.172.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.166.173.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.166.174.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.166.175.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.124.60.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.225.220.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 202.166.160.0/23 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 202.166.168.0/22 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 202.166.174.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 202.166.165.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 2401:ea00:a::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:ea00:b::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:ea00:c::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:ea00:d::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:ea00:e::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:ea00:f::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:ea00:11::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:ea00:12::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:ea00:13::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:ea00:2::/48 | Valid | RIR databaseAPNIC | 630 99% |
| 2401:ea00:3::/48 | Valid | RIR databaseAPNIC | 630 99% |
| 2401:ea00:4::/48 | Valid | RIR databaseAPNIC | 630 99% |
| 2401:ea00:5::/48 | Valid | RIR databaseAPNIC | 630 99% |
| 2401:ea00:6::/48 | Valid | RIR databaseAPNIC | 630 99% |
| 2401:ea00:7::/48 | Valid | RIR databaseAPNIC | 630 99% |
| 2401:ea00:8::/48 | Valid | RIR databaseAPNIC | 630 99% |
| 2401:ea00:9::/48 | Valid | RIR databaseAPNIC | 630 99% |
| 2401:ea00:10::/48 | Valid | RIR databaseAPNIC | 630 99% |
| 2401:ea00:20::/48 | Valid | RIR databaseAPNIC | 630 99% |
AS-SET
AS55501'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 18 are in fix.csv.
- Route object: none1
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 202.166.170.0/24 | No route object for it. A route object for 202.166.170.0/23 with origin AS55501 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55501 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS55501 whose prefix no peer sees AS55501 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 58.84.31.0/24 | APNIC | Valid |
| 103.72.65.0/24 | RADB | No ROA |
| 103.105.208.0/22 | APNIC | Valid |
| 103.105.208.0/23 | APNIC | Valid |
| 103.249.155.0/24 | APNIC | Valid |
| 160.250.97.0/24 | APNIC | Valid |
| 203.124.56.0/24 | APNIC | Valid |
| 203.124.57.0/24 | APNIC | Valid |
| 203.124.59.0/24 | APNIC | Valid |
| 203.170.66.0/24 | APNIC | Valid |
| 203.170.67.0/24 | APNIC | Valid |
| 203.170.68.0/24 | APNIC | Valid |
| 210.56.6.0/24 | APNIC | Valid |
| 210.56.7.0/24 | APNIC | Valid |
| 2401:ea00::/48 | APNIC | Valid |
| 2401:ea00:1::/48 | APNIC | Valid |
| 2401:ea00:25::/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.