#leapseconds
Live, measured metrics for the hashtag #leapseconds from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #leapseconds
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 · mastodon.social (Mastodon public tags API) · fetched 2026-10-02 12:00 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-10-02 12:00 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-02 12:00 UTCEverything below is measured over the latest 16 public posts (spanning ~31046 hours).
Posting hours (UTC) — busiest: 17:00
Languages: English (16)
Avg boosts / post: 0.3
Top of the latest posts
The leap second’s time is up: world votes to stop pausing clocks "The practice of adding #LeapSeconds to official #clocks to keep them in sync with #Earth’s rotation will be put on hold from 2035, the world’s foremost #metrology body has de
You might have heard, that CGPM will vote on whether to (de facto) abolish leapseconds in October, due to the technical problems it causes, each time we have a leapsecond. And because of the prospect of the first ever negative leapsecond. h
Just read that the International Earth Rotation and Reference Systems Service (IERS) is officially abandoning/abolishing #LeapSeconds by the year 2035, because they are just so disruptive to computer systems. Tell me you can't get a handle
#leapseconds across platforms
every network with a public tag surfaceFollow #leapseconds 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/leapseconds