bgpreport

Network · data from 2026-11-12

AS215607 DF-Transit dataforest GmbH

Registry name: DF-Transit dataforest GmbH, DE · not in PeeringDB

94IPv4 routes 69.1% RPKI valid · 73.4% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
26RPKI invalid 26 origin · 0 maxLength
3No ROA 25 with no route object for this origin
31Low visibility seen by under 10% of full-table peers
22Route objects not announced registered with origin AS215607, seen from no peer

Announced routes

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

68.164.16.0/24 Invalid: origin None 36 5%low visibility 24
68.164.28.0/24 Invalid: origin None 36 5%low visibility 24
209.102.236.0/24 Invalid: origin None 36 5%low visibility 24
66.93.18.0/24 Invalid: origin Other origin only 3 0%low visibility 3
178.94.219.0/24 Invalid: origin Other origin only 3 0%low visibility 3
40.27.23.0/24 Invalid: origin Other origin only 2 0%low visibility 2
64.81.184.0/24 Invalid: origin Other origin only 2 0%low visibility 2
64.93.17.0/24 Invalid: origin Other origin only 2 0%low visibility 2
64.204.35.0/24 Invalid: origin Other origin only 2 0%low visibility 2
74.1.140.0/24 Invalid: origin Other origin only 2 0%low visibility 2
84.75.242.0/24 Invalid: origin Other origin only 2 0%low visibility 2
85.232.178.0/24 Invalid: origin Other origin only 2 0%low visibility 2
95.155.182.0/24 Invalid: origin Other origin only 2 0%low visibility 2
168.222.5.0/24 Invalid: origin Other origin only 2 0%low visibility 2
173.232.59.0/24 Invalid: origin Other origin only 2 0%low visibility 2
178.83.252.0/24 Invalid: origin Other origin only 2 0%low visibility 2
199.48.181.0/24 Invalid: origin Other origin only 2 0%low visibility 2
207.180.7.0/24 Invalid: origin Other origin only 2 0%low visibility 2
208.66.111.0/24 Invalid: origin Other origin only 2 0%low visibility 2
216.83.41.0/24 Invalid: origin Other origin only 2 0%low visibility 2
216.98.243.0/24 Invalid: origin None 2 0%low visibility 2
216.98.244.0/24 Invalid: origin None 2 0%low visibility 2
176.105.229.0/24 Invalid: origin Other origin only 0 0%low visibility 1
162.141.179.0/24 Invalid: origin Other IRR onlyRADB 2 0%low visibility 2
162.141.183.0/24 Invalid: origin Other IRR onlyRADB 2 0%low visibility 2
207.180.48.0/24 Invalid: origin Other IRR onlyRADB 2 0%low visibility 2
45.56.193.0/24 No ROA Other origin only 2 0%low visibility 2
45.56.200.0/24 No ROA Other origin only 2 0%low visibility 2
204.29.220.0/24 No ROA Other IRR onlyRADB 671 100% 67
147.125.242.0/24 Valid Other IRR onlyRADB 673 100% 67
148.135.255.0/24 Valid Other IRR onlyRADB 673 100% 67
178.94.211.0/24 Valid Other IRR onlyRADB 673 100% 67
178.94.242.0/24 Valid Other IRR onlyRADB 673 100% 67
151.243.32.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
151.245.165.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
195.222.127.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
2.27.236.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
5.175.128.0/24 Valid RIR databaseRIPE 673 100% 67
5.175.132.0/24 Valid RIR databaseRIPE 673 100% 67
5.175.185.0/24 Valid RIR databaseRIPE 673 100% 67
5.175.186.0/24 Valid RIR databaseRIPE 673 100% 67
5.175.248.0/24 Valid RIR databaseRIPE 673 100% 67
5.231.94.0/24 Valid RIR databaseRIPE 673 100% 67
23.95.175.0/24 Valid RIR databaseARIN, RADB 673 100% 67
31.58.144.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
69.33.150.0/24 Valid RIR databaseARIN, RADB 673 100% 67
84.75.76.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
87.239.131.0/24 Valid RIR databaseRIPE 673 100% 67
89.106.89.0/24 Valid RIR databaseRIPE 673 100% 67
89.144.3.0/24 Valid RIR databaseRIPE 673 100% 67
89.144.49.0/24 Valid RIR databaseRIPE 673 100% 67
94.118.114.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
94.118.164.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
94.118.173.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
94.118.190.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
94.118.192.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
94.118.244.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
94.249.190.0/24 Valid RIR databaseRIPE 673 100% 67
94.249.203.0/24 Valid RIR databaseRIPE 673 100% 67
94.249.239.0/24 Valid RIR databaseRIPE 673 100% 67
94.249.247.0/24 Valid RIR databaseRIPE 673 100% 67
96.43.107.0/24 Valid RIR databaseARIN, RADB 673 100% 67
103.135.45.0/24 Valid RIR databaseAPNIC 673 100% 67
107.172.19.0/24 Valid RIR databaseARIN 673 100% 67
159.200.206.0/24 Valid RIR databaseRIPE 673 100% 67
168.199.154.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
168.199.155.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
178.214.97.0/24 Valid RIR databaseRIPE 673 100% 67
178.214.106.0/24 Valid RIR databaseRIPE 673 100% 67
179.254.223.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.47.141.0/24 Valid RIR databaseRIPE 673 100% 67
185.219.20.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
187.14.132.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
195.110.14.0/24 Valid RIR databaseRIPE 673 100% 67
199.235.174.0/24 Valid RIR databaseARIN, RADB 673 100% 67
5.83.146.0/24 Valid RIR databaseRIPE 672 100% 67
5.83.148.0/24 Valid RIR databaseRIPE 672 100% 67
13.141.0.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
13.141.2.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
13.141.4.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
37.202.201.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
72.244.60.0/24 Valid RIR databaseARIN, RADB 672 100% 67
72.244.126.0/24 Valid RIR databaseARIN, RADB 672 100% 67
72.244.157.0/24 Valid RIR databaseARIN, RADB 672 100% 67
85.8.148.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
90.96.91.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
90.96.108.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
90.96.109.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
94.118.208.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
94.249.170.0/24 Valid RIR databaseRIPE 672 100% 67
193.28.251.0/24 Valid RIR databaseRIPE 672 100% 67
216.24.208.0/24 Valid RIR databaseARIN, RADB 672 100% 67
77.90.33.0/24 Valid RIR databaseRIPE 671 100% 67
167.148.248.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
2a12:4041:8::/48 Valid RIR databaseRIPE 633 100% 67
2a12:4041:9::/48 Valid RIR databaseRIPE 633 100% 67
2a14:7586:5000::/36 Valid RIR databaseRIPE 633 100% 67

