bgpreport

Network · data from 2026-11-12

AS32042 EVERGATE-NETWORKS

Registry name: EVERGATE-NETWORKS - Evergate Solutions, CA · PeeringDB

2IPv4 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
3Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS32042, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS32042, 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.
192.189.89.0/24 Valid RIR databaseARIN 668 99% 67
2602:f4e3:bb::/48 Valid RIR databaseARIN 636 100% 69
2602:f4e3::/36 Valid RIR databaseARIN 635 100% 69
2602:f4e3:cc::/48 Valid RIR databaseARIN 635 100% 69
2602:f4e3:ee::/48 Valid RIR databaseARIN 635 100% 67
2602:f4e3:aa::/48 Valid RIR databaseARIN 634 100% 69
83.245.58.0/24 Valid RIR databaseRIPE 5 1%low visibility 4
2602:f4e3:dd::/48 Valid RIR databaseARIN 2 0%low visibility 2
2602:f4e3:ff::/48 Valid RIR databaseARIN 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS32042: AS32042:AS-CUSTOMERS. 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 (AS32042 isn't in the set, or no route object for AS32042 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 objectsAS32042 in itNot covered
AS32042:AS-CUSTOMERS ARIN 119 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 AS32042 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.