bgpreport

Network · data from 2026-11-12

AS214790 Brainoza OU

Registry name: BRAINOZA Brainoza OU, EE · PeeringDB

25IPv4 routes 100.0% RPKI valid · 100.0% with a route object
7IPv6 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 AS214790, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS214790, 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.
31.77.68.0/24 Valid RIR databaseRIPE 673 100% 67
89.22.192.0/24 Valid RIR databaseRIPE 673 100% 67
153.52.150.0/24 Valid RIR databaseRIPE 673 100% 67
185.36.140.0/23 Valid RIR databaseRIPE 673 100% 67
185.36.143.0/24 Valid RIR databaseRIPE 673 100% 67
185.37.8.0/24 Valid RIR databaseRIPE 673 100% 67
185.223.169.0/24 Valid RIR databaseRIPE 673 100% 67
185.223.170.0/24 Valid RIR databaseRIPE 673 100% 67
185.223.171.0/24 Valid RIR databaseRIPE 673 100% 67
185.225.205.0/24 Valid RIR databaseRIPE 673 100% 67
194.117.88.0/24 Valid RIR databaseRIPE 673 100% 67
5.181.201.0/24 Valid RIR databaseRIPE 672 100% 67
5.181.203.0/24 Valid RIR databaseRIPE 672 100% 67
5.189.254.0/24 Valid RIR databaseRIPE 672 100% 67
45.85.117.0/24 Valid RIR databaseRIPE 672 100% 67
45.155.120.0/24 Valid RIR databaseRIPE 672 100% 67
45.155.121.0/24 Valid RIR databaseRIPE 672 100% 67
45.158.81.0/24 Valid RIR databaseRIPE 672 100% 67
89.22.193.0/24 Valid RIR databaseRIPE 672 100% 67
185.36.140.0/24 Valid RIR databaseRIPE 672 100% 67
185.36.141.0/24 Valid RIR databaseRIPE 672 100% 67
185.36.142.0/24 Valid RIR databaseRIPE 672 100% 67
185.223.168.0/24 Valid RIR databaseRIPE 672 100% 67
5.181.202.0/24 Valid RIR databaseRIPE 671 100% 67
45.12.28.0/24 Valid RIR databaseRIPE 671 100% 67
2a10:c943::/32 Valid RIR databaseRIPE 634 100% 67
2a10:c943:100::/48 Valid RIR databaseRIPE 634 100% 67
2a10:c943:200::/48 Valid RIR databaseRIPE 634 100% 67
2a10:c943:300::/48 Valid RIR databaseRIPE 634 100% 67
2a10:c944::/32 Valid RIR databaseRIPE 633 100% 67
2a10:c944:100::/48 Valid RIR databaseRIPE 633 100% 67
2a10:c944:321::/48 Valid RIR databaseRIPE 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS214790: AS214790:AS-BRAINOZA. 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 (AS214790 isn't in the set, or no route object for AS214790 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 objectsAS214790 in itNot covered
AS214790:AS-BRAINOZA RIPE 5285 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 AS214790 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.