Network · data from 2026-11-12
AS132372 GB Network Solutions
Registry name: GBNETWORK-AS-AP - GB Network Solutions Sdn. Bhd., MY · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS132372, 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.
| 66.93.172.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 103.27.255.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.28.90.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.28.91.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.72.162.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.72.163.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.117.20.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.122.164.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.151.12.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.161.132.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.161.133.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.164.203.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.168.105.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.175.50.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.175.51.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.186.116.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.186.117.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.198.26.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.198.27.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 151.245.110.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 151.246.162.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 160.187.97.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 160.236.143.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 165.99.199.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 69.33.169.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 103.91.194.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 172.94.60.0/24 | Valid | RIR databaseARIN | 671 100% |
| 172.94.62.0/24 | Valid | RIR databaseARIN | 671 100% |
| 172.94.80.0/24 | Valid | RIR databaseARIN | 671 100% |
| 172.94.82.0/24 | Valid | RIR databaseARIN | 671 100% |
| 172.94.86.0/24 | Valid | RIR databaseARIN | 671 100% |
| 172.94.127.0/24 | Valid | RIR databaseARIN | 671 100% |
| 172.94.0.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.21.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.22.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.25.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.26.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.28.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.37.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.48.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.49.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.51.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.55.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.56.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.57.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.102.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.107.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.108.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.112.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.114.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.116.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.118.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.121.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.123.0/24 | Valid | RIR databaseARIN | 669 99% |
| 172.94.103.0/24 | Valid | RIR databaseARIN | 668 99% |
| 172.94.124.0/24 | Valid | RIR databaseARIN | 668 99% |
| 64.69.119.0/24 | Valid | RIR databaseARIN, RADB | 667 99% |
| 172.111.157.0/24 | Valid | RIR databaseARIN | 667 99% |
| 172.111.222.0/24 | Valid | RIR databaseARIN | 667 99% |
| 172.111.129.0/24 | Valid | RIR databaseARIN | 665 99% |
| 172.111.153.0/24 | Valid | RIR databaseARIN | 665 99% |
| 172.111.173.0/24 | Valid | RIR databaseARIN | 665 99% |
| 172.111.186.0/24 | Valid | RIR databaseARIN | 665 99% |
| 172.111.199.0/24 | Valid | RIR databaseARIN | 665 99% |
| 172.111.234.0/24 | Valid | RIR databaseARIN | 665 99% |
| 172.111.236.0/24 | Valid | RIR databaseARIN | 665 99% |
| 172.111.238.0/24 | Valid | RIR databaseARIN | 665 99% |
| 172.111.242.0/24 | Valid | RIR databaseARIN | 665 99% |
| 172.111.203.0/24 | Valid | RIR databaseARIN | 664 99% |
| 172.111.237.0/24 | Valid | RIR databaseARIN | 664 99% |
| 2001:df0:a8c0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df2:3bc0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2400:18a0:1001::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2403:fd40:1001::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2403:fd40:1002::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2403:fd40:1003::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2403:fd40:a000::/48 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS132372: AS-GBNETWORK. 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 (AS132372 isn't in the set, or no route object for AS132372 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 | AS132372 in it | Not covered |
|---|---|---|---|---|---|
| AS-GBNETWORK | APNIC | 11 | 1 | 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 5 are in fix.csv.
- Route object: RIR1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 66.93.172.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS132372 whose prefix no peer sees AS132372 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.72.162.0/23 | APNIC, NTTCOM, RADB | Valid |
| 104.243.247.0/24 | NTTCOM, RADB | No ROA |
| 170.130.116.0/24 | ARIN | Invalid: origin |
| 2400:18a0::/32 | 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.