bgpreport

Network · data from 2026-11-12

AS18594 MERCHANT-SOLUTIONS-18594 - Worldpay, LLC

Registry name: MERCHANT-SOLUTIONS-18594 - Worldpay, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18594, 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.57.149.0/24 No ROA Nonecovered by 64.57.144.0/21 672 100% 66
147.249.23.0/24 Valid None 673 100% 67
64.57.144.0/24 Valid RIR databaseARIN 672 100% 66
64.57.145.0/24 Valid RIR databaseARIN 672 100% 66
64.57.146.0/24 Valid RIR databaseARIN 672 100% 66
64.57.150.0/24 Valid RIR databaseARIN, RADB 672 100% 66
64.57.151.0/24 Valid RIR databaseARIN, RADB 672 100% 66
199.254.202.0/24 Valid RIR databaseARIN 672 100% 66
204.90.2.0/24 Valid RIR databaseARIN, RADB 672 100% 66
208.70.176.0/24 Valid RIR databaseARIN, RADB 672 100% 66
208.70.177.0/24 Valid RIR databaseARIN 672 100% 66
208.70.179.0/24 Valid RIR databaseARIN, RADB 672 100% 66
208.74.166.0/24 Valid RIR databaseARIN 672 100% 66
74.120.156.0/24 Valid RIR databaseARIN 671 100% 66
74.120.158.0/24 Valid RIR databaseARIN 671 100% 66

AS-SET

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

  • ROA: none1
  • Route object: none2
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none64.57.149.0/24No ROA covers it. Add a ROA for AS18594, maxLength 24.672 of 673
Route object: none64.57.149.0/24No route object for it. A route object for 64.57.144.0/21 with origin AS18594 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18594 in the RIR database for the space.672 of 673
Route object: none147.249.23.0/24No route object for it. Add a route object with origin AS18594 in the RIR database for the space.673 of 673

Route objects not announced

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

64.57.144.0/21RADBNo ROA
64.57.146.64/26ARINValid
64.57.146.128/26ARINValid
64.57.146.192/29ARINValid
192.225.30.0/24RADBNo ROA
204.90.0.0/22RADBNo ROA
204.90.4.0/24RADBNo 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.