Network · data from 2026-11-12
AS4762 MAHIDOL-BORDER-AS - Mahidol University, Thailand
Registry name: MAHIDOL-BORDER-AS - Mahidol University, Thailand, TH · not in PeeringDB
75IPv4 routes
100.0% RPKI valid · 100.0% with a route object
3IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
0 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS4762, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS4762, 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.
| 202.28.128.0/18 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.129.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.130.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.131.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.132.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.133.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.134.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.135.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.136.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.136.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.137.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.138.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.139.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.141.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.142.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.143.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.144.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.144.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.144.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.145.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.146.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.147.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.148.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.149.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.150.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.151.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.152.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.152.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.155.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.156.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.157.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.158.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.159.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.161.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.162.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.163.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.164.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.165.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.166.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.167.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.168.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.170.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.171.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.172.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.173.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.174.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.175.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.176.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.177.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.178.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.184.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.185.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.187.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.188.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.189.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.190.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.191.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.28.128.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.28.140.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.28.153.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.28.154.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.28.160.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.28.169.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.28.179.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.28.180.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.28.181.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.28.182.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.28.183.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.28.186.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.28.128.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 650 97% |
| 202.28.160.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 650 97% |
| 202.28.176.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 650 97% |
| 202.28.138.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 648 96% |
| 202.28.148.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 648 96% |
| 202.28.150.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 648 96% |
| 2001:3c8:2707::/48 | Valid | RIR databaseAPNIC, RADB | 634 100% |
| 2001:3c8:1606::/48 | Valid | RIR databaseAPNIC, RADB | 633 100% |
| 2001:3c8:1202::/48 | Valid | RIR databaseAPNIC, RADB | 632 99% |
AS-SET
AS4762 isn't in PeeringDB, where networks name their AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS4762 is announced.
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.