#Wireguard

Live, measured metrics for the hashtag #Wireguard 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 #wireguard

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.

$51.02/ year · 9-character #name
Claim #wireguard — $51.02/yr→
Annual, renews each year
Buy on hashtag.space (web3)
one-timepay once, yours for life
card via hashtag.org · tokens via hashtag.space
15
Uses / 7 days
Mastodon
14
Accounts / 7 days
Mastodon
40
Recent posts
Mastodon
~0.1/hr
Recent pace
Mastodon · last 40
1.1
Avg reactions / post
Mastodon · last 40

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 02:25 UTC
3
07-21
4
07-22
2
07-23
4
07-24
1
07-25
1
07-26
0
07-27

15 uses by 14 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 02:25 UTC
#WireGuardVPN
0 uses · 0 accounts / 7d
#wireguardnt
0 uses · 0 accounts / 7d
#WíreGuard
0 uses · 0 accounts / 7d
#wWireguard
0 uses · 0 accounts / 7d
#wireguardgui
0 uses · 0 accounts / 7d
#WireGuardIndicator
0 uses · 0 accounts / 7d
#WireGuardKit
0 uses · 0 accounts / 7d
#wireguardui
0 uses · 0 accounts / 7d
#wireguardvpnserver
0 uses · 0 accounts / 7d
#wireguard_vpn
0 uses · 0 accounts / 7d
#wireguardgo
0 uses · 0 accounts / 7d
#wireguardeasy
0 uses · 0 accounts / 7d

Live pulse

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

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

Posting hours (UTC) — busiest: 06:00

00:0012:0023:00

Languages: English (25) · German (6) · French (4) · Russian (3) · Spanish (1)

Avg boosts / post: 1.1

Top of the latest posts

  • are you tired of unnecessarily low bandwidth and high latency in your #wireguard network and know a more optimal route exists, but you are not able to configure it, because it is not static and could change at any time? i've built something

    kate@[email protected]♥ 19↻ 102026-07-19 07:13 UTCView post →

  • I've cleaned up my Raspberry Pi selfhosting setup a bit. I'm using two, each in an Argon ONE V5 case with a 1TB NVME drive, running Raspberry Pi OS. 'one' is serving Nextcloud All-in-one, Immich and Vaultwarden via a Caddy reverse-proxy. Al

    Michael Jack@[email protected]♥ 15↻ 22026-07-11 14:48 UTCView post →

  • @t3rcermillenium @JulianOliver @cygnathreadbare Just sharing, i'm now with #xeovo , a bit more "raw" because relying on the #wireguard app rather than its own GUI, but outstanding performance there as well. It's good to feel that we have vi

    Gauff@[email protected]♥ 7↻ 12026-07-15 07:37 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/wireguard