Network · data from 2026-11-12
AS142002 SCLOUDPTELTD-AS - Scloud Pte Ltd
Registry name: SCLOUDPTELTD-AS - Scloud Pte Ltd, SG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS142002, 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.
| 165.154.235.189/32 | Invalid: maxLength | Nonecovered by 165.154.235.0/24 | 1 0%low visibility |
| 165.154.255.128/32 | Invalid: maxLength | Nonecovered by 165.154.255.0/24 | 1 0%low visibility |
| 154.83.26.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 154.83.27.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 45.195.11.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 154.198.161.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 154.198.162.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 45.195.8.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 45.195.9.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 45.197.15.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 45.195.10.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 45.197.12.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 45.197.13.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 45.197.14.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 103.43.87.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 134.168.242.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 134.168.243.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 134.168.244.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 139.5.109.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 139.5.111.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.192.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.194.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.195.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.197.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.198.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.204.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 165.154.209.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.212.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.214.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.215.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.216.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.226.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.229.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.233.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.237.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.239.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.242.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.243.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.246.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.248.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.250.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.252.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 165.154.253.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.164.81.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 134.168.240.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 134.168.241.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 139.5.108.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 139.5.110.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 154.198.163.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 165.154.196.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 165.154.201.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 165.154.211.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 165.154.217.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 165.154.224.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 165.154.230.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 165.154.231.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 165.154.232.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 165.154.240.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 165.154.241.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 165.154.244.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 165.154.245.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 165.154.247.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 165.154.251.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 165.154.255.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 134.168.228.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 165.154.193.0/24 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 165.154.200.0/24 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 165.154.203.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 669 99% |
| 165.154.205.0/24 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 165.154.210.0/24 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 165.154.213.0/24 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 165.154.225.0/24 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 165.154.228.0/24 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 165.154.234.0/24 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 165.154.236.0/24 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 165.154.249.0/24 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 165.154.227.0/24 | Valid | RIR databaseAPNIC, RADB | 668 99% |
| 165.154.238.0/24 | Valid | RIR databaseAPNIC, RADB | 668 99% |
| 165.154.202.0/24 | Valid | RIR databaseAPNIC, RADB | 667 99% |
| 165.154.206.0/24 | Valid | RIR databaseAPNIC, RADB | 667 99% |
| 165.154.207.0/24 | Valid | RIR databaseAPNIC, RADB | 667 99% |
| 165.154.235.0/24 | Valid | RIR databaseAPNIC, RADB | 667 99% |
| 165.154.254.0/24 | Valid | RIR databaseAPNIC, RADB | 667 99% |
| 165.154.199.0/24 | Valid | RIR databaseAPNIC, RADB | 666 99% |
| 165.154.208.0/24 | Valid | RIR databaseAPNIC, RADB | 666 99% |
AS-SET
AS142002 isn't in PeeringDB, where networks name their 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 51 are in fix.csv.
- ROA: maxLength2
- Route object: none2
- Route object: RIR12
- Route object: not announced35
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 165.154.235.189/32 | ROA 165.154.224.0/19 AS142002 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 165.154.235.189/32. |
| Route object: none | 165.154.235.189/32 | No route object for it. A route object for 165.154.235.0/24 with origin AS142002 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS142002 in the RIR database for the space. |
| ROA: maxLength | 165.154.255.128/32 | ROA 165.154.224.0/19 AS142002 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 165.154.255.128/32. |
| Route object: none | 165.154.255.128/32 | No route object for it. A route object for 165.154.255.0/24 with origin AS142002 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS142002 in the RIR database for the space. |
| Route object: RIR | 154.83.26.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 154.83.27.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.195.11.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 154.198.161.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 154.198.162.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.195.8.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.195.9.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.197.15.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.195.10.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.197.12.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.197.13.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.197.14.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS142002 whose prefix no peer sees AS142002 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.197.12.0/22 | AFRINIC | No ROA |
| 134.168.240.0/21 | RIPE | Valid |
| 134.168.248.0/21 | RIPE | Valid |
| 154.198.160.0/24 | RADB | Valid |
| 165.154.224.0/19 | APNIC, RADB | Valid |
| 165.154.224.0/20 | APNIC | Valid |
| 165.154.224.0/21 | APNIC | Valid |
| 165.154.224.0/22 | APNIC | Valid |
| 165.154.224.0/23 | APNIC | Valid |
| 165.154.226.0/23 | APNIC | Valid |
| 165.154.228.0/22 | APNIC | Valid |
| 165.154.228.0/23 | APNIC | Valid |
| 165.154.230.0/23 | APNIC | Valid |
| 165.154.232.0/21 | APNIC | Valid |
| 165.154.232.0/22 | APNIC | Valid |
| 165.154.232.0/23 | APNIC | Valid |
| 165.154.234.0/23 | APNIC | Valid |
| 165.154.236.0/22 | APNIC | Valid |
| 165.154.236.0/23 | APNIC | Valid |
| 165.154.238.0/23 | APNIC | Valid |
| 165.154.240.0/20 | APNIC | Valid |
| 165.154.240.0/21 | APNIC | Valid |
| 165.154.240.0/22 | APNIC | Valid |
| 165.154.240.0/23 | APNIC | Valid |
| 165.154.242.0/23 | APNIC | Valid |
| 165.154.244.0/22 | APNIC | Valid |
| 165.154.244.0/23 | APNIC | Valid |
| 165.154.246.0/23 | APNIC | Valid |
| 165.154.248.0/21 | APNIC | Valid |
| 165.154.248.0/22 | APNIC | Valid |
| 165.154.248.0/23 | APNIC | Valid |
| 165.154.250.0/23 | APNIC | Valid |
| 165.154.252.0/22 | APNIC | Valid |
| 165.154.252.0/23 | APNIC | Valid |
| 165.154.254.0/23 | 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.