bgpreport

Network · data from 2026-11-12

AS51581 Profonika-BG Profonika EOOD

Registry name: Profonika-BG Profonika EOOD, BG · not in PeeringDB

3IPv4 routes 66.7% 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
0Route objects not announced registered with origin AS51581, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS51581, 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.
193.200.237.0/24 No ROA RIR databaseRIPE 671 100% 66
2001:678:5f8::/48 No ROA RIR databaseRIPE 633 100% 69
78.83.208.0/24 Valid RIR databaseRIPE 671 100% 66
212.36.13.0/24 Valid RIR databaseRIPE 671 100% 66

AS-SET

AS51581 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 2 are in fix.csv.

  • ROA: none2
ChangePrefix or setDetailFull-table peers
ROA: none193.200.237.0/24No ROA covers it. Add a ROA for AS51581, maxLength 24.671 of 673
ROA: none2001:678:5f8::/48No ROA covers it. Add a ROA for AS51581, maxLength 48.633 of 636

Route objects not announced

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