Network · data from 2026-11-12
AS132827 GATEWAY-AS-AP - GATEWAY INC
Registry name: GATEWAY-AS-AP - GATEWAY INC, JP · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS132827, 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.
| 216.179.204.0/23 | No ROA | None | 2 0%low visibility |
| 216.179.224.0/23 | No ROA | None | 2 0%low visibility |
| 103.27.80.0/22 | No ROA | None | 1 0%low visibility |
| 103.42.100.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 103.42.101.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 103.42.102.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 103.42.103.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 162.35.64.0/19 | No ROA | Other IRR onlyRADB | 670 100% |
| 43.251.48.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 43.251.49.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 101.0.8.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 101.0.9.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 101.0.10.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 101.0.11.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.3.16.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.3.17.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.3.19.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.6.240.0/22 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.10.38.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.10.236.0/22 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.11.6.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 103.11.236.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.11.238.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.13.45.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.13.46.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.16.36.0/22 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.23.220.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.23.223.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.27.68.0/22 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.28.168.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.28.169.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.28.170.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.30.52.0/22 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.44.128.0/22 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.246.178.0/23 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.246.254.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 123.253.164.0/22 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.5.249.0/24 | Valid | RIR databaseAPNIC, RADB | 667 99% |
| 43.231.223.0/24 | Valid | RIR databaseAPNIC | 665 99% |
| 43.249.92.0/24 | Valid | RIR databaseAPNIC, RADB | 665 99% |
| 43.249.93.0/24 | Valid | RIR databaseAPNIC, RADB | 665 99% |
| 43.249.94.0/23 | Valid | RIR databaseAPNIC, RADB | 665 99% |
| 103.20.158.0/24 | Valid | RIR databaseAPNIC | 665 99% |
| 27.123.208.0/22 | Valid | RIR databaseAPNIC, RADB | 664 99% |
| 43.229.240.0/22 | Valid | RIR databaseAPNIC, RADB | 664 99% |
| 43.248.40.0/22 | Valid | RIR databaseAPNIC, RADB | 664 99% |
| 103.37.118.0/24 | Valid | RIR databaseAPNIC, RADB | 664 99% |
| 103.249.72.0/22 | Valid | RIR databaseAPNIC, RADB | 664 99% |
AS-SET
AS132827 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 25 are in fix.csv.
- ROA: none8
- Route object: none3
- Route object: RIR5
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 216.179.204.0/23 | No ROA covers it. Add a ROA for AS132827, maxLength 23. |
| Route object: none | 216.179.204.0/23 | No route object for it. Add a route object with origin AS132827 in the RIR database for the space. |
| ROA: none | 216.179.224.0/23 | No ROA covers it. Add a ROA for AS132827, maxLength 23. |
| Route object: none | 216.179.224.0/23 | No route object for it. Add a route object with origin AS132827 in the RIR database for the space. |
| ROA: none | 103.27.80.0/22 | No ROA covers it. Add a ROA for AS132827, maxLength 22. |
| Route object: none | 103.27.80.0/22 | No route object for it. Add a route object with origin AS132827 in the RIR database for the space. |
| ROA: none | 103.42.100.0/24 | No ROA covers it. Add a ROA for AS132827, maxLength 24. |
| Route object: RIR | 103.42.100.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.42.101.0/24 | No ROA covers it. Add a ROA for AS132827, maxLength 24. |
| Route object: RIR | 103.42.101.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.42.102.0/24 | No ROA covers it. Add a ROA for AS132827, maxLength 24. |
| Route object: RIR | 103.42.102.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.42.103.0/24 | No ROA covers it. Add a ROA for AS132827, maxLength 24. |
| Route object: RIR | 103.42.103.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 162.35.64.0/19 | No ROA covers it. Add a ROA for AS132827, maxLength 19. |
| Route object: RIR | 162.35.64.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS132827 whose prefix no peer sees AS132827 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.249.95.0/24 | APNIC | Valid |
| 101.0.20.0/22 | RADB | No ROA |
| 101.0.24.0/24 | APNIC, RADB | Valid |
| 101.0.25.0/24 | APNIC, RADB | Valid |
| 101.0.26.0/23 | APNIC, RADB | Valid |
| 103.8.20.0/24 | RADB | No ROA |
| 103.11.120.0/22 | APNIC, RADB | Valid |
| 103.25.100.0/22 | RADB | No ROA |
| 216.74.118.0/24 | RADB | No ROA |
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.