AS-SET

AS215607 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 87 are in fix.csv.

  • ROA: origin26
  • ROA: none3
  • Route object: none25
  • Route object: RIR11
  • Route object: not announced22
ChangePrefix or setDetailFull-table peers
ROA: origin68.164.16.0/24ROAs covering it name AS834, not AS215607. If AS215607 should announce it, add a ROA for AS215607.36 of 673
Route object: none68.164.16.0/24No route object for it. Add a route object with origin AS215607 in the RIR database for the space.36 of 673
ROA: origin68.164.28.0/24ROAs covering it name AS834, not AS215607. If AS215607 should announce it, add a ROA for AS215607.36 of 673
Route object: none68.164.28.0/24No route object for it. Add a route object with origin AS215607 in the RIR database for the space.36 of 673
ROA: origin209.102.236.0/24ROAs covering it name AS834, not AS215607. If AS215607 should announce it, add a ROA for AS215607.36 of 673
Route object: none209.102.236.0/24No route object for it. Add a route object with origin AS215607 in the RIR database for the space.36 of 673
ROA: origin66.93.18.0/24ROAs covering it name AS834, not AS215607. If AS215607 should announce it, add a ROA for AS215607.3 of 673
Route object: none66.93.18.0/24Route objects for it name AS834. Add a route object with origin AS215607 in the RIR database for the space.3 of 673
ROA: origin178.94.219.0/24ROAs covering it name AS834, not AS215607. If AS215607 should announce it, add a ROA for AS215607.3 of 673
Route object: none178.94.219.0/24Route objects for it name AS834. Add a route object with origin AS215607 in the RIR database for the space.3 of 673
ROA: origin40.27.23.0/24ROAs covering it name AS15830, not AS215607. If AS215607 should announce it, add a ROA for AS215607.2 of 673
Route object: none40.27.23.0/24Route objects for it name AS15830. Add a route object with origin AS215607 in the RIR database for the space.2 of 673
ROA: origin64.81.184.0/24ROAs covering it name AS834, not AS215607. If AS215607 should announce it, add a ROA for AS215607.2 of 673
Route object: none64.81.184.0/24Route objects for it name AS834. Add a route object with origin AS215607 in the RIR database for the space.2 of 673
ROA: origin64.93.17.0/24ROAs covering it name AS152726, AS400906, not AS215607. If AS215607 should announce it, add a ROA for AS215607.2 of 673
Route object: none64.93.17.0/24Route objects for it name AS152726, AS400906. Add a route object with origin AS215607 in the RIR database for the space.2 of 673
ROA: origin64.204.35.0/24ROAs covering it name AS16276, not AS215607. If AS215607 should announce it, add a ROA for AS215607.2 of 673
Route object: none64.204.35.0/24Route objects for it name AS16276. Add a route object with origin AS215607 in the RIR database for the space.2 of 673
ROA: origin74.1.140.0/24ROAs covering it name AS834, not AS215607. If AS215607 should announce it, add a ROA for AS215607.2 of 673
Route object: none74.1.140.0/24Route objects for it name AS834. Add a route object with origin AS215607 in the RIR database for the space.2 of 673
ROA: origin84.75.242.0/24ROAs covering it name AS834, not AS215607. If AS215607 should announce it, add a ROA for AS215607.2 of 673
Route object: none84.75.242.0/24Route objects for it name AS834. Add a route object with origin AS215607 in the RIR database for the space.2 of 673
ROA: origin85.232.178.0/24ROAs covering it name AS25369, AS199856, not AS215607. If AS215607 should announce it, add a ROA for AS215607.2 of 673
Route object: none85.232.178.0/24Route objects for it name AS25369, AS199856. Add a route object with origin AS215607 in the RIR database for the space.2 of 673
ROA: origin95.155.182.0/24ROAs covering it name AS834, not AS215607. If AS215607 should announce it, add a ROA for AS215607.2 of 673
Route object: none95.155.182.0/24Route objects for it name AS834. Add a route object with origin AS215607 in the RIR database for the space.2 of 673
ROA: origin168.222.5.0/24ROAs covering it name AS199550, not AS215607. If AS215607 should announce it, add a ROA for AS215607.2 of 673
Route object: none168.222.5.0/24Route objects for it name AS199550. Add a route object with origin AS215607 in the RIR database for the space.2 of 673
ROA: origin173.232.59.0/24ROAs covering it name AS834, not AS215607. If AS215607 should announce it, add a ROA for AS215607.2 of 673
Route object: none173.232.59.0/24Route objects for it name AS834. Add a route object with origin AS215607 in the RIR database for the space.2 of 673
ROA: origin178.83.252.0/24ROAs covering it name AS834, not AS215607. If AS215607 should announce it, add a ROA for AS215607.2 of 673
Route object: none178.83.252.0/24Route objects for it name AS834. Add a route object with origin AS215607 in the RIR database for the space.2 of 673
ROA: origin199.48.181.0/24ROAs covering it name AS834, not AS215607. If AS215607 should announce it, add a ROA for AS215607.2 of 673
Route object: none199.48.181.0/24Route objects for it name AS834, AS2914. Add a route object with origin AS215607 in the RIR database for the space.2 of 673
ROA: origin207.180.7.0/24ROAs covering it name AS136809, not AS215607. If AS215607 should announce it, add a ROA for AS215607.2 of 673
Route object: none207.180.7.0/24Route objects for it name AS136809. Add a route object with origin AS215607 in the RIR database for the space.2 of 673
ROA: origin208.66.111.0/24ROAs covering it name AS13649, AS31916, not AS215607. If AS215607 should announce it, add a ROA for AS215607.2 of 673
Route object: none208.66.111.0/24Route objects for it name AS31916. Add a route object with origin AS215607 in the RIR database for the space.2 of 673
ROA: origin216.83.41.0/24ROAs covering it name AS147281, not AS215607. If AS215607 should announce it, add a ROA for AS215607.2 of 673
Route object: none216.83.41.0/24Route objects for it name AS147281. Add a route object with origin AS215607 in the RIR database for the space.2 of 673
ROA: origin216.98.243.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS215607 should announce it, add a ROA for AS215607.2 of 673
Route object: none216.98.243.0/24No route object for it. Add a route object with origin AS215607 in the RIR database for the space.2 of 673
ROA: origin216.98.244.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS215607 should announce it, add a ROA for AS215607.2 of 673
Route object: none216.98.244.0/24No route object for it. Add a route object with origin AS215607 in the RIR database for the space.2 of 673
ROA: origin176.105.229.0/24ROAs covering it name AS137410, not AS215607. If AS215607 should announce it, add a ROA for AS215607.0 of 673
Route object: none176.105.229.0/24Route objects for it name AS137410. Add a route object with origin AS215607 in the RIR database for the space.0 of 673
ROA: origin162.141.179.0/24ROAs covering it name AS834, not AS215607. If AS215607 should announce it, add a ROA for AS215607.2 of 673
Route object: RIR162.141.179.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: origin162.141.183.0/24ROAs covering it name AS834, not AS215607. If AS215607 should announce it, add a ROA for AS215607.2 of 673
Route object: RIR162.141.183.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: origin207.180.48.0/24ROAs covering it name AS834, not AS215607. If AS215607 should announce it, add a ROA for AS215607.2 of 673
Route object: RIR207.180.48.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none45.56.193.0/24No ROA covers it. Add a ROA for AS215607, maxLength 24.2 of 673
Route object: none45.56.193.0/24Route objects for it name AS19318, AS30633. Add a route object with origin AS215607 in the RIR database for the space.2 of 673
ROA: none45.56.200.0/24No ROA covers it. Add a ROA for AS215607, maxLength 24.2 of 673
Route object: none45.56.200.0/24Route objects for it name AS19318, AS262287. Add a route object with origin AS215607 in the RIR database for the space.2 of 673
ROA: none204.29.220.0/24No ROA covers it. Add a ROA for AS215607, maxLength 24.671 of 673
Route object: RIR204.29.220.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR147.125.242.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR148.135.255.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR178.94.211.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR178.94.242.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR151.243.32.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR151.245.165.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR195.222.127.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

71.5.40.0/22ALTDBNo ROA
85.118.163.0/24RIPEValid
94.26.106.0/24RIPEValid
94.118.68.0/24RADB, RIPEValid
192.65.202.0/24RADBNo ROA
192.207.169.0/24RADBNo ROA
198.160.214.0/24RADBNo ROA
198.160.215.0/24RADBNo ROA
198.180.196.0/24RADBNo ROA
198.203.165.0/24RADBNo ROA
199.5.24.0/24RADBNo ROA
199.107.152.0/21ALTDBNo ROA
199.178.64.0/19ALTDBNo ROA
199.178.144.0/20ALTDBNo ROA
199.178.160.0/21ALTDBNo ROA
199.178.170.0/24ALTDBNo ROA
204.80.210.0/24RADBNo ROA
204.110.8.0/21ALTDBNo ROA
204.115.112.0/24RADBNo ROA
204.238.121.0/24RADBNo ROA
216.237.144.0/20ALTDBNo ROA
2a14:c380:140::/44RIPEInvalid: origin

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.