Парочка описаний блокировки Telegram: (1) Хабр (2) блог Anurag Bhatia
👍3

Channel
@qrator_radar
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
574subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001813742929 |
|---|---|
| Type | Channel |
| Username | @qrator_radar |
| Description | Real-time BGP мониторинг и наши другие сервисы: обновления, фичареквесты, обратная связь. Информация об АС: https://radar.qrator.net/as/197068 Освещение глобальных инцидентов: https://twitter.com/Qrator_Radar Болталка: https://t.me/qrator_radar_chat |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/qrator_radar |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 10:18 | 574 | no change |
| 7 Aug 2026, 09:18 | 574 | first reading |
11 posts held, back to 2 December 2025 — 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 pageof 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 11 posts for this entry, the most recent from 18 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 7 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.
173 reactions across 11 posts, in 16 distinct kinds. The most used accounts for 40.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 70 | 40.5% | |
| 👍 | 41 | 23.7% | |
| 🎉 | 12 | 6.94% | |
| 😁 | 10 | 5.78% | |
| 🐳 | 8 | 4.62% | |
| 🤣 | 6 | 3.47% | |
| 👀 | 4 | 2.31% | |
| 😎 | 4 | 2.31% | |
| 🥴 | 4 | 2.31% | |
| 💩 | 3 | 1.73% | |
| 😱 | 3 | 1.73% | |
| 👎 | 2 | 1.16% | |
| 🙈 | 2 | 1.16% | |
| 🤬 | 2 | 1.16% | |
| ❤ | 1 | 0.578% | |
| 👏 | 1 | 0.578% |
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 11 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 173reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 2 December 2025 to 18 June 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.
Парочка описаний блокировки Telegram: (1) Хабр (2) блог Anurag Bhatia
👍3
🚨BGP Hijack Телеграмма 🇮🇳 AS18101 (RELIANCE) анонсирует префиксы AS-ок принадлежащих Telegram (🇻🇬 AS62041, 🇻🇬 AS62041, 🇻🇬 AS211157, 🇻🇬 AS44907). Вероятно для "локальной" блокировки, дабы предотвратить утечку ответов на экзаменационные вопросы.. Распространение идет через провайдеров AS18101: 🇮🇳 AS4755 (TATA), 🇮🇳 AS9583 (SIFY), 🇬🇧AS15412 (FLAG Telecom).
🔥10😁10💩3👎2🤬2🤣1
Привет 👋 ✨ Продолжаем добавлять улучшения на сайт по вашим заявкам. 📊 Количество активных и подтвержденных ASPA-записью провайдеров теперь можно увидеть на странице AS Overview. Пионеры имеют зеленый статус! 🌌 На странице с графом теперь указывается информация по выбранному префиксу: статусы RPKI ROA и Route Object, а также propagation (количество AS принявших префикс). Теперь не уходя со страницы можно оценить ра…
🔥9👍3
🚨 Глобальная утечка BGP маршрутов, 2026-02-11 12:21 UTC 🇰🇿 AS51878 (BAINET-AS) распространила (leaked) 18 646 префиксов, полученных в основном от 🇰🇿 AS9198 (KAZTELECOM-AS) и 🇰🇿 AS35168 (TNS-Plus), в сторону 🇰🇿 AS41798 (TTC-AS). Затронуло 82 страны и 1319 автономных систем (ASN). 🌏 Максимальное распространение: 100% точек наблюдения ⏱️ Длительность: ~12 минут (основная часть, без хвоста)
🐳5🥴4🤣2
Тем временем уже 1% процент автономных систем имеет ASPA-запись. https://bgp.he.net/report/rpki_and_aspa Спасибо за наводку @serverX
👍9🎉7🔥1
Хорошие новости, 🚀 поддержка RFC9234 (Route leak prevention and detection using roles) теперь в стабильной версии RouterOS 7.21. Changelog
👍8🔥7🎉5👏1
Вот и настал последний день 2025 года! ❄️ Прекрасная зимняя погода, новогоднее настроение, мы запустили IPv6-коллектор! 🥳 Теперь для передачи нам IPv6 префиксов можно: - не использовать Multi-protocol BGP (MP-BGP) для передачи через IPv4 стык - не делать хаки с маппингом IPv6 на IPv4 а просто создать прямую IPv6 сессию с нашим BGP коллектором. Создать IPv6 сессию, для выбранной AS, можно точно так же как и IPv4, че…
🔥29👍5
В интернетах время от времени случаются неправильные маршруты (BGP route leaks). Они случаютсяиз-за недосмотра, незнания или злонамеренности технического персонала - какая-та AS начинает анонсить не свои префиксы и не префиксы своих клиентов или не туда. И трафик не туда разворачивается и либо теряется по пути - такой роут лик сразу находится, виноватых награждают, непричастных отчитывают. Или удлинняется время путеш…
🔥6👍5❤1
⏱️ Время идет и трафик продолжает идти, через 🇨🇳 Китай. Утечка никуда не делась. Добавляем в коллекцию еще один пример трейса пиринговой утечки, через China Telecom Global (AS23764) и Hurricane (AS6939). Сверху докидываем содержащие лик BGP маршруты от разных спикеров к префиксу из трейса. За трейс спасибо @Kirya2k
😎4🐳3😱3🙈2
Доброго дня 👋 По заявкам пользователей, в продолжение истории c "неверным" OTC, написали небольшой пост-описание инцидента. 🛠 В посте описываем: - Что такое и как работает атрибут OTC - Почему некорректный атрибут привел к сбросу BGP-сессий - Разбор механики проблемы, бонусом – немного парсинга HEX-дампа. Пост уже 👉 в блоге Радара (EN) 👉 на сайте Curator (RU) Приятного чтения! 🤓
👍8👀1
Если вдруг слышали подземные стуки сегодня с Интернетом, как на картинках, с задержками 300мс и транзитом через China Telecom Global - так выглядит утечка маршрутов, о чём пишет Qrator Radar. На обоих скринах транзитом был Билайн. Спасибо большое друзьям за картинки.
🔥8👀3🤣3
Showing the 11 most recent of 11 posts we hold for @qrator_radar. 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.
Citation-graph rank — 1,303,545 of 1,350,102entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“Qrator.Radar” (@qrator_radar), 574 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/qrator_radar.
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.