bgpreport

Network · data from 2026-11-12

AS46597 ECOMMERCE - Ecommerce Discovery, LLC

Registry name: ECOMMERCE - Ecommerce Discovery, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS46597, 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.
192.190.225.0/24 No ROA RIR databaseARIN 673 100% 67
206.108.48.0/24 Valid Nonecovered by 206.108.48.0/21 670 100% 68
206.108.49.0/24 Valid Nonecovered by 206.108.48.0/21 670 100% 68
206.108.50.0/24 Valid Nonecovered by 206.108.48.0/21 670 100% 68
206.108.51.0/24 Valid Nonecovered by 206.108.48.0/21 670 100% 68
206.108.52.0/24 Valid Nonecovered by 206.108.48.0/21 670 100% 68
206.108.54.0/24 Valid Nonecovered by 206.108.48.0/21 670 100% 68
206.108.55.0/24 Valid Nonecovered by 206.108.48.0/21 670 100% 68
206.108.48.0/21 Valid RIR databaseARIN 670 100% 68

AS-SET

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

  • ROA: none1
  • Route object: none7
ChangePrefix or setDetailFull-table peers
ROA: none192.190.225.0/24No ROA covers it. Add a ROA for AS46597, maxLength 24.673 of 673
Route object: none206.108.48.0/24No route object for it. A route object for 206.108.48.0/21 with origin AS46597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46597 in the RIR database for the space.670 of 673
Route object: none206.108.49.0/24No route object for it. A route object for 206.108.48.0/21 with origin AS46597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46597 in the RIR database for the space.670 of 673
Route object: none206.108.50.0/24No route object for it. A route object for 206.108.48.0/21 with origin AS46597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46597 in the RIR database for the space.670 of 673
Route object: none206.108.51.0/24No route object for it. A route object for 206.108.48.0/21 with origin AS46597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46597 in the RIR database for the space.670 of 673
Route object: none206.108.52.0/24No route object for it. A route object for 206.108.48.0/21 with origin AS46597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46597 in the RIR database for the space.670 of 673
Route object: none206.108.54.0/24No route object for it. A route object for 206.108.48.0/21 with origin AS46597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46597 in the RIR database for the space.670 of 673
Route object: none206.108.55.0/24No route object for it. A route object for 206.108.48.0/21 with origin AS46597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46597 in the RIR database for the space.670 of 673

Route objects not announced

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