Companies Using Amazon ELB

We detect Amazon ELB on 16,312 domains, 6,720 of which match to a company record. The population has two distinct halves: large organisations running long-lived internal applications — Hewlett Packard Enterprise, CBRE, Jacobs, Toyota, ICICI Prudential — and a 3,837-domain fleet of US youth-sports league sites belonging to a single hosting platform.

Our August 2026 rollup reads 16,312 domains. Roughly 22.5% of the domains we currently see are tenant sites of one platform rather than independent adopters, so the count of distinct organisations choosing Amazon ELB is materially lower than the domain count.

5.33% of Load Balancers & Proxies, fifth of twelve. Its share is not shrinking in our three rollups, but that is a coverage artefact rather than stability — the 927-to-131 outflow to Amazon ALB is the number that describes the direction of this product.

For anyone already on AWS the answer our data supports is Amazon ALB, which is where 927 domains went. Outside AWS, the equivalents are Azure Front Door and Google Cloud Load Balancing on the other large clouds, or Envoy if you would rather run the balancer yourself.

The United States, on 4,114 of the 6,453 companies where we hold a country — 63.75%. That is more US-concentrated than Amazon ALB at 52.59%, largely because the youth-sports platform fleet is almost entirely American.

57.24% of the 6,209 sized companies have 1-10 employees, but that figure is inflated by the platform fleet of small volunteer-run sports organisations. The independent deployments cluster at the other end of the range, among enterprises running careers and authentication portals.

The 2010s lead at 34.58% of the 2,672 companies with a founding year, followed by the 2000s at 16.62%. An 11.56% pre-1960 block covers the universities, insurers and manufacturers near the top of the company list.

A US organisation running an established internal web application — a careers site, partner portal, authentication endpoint or learning-management system — on infrastructure that predates the current generation of AWS balancers and has not yet been migrated.

It means the hostname either returned an AWSELB cookie or answered with a Server header containing awselb. Unlike Amazon ALB, which we can only see when target-group stickiness is enabled, the header clause fires regardless of configuration — so Amazon ELB has the wider detection surface of the two.

No. Amazon ELB here is the original Classic load balancer, operating at the connection level; Amazon ALB is the newer layer-7 balancer that routes on HTTP content. We identify them through different signals and count them separately, and only 4.08% of Amazon ELB domains also show an ALB.

Yes. 927 domains dropped Amazon ELB and now answer from an Amazon ALB, 917 within 90 days, against 131 in the reverse direction. Only 1.6% of the leavers still run a Classic balancer on any hostname, which makes this a replacement rather than a gradual coexistence.

Because it is not really an industry in this data. Those 587 companies are US youth-sports leagues hosted on a single platform: 94.4% of them run DNN and Microsoft ASP.NET, and the same 94.4% run OneTrust, Segment and Pendo. Identical rates across unrelated software mean one platform installed all of it, and the wider fleet reaches 3,837 domains once you count sites without an industry label.

Around a third do. Cloudflare appears on 31.32% of Amazon ELB domains and Amazon CloudFront on 21.26%. As with any load balancer, the CDN caches and shields at the edge while the balancer distributes traffic to targets behind it.

We do not track vendor roadmaps, so we will not characterise AWS's plans. What our crawl can say is that the movement between the two products is one-directional and heavily so — 927 domains out against 131 in over the period we have observed — and that the domains still on it are dominated by long-lived internal applications and one large hosting platform.