Network · data from 2026-11-12
AS10024 LGA Telecom Pte Ltd
Registry name: LGA-AS-SG-AP - LGA International, SG · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS10024, 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.
| 119.75.195.0/24 | Valid | Nonecovered by 119.75.194.0/23 | 671 100% |
| 203.92.101.0/24 | Valid | Nonecovered by 203.92.100.0/23 | 671 100% |
| 27.125.196.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 43.245.16.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 103.3.203.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 119.75.192.0/20 | Valid | Other IRR onlyRADB | 672 100% |
| 203.92.64.0/18 | Valid | Other IRR onlyRADB, REACH | 672 100% |
| 203.92.77.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 2406:a400::/32 | Valid | Other IRR onlyRADB | 636 100% |
| 27.125.196.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 43.245.16.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 43.245.18.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.3.200.0/22 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.3.202.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 119.75.192.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 119.75.192.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 119.75.193.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 119.75.194.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 119.75.196.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 119.75.196.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 119.75.198.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 119.75.199.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 119.75.200.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 119.75.202.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 119.75.206.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.64.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.92.68.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.68.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.70.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.70.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.72.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.72.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.74.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.74.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.76.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.78.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.80.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.80.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.82.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.82.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.83.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.84.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.84.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.92.90.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.91.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.92.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.93.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.94.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.94.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.100.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.100.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.102.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.103.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.104.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.104.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.108.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.108.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.110.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.92.112.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.112.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.120.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.120.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.92.121.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.124.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.126.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.92.126.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.92.127.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 27.125.198.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.3.200.0/23 | Valid | RIR databaseAPNIC | 671 100% |
| 119.75.194.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 119.75.197.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 119.75.200.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 119.75.201.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 119.75.207.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.92.71.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 203.92.75.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 203.92.81.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 203.92.92.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 203.92.95.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 203.92.109.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 203.92.118.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 27.125.199.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 43.245.16.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 43.245.17.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.3.202.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 119.75.204.0/23 | Valid | RIR databaseAPNIC | 670 100% |
| 119.75.204.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 119.75.205.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 203.92.73.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.3.201.0/24 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 119.75.203.0/24 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 203.92.78.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 203.92.124.0/23 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 2406:a400:6000::/35 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2406:a400:8000::/35 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 119.75.198.0/24 | Valid | RIR databaseAPNIC | 134 20% |
| 119.75.202.0/23 | Valid | RIR databaseAPNIC | 134 20% |
| 119.75.206.0/24 | Valid | RIR databaseAPNIC, RADB | 134 20% |
| 203.92.105.0/24 | Valid | RIR databaseAPNIC | 134 20% |
| 27.125.196.0/24 | Valid | RIR databaseAPNIC, RADB | 133 20% |
| 27.125.197.0/24 | Valid | RIR databaseAPNIC, RADB | 133 20% |
| 43.245.19.0/24 | Valid | RIR databaseAPNIC, RADB | 133 20% |
| 203.92.96.0/23 | Valid | RIR databaseAPNIC | 133 20% |
| 203.92.98.0/24 | Valid | RIR databaseAPNIC | 133 20% |
| 203.92.122.0/23 | Valid | RIR databaseAPNIC, RADB | 133 20% |
| 203.92.125.0/24 | Valid | RIR databaseAPNIC | 133 20% |
AS-SET
AS10024'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 49 are in fix.csv.
- Route object: none2
- Route object: RIR7
- Route object: not announced40
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 119.75.195.0/24 | No route object for it. A route object for 119.75.194.0/23 with origin AS10024 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10024 in the RIR database for the space. |
| Route object: none | 203.92.101.0/24 | No route object for it. A route object for 203.92.100.0/23 with origin AS10024 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10024 in the RIR database for the space. |
| Route object: RIR | 27.125.196.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 43.245.16.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.3.203.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.75.192.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.92.64.0/18 | Route object only in RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 203.92.77.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2406:a400::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS10024 whose prefix no peer sees AS10024 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 27.125.198.0/23 | APNIC | Valid |
| 43.245.18.0/24 | APNIC, RADB | Valid |
| 103.3.200.0/24 | APNIC, RADB | Valid |
| 203.92.64.0/23 | APNIC | Valid |
| 203.92.65.0/24 | APNIC | Valid |
| 203.92.66.0/23 | APNIC | Valid |
| 203.92.66.0/24 | APNIC, RADB | Valid |
| 203.92.67.0/24 | APNIC, RADB | Valid |
| 203.92.69.0/24 | APNIC | Valid |
| 203.92.76.0/24 | APNIC | Valid |
| 203.92.79.0/24 | APNIC | Valid |
| 203.92.85.0/24 | APNIC | Valid |
| 203.92.86.0/23 | APNIC | Valid |
| 203.92.86.0/24 | APNIC, RADB | Valid |
| 203.92.87.0/24 | APNIC | Valid |
| 203.92.88.0/23 | APNIC | Valid |
| 203.92.88.0/24 | APNIC, RADB | Valid |
| 203.92.89.0/24 | APNIC | Valid |
| 203.92.90.0/24 | APNIC | Valid |
| 203.92.96.0/24 | APNIC, RADB | Valid |
| 203.92.97.0/24 | APNIC | Valid |
| 203.92.98.0/23 | APNIC | Valid |
| 203.92.99.0/24 | RADB | Valid |
| 203.92.102.0/24 | APNIC | Valid |
| 203.92.106.0/23 | APNIC | Valid |
| 203.92.106.0/24 | APNIC, RADB | Valid |
| 203.92.107.0/24 | APNIC | Valid |
| 203.92.110.0/23 | APNIC, RADB | Valid |
| 203.92.111.0/24 | APNIC, RADB | Valid |
| 203.92.113.0/24 | APNIC, RADB | Valid |
| 203.92.114.0/23 | APNIC, RADB | Valid |
| 203.92.114.0/24 | APNIC, RADB | Valid |
| 203.92.115.0/24 | APNIC, RADB | Valid |
| 203.92.116.0/23 | APNIC | Valid |
| 203.92.116.0/24 | APNIC | Valid |
| 203.92.117.0/24 | APNIC | Valid |
| 203.92.118.0/23 | APNIC | Valid |
| 203.92.119.0/24 | APNIC | Valid |
| 203.92.122.0/24 | APNIC | Valid |
| 203.92.123.0/24 | APNIC, RADB | 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.