bgpreport

Network · data from 2026-11-12

AS47690 TNGNET B.V. (AS47690)

Registry name: TNGNET TNGNET B.V., NL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS47690, 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.

94.193.104.0/22 Invalid: origin Other origin only 2 0%low visibility 2
94.193.156.0/22 Invalid: origin Other origin only 2 0%low visibility 2
94.193.180.0/22 Invalid: origin None 2 0%low visibility 2
94.193.204.0/22 Invalid: origin Other origin only 2 0%low visibility 2
185.86.164.0/24 Valid Other origin only 670 100% 69
185.86.165.0/24 Valid Other origin only 670 100% 69
185.86.166.0/24 Valid Other origin only 670 100% 69
185.86.167.0/24 Valid Other origin only 670 100% 69
185.87.123.0/24 Valid Other origin only 670 100% 69
64.205.232.0/22 Valid Other IRR onlyRADB 671 100% 69
23.27.242.0/24 Valid RIR databaseARIN 671 100% 67
45.10.19.0/24 Valid RIR databaseRIPE 671 100% 68
50.114.161.0/24 Valid RIR databaseARIN 671 100% 67
78.17.140.0/22 Valid RIR databaseRIPE 671 100% 67
81.181.132.0/22 Valid RIR databaseRIPE 671 100% 67
85.120.45.0/24 Valid RIR databaseRIPE 671 100% 67
85.120.185.0/24 Valid RIR databaseRIPE 671 100% 67
89.43.87.0/24 Valid RIR databaseRIPE 671 100% 67
94.76.182.0/24 Valid RIR databaseRIPE 671 100% 67
104.238.12.0/24 Valid RIR databaseRIPE 671 100% 68
108.165.4.0/23 Valid RIR databaseARIN 671 100% 67
136.0.84.0/24 Valid RIR databaseARIN 671 100% 67
140.225.200.0/22 Valid RIR databaseRIPE 671 100% 67
140.225.216.0/22 Valid RIR databaseRIPE 671 100% 67
142.111.3.0/24 Valid RIR databaseARIN 671 100% 67
142.111.11.0/24 Valid RIR databaseARIN 671 100% 67
142.111.14.0/24 Valid RIR databaseARIN 671 100% 67
142.111.23.0/24 Valid RIR databaseARIN 671 100% 67
142.111.26.0/24 Valid RIR databaseARIN 671 100% 67
142.111.28.0/24 Valid RIR databaseARIN 671 100% 67
142.111.43.0/24 Valid RIR databaseARIN 671 100% 67
142.111.134.0/24 Valid RIR databaseARIN 671 100% 67
142.111.237.0/24 Valid RIR databaseARIN 671 100% 67
142.111.241.0/24 Valid RIR databaseARIN 671 100% 67
147.90.60.0/22 Valid RIR databaseRADB, RIPE 671 100% 68
147.90.68.0/22 Valid RIR databaseRADB, RIPE 671 100% 68
147.90.80.0/22 Valid RIR databaseRADB, RIPE 671 100% 68
147.90.92.0/22 Valid RIR databaseRADB, RIPE 671 100% 68
166.88.112.0/24 Valid RIR databaseARIN 671 100% 67
166.88.207.0/24 Valid RIR databaseARIN 671 100% 67
179.254.83.0/24 Valid RIR databaseRIPE 671 100% 67
179.254.87.0/24 Valid RIR databaseRIPE 671 100% 67
194.153.252.0/22 Valid RIR databaseRIPE 671 100% 67
198.20.137.0/24 Valid RIR databaseARIN 671 100% 67
216.173.91.0/24 Valid RIR databaseRIPE 671 100% 68
78.31.251.0/24 Valid RIR databaseRADB, RIPE 670 100% 68
81.180.205.0/24 Valid RIR databaseRIPE 670 100% 67
81.181.174.0/24 Valid RIR databaseRIPE 670 100% 67
104.234.247.0/24 Valid RIR databaseARIN, RADB 670 100% 68
151.243.235.0/24 Valid RIR databaseRADB, RIPE 670 100% 68
216.183.248.0/24 Valid RIR databaseARIN, RADB 670 100% 68
216.183.251.0/24 Valid RIR databaseARIN, RADB 670 100% 68
188.255.242.0/24 Valid RIR databaseRADB, RIPE 669 99% 68
104.238.13.0/24 Valid RIR databaseRIPE 0 0%low visibility 1
104.249.9.0/24 Valid RIR databaseRIPE 0 0%low visibility 1

AS-SET

AS47690'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 14 are in fix.csv.

  • ROA: origin4
  • Route object: none9
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: origin94.193.104.0/22ROAs covering it name AS4766, not AS47690. If AS47690 should announce it, add a ROA for AS47690.2 of 673
Route object: none94.193.104.0/22Route objects for it name AS4766. Add a route object with origin AS47690 in the RIR database for the space.2 of 673
ROA: origin94.193.156.0/22ROAs covering it name AS4766, not AS47690. If AS47690 should announce it, add a ROA for AS47690.2 of 673
Route object: none94.193.156.0/22Route objects for it name AS4766. Add a route object with origin AS47690 in the RIR database for the space.2 of 673
ROA: origin94.193.180.0/22ROAs covering it name AS834, not AS47690. If AS47690 should announce it, add a ROA for AS47690.2 of 673
Route object: none94.193.180.0/22No route object for it. Add a route object with origin AS47690 in the RIR database for the space.2 of 673
ROA: origin94.193.204.0/22ROAs covering it name AS4766, not AS47690. If AS47690 should announce it, add a ROA for AS47690.2 of 673
Route object: none94.193.204.0/22Route objects for it name AS4766. Add a route object with origin AS47690 in the RIR database for the space.2 of 673
Route object: none185.86.164.0/24Route objects for it name AS174. Add a route object with origin AS47690 in the RIR database for the space.670 of 673
Route object: none185.86.165.0/24Route objects for it name AS174. Add a route object with origin AS47690 in the RIR database for the space.670 of 673
Route object: none185.86.166.0/24Route objects for it name AS174. Add a route object with origin AS47690 in the RIR database for the space.670 of 673
Route object: none185.86.167.0/24Route objects for it name AS174. Add a route object with origin AS47690 in the RIR database for the space.670 of 673
Route object: none185.87.123.0/24Route objects for it name AS174. Add a route object with origin AS47690 in the RIR database for the space.670 of 673
Route object: RIR64.205.232.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS47690 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.