Autonomous system detail

AS604

Not announced

Last known operator One Lambda, Incorporated (Thermo Fisher Scientific brand, ONELAMBDA-INC). RIPEstat has no current registration record for this AS number.

Summary

// analyst note
Dormant, effectively deregistered legacy ASN. All routing sources (RIPEstat, CAIDA, bgp.he.net) agree on zero announcements, zero peers, zero customer cone. ARIN's live registry carries no autnum record for AS604, so allocated_date is a genuine registry gap rather than an unverified guess — a third-party aggregator's mirrored date (2009-07-21, IPinfo.io) could not be confirmed first-party this cycle.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-16/17; not in RIPEstat abuse contacts, Spamhaus ASN-DROP (inconclusive), NANOG archives, or BGP hijack reports.
IPv4 prefixes
0
~0 addresses
IPv6 prefixes
0
Peer networks
0
0 up · 0 down
IANA block
1-1876
Assigned by ARIN
[ 01 ] — Context

About this ASN.

Updated  ·  Confidence: Medium

AS604 is a legacy 16-bit ASN whose WHOIS trail points to One Lambda, Incorporated, a transplant-immunogenetics diagnostics company (HLA typing) that Thermo Fisher Scientific acquired in mid-2012. This was never a transit, access, or content network — no PeeringDB object exists for it, and nothing in the routing data suggests it served as anything beyond a small end-user enterprise ASN, if it was ever announced at all. The defining fact about AS604 today is that it has effectively vanished from the live registry: ARIN's own RDAP and Whois-RWS both return "not found" for it, and RIPEstat's whois passthrough — while confirming ARIN as the resource's delegated RIR — likewise turns up zero records. Every routing source checked (RIPEstat routing-status, RIPEstat announced-prefixes, bgp.he.net) agrees the ASN currently announces zero IPv4 and zero IPv6 prefixes, has zero observed BGP neighbours, and is invisible to all 325/321 RIS route collectors queried. CAIDA has no AS-rank entry for it at all. No abuse signal, hijack history, or NANOG discussion was found anywhere. A third-party aggregator (IPinfo.io) carries a stale mirrored value of an ARIN allocation date, but that value could not be reproduced against any live first-party ARIN source this cycle, since the underlying ARIN record itself is gone.

Operator
One Lambda, Incorporated (org handle ONELAMBDA-INC), a Thermo Fisher Scientific Inc. brand since its 2012 acquisition of One Lambda [Confirmed — two independent angles] — https://ipinfo.io/AS604, https://www.thermofisher.com/us/en/home/brands/onelambda.html
Country / RIR
United States, ARIN (per RIPEstat as-overview block "1-1876, Assigned by ARIN") [Confirmed] — https://stat.ripe.net/data/as-overview/data.json?resource=604
Allocated date
Unknown — ARIN's own live RDAP (rdap.arin.net/registry/autnum/604) returns HTTP 404 and ARIN Whois-RWS returns "no record found," so no autnum object with a top-level events[] array exists to read a registration date from; the record has been withdrawn/deregistered from ARIN's current registry. A third-party aggregator (IPinfo.io) shows a mirrored value of 2009-07-21, but this could not be confirmed against any live first-party RIR source this cycle — recorded here only as an unverified third-party claim, not written into the JSON
[Unknown] — https://rdap.arin.net/registry/autnum/604, https://whois.arin.net/rest/asn/AS604, https://ipinfo.io/AS604
Org status
Deregistered / not present in ARIN's current authoritative registry as of 2026-07-16/17 — ARIN RDAP and Whois-RWS both return no record; RIPEstat confirms ARIN as the delegated RIR for resource 604 but also returns zero WHOIS records
[Confirmed] — https://rdap.arin.net/registry/autnum/604, https://whois.arin.net/rest/asn/AS604
Website
Formerly onelambda.com (2015 Wayback snapshot); the brand now lives at thermofisher.com/us/en/home/brands/onelambda.html — neither is a network-operator site [Likely — live fetch of both pages failed at the tool layer; existence corroborated via Wayback's "available" API and search indexing] — https://web.archive.org/web/20150217031611/http://www.onelambda.com:80/, https://www.thermofisher.com/us/en/home/brands/onelambda.html

Abuse/security context

No notable public abuse signal found — RIPEstat abuse-contact-finder returns an empty contact list, no Spamhaus ASN-DROP hit (fetch inconclusive), no BGP hijack/leak history, and no NANOG mailing-list discussion located, consistent with an ASN that has no live announced address space

[Likely — two independent angles] — https://stat.ripe.net/data/abuse-contact-finder/data.json?resource=604, https://bgp.he.net/AS604

Network & routing

Network type
Not an Internet network operator/ISP — a non-transit, end-user (enterprise) ASN associated with a diagnostics company, not a backbone/access/content/IX network [Likely] — https://ipinfo.io/AS604, https://www.thermofisher.com/us/en/home/brands/onelambda.html
Routing status
Dormant/inactive — 0 announced IPv4 and 0 announced IPv6 prefixes, 0 observed BGP neighbours, seen by 0 of 325 (v4) and 0 of 321 (v6) RIPE RIS peers; corroborated by bgp.he.net showing 0 announced/originated prefixes and 0 peers
[Confirmed — two independent angles] — https://stat.ripe.net/data/routing-status/data.json?resource=604, https://bgp.he.net/AS604
CAIDA AS rank / customer cone
Unranked — CAIDA ASRank has no record for AS604 (asn: null), so no rank or customer-cone size can be reported [Confirmed] — CAIDA ASRank API (asn=null response)
Peering
No PeeringDB network object exists for AS604 (both the web page and the API return not-found); no operator-published peering policy located [Confirmed] — https://www.peeringdb.com/api/net?asn=604, https://www.peeringdb.com/asn/604
RPKI
Not evaluable — AS604 has no announced prefixes, so there is nothing to validate against ROAs [Unknown] — RIPEstat rpki-validation (skipped, requires a prefix parameter)
ASN
AS604 [Confirmed] — https://stat.ripe.net/data/as-overview/data.json?resource=604
Analyst note
Encountered as a dormant, effectively deregistered legacy ASN. WHOIS mirrors attribute it to One Lambda (now a Thermo Fisher brand), but ARIN's own live registry no longer carries a record for it — a genuine registry-withdrawal case, distinct from an unverified allocation date.
[ 02 ] — Announced prefixes

What this network routes.

0 prefixes total · RIPEstat data · cached, not real-time
// IPv4 prefixes0
No IPv4 prefixes announced.
// IPv6 prefixes0
No IPv6 prefixes announced.
[ 03 ] — Notable peers & upstreams

Who it talks to.

0 observed neighbours
Neighbour data unavailable from public BGP collectors.