bgpreport

Network · data from 2026-11-12

AS395097 PACHEZ HOLDINGS

Registry name: PACHEZ2 - PACHEZ HOLDINGS LTD., CA · PeeringDB

2IPv4 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
3No 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 AS395097, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS395097, 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.
198.199.7.0/24 No ROA RIR databaseARIN 668 99% 67
205.234.115.0/24 No ROA RIR databaseARIN 668 99% 67
2620:36:c000::/48 No ROA RIR databaseARIN 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS395097: AS-PHL2. 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 (AS395097 isn't in the set, or no route object for AS395097 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 objectsAS395097 in itNot covered
AS-PHL2 ARIN 113 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 3 are in fix.csv.

  • ROA: none3
ChangePrefix or setDetailFull-table peers
ROA: none198.199.7.0/24No ROA covers it. Add a ROA for AS395097, maxLength 24.668 of 673
ROA: none205.234.115.0/24No ROA covers it. Add a ROA for AS395097, maxLength 24.668 of 673
ROA: none2620:36:c000::/48No ROA covers it. Add a ROA for AS395097, maxLength 48.635 of 636

Route objects not announced

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