#eserver
Live, measured metrics for the hashtag #eserver from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #eserver
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-13 09:31 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-13 09:31 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-09-13 09:31 UTCEverything below is measured over the latest 2 public posts (spanning ~11123 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0
Top of the latest posts
An #IBM #eServer #iSeries 810 (9406-810) followed me home nine days ago and has taken up residence in my basement. It has firmly planted its power cord; thankfully 110 VAC, and #Twinax tentacle and refuses to leave. It is taunting me with m
IBM xSeries eServer 346 #1 – First Look https://blog.krafting.net/ibm-xseries-eserver-346-1-first-look/ #eserver #floppy #hardware #homelab #ibm #server #xseries
What “eserver” means
WikipediaIBM eServer was a family of computer servers from IBM. Announced in 2000, it combined the various IBM server brands under one brand. The various sub-brands were at the same time rebranded from:IBM RS/6000 to IBM eServer pSeries, p for POWER IBM AS/400 to IBM eServer iSeries, i for Integrated IBM Netfinity to IBM eServer xSeries, x for eXtended architecture IBM System/390 was replaced by the 64-bit IBM eServer zSeries, z for Zero downtime.
“IBM eServer” on Wikipedia (CC BY-SA) →#eserver across platforms
every network with a public tag surfaceFollow #eserver 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/eserver