#jepsen

Live, measured metrics for the hashtag #jepsen from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #jepsen

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.

$520.70/ year · 6-character #name
Claim #jepsen$520.70/yr
Annual, renews each year
Buy on hashtag.space (web3)
one-timepay once, yours for life
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
40
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 40
0.3
Avg reactions / post
Mastodon · last 40

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 05:44 UTC
0
07-21
0
07-22
0
07-23
0
07-24
0
07-25
0
07-26
0
07-27

0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.

Related hashtags

measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-27 05:44 UTC

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 05:44 UTC

Everything below is measured over the latest 40 public posts (spanning ~37037 hours).

Posting hours (UTC) — busiest: 14:00

00:0012:0023:00

Languages: English (32) · Chinese (Taiwan) (2) · Chinese (2) · Russian (1) · Spanish (1) · German (1)

Avg boosts / post: 2.9

Top of the latest posts

  • I've been itching for years to try #jepsen but I thought it's too advanced for normal people but this article is totally motivating https://www.binwang.me/2024-12-02-PostgreSQL-High-Availability-Solutions-Part-1.html (jepsen unleashed on #p

    Su-Shee@sushee412024-12-08 10:30 UTCView post →
  • A new #Jepsen report! We worked with Buf to analyze the safety of Bufstream, a Kafka-compatible streaming system. We found three safety and two liveness issues in Bufstream 0.1.0, including the loss of acknowledged writes in healthy cluster

    Jepsen@[email protected]282024-11-12 14:15 UTCView post →
  • A new #Jepsen report: we demonstrate data loss and persistent split-brain in the NATS streaming system, in response to simulated power failures/OS crashes. https://jepsen.io/analyses/nats-2.12.1

    Jepsen@[email protected]172025-12-08 18:47 UTCView post →

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/jepsen