bgpreport

Network · data from 2026-11-12

AS214647 YADDA

Registry name: YADDA Yadda OU, EE · PeeringDB

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

Announced routes

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

206.245.144.0/24 Invalid: origin Other origin only 3 0%low visibility 3
206.245.156.0/24 Invalid: origin Other origin only 3 0%low visibility 3
143.14.198.0/24 Invalid: origin Other origin only 2 0%low visibility 2
155.117.201.0/24 Invalid: origin Other origin only 2 0%low visibility 2
162.141.39.0/24 Invalid: origin Other origin only 2 0%low visibility 2
62.105.198.0/24 Invalid: origin Other origin only 1 0%low visibility 1
143.20.214.0/24 Invalid: origin Other origin only 1 0%low visibility 1
212.189.27.0/24 Invalid: origin Other origin only 1 0%low visibility 1
9.247.57.0/24 Valid RIR databaseRIPE 672 100% 67
9.247.87.0/24 Valid RIR databaseRIPE 672 100% 67
9.247.207.0/24 Valid RIR databaseRIPE 672 100% 67
82.27.36.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
82.27.37.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
82.27.65.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
143.14.122.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
155.117.137.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
179.236.136.0/24 Valid RIR databaseRIPE 672 100% 67
179.236.137.0/24 Valid RIR databaseRIPE 672 100% 67
179.236.138.0/24 Valid RIR databaseRIPE 672 100% 67
193.124.5.0/24 Valid RIR databaseRIPE 672 100% 67
193.124.7.0/24 Valid RIR databaseRIPE 672 100% 67
194.87.119.0/24 Valid RIR databaseRIPE 672 100% 67
194.87.136.0/24 Valid RIR databaseRIPE 672 100% 67
194.87.179.0/24 Valid RIR databaseRIPE 672 100% 67
195.133.29.0/24 Valid RIR databaseRIPE 672 100% 67
201.58.164.0/24 Valid RIR databaseRIPE 672 100% 67
201.58.165.0/24 Valid RIR databaseRIPE 672 100% 67
201.58.166.0/24 Valid RIR databaseRIPE 672 100% 67
201.58.167.0/24 Valid RIR databaseRIPE 672 100% 67
201.58.168.0/24 Valid RIR databaseRIPE 672 100% 67
201.58.169.0/24 Valid RIR databaseRIPE 672 100% 67
201.58.170.0/24 Valid RIR databaseRIPE 672 100% 67
206.245.147.0/24 Valid RIR databaseRIPE 672 100% 67
206.245.150.0/24 Valid RIR databaseRIPE 672 100% 67
206.245.155.0/24 Valid RIR databaseRIPE 672 100% 67
212.192.241.0/24 Valid RIR databaseRIPE 672 100% 67
212.193.7.0/24 Valid RIR databaseRIPE 672 100% 67
82.22.4.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
131.143.38.0/24 Valid RIR databaseARIN 671 100% 67
213.193.241.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
176.105.228.0/24 Valid RIR databaseARIN, RADB 670 100% 67
2a0b:ba40::/29 Valid RIR databaseRADB, RIPE 635 100% 67
2a0b:ba40::/48 Valid RIR databaseRIPE 635 100% 67
2a0b:ba40:1::/48 Valid RIR databaseRIPE 635 100% 67
82.21.57.0/24 Valid RIR databaseRADB, RIPE 1 0%low visibility 1

AS-SET

AS214647'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 101 are in fix.csv.

  • ROA: origin8
  • Route object: none8
  • Route object: not announced85
ChangePrefix or setDetailFull-table peers
ROA: origin206.245.144.0/24ROAs covering it name AS3223, not AS214647. If AS214647 should announce it, add a ROA for AS214647.3 of 673
Route object: none206.245.144.0/24Route objects for it name AS3223. Add a route object with origin AS214647 in the RIR database for the space.3 of 673
ROA: origin206.245.156.0/24ROAs covering it name AS3223, not AS214647. If AS214647 should announce it, add a ROA for AS214647.3 of 673
Route object: none206.245.156.0/24Route objects for it name AS3223. Add a route object with origin AS214647 in the RIR database for the space.3 of 673
ROA: origin143.14.198.0/24ROAs covering it name AS834, not AS214647. If AS214647 should announce it, add a ROA for AS214647.2 of 673
Route object: none143.14.198.0/24Route objects for it name AS834. Add a route object with origin AS214647 in the RIR database for the space.2 of 673
ROA: origin155.117.201.0/24ROAs covering it name AS834, not AS214647. If AS214647 should announce it, add a ROA for AS214647.2 of 673
Route object: none155.117.201.0/24Route objects for it name AS834. Add a route object with origin AS214647 in the RIR database for the space.2 of 673
ROA: origin162.141.39.0/24ROAs covering it name AS834, not AS214647. If AS214647 should announce it, add a ROA for AS214647.2 of 673
Route object: none162.141.39.0/24Route objects for it name AS834. Add a route object with origin AS214647 in the RIR database for the space.2 of 673
ROA: origin62.105.198.0/24ROAs covering it name AS401617, not AS214647. If AS214647 should announce it, add a ROA for AS214647.1 of 673
Route object: none62.105.198.0/24Route objects for it name AS401617. Add a route object with origin AS214647 in the RIR database for the space.1 of 673
ROA: origin143.20.214.0/24ROAs covering it name AS834, not AS214647. If AS214647 should announce it, add a ROA for AS214647.1 of 673
Route object: none143.20.214.0/24Route objects for it name AS834. Add a route object with origin AS214647 in the RIR database for the space.1 of 673
ROA: origin212.189.27.0/24ROAs covering it name AS3257, AS134494, not AS214647. If AS214647 should announce it, add a ROA for AS214647.1 of 673
Route object: none212.189.27.0/24Route objects for it name AS134494. Add a route object with origin AS214647 in the RIR database for the space.1 of 673

