bgpreport

Network · data from 2026-11-12

AS11870 ALTICOR

Registry name: ALTICOR-INC - ALTICOR INC, US · PeeringDB

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

Announced routes

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

167.23.68.11/32 Invalid: maxLength Nonecovered by 167.23.68.0/23 1 0%low visibility 1
167.23.68.64/30 Invalid: maxLength Nonecovered by 167.23.68.0/23 1 0%low visibility 1
167.23.68.130/32 Invalid: maxLength Nonecovered by 167.23.68.0/23 1 0%low visibility 1
167.23.68.131/32 Invalid: maxLength Nonecovered by 167.23.68.0/23 1 0%low visibility 1
167.23.0.0/16 Valid RIR databaseARIN, RADB 672 100% 67
167.23.0.0/17 Valid RIR databaseARIN, RADB 672 100% 67
167.23.20.0/24 Valid RIR databaseARIN, RADB 672 100% 67
167.23.28.0/24 Valid RIR databaseARIN, RADB 672 100% 67
167.23.64.0/23 Valid RIR databaseARIN, RADB 672 100% 67
167.23.66.0/23 Valid RIR databaseARIN, RADB 672 100% 67
167.23.71.0/24 Valid RIR databaseARIN, RADB 672 100% 66
167.23.74.0/23 Valid RIR databaseARIN, RADB, RIPE-NONAUTH 672 100% 66
167.23.76.0/23 Valid RIR databaseARIN, RADB, RIPE-NONAUTH 672 100% 66
167.23.96.0/23 Valid RIR databaseARIN, RADB, RIPE-NONAUTH 672 100% 66
167.23.100.0/24 Valid RIR databaseARIN, RADB 672 100% 66
167.23.124.0/24 Valid RIR databaseARIN, RADB 672 100% 66
167.23.148.0/24 Valid RIR databaseARIN, RADB 672 100% 67
167.23.248.0/24 Valid RIR databaseARIN, RADB 672 100% 67
167.23.80.0/22 Valid RIR databaseARIN, RADB 671 100% 67
167.23.102.0/23 Valid RIR databaseARIN, RADB 671 100% 67
103.44.16.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
103.44.17.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
167.23.68.0/23 Valid RIR databaseARIN, RADB 670 100% 67
167.23.72.0/23 Valid RIR databaseARIN, NTTCOM, RADB 670 100% 67
167.23.88.0/23 Valid RIR databaseARIN, RADB 670 100% 67
167.23.88.0/24 Valid RIR databaseARIN, RADB 670 100% 67
167.23.89.0/24 Valid RIR databaseARIN, RADB 670 100% 67
167.23.90.0/23 Valid RIR databaseARIN, RADB 670 100% 67
167.23.96.0/24 Valid RIR databaseARIN, RADB 670 100% 66
167.23.128.0/17 Valid RIR databaseARIN, RADB 669 99% 67

AS-SET

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

  • ROA: maxLength4
  • Route object: none4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength167.23.68.11/32ROA 167.23.0.0/16 AS11870 has maxLength 16; ROA 167.23.0.0/17 AS11870 has maxLength 17; ROA 167.23.68.0/23 AS11870 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 167.23.68.11/32.1 of 673
Route object: none167.23.68.11/32No route object for it. A route object for 167.23.68.0/23 with origin AS11870 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS11870 in the RIR database for the space.1 of 673
ROA: maxLength167.23.68.64/30ROA 167.23.0.0/16 AS11870 has maxLength 16; ROA 167.23.0.0/17 AS11870 has maxLength 17; ROA 167.23.68.0/23 AS11870 has maxLength 23; the route is a /30. Raise the maxLength, or add a ROA for 167.23.68.64/30.1 of 673
Route object: none167.23.68.64/30No route object for it. A route object for 167.23.68.0/23 with origin AS11870 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS11870 in the RIR database for the space.1 of 673
ROA: maxLength167.23.68.130/32ROA 167.23.0.0/16 AS11870 has maxLength 16; ROA 167.23.0.0/17 AS11870 has maxLength 17; ROA 167.23.68.0/23 AS11870 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 167.23.68.130/32.1 of 673
Route object: none167.23.68.130/32No route object for it. A route object for 167.23.68.0/23 with origin AS11870 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS11870 in the RIR database for the space.1 of 673
ROA: maxLength167.23.68.131/32ROA 167.23.0.0/16 AS11870 has maxLength 16; ROA 167.23.0.0/17 AS11870 has maxLength 17; ROA 167.23.68.0/23 AS11870 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 167.23.68.131/32.1 of 673
Route object: none167.23.68.131/32No route object for it. A route object for 167.23.68.0/23 with origin AS11870 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS11870 in the RIR database for the space.1 of 673

Route objects not announced

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

167.23.34.0/24ARIN, RADBValid
2620:150::/36RADBNo 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.