bgpreport

Network · data from 2026-11-12

AS19128 TTN - TTN Global Operations Limited

Registry name: TTN - TTN Global Operations Limited, BS · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS19128, 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.216.30.216/29 No ROA None 6 1%low visibility 7
66.226.160.0/24 No ROA Other IRR onlyRADB 664 99% 67
66.226.161.0/24 No ROA Other IRR onlyRADB 664 99% 67
66.226.164.0/24 No ROA Other IRR onlyRADB 664 99% 67
66.226.166.0/24 No ROA Other IRR onlyRADB 664 99% 67
66.226.176.0/24 No ROA Other IRR onlyRADB 664 99% 67
66.226.177.0/24 No ROA Other IRR onlyRADB 664 99% 67
66.226.180.0/24 No ROA Other IRR onlyRADB 664 99% 67
66.226.182.0/24 No ROA Other IRR onlyRADB 664 99% 67

AS-SET

AS19128 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 73 are in fix.csv.

  • ROA: none9
  • Route object: none1
  • Route object: RIR8
  • Route object: not announced55
ChangePrefix or setDetailFull-table peers
ROA: none66.216.30.216/29No ROA covers it. Add a ROA for AS19128, maxLength 29.6 of 673
Route object: none66.216.30.216/29No route object for it. Add a route object with origin AS19128 in the RIR database for the space.6 of 673
ROA: none66.226.160.0/24No ROA covers it. Add a ROA for AS19128, maxLength 24.664 of 673
Route object: RIR66.226.160.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
ROA: none66.226.161.0/24No ROA covers it. Add a ROA for AS19128, maxLength 24.664 of 673
Route object: RIR66.226.161.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
ROA: none66.226.164.0/24No ROA covers it. Add a ROA for AS19128, maxLength 24.664 of 673
Route object: RIR66.226.164.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
ROA: none66.226.166.0/24No ROA covers it. Add a ROA for AS19128, maxLength 24.664 of 673
Route object: RIR66.226.166.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
ROA: none66.226.176.0/24No ROA covers it. Add a ROA for AS19128, maxLength 24.664 of 673
Route object: RIR66.226.176.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
ROA: none66.226.177.0/24No ROA covers it. Add a ROA for AS19128, maxLength 24.664 of 673
Route object: RIR66.226.177.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
ROA: none66.226.180.0/24No ROA covers it. Add a ROA for AS19128, maxLength 24.664 of 673
Route object: RIR66.226.180.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
ROA: none66.226.182.0/24No ROA covers it. Add a ROA for AS19128, maxLength 24.664 of 673
Route object: RIR66.226.182.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673

Route objects not announced

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

66.226.160.0/19ALTDB, BBOINo ROA
66.226.160.0/20RADBNo ROA
66.226.160.0/21RADBNo ROA
66.226.160.0/22RADBNo ROA
66.226.160.0/23RADBNo ROA
66.226.162.0/23RADBNo ROA
66.226.162.0/24RADBNo ROA
66.226.163.0/24RADBNo ROA
66.226.164.0/22RADBNo ROA
66.226.164.0/23RADBNo ROA
66.226.165.0/24RADBNo ROA
66.226.166.0/23RADBNo ROA
66.226.167.0/24RADBNo ROA
66.226.168.0/21RADBNo ROA
66.226.168.0/22RADBNo ROA
66.226.168.0/23RADBNo ROA
66.226.168.0/24RADBNo ROA
66.226.169.0/24RADBNo ROA
66.226.170.0/23RADBNo ROA
66.226.170.0/24RADBNo ROA
66.226.171.0/24RADBNo ROA
66.226.172.0/22RADBNo ROA
66.226.172.0/23RADBNo ROA
66.226.172.0/24RADBNo ROA
66.226.173.0/24RADBNo ROA
66.226.174.0/23RADBNo ROA
66.226.174.0/24RADBNo ROA
66.226.175.0/24RADBNo ROA
66.226.176.0/20RADBNo ROA
66.226.176.0/21RADBNo ROA
66.226.176.0/22RADBNo ROA
66.226.176.0/23RADBNo ROA
66.226.178.0/23RADBNo ROA
66.226.178.0/24RADBNo ROA
66.226.179.0/24RADBNo ROA
66.226.180.0/22RADBNo ROA
66.226.180.0/23RADBNo ROA
66.226.181.0/24RADBNo ROA
66.226.182.0/23RADBNo ROA
66.226.183.0/24RADBNo ROA
66.226.184.0/21RADBNo ROA
66.226.184.0/22RADBNo ROA
66.226.184.0/23RADBNo ROA
66.226.184.0/24RADBNo ROA
66.226.185.0/24RADBNo ROA
66.226.186.0/23RADBNo ROA
66.226.186.0/24RADBNo ROA
66.226.187.0/24RADBNo ROA
66.226.188.0/22RADBNo ROA
66.226.188.0/23RADBNo ROA
66.226.188.0/24RADBNo ROA
66.226.189.0/24RADBNo ROA
66.226.190.0/23RADBNo ROA
66.226.190.0/24RADBNo ROA
66.226.191.0/24RADBNo ROA

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.