Telegram RegisterThe public register of Telegram

Channel

IncogNET

@incognet_io

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

106subscribers

+2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002209733427
TypeChannel
Username@incognet_io
DescriptionWebsite: https://incognet.io This is NOT a support or pre-sales channel. For support or sales requests, we will only respond from our helpdesk. This channel is for cross posting of announcements from our Twitter feed and Network / Service announcements.
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live14 August 2026
Measurements held3
On Telegramt.me/incognet_io

Growth

1041061057 Aug 2026, 21:25 — 104 subscribers8 Aug 2026, 02:30 — 106 subscribers9 Aug 2026, 08:46 — 106 subscribers7 Aug 2026, 21:259 Aug 2026, 08:46
3 measurements spanning 1 day, net +2. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 104–106 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 08:46106no change
8 Aug 2026, 02:30106+2
7 Aug 2026, 21:25104first reading

Engagement

20 posts held, back to 22 September 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
64.2%
avg views ÷ 106 subscribers
Avg views / post
68.0
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 19 July 2026
Posts held20 (22 September 202519 July 2026)
Views total68
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 08:46 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Links
119

Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

24 reactions across 10 posts, in 9 distinct kinds. The most used accounts for 29.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
729.2%
👍625.0%
👀28.33%
👏28.33%
💯28.33%
🙏28.33%
14.17%
🤝14.17%
🤡14.17%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 11 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 24reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 22 September 2025 to 19 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

19 Jul 2026, 01:51 UTC68 viewsread 9 August 2026

Be advised that there is currently an ongoing DDoS attack against our Kansas City infrastructure. DDoS mitigation is in place however there may still be degraded network performance until the attacks subside. — IncogNET (@IncogNetLLC) Jul 19, 2026

9 Jul 2026, 12:11 UTC121 viewsread 9 August 2026

No, but seriously. We mass applied some CVE patches in Washington and two hypervisors are being problematic and are still down. Awaiting for the data center to hook us up with a remote access. — IncogNET (@IncogNetLLC) Jul 9, 2026

9 Jul 2026, 12:06 UTC102 viewsread 9 August 2026

Just got off the phone with good friend, Senior Senator Mitch McConnell. He apologizes for the impacted hypervisors in Washington State that are down and was quoted saying, "Shit happens when you apply patches in bulk." We spoke for just shy of 20 minutes. — IncogNET (@IncogNetLLC) Jul 9, 2026

8 Jun 2026, 11:36 UTC157 views4 reactionsread 9 August 2026

Everything should be back up in the Netherlands at the moment. The POP was targeted by a decent sized DDoS attack and our upstream null-routed our prefixes that were getting carpet-bombed. So, the bad news is/was service disruption. Sorry, even Sony, Cloudflare, and other big — IncogNET (@IncogNetLLC) Jun 8, 2026

👏21🤝1

7 Jun 2026, 11:16 UTC146 views4 reactionsread 9 August 2026

Currently undergoing a DDoS attack in the Netherlands. Your patience is appreciated while we work on mitigation. — IncogNET (@IncogNetLLC) Jun 7, 2026

🙏21👍1

7 Jun 2026, 11:16 UTC128 viewsread 9 August 2026

Happy to help 💪 https://t.co/DfLBNN4uXz — IncogNET (@IncogNetLLC) Jun 7, 2026

20 May 2026, 07:31 UTC160 viewsread 9 August 2026

Doing some maintenance on the portal, so expect it to be unavailable for the next hour or so. Sorry for the inconvenience, need make some upgrades. — IncogNET (@IncogNetLLC) May 20, 2026

16 May 2026, 16:16 UTC162 views1 reactionsread 9 August 2026

Probably rustle some jimmies and ruffle some feathers, but unfortunately we're implementing email verification. Before you complain: Email isn't PII, you can use whatever working email service or privacy forwarding service that you wish. This is to reduce bounced automated — IncogNET (@IncogNetLLC) May 16, 2026

👍1

24 Apr 2026, 13:01 UTC176 viewsread 9 August 2026

Some general updates: - IncogNET turned 5 years old the other day, wow! - We're now a happy new sponsor of @ghostbsdproject, check out the project as it's worthy of your attention. - We also contribute to @FOSSBilling. Although we are not using the software in production, we've — IncogNET (@IncogNetLLC) Apr 24, 2026

10 Apr 2026, 15:06 UTC171 viewsread 9 August 2026

Reposting, without commentary. 👀 https://t.co/PICGIFt88B — IncogNET (@IncogNetLLC) Apr 10, 2026

31 Mar 2026, 16:36 UTC159 viewsread 9 August 2026

[Notice of Emergency Maintenance] The Liberty Lake, Washington, USA KVM VPS Hypervisor "PedalFast" was scheduled for maintenance at 8:00PM EST today as announced recently via email. This maintenance has been re-scheduled for ASAP to address service degradation due to hardware — IncogNET (@IncogNetLLC) Mar 31, 2026

23 Mar 2026, 16:26 UTC156 viewsread 9 August 2026

We've got a metric shit-ton of OS templates to choose from, and we've just added NetBSD to the mix to join FreeBSD. OpenBSD next? https://t.co/vTgeck4g3k — IncogNET (@IncogNetLLC) Mar 23, 2026

Showing the 12 most recent of 20 posts we hold for @incognet_io. 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.

Mentions

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.

Cite this entry

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 9 August 2026 — this entry's latest reading, not the date you are reading this.

“IncogNET” (@incognet_io), 106 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/incognet_io.

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.