Network · data from 2026-11-12
AS141031 Connect Communications pvt ltd
Registry name: CONNECT-AS-AP - Connect Communication, PK · PeeringDB
27IPv4 routes
100.0% RPKI valid · 100.0% with a route object
10IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
0 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
64Route objects not announced
registered with origin AS141031, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS141031, 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.
| 39.34.168.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 39.34.169.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 39.34.170.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 39.34.171.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 39.34.172.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 39.34.173.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 39.34.174.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 39.34.175.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 59.103.216.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 59.103.217.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 59.103.218.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 59.103.219.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 59.103.221.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 59.103.222.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 59.103.223.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 111.88.0.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 111.88.1.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 113.203.192.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 113.203.194.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 113.203.196.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 113.203.197.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 113.203.198.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 113.203.199.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 118.103.224.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 118.103.225.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 151.123.232.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 59.103.220.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 2406:d00:ee00::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2406:d00:ee01::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2406:d00:ee02::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2406:d00:ee03::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2406:d00:ee04::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2406:d00:ee05::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2406:d00:ee0b::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2406:d00:ee0d::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2406:d00:ee0f::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2406:d00:ee55::/48 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
AS141031'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 64 are in fix.csv.
- Route object: not announced64
Route objects not announced
Route objects with origin AS141031 whose prefix no peer sees AS141031 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 39.34.164.0/24 | APNIC | Valid |
| 39.34.165.0/24 | APNIC | Valid |
| 39.34.166.0/24 | APNIC | Valid |
| 39.34.167.0/24 | APNIC | Valid |
| 39.34.168.0/21 | APNIC | Valid |
| 39.34.168.0/22 | APNIC | Valid |
| 39.34.168.0/23 | APNIC | Valid |
| 39.34.170.0/23 | APNIC | Valid |
| 39.34.172.0/22 | APNIC | Valid |
| 39.34.172.0/23 | APNIC | Valid |
| 39.34.174.0/23 | APNIC | Valid |
| 39.34.184.0/21 | APNIC | Valid |
| 39.34.184.0/22 | APNIC | Valid |
| 39.34.184.0/23 | APNIC | Valid |
| 39.34.184.0/24 | APNIC, RADB | Valid |
| 39.34.185.0/24 | APNIC, RADB | Valid |
| 39.34.186.0/23 | APNIC | Valid |
| 39.34.186.0/24 | APNIC, RADB | Valid |
| 39.34.187.0/24 | APNIC, RADB | Valid |
| 39.34.188.0/22 | APNIC | Valid |
| 39.34.188.0/23 | APNIC | Valid |
| 39.34.188.0/24 | APNIC, RADB | Valid |
| 39.34.189.0/24 | APNIC, RADB | Valid |
| 39.34.190.0/23 | APNIC | Valid |
| 39.34.190.0/24 | APNIC, RADB | Valid |
| 39.34.191.0/24 | APNIC, RADB | Valid |
| 59.103.208.0/20 | APNIC | Valid |
| 59.103.208.0/21 | APNIC | Valid |
| 59.103.208.0/22 | APNIC | Valid |
| 59.103.208.0/23 | APNIC | Valid |
| 59.103.208.0/24 | APNIC | Valid |
| 59.103.209.0/24 | APNIC | Valid |
| 59.103.210.0/23 | APNIC | Valid |
| 59.103.210.0/24 | APNIC | Valid |
| 59.103.211.0/24 | APNIC | Valid |
| 59.103.212.0/22 | APNIC | Valid |
| 59.103.212.0/23 | APNIC | Valid |
| 59.103.212.0/24 | APNIC | Valid |
| 59.103.213.0/24 | APNIC | Valid |
| 59.103.214.0/23 | APNIC | Valid |
| 59.103.214.0/24 | APNIC | Valid |
| 59.103.215.0/24 | APNIC | Valid |
| 59.103.216.0/21 | APNIC | Valid |
| 59.103.216.0/22 | APNIC | Valid |
| 59.103.216.0/23 | APNIC | Valid |
| 59.103.218.0/23 | APNIC | Valid |
| 59.103.220.0/22 | APNIC | Valid |
| 59.103.220.0/23 | APNIC | Valid |
| 59.103.222.0/23 | APNIC | Valid |
| 119.152.40.0/24 | APNIC | Valid |
| 119.152.41.0/24 | APNIC | Valid |
| 119.152.42.0/24 | APNIC | Valid |
| 119.152.43.0/24 | APNIC | Valid |
| 119.152.44.0/24 | APNIC | Valid |
| 151.123.232.0/25 | APNIC | Valid |
| 151.123.232.0/26 | APNIC | Valid |
| 151.123.232.64/26 | APNIC | Valid |
| 151.123.232.128/25 | APNIC | Valid |
| 151.123.232.128/26 | APNIC | Valid |
| 151.123.232.192/26 | APNIC | Valid |
| 2406:d00:ee06::/48 | APNIC | Valid |
| 2406:d00:ee0a::/48 | APNIC | Valid |
| 2406:d00:ee0c::/48 | APNIC | Valid |
| 2406:d00:ee0e::/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.