Network · data from 2026-11-12
AS137990 Suniway Group Hong Kong
Registry name: SUNIWAY1-AS-AP - SUNIWAY GROUP LIMITED, HK · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS137990, 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.
| 154.197.28.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 669 99% |
| 154.197.29.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 669 99% |
| 103.119.128.0/22 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.119.128.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 103.119.129.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 103.119.130.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 103.119.131.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 202.43.226.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 2402:940::/32 | Valid | RIR databaseAPNIC | 636 100% |
| 2403:43c0::/32 | Valid | RIR databaseAPNIC | 636 100% |
| 202.43.225.0/24 | Valid | RIR databaseAPNIC, RADB | 44 7%low visibility |
AS-SET
PeeringDB's irr_as_set for AS137990: AS-SUNIWAYY1-HK. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS137990 isn't in the set, or no route object for AS137990 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS137990 in it | Not covered |
|---|---|---|---|---|---|
| AS-SUNIWAYY1-HK | APNIC1 member set in no database: AS200105:AS-HK | 44 | 15 | Yes | 0 |
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 14 are in fix.csv.
- Route object: RIR2
- AS-SET: missing member1
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 154.197.28.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 154.197.29.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| AS-SET: missing member | AS-SUNIWAYY1-HK | AS-SUNIWAYY1-HK (APNIC) lists AS200105:AS-HK; no IRR database read has it. |
Route objects not announced
Route objects with origin AS137990 whose prefix no peer sees AS137990 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.104.100.0/22 | APNIC | Valid |
| 103.104.100.0/24 | APNIC | Valid |
| 103.104.101.0/24 | APNIC | Valid |
| 103.104.102.0/24 | APNIC | Valid |
| 103.104.103.0/24 | APNIC | Valid |
| 154.197.28.0/22 | RADB | No ROA |
| 154.197.28.0/23 | AFRINIC, RADB | Valid |
| 156.250.2.0/23 | RADB | No ROA |
| 202.43.224.0/22 | RADB | No ROA |
| 202.43.224.0/24 | APNIC, RADB | Valid |
| 2406:840:eb83::/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.