bgpreport

Network · data from 2026-11-12

AS25147 SOFIANET Ecoplast EOOD

Registry name: SOFIANET Ecoplast EOOD, BG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25147, 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.151.0/24 Invalid: origin Other origin onlycovered by 85.11.144.0/20 1 0%low visibility 1
85.11.145.82/32 Invalid: maxLength Nonecovered by 85.11.145.0/24 3 0%low visibility 6
85.11.144.0/24 Valid RIR databaseRIPE 673 100% 66
85.11.145.0/24 Valid RIR databaseRIPE 673 100% 66
85.11.146.0/24 Valid RIR databaseRIPE 673 100% 66
85.11.147.0/24 Valid RIR databaseRIPE 673 100% 66
85.11.148.0/24 Valid RIR databaseRIPE 673 100% 66
85.11.149.0/24 Valid RIR databaseRIPE 673 100% 66
85.11.150.0/24 Valid RIR databaseRIPE 673 100% 66
85.11.156.0/24 Valid RIR databaseRIPE 673 100% 66
85.11.157.0/24 Valid RIR databaseRIPE 673 100% 66
85.11.158.0/24 Valid RIR databaseRIPE 673 100% 66
85.11.159.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS25147 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 5 are in fix.csv.

  • ROA: origin1
  • ROA: maxLength1
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin85.11.151.0/24ROAs covering it name AS48747, not AS25147. If AS25147 should announce it, add a ROA for AS25147.1 of 673
Route object: none85.11.151.0/24Route objects for it name AS48747. A route object for 85.11.144.0/20 with origin AS25147 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25147 in the RIR database for the space.1 of 673
ROA: maxLength85.11.145.82/32ROA 85.11.145.0/24 AS25147 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 85.11.145.82/32.3 of 673
Route object: none85.11.145.82/32No route object for it. A route object for 85.11.145.0/24 with origin AS25147 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS25147 in the RIR database for the space.3 of 673

Route objects not announced

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

85.11.144.0/20RIPENo 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.