akstat.io: 92 sites, and what they have in common
akstat.io is a hostname that shows up in the network log of large enterprise websites. This index has no vendor entry for it: no company name, no category, no tracking classification. It was found on 92 of the 5,294 sites measured. What can be established from the outside is the company it keeps and the kind of page it sits on, and on both counts it is unlike almost everything else in this index. By median first contact its pages rank 2 of the 88 companies here, where rank 1 is the longest wait.
Nearly a second before the first third-party request
Median first contact on a site carrying akstat.io was 998 ms. Among the 88 companies in this index that is rank 2, where rank 1 is the longest wait: exactly one entry sits on pages that take longer to reach out. The earliest single first contact recorded across the 92 sites was 183 ms.
That is a very different page from the ad-funded norm, where the first connection typically opens inside half a second. These sites render something first.
Its neighbours are infrastructure, not exchanges
go-mpulse.net was present on 64 of the 92 sites, 69.6 percent — the most frequent companion by a distance. Then Google on 48 sites, 52.2 percent; Akamai on 42, 45.7 percent; OneTrust on 37, 40.2 percent; adobedtm.com on 31, 33.7 percent; demdex.net on 21, 22.8 percent; tiqcdn.com on 15, 16.3 percent. Meta and LinkedIn appear on 8 and 7 sites respectively, under 9 percent each.
What is missing is as informative as what is there. Most entities in this index with 90-plus sites have a co-presence list full of advertising exchanges and identity hosts. This one has content delivery, performance monitoring, tag management and a consent platform. The crawl does not establish who operates akstat.io or what relationship it has to any name on that list — only that they appear on the same pages, at those rates.
The sites are enterprise technology vendors
The examples are unusually homogeneous: azure.com, samsung.com, intuit.com, webex.com, cisco.com, meraki.com, dell.com, mysql.com, paloaltonetworks.com, mcafee.com and viber.com, with dailymail.co.uk the one publisher in the set.
These are documentation portals, product pages and support sites — the kind of property where page weight is a support cost and where a performance team usually exists. mcafee.com is the heaviest example at 33 companies contacted, of which 7 arrived before the window closed, first contact 991 ms. dell.com: 15 companies, 4 early, at 1352 ms. samsung.com reached 5 companies with 1 early, first contact 1875 ms. paloaltonetworks.com: 9 companies, 4 early, at 1614 ms.
Where the early-contact number lands
79 of the 92 sites had at least one company contacted before a consent choice could have been recorded — 85.9 percent, rank 81 of the 88 companies here. That is near the bottom of the field, and 13 sites had no early contact at all.
The median count of companies arriving inside that window is 4, rank 80 of 88, level with seven others. The median count arriving after it closes is 3, which is high for this index: on the typical akstat.io page, a real part of the stack is still arriving later in the load. intuit.com is the counterexample that keeps this honest — 9 companies, all 9 of them inside the window, first contact 795 ms, behind a OneTrust banner.
akstat.io was present on those 79 sites where early contact happened. The crawl counts that per site and does not record which companies arrived, so nothing here places akstat.io among them.
OneTrust runs the banners
54 of the 92 sites carried a consent tool the crawl could detect. OneTrust was seen alongside on 42 of them, an IAB TCF consent tool on 10, Usercentrics on 1 and Cookiebot on 1. Counts per tool are recorded per site and a site may run more than one, so these are not shares of the 54.
A 42-to-10 split toward OneTrust is what an enterprise population looks like. cisco.com, webex.com, dell.com, viber.com and paloaltonetworks.com all sit behind OneTrust banners in this set; dailymail.co.uk is the one carrying an IAB TCF tool, which is the framework its business needs.
| Site | Companies | Before consent | First contact |
|---|---|---|---|
| azure.com | 9 | 5 | 1275 ms |
| samsung.com | 5 | 1 | 1875 ms |
| intuit.com | 9 | 9 | 795 ms |
| webex.com | 12 | 6 | 1185 ms |
| cisco.com | 10 | 7 | 744 ms |
| meraki.com | 3 | 3 | 887 ms |
| dell.com | 15 | 4 | 1352 ms |
| mysql.com | 11 | 8 | 1226 ms |
| paloaltonetworks.com | 9 | 4 | 1614 ms |
| mcafee.com | 33 | 7 | 991 ms |
| dailymail.co.uk | 12 | 4 | 1661 ms |
| viber.com | 4 | 4 | 887 ms |
| Tool | Sites |
|---|---|
| OneTrust | 42 |
| IAB TCF consent tool | 10 |
| Usercentrics | 1 |
| Cookiebot | 1 |
Seen on the same pages
Companies most often contacted by the same sites. Co-presence only — the crawl records what arrived, not who called whom.
- go-mpulse.netTogether on 64 of these sites
- GoogleTogether on 48 of these sites
- AkamaiTogether on 42 of these sites
- OneTrustTogether on 37 of these sites
- adobedtm.comTogether on 31 of these sites
- demdex.netTogether on 21 of these sites
- tiqcdn.comTogether on 15 of these sites
- MetaTogether on 8 of these sites
Questions
What is akstat.io?
A hostname with no entry in this index's vendor catalogue — no company, no category, no tracking classification. The measured facts are that it appeared on 92 of 5,294 sites, that go-mpulse.net was on 69.6 percent of them and Akamai on 45.7 percent, and that its pages start later than almost any others here.
Is akstat.io a tracker?
This index does not classify it either way, and a single cold page load cannot settle it. What the load shows is routing and timing: a connection to that host, on those pages, at those moments.
Why does first contact take so long on these sites?
998 ms at the median, rank 2 of the 88 companies indexed. The set is dominated by enterprise vendor sites — documentation, support and product pages — which tend to render first-party content before third parties load.
How many of these sites had a cookie banner?
54 of the 92. OneTrust was the tool seen alongside most often, on 42 sites.