bgpreport

Network · data from 2026-11-12

AS18725 PVH Corp.

Registry name: PVH-INTERNET1 - PVH Corp., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18725, 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.
64.250.17.0/24 No ROA Other IRR onlyRADB 673 100% 67
64.250.18.0/24 No ROA Other IRR onlyRADB 672 100% 67
198.212.213.0/24 Valid RIR databaseARIN, RADB 673 100% 67
198.212.215.0/24 Valid RIR databaseARIN 672 100% 67
64.250.20.0/24 Valid RIR databaseARIN, RADB 671 100% 67
64.250.21.0/24 Valid RIR databaseARIN, RADB 669 99% 66

AS-SET

AS18725's PeeringDB record names no 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 8 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none64.250.17.0/24No ROA covers it. Add a ROA for AS18725, maxLength 24.673 of 673
Route object: RIR64.250.17.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none64.250.18.0/24No ROA covers it. Add a ROA for AS18725, maxLength 24.672 of 673
Route object: RIR64.250.18.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Route objects with origin AS18725 whose prefix no peer sees AS18725 announce. Many are kept on purpose (backup routes, space announced only in some places).

64.250.19.0/24RADBNo ROA
68.64.148.0/23RADBNo ROA
198.212.214.0/24ARIN, RADBValid
206.51.240.0/21RADBNo ROA

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.