bgpreport

Network · data from 2026-11-12

AS197825 EMAXY AS197825

Registry name: EMAXY EMAXY SRL, IT · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS197825, 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.
176.10.56.0/24 Valid RIR databaseRIPE 673 100% 67
176.10.57.0/24 Valid RIR databaseRIPE 673 100% 67
176.10.58.0/24 Valid RIR databaseRIPE 673 100% 67
176.10.59.0/24 Valid RIR databaseRIPE 673 100% 67
176.10.60.0/24 Valid RIR databaseRIPE 673 100% 67
176.10.61.0/24 Valid RIR databaseRIPE 673 100% 67
176.10.62.0/24 Valid RIR databaseRIPE 673 100% 67
176.10.63.0/24 Valid RIR databaseRIPE 673 100% 67
2a06:2085::/32 Valid RIR databaseRIPE 636 100% 67
2a06:2080::/32 Valid RIR databaseRIPE 635 100% 67
2a06:2081::/32 Valid RIR databaseRIPE 635 100% 67
2a06:2082::/32 Valid RIR databaseRIPE 635 100% 67
2a06:2083::/32 Valid RIR databaseRIPE 635 100% 67
2a06:2084::/32 Valid RIR databaseRIPE 635 100% 67
2a06:2086::/32 Valid RIR databaseRIPE 635 100% 67
2a06:2087::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS197825: AS-EMAXY. 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 (AS197825 isn't in the set, or no route object for AS197825 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 objectsAS197825 in itNot covered
AS-EMAXY RIPE 2141 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 AS197825 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.