bgpreport

Network · data from 2026-11-12

AS1613 AS1613 - E SHELLS INC

Registry name: AS1613 - E SHELLS INC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS1613, 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.

168.100.232.0/22 No ROA Nonecovered by 168.100.224.0/19 673 100% 67
168.100.247.0/24 No ROA Nonecovered by 168.100.224.0/19 673 100% 67
168.100.238.0/23 No ROA RIR databaseARIN 673 100% 67
168.100.253.0/24 No ROA RIR databaseARIN 673 100% 67
2605:e740:200::/40 No ROA RIR databaseARIN 635 100% 67
2605:e740:ff05::/48 No ROA RIR databaseARIN 632 99% 69
2605:e740:700::/40 No ROA RIR databaseARIN 605 95% 67
168.100.248.0/24 Valid Nonecovered by 168.100.248.0/23 670 100% 68
168.100.249.0/24 Valid Nonecovered by 168.100.248.0/23 670 100% 68
168.100.224.0/23 Valid RIR databaseARIN 673 100% 67
168.100.244.0/24 Valid RIR databaseARIN 673 100% 67
168.100.250.0/24 Valid RIR databaseARIN 673 100% 67
185.176.52.0/22 Valid RIR databaseARIN 673 100% 67
168.100.254.0/24 Valid RIR databaseARIN 671 100% 68
168.100.255.0/24 Valid RIR databaseARIN 671 100% 68
168.100.240.0/23 Valid RIR databaseARIN 670 100% 68
168.100.245.0/24 Valid RIR databaseARIN 670 100% 68
168.100.252.0/24 Valid RIR databaseARIN 637 95% 68
2605:e740:400::/40 Valid RIR databaseARIN 635 100% 67
2605:e740:ff04::/48 Valid RIR databaseARIN 635 100% 67
2605:57c0::/32 Valid RIR databaseARIN 634 100% 69
2605:e740::/40 Valid RIR databaseARIN 634 100% 69
2605:e740:8000::/40 Valid RIR databaseARIN 634 100% 69
2605:e740:500::/40 Valid RIR databaseARIN 632 99% 69

AS-SET

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

  • ROA: none7
  • Route object: none4
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none168.100.232.0/22No ROA covers it. Add a ROA for AS1613, maxLength 22.673 of 673
Route object: none168.100.232.0/22No route object for it. A route object for 168.100.224.0/19 with origin AS1613 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1613 in the RIR database for the space.673 of 673
ROA: none168.100.247.0/24No ROA covers it. Add a ROA for AS1613, maxLength 24.673 of 673
Route object: none168.100.247.0/24No route object for it. A route object for 168.100.224.0/19 with origin AS1613 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1613 in the RIR database for the space.673 of 673
ROA: none168.100.238.0/23No ROA covers it. Add a ROA for AS1613, maxLength 23.673 of 673
ROA: none168.100.253.0/24No ROA covers it. Add a ROA for AS1613, maxLength 24.673 of 673
ROA: none2605:e740:200::/40No ROA covers it. Add a ROA for AS1613, maxLength 40.635 of 636
ROA: none2605:e740:ff05::/48No ROA covers it. Add a ROA for AS1613, maxLength 48.632 of 636
ROA: none2605:e740:700::/40No ROA covers it. Add a ROA for AS1613, maxLength 40.605 of 636
Route object: none168.100.248.0/24No route object for it. A route object for 168.100.248.0/23 with origin AS1613 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1613 in the RIR database for the space.670 of 673
Route object: none168.100.249.0/24No route object for it. A route object for 168.100.248.0/23 with origin AS1613 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1613 in the RIR database for the space.670 of 673

Route objects not announced

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

23.174.56.0/24ARINValid
168.100.224.0/19ARINNo ROA
168.100.228.0/23ARINValid
168.100.236.0/23ARINValid
168.100.248.0/23ARINValid
168.100.254.0/23ARINValid
2001:218:3002::/48APNICValid
2001:470:5b6::/48ARINValid
2605:e740::/32ARINNo ROA
2605:e740:100::/40ARINValid
2605:e740:300::/40ARINValid
2607:a140::/32ARINValid

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.