bgpreport

Network · data from 2026-11-12

AS131322 Yatanarpon Teleport

Registry name: YTCL-AS-AP - Yatanarpon Teleport Company Limited, MM · PeeringDB

10IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 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
22Route objects not announced registered with origin AS131322, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS131322, 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.
61.4.64.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
61.4.66.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
61.4.67.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
122.248.108.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
122.248.109.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
122.248.110.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.81.167.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.81.170.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
122.248.107.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
122.248.111.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
2406:ea00::/32 Valid RIR databaseAPNIC 635 100% 69

AS-SET

AS131322'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 22 are in fix.csv.

  • Route object: not announced22

Route objects not announced

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

61.4.64.0/20APNIC, NTTCOM, RADBValid
61.4.65.0/24APNIC, NTTCOM, RADBValid
61.4.68.0/24APNIC, NTTCOM, RADBValid
61.4.69.0/24APNIC, NTTCOM, RADBValid
61.4.70.0/24APNIC, NTTCOM, RADBValid
61.4.71.0/24APNIC, NTTCOM, RADBValid
61.4.73.0/24APNIC, NTTCOM, RADBValid
61.4.74.0/24APNIC, NTTCOM, RADBValid
61.4.75.0/24APNIC, NTTCOM, RADBValid
61.4.76.0/24APNIC, NTTCOM, RADBValid
61.4.77.0/24APNIC, NTTCOM, RADBValid
61.4.78.0/24APNIC, NTTCOM, RADBValid
61.4.79.0/24APNIC, NTTCOM, RADBValid
103.219.108.0/22NTTCOM, RADBNo ROA
103.219.108.0/23NTTCOM, RADBNo ROA
103.219.110.0/23NTTCOM, RADBNo ROA
103.219.110.0/24NTTCOM, RADBNo ROA
103.219.111.0/24NTTCOM, RADBNo ROA
122.248.96.0/19APNIC, NTTCOM, RADBValid
122.248.117.0/24APNIC, NTTCOM, RADBValid
203.81.160.0/20APNIC, NTTCOM, RADBValid
203.81.166.0/24APNIC, 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.