bgpreport

Network · data from 2026-11-12

AS23917 TTC-AS-AP - Tuvalu Telecommunications Corporation

Registry name: TTC-AS-AP - Tuvalu Telecommunications Corporation, TV · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS23917, 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.2.96.0/20 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
202.2.96.0/21 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
202.2.104.0/21 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
202.2.112.0/20 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
202.2.112.0/21 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
202.2.120.0/21 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67

AS-SET

AS23917 isn't in PeeringDB, where networks name their 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 94 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced88
ChangePrefix or setDetailFull-table peers
ROA: none202.2.96.0/20No ROA covers it. Add a ROA for AS23917, maxLength 20.673 of 673
Route object: RIR202.2.96.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.2.96.0/21No ROA covers it. Add a ROA for AS23917, maxLength 21.673 of 673
Route object: RIR202.2.96.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.2.104.0/21No ROA covers it. Add a ROA for AS23917, maxLength 21.673 of 673
Route object: RIR202.2.104.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

202.2.96.0/19NTTCOM, RADBNo ROA
202.2.96.0/22NTTCOM, RADBNo ROA
202.2.96.0/23NTTCOM, RADBNo ROA
202.2.96.0/24NTTCOM, RADBNo ROA
202.2.97.0/24NTTCOM, RADBNo ROA
202.2.98.0/23NTTCOM, RADBNo ROA
202.2.98.0/24NTTCOM, RADBNo ROA
202.2.99.0/24NTTCOM, RADBNo ROA
202.2.100.0/22NTTCOM, RADBNo ROA
202.2.100.0/23NTTCOM, RADBNo ROA
202.2.100.0/24NTTCOM, RADBNo ROA
202.2.101.0/24NTTCOM, RADBNo ROA
202.2.102.0/23NTTCOM, RADBNo ROA
202.2.102.0/24NTTCOM, RADBNo ROA
202.2.103.0/24NTTCOM, RADBNo ROA
202.2.104.0/22NTTCOM, RADBNo ROA
202.2.104.0/23NTTCOM, RADBNo ROA
202.2.104.0/24NTTCOM, RADBNo ROA
202.2.105.0/24NTTCOM, RADBNo ROA
202.2.106.0/23NTTCOM, RADBNo ROA
202.2.106.0/24NTTCOM, RADBNo ROA
202.2.107.0/24NTTCOM, RADBNo ROA
202.2.108.0/22NTTCOM, RADBNo ROA
202.2.108.0/23NTTCOM, RADBNo ROA
202.2.108.0/24NTTCOM, RADBNo ROA
202.2.109.0/24NTTCOM, RADBNo ROA
202.2.110.0/23NTTCOM, RADBNo ROA
202.2.110.0/24NTTCOM, RADBNo ROA
202.2.111.0/24NTTCOM, RADBNo ROA
202.2.112.0/22APNIC, NTTCOM, RADBValid
202.2.112.0/23APNIC, NTTCOM, RADBValid
202.2.112.0/24APNIC, NTTCOM, RADBValid
202.2.113.0/24APNIC, NTTCOM, RADBValid
202.2.114.0/23APNIC, NTTCOM, RADBValid
202.2.114.0/24APNIC, NTTCOM, RADBValid
202.2.115.0/24APNIC, NTTCOM, RADBValid
202.2.116.0/22APNIC, NTTCOM, RADBValid
202.2.116.0/23APNIC, NTTCOM, RADBValid
202.2.116.0/24APNIC, NTTCOM, RADBValid
202.2.117.0/24APNIC, NTTCOM, RADBValid
202.2.118.0/23APNIC, NTTCOM, RADBValid
202.2.118.0/24APNIC, NTTCOM, RADBValid
202.2.119.0/24APNIC, NTTCOM, RADBValid
202.2.120.0/22APNIC, NTTCOM, RADBValid
202.2.120.0/23APNIC, NTTCOM, RADBValid
202.2.120.0/24APNIC, NTTCOM, RADBValid
202.2.121.0/24APNIC, NTTCOM, RADBValid
202.2.122.0/23APNIC, NTTCOM, RADBValid
202.2.122.0/24APNIC, NTTCOM, RADBValid
202.2.123.0/24APNIC, NTTCOM, RADBValid
202.2.124.0/22APNIC, NTTCOM, RADBValid
202.2.124.0/23APNIC, NTTCOM, RADBValid
202.2.124.0/24APNIC, NTTCOM, RADBValid
202.2.125.0/24APNIC, NTTCOM, RADBValid
202.2.126.0/23APNIC, NTTCOM, RADBValid
202.2.126.0/24APNIC, NTTCOM, RADBValid
202.2.127.0/24APNIC, NTTCOM, RADBValid
2401:c720::/32APNICValid
2401:c720::/33APNICValid
2401:c720::/34APNICValid
2401:c720::/35APNICValid
2401:c720::/36APNICValid
2401:c720:1000::/36APNICValid
2401:c720:2000::/35APNICValid
2401:c720:2000::/36APNICValid
2401:c720:3000::/36APNICValid
2401:c720:4000::/34APNICValid
2401:c720:4000::/35APNICValid
2401:c720:4000::/36APNICValid
2401:c720:5000::/36APNICValid
2401:c720:6000::/35APNICValid
2401:c720:6000::/36APNICValid
2401:c720:7000::/36APNICValid
2401:c720:8000::/33APNICValid
2401:c720:8000::/34APNICValid
2401:c720:8000::/35APNICValid
2401:c720:8000::/36APNICValid
2401:c720:9000::/36APNICValid
2401:c720:a000::/35APNICValid
2401:c720:a000::/36APNICValid
2401:c720:b000::/36APNICValid
2401:c720:c000::/34APNICValid
2401:c720:c000::/35APNICValid
2401:c720:c000::/36APNICValid
2401:c720:d000::/36APNICValid
2401:c720:e000::/35APNICValid
2401:c720:e000::/36APNICValid
2401:c720:f000::/36APNICValid

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.