#CPUID
Live, measured metrics for the hashtag #CPUID from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #cpuid
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · mas.to (Mastodon public tags API) · fetched 2026-09-10 19:48 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-09-10 19:48 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-09-10 19:48 UTCEverything below is measured over the latest 11 public posts (spanning ~21919 hours).
Posting hours (UTC)
Languages: English (4) · German (4) · Italian (1) · Polish (1) · Russian (1)
Avg boosts / post: 1.6
Top of the latest posts
We would appreciate a few more sponsors to assist with a speaker’s accommodations. Rest assured, their topic is AWESOME. #CPUID #bhyve @EuroBSDCon
Security in 2016: Make sure all your software is upto date Security in 2026: For the love of god, dont update anything https://www.bleepingcomputer.com/news/security/supply-chain-attack-at-cpuid-pushes-malware-with-cpu-z-hwmonitor/ #supplyc
#CPUID: Angreifer haben über Webseite #Malware-Installer verteilt | Security https://www.heise.de/news/CPUID-Durch-Schwachstelle-mehrere-Stunden-Malware-verteilt-11256219.html
What “cpuid” means
WikipediaIn the x86 architecture, the CPUID instruction is a processor supplementary instruction allowing software to discover details of the processor. It was introduced by Intel in 1993 with the launch of the Pentium and late 486 processors.
“CPUID” on Wikipedia (CC BY-SA) →#cpuid across platforms
every network with a public tag surfaceFollow #cpuid straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/cpuid