bgpreport

Network · data from 2026-11-12

AS219105 APFB AppFabric LLC

Registry name: APFB AppFabric LLC, AE · not in PeeringDB

39IPv4 routes 61.5% RPKI valid · 64.1% with a route object
0IPv6 routes
15RPKI invalid 15 origin · 0 maxLength
0No ROA 14 with no route object for this origin
15Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS219105, seen from no peer

Announced routes

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

31.56.192.0/24 Invalid: origin None 2 0%low visibility 2
64.204.128.0/24 Invalid: origin None 2 0%low visibility 2
84.247.75.0/24 Invalid: origin None 2 0%low visibility 2
91.124.57.0/24 Invalid: origin None 2 0%low visibility 2
146.103.51.0/24 Invalid: origin Other origin only 2 0%low visibility 2
151.240.249.0/24 Invalid: origin Other origin only 2 0%low visibility 2
151.242.137.0/24 Invalid: origin Other origin only 2 0%low visibility 2
163.8.220.0/24 Invalid: origin Other origin only 2 0%low visibility 2
178.92.123.0/24 Invalid: origin None 2 0%low visibility 2
178.93.118.0/24 Invalid: origin Other origin only 2 0%low visibility 2
178.93.226.0/24 Invalid: origin Other origin only 2 0%low visibility 2
180.210.222.0/24 Invalid: origin Other origin only 2 0%low visibility 2
212.17.234.0/24 Invalid: origin Other origin only 1 0%low visibility 1
176.102.168.0/24 Invalid: origin Other origin only 0 0%low visibility 1
102.129.183.0/24 Invalid: origin RIR databaseAFRINIC 2 0%low visibility 2
40.27.114.0/24 Valid RIR databaseARIN, RADB 672 100% 67
40.27.134.0/24 Valid RIR databaseARIN, RADB 672 100% 67
40.27.219.0/24 Valid RIR databaseARIN, RADB 672 100% 67
64.204.216.0/24 Valid RIR databaseARIN, RADB 672 100% 67
64.226.205.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
91.238.92.0/24 Valid RIR databaseARIN, RADB 672 100% 67
93.92.18.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
141.11.235.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
143.20.148.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
151.241.23.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
151.246.5.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
178.94.208.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
179.61.204.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
188.220.139.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
195.72.168.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
216.75.147.0/24 Valid RIR databaseARIN, RADB 672 100% 67
40.27.127.0/24 Valid RIR databaseARIN, RADB 671 100% 67
72.244.58.0/24 Valid RIR databaseARIN, RADB 671 100% 67
72.244.64.0/24 Valid RIR databaseARIN, RADB 671 100% 67
72.244.67.0/24 Valid RIR databaseARIN, RADB 671 100% 67
72.244.74.0/24 Valid RIR databaseARIN, RADB 671 100% 67
72.244.79.0/24 Valid RIR databaseARIN, RADB 671 100% 67
74.1.46.0/24 Valid RIR databaseARIN, RADB 671 100% 67
89.116.45.0/24 Valid RIR databaseRADB, RIPE 662 98% 67

AS-SET

AS219105 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 30 are in fix.csv.

  • ROA: origin15
  • Route object: none14
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin31.56.192.0/24ROAs covering it name AS834, not AS219105. If AS219105 should announce it, add a ROA for AS219105.2 of 673
Route object: none31.56.192.0/24No route object for it. Add a route object with origin AS219105 in the RIR database for the space.2 of 673
ROA: origin64.204.128.0/24ROAs covering it name AS834, AS14618, AS16509, not AS219105. If AS219105 should announce it, add a ROA for AS219105.2 of 673
Route object: none64.204.128.0/24No route object for it. Add a route object with origin AS219105 in the RIR database for the space.2 of 673
ROA: origin84.247.75.0/24ROAs covering it name AS12310, not AS219105. If AS219105 should announce it, add a ROA for AS219105.2 of 673
Route object: none84.247.75.0/24No route object for it. Add a route object with origin AS219105 in the RIR database for the space.2 of 673
ROA: origin91.124.57.0/24ROAs covering it name AS834, not AS219105. If AS219105 should announce it, add a ROA for AS219105.2 of 673
Route object: none91.124.57.0/24No route object for it. Add a route object with origin AS219105 in the RIR database for the space.2 of 673
ROA: origin146.103.51.0/24ROAs covering it name AS834, not AS219105. If AS219105 should announce it, add a ROA for AS219105.2 of 673
Route object: none146.103.51.0/24Route objects for it name AS834. Add a route object with origin AS219105 in the RIR database for the space.2 of 673
ROA: origin151.240.249.0/24ROAs covering it name AS834, not AS219105. If AS219105 should announce it, add a ROA for AS219105.2 of 673
Route object: none151.240.249.0/24Route objects for it name AS834. Add a route object with origin AS219105 in the RIR database for the space.2 of 673
ROA: origin151.242.137.0/24ROAs covering it name AS834, not AS219105. If AS219105 should announce it, add a ROA for AS219105.2 of 673
Route object: none151.242.137.0/24Route objects for it name AS834. Add a route object with origin AS219105 in the RIR database for the space.2 of 673
ROA: origin163.8.220.0/24ROAs covering it name AS834, not AS219105. If AS219105 should announce it, add a ROA for AS219105.2 of 673
Route object: none163.8.220.0/24Route objects for it name AS834. Add a route object with origin AS219105 in the RIR database for the space.2 of 673
ROA: origin178.92.123.0/24ROAs covering it name AS834, AS20473, not AS219105. If AS219105 should announce it, add a ROA for AS219105.2 of 673
Route object: none178.92.123.0/24No route object for it. Add a route object with origin AS219105 in the RIR database for the space.2 of 673
ROA: origin178.93.118.0/24ROAs covering it name AS834, AS20473, not AS219105. If AS219105 should announce it, add a ROA for AS219105.2 of 673
Route object: none178.93.118.0/24Route objects for it name AS834. Add a route object with origin AS219105 in the RIR database for the space.2 of 673
ROA: origin178.93.226.0/24ROAs covering it name AS834, AS20473, not AS219105. If AS219105 should announce it, add a ROA for AS219105.2 of 673
Route object: none178.93.226.0/24Route objects for it name AS20473. Add a route object with origin AS219105 in the RIR database for the space.2 of 673
ROA: origin180.210.222.0/24ROAs covering it name AS136809, AS402298, not AS219105. If AS219105 should announce it, add a ROA for AS219105.2 of 673
Route object: none180.210.222.0/24Route objects for it name AS136809, AS402298. Add a route object with origin AS219105 in the RIR database for the space.2 of 673
ROA: origin212.17.234.0/24ROAs covering it name AS152606, not AS219105. If AS219105 should announce it, add a ROA for AS219105.1 of 673
Route object: none212.17.234.0/24Route objects for it name AS152606. Add a route object with origin AS219105 in the RIR database for the space.1 of 673
ROA: origin176.102.168.0/24ROAs covering it name AS198377, not AS219105. If AS219105 should announce it, add a ROA for AS219105.0 of 673
Route object: none176.102.168.0/24Route objects for it name AS198377. Add a route object with origin AS219105 in the RIR database for the space.0 of 673
ROA: origin102.129.183.0/24ROAs covering it name AS834, not AS219105. If AS219105 should announce it, add a ROA for AS219105.2 of 673

Route objects not announced

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

2a03:5840:15a::/48RIPEValid

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.