bgpreport

Network · data from 2026-11-12

AS19462 USSCO-AS19462 - Essendant Co.

Registry name: USSCO-AS19462 - Essendant Co., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS19462, 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.
162.253.88.0/23 No ROA RIR databaseARIN, RADB 671 100% 67
162.253.90.0/23 No ROA RIR databaseARIN, RADB 671 100% 67
74.115.188.0/24 No ROA RIR databaseARIN, RADB 670 100% 67
74.115.189.0/24 No ROA RIR databaseARIN, RADB 670 100% 67

AS-SET

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

  • ROA: none4
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none162.253.88.0/23No ROA covers it. Add a ROA for AS19462, maxLength 23.671 of 673
ROA: none162.253.90.0/23No ROA covers it. Add a ROA for AS19462, maxLength 23.671 of 673
ROA: none74.115.188.0/24No ROA covers it. Add a ROA for AS19462, maxLength 24.670 of 673
ROA: none74.115.189.0/24No ROA covers it. Add a ROA for AS19462, maxLength 24.670 of 673

Route objects not announced

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

38.106.88.0/24RADBNo ROA
63.85.20.0/24RADBNo ROA
72.5.204.0/24RADBNo ROA
74.115.190.0/24ARIN, RADBNo ROA
74.115.191.0/24ARIN, RADBNo ROA
162.253.92.0/23ARINNo ROA
162.253.94.0/23ARINNo ROA
198.140.160.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.