Channel
@InternetHealthDashboard
On this record: Growth · Engagement · Posts · Citations · Cite this entry
6subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002379361042 |
|---|---|
| Type | Channel |
| Username | @InternetHealthDashboard |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 5 times, most recently 12 September 2026 |
| On Telegram | t.me/InternetHealthDashboard |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 07:18 | 6 | no change |
| 13 Aug 2026, 04:01 | 6 | first reading |
20 posts held, back to 8 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.
✅ INCIDENT RESOLVED Service: Claude Incident: Degraded performance for multiple models Duration: 270 minutes Resolved At: 8/12/2026, 6:20:31 PM Final Impact: 🟡 Minor Total Active Incidents: 4 #incident #resolved #claude
Signed Push Bot
✅ INCIDENT RESOLVED Service: Cloudflare Incident: Email Security delivery impacted by Spamhaus listing Duration: 156 minutes Resolved At: 8/12/2026, 5:40:31 PM Final Impact: 🟠 Major Total Active Incidents: 5 #incident #resolved #cloudflare
Signed Push Bot
🔄 INCIDENT UPDATED Service: Cloudflare Incident: Email Security delivery impacted by Spamhaus listing Current Status: monitoring Current Impact: 🟠 Major Changes detected: • Status: investigating → monitoring Event URL: Status Page Affected Components: 🔴 Email Security (Area1) (major_outage) 🔴 Email Security (Zero Trust) (major_outage) Total Active Incidents: 1 #incident #updated #cloudflare
Signed Push Bot
🔄 INCIDENT UPDATED Service: Claude Incident: Degraded performance for multiple models Current Status: identified Current Impact: 🟡 Minor Changes detected: • Status: investigating → identified Event URL: Status Page Affected Components: ⚠️ claude.ai (degraded_performance) ⚠️ Claude API (api.anthropic.com) (degraded_performance) ⚠️ Claude Code (degraded_performance) ⚠️ Claude Cowork (degraded_performance) Total Ac…
Signed Push Bot
🚨 NEW INCIDENT DETECTED Service: Cloudflare Incident: Email Security delivery impacted by Spamhaus listing Status: investigating Impact: 🟠 Major Event URL: Status Page Started At: 8/12/2026, 3:04:14 PM Affected Components: 🔴 Email Security (Area1) (major_outage) 🔴 Email Security (Zero Trust) (major_outage) Total Active Incidents: 1 #incident #new #cloudflare
Signed Push Bot
🚨 NEW INCIDENT DETECTED Service: Claude Incident: Degraded performance for multiple models Status: investigating Impact: 🟡 Minor Event URL: Status Page Started At: 8/12/2026, 1:50:28 PM Affected Components: ⚠️ claude.ai (degraded_performance) ⚠️ Claude API (api.anthropic.com) (degraded_performance) ⚠️ Claude Code (degraded_performance) ⚠️ Claude Cowork (degraded_performance) Total Active Incidents: 3 #incident #…
Signed Push Bot
🚨 NEW INCIDENT DETECTED Service: Akamai Incident: Edge Delivery Issues in India Status: monitoring Impact: ✅ None Event URL: Status Page Started At: 8/12/2026, 1:02:24 PM Affected Components: ✅ Edge Delivery (operational) Total Active Incidents: 2 #incident #new #akamai
Signed Push Bot
🔄 INCIDENT UPDATED Service: Linode Incident: Upstream Issues - Ubuntu Current Status: identified Current Impact: ✅ None Changes detected: • Status: investigating → identified Event URL: Status Page Affected Components: None Total Active Incidents: 2 #incident #updated #linode
Signed Push Bot
✅ INCIDENT RESOLVED Service: Cloudflare Incident: Cloudflare Analytics Delays Duration: 139 minutes Resolved At: 8/11/2026, 4:40:30 PM Final Impact: 🟡 Minor Total Active Incidents: 3 #incident #resolved #cloudflare
Signed Push Bot
🔄 INCIDENT UPDATED Service: Cloudflare Incident: Cloudflare Analytics Delays Current Status: monitoring Current Impact: 🟡 Minor Changes detected: • Status: investigating → monitoring Event URL: Status Page Affected Components: ⚠️ Analytics (degraded_performance) Total Active Incidents: 1 #incident #updated #cloudflare
Signed Push Bot
🔄 INCIDENT UPDATED Service: Cloudflare Incident: Cloudflare Analytics Delays Current Status: investigating Current Impact: 🟡 Minor Changes detected: Event URL: Status Page Affected Components: ⚠️ Analytics (degraded_performance) Total Active Incidents: 1 #incident #updated #cloudflare
Signed Push Bot
🚨 NEW INCIDENT DETECTED Service: Cloudflare Incident: Cloudflare Analytics Delays Status: investigating Impact: 🟡 Minor Event URL: Status Page Started At: 8/11/2026, 2:22:00 PM Affected Components: ⚠️ Analytics (degraded_performance) Total Active Incidents: 1 #incident #new #cloudflare
Signed Push Bot
Showing the 12 most recent of 20 posts we hold for @InternetHealthDashboard. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Internet Health Dashboard” (@InternetHealthDashboard), 6 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/InternetHealthDashboard.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.