#err_http2_protocol_error
Live, measured metrics for the hashtag #err_http2_protocol_error from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #err_http2_protocol_error
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-07-27 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.social (Mastodon public search API) · fetched 2026-07-27 12:00 UTCNo related tags with measured usage found for #err_http2_protocol_error.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-27 12:00 UTCEverything below is measured over the latest 1 public posts.
Posting hours (UTC)
Languages: English (1)
Avg boosts / post: 0
Used together with
Top of the latest posts
Morning all. I am seeing #ERR_HTTP2_PROTOCOL_ERROR on my browsers connected to my #Tomcat9 server. Tomcat just got bumped by #debian unnattended-upgrade to version 9.0.43-2~deb11u7. I have reflexively disabled HTTP/2. The error has gone awa
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/err_http2_protocol_error