bgpreport

Network · data from 2026-11-12

AS57455 Filanco Ukraine

Registry name: Filanco-LTD-UA Filanco Ukraine Ltd., UA · PeeringDB

2IPv4 routes 100.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
1No ROA 0 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS57455, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS57455, 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.
2001:67c:2b8c::/48 No ROA RIR databaseRIPE 1 0%low visibility 1
193.222.52.0/22 Valid RIR databaseRIPE 671 100% 68
193.222.53.0/24 Valid RIR databaseRIPE 671 100% 68

AS-SET

PeeringDB's irr_as_set for AS57455: AS-FILANCO-IX-UA. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS57455 isn't in the set, or no route object for AS57455 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS57455 in itNot covered
AS-FILANCO-IX-UA RIPElists itself further down7 member sets in no database: AS-AIREXPRESS, AS-HORS, AS-INFOBYTE-IFIX, AS-S3W-UA, AS-UNETCOM … 1,11927914,428 Yes 0

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

  • ROA: none1
  • AS-SET: missing member7
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none2001:67c:2b8c::/48No ROA covers it. Add a ROA for AS57455, maxLength 48.1 of 636
AS-SET: missing memberAS-FILANCO-IX-UAAS-FILANCO-IX-UA (RIPE) lists AS-AIREXPRESS; no IRR database read has it.
AS-SET: missing memberAS-FILANCO-IX-UAAS-FILANCO-IX-UA (RIPE) lists AS-HORS; no IRR database read has it.
AS-SET: missing memberAS-FILANCO-IX-UAAS-FILANCO-IX-UA (RIPE) lists AS-INFOBYTE-IFIX; no IRR database read has it.
AS-SET: missing memberAS-FILANCO-IX-UAAS-FILANCO-IX-UA (RIPE) lists AS-S3W-UA; no IRR database read has it.
AS-SET: missing memberAS-FILANCO-IX-UAAS-FILANCO-IX-UA (RIPE) lists AS-UNETCOM; no IRR database read has it.
AS-SET: missing memberAS-FILANCO-IX-UAAS-FILANCO-IX-UA (RIPE) lists AS-WINTELECOM; no IRR database read has it.
AS-SET: missing memberAS-FILANCO-IX-UAAS-FILANCO-IX-UA (RIPE) lists AS199986:AS-SET; no IRR database read has it.

Route objects not announced

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

193.222.52.0/24RIPEInvalid: maxLength
193.222.54.0/24RIPEInvalid: maxLength
193.222.55.0/24RIPEInvalid: maxLength
2001:470:3a3::/48ARINValid
2001:678:1254::/48RIPENo 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.