bgpreport

Network · data from 2026-11-12

AS16843 CELLTEX-NETWORKS - Celltex Networks, LLC

Registry name: CELLTEX-NETWORKS - Celltex Networks, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS16843, 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.
38.103.213.0/24 No ROA Other IRR onlyRADB 672 100% 67
104.218.76.0/22 Valid RIR databaseARIN 673 100% 67
141.193.216.0/23 Valid RIR databaseARIN 673 100% 67
141.193.255.0/24 Valid RIR databaseARIN 673 100% 67
147.160.54.0/24 Valid RIR databaseARIN 673 100% 67
147.160.140.0/23 Valid RIR databaseARIN 673 100% 67
147.185.178.0/24 Valid RIR databaseARIN 673 100% 67
148.59.156.0/22 Valid RIR databaseARIN 673 100% 67
148.59.236.0/22 Valid RIR databaseARIN 673 100% 67
199.74.228.0/24 Valid RIR databaseARIN 673 100% 67
206.166.198.0/24 Valid RIR databaseARIN 673 100% 67
208.52.138.0/23 Valid RIR databaseARIN 673 100% 67
2605:7d80::/32 Valid RIR databaseARIN 605 95% 67

AS-SET

AS16843 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 2 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none38.103.213.0/24No ROA covers it. Add a ROA for AS16843, maxLength 24.672 of 673
Route object: RIR38.103.213.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS16843 is announced.

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.