bgpreport

Network · data from 2026-11-12

AS13821 ACML - AllianceBernstein L.P.

Registry name: ACML - AllianceBernstein L.P., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13821, 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.
83.126.58.224/28 Invalid: origin None 2 0%low visibility 2
206.218.229.0/24 No ROA None 673 100% 67
103.216.134.0/24 No ROA Other origin only 671 100% 67
165.101.85.0/24 Valid None 671 100% 67
206.218.214.0/24 Valid RIR databaseARIN, RADB 673 100% 67
206.218.232.0/24 Valid RIR databaseARIN 673 100% 67
206.218.234.0/24 Valid RIR databaseARIN, RADB 673 100% 66
206.218.235.0/24 Valid RIR databaseARIN 673 100% 67
206.218.248.0/24 Valid RIR databaseARIN 673 100% 67
206.218.249.0/24 Valid RIR databaseARIN 673 100% 67
206.218.213.0/24 Valid RIR databaseARIN, RADB 672 100% 67
206.218.215.0/24 Valid RIR databaseARIN, RADB 672 100% 67
206.218.223.0/24 Valid RIR databaseARIN, RADB 672 100% 67
206.218.206.0/24 Valid RIR databaseALTDB, ARIN 671 100% 67
206.218.207.0/24 Valid RIR databaseALTDB, ARIN 671 100% 67
206.218.209.0/24 Valid RIR databaseALTDB, ARIN 671 100% 67
206.218.240.0/24 Valid RIR databaseARIN 670 100% 67
206.218.246.0/23 Valid RIR databaseALTDB, ARIN 670 100% 67

AS-SET

AS13821 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: origin1
  • ROA: none2
  • Route object: none4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin83.126.58.224/28ROAs covering it name AS13237, not AS13821. If AS13821 should announce it, add a ROA for AS13821.2 of 673
Route object: none83.126.58.224/28No route object for it. Add a route object with origin AS13821 in the RIR database for the space.2 of 673
ROA: none206.218.229.0/24No ROA covers it. Add a ROA for AS13821, maxLength 24.673 of 673
Route object: none206.218.229.0/24No route object for it. Add a route object with origin AS13821 in the RIR database for the space.673 of 673
ROA: none103.216.134.0/24No ROA covers it. Add a ROA for AS13821, maxLength 24.671 of 673
Route object: none103.216.134.0/24Route objects for it name AS9269, AS10103, AS135413. Add a route object with origin AS13821 in the RIR database for the space.671 of 673
Route object: none165.101.85.0/24No route object for it. Add a route object with origin AS13821 in the RIR database for the space.671 of 673

Route objects not announced

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

216.52.91.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.