bgpreport

Network · data from 2026-11-12

AS208057 FILI-01 Filip informatika d.o.o.

Registry name: FILI-01 Filip informatika d.o.o., HR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS208057, 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.
147.78.148.0/23 No ROA RIR databaseRIPE 673 100% 67
147.78.150.0/23 No ROA RIR databaseRIPE 671 100% 68
213.191.140.0/24 Valid None 673 100% 67

AS-SET

AS208057 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 3 are in fix.csv.

  • ROA: none2
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none147.78.148.0/23No ROA covers it. Add a ROA for AS208057, maxLength 23.673 of 673
ROA: none147.78.150.0/23No ROA covers it. Add a ROA for AS208057, maxLength 23.671 of 673
Route object: none213.191.140.0/24No route object for it. Add a route object with origin AS208057 in the RIR database for the space.673 of 673

Route objects not announced

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