bgpreport

Network · data from 2026-11-12

AS4767 Asian Institute of Technology

Registry name: AIT-CS-ASN - Computer Science, TH · PeeringDB

7IPv4 routes 100.0% RPKI valid · 71.4% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
10Route objects not announced registered with origin AS4767, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS4767, 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.8.66.0/23 Valid None 673 100% 67
202.8.68.0/22 Valid None 673 100% 67
192.41.170.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.8.65.0/24 Valid RIR databaseAPNIC 673 100% 67
203.159.0.0/18 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
203.159.0.0/19 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
203.159.32.0/19 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
2403:e240::/32 Valid RIR databaseAPNIC, RADB 636 100% 70

AS-SET

AS4767'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 12 are in fix.csv.

  • Route object: none2
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
Route object: none202.8.66.0/23No route object for it. Add a route object with origin AS4767 in the RIR database for the space.673 of 673
Route object: none202.8.68.0/22No route object for it. Add a route object with origin AS4767 in the RIR database for the space.673 of 673

Route objects not announced

Route objects with origin AS4767 whose prefix no peer sees AS4767 announce. Many are kept on purpose (backup routes, space announced only in some places).

202.8.66.0/24APNICValid
202.8.67.0/24APNICValid
202.8.68.0/24APNICValid
202.8.69.0/24APNICValid
202.8.70.0/24APNICValid
202.8.71.0/24APNICValid
203.159.0.0/20APNIC, NTTCOM, RADBValid
203.159.16.0/20APNIC, NTTCOM, RADBValid
203.159.32.0/20APNIC, NTTCOM, RADBValid
203.159.48.0/20APNIC, NTTCOM, RADBValid

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.