bgpreport

Network · data from 2026-11-12

AS207144 BG-SOFCOMPANY-AS SOFCOMPANY Ltd

Registry name: BG-SOFCOMPANY-AS SOFCOMPANY Ltd, BG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS207144, 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.
85.11.160.0/24 Valid None 94 14% 33
85.11.168.0/24 Valid None 94 14% 33
85.11.128.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.129.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.130.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.131.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.132.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.133.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.134.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.135.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.136.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.137.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.138.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.139.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.140.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.141.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.142.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.143.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.162.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.164.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.165.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.166.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.169.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.170.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.171.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.172.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.173.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.174.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.175.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.176.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.177.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.178.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.179.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.184.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.185.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.186.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.188.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.189.0/24 Valid RIR databaseRIPE 673 100% 67
85.11.191.0/24 Valid RIR databaseRIPE 673 100% 67
185.164.240.0/24 Valid RIR databaseRIPE 673 100% 67
185.164.241.0/24 Valid RIR databaseRIPE 673 100% 67
185.164.242.0/24 Valid RIR databaseRIPE 673 100% 67
185.164.243.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

AS207144 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.

  • Route object: none2
ChangePrefix or setDetailFull-table peers
Route object: none85.11.160.0/24No route object for it. Add a route object with origin AS207144 in the RIR database for the space.94 of 673
Route object: none85.11.168.0/24No route object for it. Add a route object with origin AS207144 in the RIR database for the space.94 of 673

Route objects not announced

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