bgpreport

Network · data from 2026-11-12

AS21858 ASCENT-DATA-LLC - Ascent Data, LLC

Registry name: ASCENT-DATA-LLC - Ascent Data, LLC, US · not in PeeringDB

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

Announced routes

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

208.70.64.0/24 Valid Nonecovered by 208.70.64.0/23 673 100% 67
2607:ffa8::/32 Valid Other IRR onlyRADB 635 100% 68
208.70.64.0/21 Valid RIR databaseARIN 673 100% 67
208.70.64.0/23 Valid RIR databaseARIN 673 100% 67
208.70.66.0/24 Valid RIR databaseARIN 673 100% 67
208.70.68.0/24 Valid RIR databaseARIN 673 100% 67
208.70.71.0/24 Valid RIR databaseARIN 673 100% 67

AS-SET

AS21858 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 16 are in fix.csv.

  • Route object: none1
  • Route object: RIR1
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
Route object: none208.70.64.0/24No route object for it. A route object for 208.70.64.0/23 with origin AS21858 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21858 in the RIR database for the space.673 of 673
Route object: RIR2607:ffa8::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

63.166.28.0/22RADBNo ROA
199.2.135.0/24RADBNo ROA
204.250.80.0/21RADBNo ROA
205.149.8.0/21RADBNo ROA
205.243.72.0/23RADBNo ROA
206.228.139.0/24RADBNo ROA
206.228.140.0/22RADBNo ROA
207.14.160.0/23RADBNo ROA
208.14.180.0/24RADBNo ROA
208.70.67.0/24ARINValid
208.70.69.0/24ARINValid
208.70.70.0/24ARINValid
2606:1180::/32RADBNo ROA
2620:15:e000::/48RADBNo 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.