bgpreport

Network · data from 2026-11-12

AS213382 PEERYX NETWORK SAS

Registry name: PEERYX PEERYX NETWORK SAS, FR · PeeringDB

7IPv4 routes 85.7% RPKI valid · 85.7% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
0No ROA 1 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS213382, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS213382, 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.
108.165.190.0/24 Invalid: origin Other origin only 2 0%low visibility 2
9.247.19.0/24 Valid RIR databaseRIPE 671 100% 66
9.247.26.0/24 Valid RIR databaseRIPE 670 100% 66
108.59.252.0/24 Valid RIR databaseARIN 669 99% 66
66.6.59.0/24 Valid RIR databaseARIN 664 99% 66
185.165.78.0/24 Valid RIR databaseRIPE 661 98% 66
78.108.119.0/24 Valid RIR databaseRIPE 660 98% 66
2a0c:b641:830::/44 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS213382: RIPE::AS213382:AS-PEERYX. 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 (AS213382 isn't in the set, or no route object for AS213382 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 objectsAS213382 in itNot covered
RIPE::AS213382:AS-PEERYX RIPElists itself further down3 member sets in no database: AS-NIXCON, AS-PIXOOF, AS18002:AS-WORLDPHONE-IN 166243,606 Yes 1

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 5 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • AS-SET: missing member3
ChangePrefix or setDetailFull-table peers
ROA: origin108.165.190.0/24ROAs covering it name AS219284, not AS213382. If AS213382 should announce it, add a ROA for AS213382.2 of 673
Route object: none108.165.190.0/24Route objects for it name AS219284. Add a route object with origin AS213382 in the RIR database for the space.2 of 673
AS-SET: missing memberRIPE::AS213382:AS-PEERYXAS213382:AS-PEERYX (RIPE) lists AS-NIXCON; no IRR database read has it.
AS-SET: missing memberRIPE::AS213382:AS-PEERYXAS213382:AS-PEERYX (RIPE) lists AS-PIXOOF; no IRR database read has it.
AS-SET: missing memberRIPE::AS213382:AS-PEERYXAS213382:AS-PEERYX (RIPE) lists AS18002:AS-WORLDPHONE-IN; no IRR database read has it.

Route objects not announced

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