bgpreport

Network · data from 2026-11-12

AS59878 ASBFB BFB ONE FZ-LLC

Registry name: ASBFB BFB ONE FZ-LLC, AE · not in PeeringDB

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

Announced routes

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

77.74.201.0/24 No ROA RIR databaseRADB, RIPE 673 100% 66
2a13:8a40::/48 No ROA RIR databaseRADB, RIPE 633 100% 68
89.125.150.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
91.132.48.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
188.208.110.0/24 Valid RIR databaseRADB, RIPE 673 100% 66

AS-SET

AS59878 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 31 are in fix.csv.

  • ROA: none2
  • Route object: not announced29
ChangePrefix or setDetailFull-table peers
ROA: none77.74.201.0/24No ROA covers it. Add a ROA for AS59878, maxLength 24.673 of 673
ROA: none2a13:8a40::/48No ROA covers it. Add a ROA for AS59878, maxLength 48.633 of 636

Route objects not announced

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

2.56.242.0/24RADBNo ROA
31.129.123.0/24RADBNo ROA
45.8.158.0/23RADBNo ROA
45.89.228.0/23RADBNo ROA
45.130.146.0/23RADBNo ROA
45.135.134.0/23RADBNo ROA
45.136.244.0/23RADBNo ROA
45.140.168.0/23RADBNo ROA
45.147.200.0/23RADBNo ROA
50.114.164.0/22RADBNo ROA
91.224.23.0/24RADBNo ROA
93.89.218.0/24RADBNo ROA
104.166.124.0/22RADBNo ROA
107.182.140.0/22RADBNo ROA
134.195.98.0/23RADBNo ROA
172.82.86.0/23RADBNo ROA
172.99.172.0/22RADBNo ROA
185.143.220.0/23RADBNo ROA
185.143.222.0/24RADBNo ROA
185.143.223.0/24RADBNo ROA
188.119.64.0/23RADBNo ROA
193.53.126.0/23RADBNo ROA
193.124.15.0/24RADBNo ROA
194.165.2.0/24RADBNo ROA
195.133.56.0/22RADBNo ROA
209.209.112.0/22RADBNo ROA
212.60.5.0/24RADBNo ROA
212.193.24.0/22RADBNo ROA
213.109.193.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.