#slackoutage
Live, measured metrics for the hashtag #slackoutage from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #slackoutage
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 · fosstodon.org (Mastodon public tags API) · fetched 2026-07-31 02:18 UTC0 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-31 02:18 UTCNo related tags with measured usage found for #slackoutage.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-31 02:18 UTCEverything below is measured over the latest 7 public posts (spanning ~15595 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 0
Top of the latest posts
On February 26, 2025, Slack experienced a major global outage caused by database shard failures, disrupting messaging, thread loading, and workflows for over 6,000 users. The issue lasted about 10 hours and significantly impacted businesses
Slack Down: Thousands Reported Issues With Messaging Platform https://tinyurl.com/slack-outage-2025 #Slack #SlackDown #SlackOutage #TechTweakster
Slack Down: Thousands Reported Issues With Messaging Platform https://tinyurl.com/slack-outage-2025 #Slack #SlackDown #SlackOutage #TechTweakster
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/slackoutage