bgpreport

Network · data from 2026-11-12

AS29074 Faust ISP

Registry name: FAUST-ASN FAUST ISP LTD., UA · PeeringDB

6IPv4 routes 0.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
7No 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 AS29074, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS29074, 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.
91.206.4.0/23 No ROA RIR databaseRIPE 672 100% 67
91.215.8.0/22 No ROA RIR databaseRIPE 672 100% 67
91.221.234.0/23 No ROA RIR databaseRIPE 672 100% 67
195.49.148.0/22 No ROA RIR databaseRIPE 672 100% 67
195.60.228.0/22 No ROA RIR databaseRIPE 672 100% 67
195.68.202.0/23 No ROA RIR databaseRIPE 672 100% 67
2001:67c:ce8::/48 No ROA RIR databaseRIPE 633 100% 69

AS-SET

PeeringDB's irr_as_set for AS29074: AS-FAUST. 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 (AS29074 isn't in the set, or no route object for AS29074 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 objectsAS29074 in itNot covered
AS-FAUST RIPE 7235 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 7 are in fix.csv.

  • ROA: none7
ChangePrefix or setDetailFull-table peers
ROA: none91.206.4.0/23No ROA covers it. Add a ROA for AS29074, maxLength 23.672 of 673
ROA: none91.215.8.0/22No ROA covers it. Add a ROA for AS29074, maxLength 22.672 of 673
ROA: none91.221.234.0/23No ROA covers it. Add a ROA for AS29074, maxLength 23.672 of 673
ROA: none195.49.148.0/22No ROA covers it. Add a ROA for AS29074, maxLength 22.672 of 673
ROA: none195.60.228.0/22No ROA covers it. Add a ROA for AS29074, maxLength 22.672 of 673
ROA: none195.68.202.0/23No ROA covers it. Add a ROA for AS29074, maxLength 23.672 of 673
ROA: none2001:67c:ce8::/48No ROA covers it. Add a ROA for AS29074, maxLength 48.633 of 636

Route objects not announced

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