#error500

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

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.

$110.68/ year · 8-character #name
Claim #error500$110.68/yrBuy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
28
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 28
0.1
Avg reactions / post
Mastodon · last 28

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-30 11:01 UTC
0
07-24
0
07-25
0
07-26
0
07-27
0
07-28
0
07-29
0
07-30

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-30 11:01 UTC

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-30 11:01 UTC

Everything below is measured over the latest 28 public posts (spanning ~55780 hours).

Posting hours (UTC) — busiest: 11:00

00:0012:0023:00

Languages: English (13) · Spanish (4) · German (3) · French (3) · Dutch (1) · Russian (1)

Avg boosts / post: 0.4

Top of the latest posts

  • @Jackiemauro it should be: "congratulations with the error 500. You have beaten the system. Come back a little later." #error500 @Teri_Kanefield

    🇪🇺 Paul Schoonhoven 🍋🍉@[email protected]102024-01-14 04:16 UTCView post →
  • Modern web apps are weird. It appears that #Mastodon as well as #Pleroma / #Akkoma sometimes prefer to throw #Error500 to avoid a slow request. Why would you ever want to sacrifice stability? I'd rather wait than see an error message.

    Felix Urbasik@[email protected]112023-01-11 18:34 UTCView post →
  • Oh... #codeberg down with error: `504 Gateway Time-out. The server didn't respond in time.` Update: It's now error 500 Internal server error. Forgejo version: 15.0.0-108-6d221141+gitea-1.22.0 https://status.codeberg.org/status/codeberg http

    Naty S@eclecticpassions012026-05-22 15:01 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/error500