bgpreport

Network · data from 2026-11-12

AS15377 Fregat

Registry name: FREGAT TRADITIONAL LLC, UA · PeeringDB

15IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS15377, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS15377, 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.
5.252.180.0/22 Valid RIR databaseRIPE 671 100% 68
46.98.0.0/16 Valid RIR databaseRIPE 671 100% 68
88.218.180.0/22 Valid RIR databaseRIPE 671 100% 68
91.201.68.0/22 Valid RIR databaseRIPE 671 100% 68
91.215.52.0/22 Valid RIR databaseRIPE 671 100% 68
91.233.96.0/22 Valid RIR databaseRIPE 671 100% 68
91.236.96.0/22 Valid RIR databaseRIPE 671 100% 68
91.243.192.0/19 Valid RIR databaseRIPE 671 100% 68
178.215.160.0/20 Valid RIR databaseRIPE 671 100% 68
185.205.144.0/22 Valid RIR databaseRIPE 671 100% 68
185.244.140.0/22 Valid RIR databaseRIPE 671 100% 68
192.162.108.0/22 Valid RIR databaseRIPE 671 100% 68
193.108.248.0/22 Valid RIR databaseRIPE 671 100% 68
212.115.224.0/19 Valid RIR databaseRIPE 671 100% 68
213.177.180.0/24 Valid RIR databaseRIPE 671 100% 68
2a05:8dc0::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS15377: RIPE::AS-FREGAT. 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 (AS15377 isn't in the set, or no route object for AS15377 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 objectsAS15377 in itNot covered
RIPE::AS-FREGAT RIPE 4119 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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