Summary
- ARIN's record of AS17104 splits into three views that answer three different questions: the autonomous-system object attributes no address block at all, the organization object lists exactly one /24, and the structured field on that network named for the origin autonomous system prints an empty array.
- The claim that the space is routed through AS17104 exists only as registrant-authored prose, while two independent observation sets covering 6 to 20 November 2026 show nothing announced for either the ASN or the prefix, each bounded by its own visibility threshold.
Start in the wrong place and the registry tells you nothing. ARIN's RDAP object for AS17104 registers a single-ASN range — handle AS17104, start and end both 17104, name FEDCOMM-USA, status active — held by organization handle FCOCL, printed as Federal Communications on Command, LLC, at 374 Crossfield Dr, Versailles, KY 40383. It contains no network member. Open that object alone and ask whether the holder has address space: the answer you leave with is none.
The second view corrects it. ARIN's network-resource listing for organization handle FCOCL enumerates exactly one network: RLC-NETWORKS-01, handle NET-52-144-30-0-1, 52.144.30.0 through 52.144.30.255. The organization object types that network DIRECT ALLOCATION, status active, parent handle NET-52-0-0-0-0. Two hundred and fifty-six addresses — my count from the printed endpoints, not a registry figure.
The dates do not sit on one clock. The ASN's registration event and its last-changed event both print 2023-05-15, corroborated in ARIN's Whois-RWS view for the autonomous system. The FCOCL organization was registered 2023-04-24 and last changed 2023-05-08. The network object prints its registration event and its last-changed event as the same instant, 2026-10-02T15:04:08-04:00 — an identity the page does not explain, and I will not invent a cause for it. By my own count that is 1,236 days from the ASN's registration to the network's printed event, and 50 days from that event to 21 November 2026, the date on every statement in this piece.
Now the part that makes this a case file. The network object itself carries a structured field named arin_originas0_originautnums. In the object retrieved, that array is empty. The registry's own machine-readable slot for the origin autonomous system of 52.144.30.0/24 prints no number at all.
The routing claim lives in the one layer no registry validates. The network's Registration Comments are registrant-authored, and they state that the address space supports business customer services, infrastructure deployment and “BGP routing via AS17104”, adding separately that “RLC-Networks is the operating DBA of Federal Communications on Command, LLC.” I hold that wording as a provider-reported excerpt of the RDAP JSON rather than as raw bytes, and the excerpt and its publisher's summary disagree about one verb, so only those two fragments appear here in quotation marks and the rest is paraphrased.
Two observation sets were asked the same question over the same fortnight. RIPEstat's announced-prefixes response for AS17104 returned status ok with an empty prefixes array for the window 2026-11-06T16:00:00Z to 2026-11-20T16:00:00Z. Its prefix-overview for the block returned announced false, an empty asns array and actual_num_related 0 against a query time of 2026-11-20T16:00:00. Its routing-status for the same prefix returned an empty origins array and 0 of 321 RIS IPv4 peers seeing it, with no less- or more-specifics; the 321 is every RIS IPv4 peer inside that response, not a sample I chose. RIPEstat states in the same responses that routes seen by fewer than 10 RIS full-feed peers are excluded, so what those zeros establish is that nothing was observable above that threshold over that window — not that nothing was ever sent.
Hurricane Electric, working from its own vantage, reports the same silence for the ASN: 0 prefixes originated, 0 prefixes announced, 0 RPKI-valid originations, 0 BGP peers observed, 0 IPs originated, with the data updated 20 Nov 2026 14:04 PST. Its page for the block states that 52.144.30.0/24 is not visible in the global routing table and reports no IRR records, while listing a delegation whose registry is arin, status allocated, country US. Those figures carry their own stamp and can lag or miss low-visibility routes; read them as a dated observation, never as a permanent condition.
The historical layer is where the prefix acquires a past. The routing-status response records a first observation of exactly 52.144.30.0/24 on 2018-03-10T08:00:00 with origin 32832, and a last on 2025-02-25T16:00:00 with origin 32832. No field in any source read for this piece prints AS17104 as an origin for that prefix at any time. The identity of AS32832 is not stated by any document I read, and a RIS observation is not allocation history: I draw no conclusion about who held the space before, and the ARIN pages read print no previous holder, no statement of transfer and no first-allocation date.
Then the operator, on its own terms. The site the ASN's comment names presents RLC-NETWORKS as a telecommunications company founded in Versailles, Kentucky in March 2022, advertising internet, cable television, VoIP/TDM telephony, networking and security services plus fibre construction and installation work, with contact address 374 Crossfield Drive, Versailles, Kentucky 40383 — the same street address as the registry record. On the page read it does not mention AS17104, BGP, IP addresses or Federal Communications on Command, LLC. That page is self-published marketing, not a corporate registration, and its silence about the ASN is a property of the page rather than a finding about the company. The holder has its own directory record at BTW if you want the entity as we file it.
The delta against our own shelf is simple. BTW has not written about this holder before; a prior-coverage search for AS17104 returned nothing at all. The adjacent comparison is my briefing on ARIN's NRPM section 12 review, which read ARIN as a policy instrument. This piece reads ARIN's registration data as an evidentiary object and asks which of its views answers which question.
The finding is the direction the evidence travels. A registry field exists for the origin autonomous system of a /24, and it is printed empty. The statement that the block is routed through AS17104 also exists, but only as free text the registrant wrote and the registry does not verify. Both of those facts are checkable on 21 November 2026 by anyone with a browser and five minutes. What is not checkable from outside is what the holder does with 256 addresses in private: the observation sets reproduce an absence at a visibility threshold, and absence at a threshold is not absence in fact.
So the accountability question is not whether this holder has done anything wrong. Nothing in the documents read supports an allegation of misuse, hijack or abuse, and I make none. The question is why a record that already contains a box for the answer leaves the box empty while publishing the answer as prose, and what an outsider is meant to do with the difference. Populating the origin field, with a route object to match, would cost nothing and would move this block from a visibility question to a data-quality question.
Until then the honest reading of the public record is the one printed above: one /24, active, allocated, its origin field blank and its routing intention in the comments.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