Route objects not announced

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

5.10.209.0/24RIPEValid
9.247.49.0/24RIPEValid
9.247.55.0/24RIPEValid
9.247.59.0/24RIPEValid
9.247.61.0/24RIPEValid
9.247.68.0/24RIPEValid
9.247.69.0/24RIPEValid
9.247.73.0/24RIPEValid
9.247.75.0/24RIPEValid
9.247.76.0/24RIPEValid
9.247.85.0/24RIPEValid
9.247.93.0/24RIPEValid
9.247.94.0/24RIPEValid
9.247.95.0/24RIPEValid
9.247.97.0/24RIPEValid
9.247.99.0/24RIPEValid
9.247.101.0/24RIPEValid
9.247.105.0/24RIPEValid
9.247.106.0/24RIPEValid
9.247.108.0/24RIPEValid
9.247.114.0/24RIPEValid
9.247.116.0/24RIPEValid
9.247.117.0/24RIPEValid
9.247.120.0/24RIPEValid
9.247.123.0/24RIPEValid
9.247.125.0/24RIPEValid
9.247.129.0/24RIPEValid
9.247.130.0/24RIPEValid
9.247.137.0/24RIPEValid
9.247.152.0/24RIPEValid
9.247.153.0/24RIPEValid
9.247.154.0/24RIPEValid
9.247.156.0/24RIPEValid
9.247.161.0/24RIPEValid
9.247.162.0/24RIPEValid
9.247.163.0/24RIPEValid
9.247.170.0/24RIPEValid
9.247.176.0/24RIPEValid
9.247.182.0/24RIPEValid
9.247.198.0/24RIPEValid
9.247.203.0/24RIPEValid
9.247.205.0/24RIPEValid
9.247.208.0/24RIPEValid
9.247.211.0/24RIPEValid
9.247.214.0/24RIPEValid
9.247.216.0/24RIPEValid
9.247.219.0/24RIPEValid
9.247.220.0/24RIPEValid
9.247.232.0/24RIPEValid
9.247.242.0/24RIPEValid
9.247.254.0/24RIPEValid
78.17.228.0/24RIPEValid
78.17.235.0/24RIPEValid
78.17.241.0/24RIPEValid
78.17.252.0/24RIPEValid
78.17.253.0/24RIPEValid
78.17.254.0/24RIPEValid
82.21.125.0/24RADB, RIPEValid
82.39.247.0/24RADB, RIPEValid
84.75.41.0/24RADB, RIPEValid
132.243.215.0/24RIPEValid
143.14.92.0/24RADB, RIPEValid
143.20.229.0/24RADB, RIPEValid
155.117.38.0/24RADB, RIPEValid
163.245.44.0/24RIPEValid
167.148.83.0/24RADB, RIPEValid
178.83.133.0/24RADB, RIPEValid
194.87.150.0/24RIPEValid
195.58.59.0/24RIPEValid
195.58.60.0/24RIPEValid
201.58.140.0/24RIPEValid
201.58.141.0/24RIPEValid
201.58.142.0/24RIPEValid
201.58.143.0/24RIPEValid
201.58.144.0/24RIPEValid
201.58.145.0/24RIPEValid
201.58.146.0/24RIPEValid
201.58.147.0/24RIPEValid
201.58.148.0/24RIPEValid
201.58.149.0/24RIPEValid
201.58.157.0/24RIPEValid
209.161.105.0/24RIPEValid
209.161.107.0/24RIPEValid
212.193.12.0/24RIPEValid
212.193.13.0/24RIPEValid

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.