Network · data from 2026-11-12
AS58521 Garena Online
Registry name: GARENA-SG - Garena Online Pte Ltd, SG · PeeringDB
92IPv4 routes
98.9% RPKI valid · 98.9% with a route object
2IPv6 routes
100.0% RPKI valid · 100.0% with a route object
1RPKI invalid
0 origin · 1 maxLength
0No ROA
1 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
72Route objects not announced
registered with origin AS58521, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS58521, 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.
| 143.92.120.0/23 | Invalid: maxLength | Nonecovered by 143.92.120.0/22 | 2 0%low visibility |
| 103.247.206.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 103.247.204.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.247.205.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.247.206.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.247.207.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 143.92.112.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 143.92.112.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 143.92.113.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 143.92.116.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 143.92.117.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 143.92.118.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 143.92.120.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 143.92.120.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 143.92.121.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 143.92.122.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 143.92.124.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 143.92.127.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 148.222.64.0/20 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 148.222.85.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.96.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.96.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.97.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.98.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.100.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.81.104.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.105.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.106.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.107.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.108.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.108.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.109.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.110.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.111.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.112.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.112.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.113.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.114.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.115.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.116.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.116.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.81.116.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.117.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.120.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.81.120.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.121.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.122.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.123.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.124.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.81.124.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.125.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.126.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.81.126.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.81.127.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.181.64.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.181.65.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.181.67.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.181.68.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.181.71.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.181.72.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.181.72.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.181.73.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.181.74.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.181.76.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.181.76.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.181.77.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.181.78.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.181.79.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.181.75.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 148.222.64.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 148.222.64.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 148.222.65.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 148.222.68.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 148.222.68.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 148.222.69.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 148.222.70.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 148.222.72.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 148.222.72.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 148.222.73.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 148.222.74.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 148.222.92.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 143.92.123.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 148.222.66.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 148.222.84.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.81.118.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.81.119.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.181.70.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.81.99.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 669 99% |
| 143.92.125.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 143.92.126.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 148.222.71.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 2403:b00::/48 | Valid | RIR databaseAPNIC, RADB | 634 100% |
| 2403:b00:1::/48 | Valid | RIR databaseAPNIC, RADB | 634 100% |
| 202.81.100.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
AS-SET
AS58521'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 75 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: RIR1
- Route object: not announced72
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 143.92.120.0/23 | ROA 143.92.120.0/22 AS58521 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 143.92.120.0/23. |
| Route object: none | 143.92.120.0/23 | No route object for it. A route object for 143.92.120.0/22 with origin AS58521 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58521 in the RIR database for the space. |
| Route object: RIR | 103.247.206.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS58521 whose prefix no peer sees AS58521 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.17.223.0/24 | NTTCOM | No ROA |
| 143.92.112.0/21 | APNIC, NTTCOM, RADB | Valid |
| 143.92.112.0/22 | APNIC, RADB | Valid |
| 143.92.114.0/24 | APNIC, NTTCOM, RADB | Valid |
| 143.92.115.0/24 | APNIC, NTTCOM, RADB | Valid |
| 143.92.119.0/24 | APNIC, NTTCOM, RADB | Valid |
| 143.92.124.0/22 | APNIC, NTTCOM, RADB | Valid |
| 143.92.124.0/23 | APNIC, RADB | Valid |
| 143.92.126.0/23 | APNIC, RADB | Valid |
| 148.222.66.0/24 | APNIC, NTTCOM, RADB | Valid |
| 148.222.67.0/24 | APNIC, NTTCOM, RADB | Valid |
| 148.222.75.0/24 | APNIC, NTTCOM, RADB | Valid |
| 148.222.76.0/22 | APNIC, NTTCOM, RADB | Valid |
| 148.222.76.0/24 | APNIC, NTTCOM, RADB | Valid |
| 148.222.77.0/24 | APNIC, NTTCOM, RADB | Valid |
| 148.222.78.0/24 | APNIC, NTTCOM, RADB | Valid |
| 148.222.79.0/24 | APNIC, NTTCOM, RADB | Valid |
| 148.222.80.0/22 | NTTCOM, RADB | No ROA |
| 148.222.84.0/22 | APNIC, RADB | Valid |
| 148.222.86.0/24 | APNIC, NTTCOM, RADB | Valid |
| 148.222.87.0/24 | APNIC, NTTCOM, RADB | Valid |
| 148.222.88.0/22 | NTTCOM, RADB | No ROA |
| 148.222.92.0/22 | NTTCOM, RADB | No ROA |
| 202.81.96.0/19 | APNIC, RADB | Valid |
| 202.81.96.0/20 | APNIC, RADB | Valid |
| 202.81.96.0/21 | APNIC, RADB | Valid |
| 202.81.96.0/23 | APNIC, RADB | Valid |
| 202.81.98.0/23 | APNIC, RADB | Valid |
| 202.81.100.0/22 | APNIC, NTTCOM, RADB | Valid |
| 202.81.101.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.81.102.0/23 | APNIC, RADB | Valid |
| 202.81.102.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.81.103.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.81.104.0/21 | APNIC | Valid |
| 202.81.104.0/23 | APNIC, RADB | Valid |
| 202.81.104.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.81.106.0/23 | APNIC, RADB | Valid |
| 202.81.108.0/23 | APNIC, RADB | Valid |
| 202.81.110.0/23 | APNIC, RADB | Valid |
| 202.81.112.0/20 | APNIC, RADB | Valid |
| 202.81.112.0/21 | APNIC, RADB | Valid |
| 202.81.112.0/23 | APNIC, RADB | Valid |
| 202.81.114.0/23 | APNIC, RADB | Valid |
| 202.81.118.0/23 | APNIC, RADB | Valid |
| 202.81.120.0/21 | APNIC, RADB | Valid |
| 202.81.120.0/23 | APNIC, RADB | Valid |
| 202.81.122.0/23 | APNIC, RADB | Valid |
| 202.81.124.0/23 | APNIC, RADB | Valid |
| 202.181.64.0/19 | RADB | No ROA |
| 202.181.64.0/20 | APNIC, RADB | Valid |
| 202.181.64.0/21 | APNIC, RADB | Valid |
| 202.181.64.0/22 | APNIC, NTTCOM, RADB | Valid |
| 202.181.64.0/23 | APNIC, RADB | Valid |
| 202.181.66.0/23 | APNIC, RADB | Valid |
| 202.181.66.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.181.68.0/22 | APNIC, RADB | Valid |
| 202.181.68.0/23 | APNIC, RADB | Valid |
| 202.181.69.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.181.70.0/23 | APNIC, RADB | Valid |
| 202.181.72.0/21 | APNIC, RADB | Valid |
| 202.181.72.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.181.74.0/23 | APNIC, NTTCOM, RADB | Valid |
| 202.181.76.0/23 | APNIC, RADB | Valid |
| 202.181.78.0/23 | APNIC, RADB | Valid |
| 202.181.80.0/20 | RADB | No ROA |
| 2403:b00::/32 | APNIC, RADB | Valid |
| 2403:b00:2::/48 | APNIC, RADB | Valid |
| 2403:b00:3::/48 | APNIC, RADB | Valid |
| 2403:b00:4::/48 | APNIC, RADB | Valid |
| 2403:b00:5::/48 | APNIC, RADB | Valid |
| 2403:b00:6::/48 | APNIC, RADB | Valid |
| 2403:b00:7::/48 | 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.