bgpreport

Network · data from 2026-11-12

AS30714 PHX-ASN - Axway Inc

Registry name: PHX-ASN - Axway Inc, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS30714, 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.
208.67.128.0/24 Valid Nonecovered by 208.67.128.0/22 673 100% 67
2620:ad:8081::/48 Valid Other IRR onlyRADB 636 100% 67
208.67.128.0/22 Valid RIR databaseARIN, RADB 673 100% 67
2620:ad:8000::/40 Valid RIR databaseARIN, RADB 636 100% 67

AS-SET

AS30714 isn't in PeeringDB, where networks name their AS-SET.

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

  • Route object: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
Route object: none208.67.128.0/24No route object for it. A route object for 208.67.128.0/22 with origin AS30714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30714 in the RIR database for the space.673 of 673
Route object: RIR2620:ad:8081::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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