⚙️ Lucrări tehnice neplanificate – înlocuire UPS Vă informăm că, în următoarele aproximativ 30 de minute, vom efectua lucrări tehnice neplanificate pentru înlocuirea preventivă a unuia dintre UPS-urile existente, care a început să prezinte semne de funcționare necorespunzătoare. UPS-ul va fi înlocuit cu un echipament nou. Pe durata intervenției, una dintre cele două surse independente de alimentare electrică va fi…

Channel
IPHOST & Amplica alerts
@iphmdann
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
357subscribers
+0 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 | -1001422951118 |
|---|---|
| Type | Channel |
| Username | @iphmdann |
| Description | Anunțuri urgente despre starea tehnica a data centrului și disponibilitatea serviciilor |
| Created | Between 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/iphmdann |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 06:35 | 357 | no change |
| 7 Aug 2026, 21:27 | 357 | first reading |
Engagement
19 posts held, back to 5 May 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.
- ERR · 30 days
- 67.2%
- avg views ÷ 357 subscribers
- Avg views / post
- 240
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 19 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.
| Window | Rolling 30 days · latest post in window 21 July 2026 |
|---|---|
| Posts held | 19 (5 May 2025 – 21 July 2026) |
| Views total | 240 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 06:35 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
- Photos
- 38
- Videos
- 3
- Links
- 9
Lifetime counters from Telegram’s own channel header, read 8 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
97 reactions across 17 posts, in 11 distinct kinds. The most used accounts for 44.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 43 | 44.3% | |
| ❤ | 22 | 22.7% | |
| 👏 | 13 | 13.4% | |
| 😁 | 5 | 5.15% | |
| 👎 | 4 | 4.12% | |
| ⚡ | 3 | 3.09% | |
| 🔥 | 2 | 2.06% | |
| 😱 | 2 | 2.06% | |
| 👻 | 1 | 1.03% | |
| 🤬 | 1 | 1.03% | |
| 🤯 | 1 | 1.03% |
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 17 of the 19 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 97reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 5 May 2025 to 21 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
📢 Actualizare incident – Data Center NXDATA2 București Am primit o nouă actualizare din partea echipei NXDATA2. La ora 13:00, sistemul de climatizare al centrului de date a fost reparat și repus în funcțiune. În prezent, se așteaptă ca temperatura din sala serverelor să scadă sub 28°C, după care echipa centrului de date va începe pornirea controlată a infrastructurii și a serverelor. IPHOST monitorizează permanen…
⚡1👍1🤯1
⚠️ Incident: Serverele din București sunt Offline 📅 Data: 01.07.2026 ⏱ Ora: -:- 📊 Statut: Analizăm soluționarea incidentului În urma unei furtuni puternice din București, sistemul de climatizare al centrului de date NXDATA2 a fost afectat. Ca măsură de protecție a echipamentelor, o parte dintre serverele găzduite în această locație au fost oprite din cauza temperaturii ridicate din centrul de date. Incidentul afec…
👎2🔥1😱1
📢 Atenție – incident tehnic în data center-ul NXDATA2 În prezent, o parte din serviciile IPHOST găzduite în România pot fi temporar indisponibile. În urma investigațiilor efectuate, am identificat că în jurul orei 03:00 AM a avut loc o creștere bruscă a temperaturii în centrul de date NXDATA2, unde este colocată o parte din infrastructura IPHOST destinată clienților din România. Conform confirmării primite din par…
👎2⚡1❤1👍1
📢 Atenție – emailuri false în numele IPHOST Am identificat o campanie de emailuri frauduloase (phishing) în care atacatorii folosesc identitatea IPHOST și trimit mesaje către adrese aleatorii, inclusiv deținători de domenii .md. Aceste mesaje NU sunt trimise de IPHOST și pot conține solicitări false de plată (ex: „domeniul expiră”, „serviciul va fi suspendat”). ⚠️ Vă rugăm să verificați cu atenție: • Emailurile o…
👍3❤2⚡1
✅ Update: Incident fibră optică remediat 📅 Data: 11.03.2026 ⏱ Ora: acum câteva minute 📊 Statut: Serviciu normal Descriere: Incidentul de fibră optică din sectorul Botanica, provocat în timpul lucrărilor de schimbare a pavajului efectuate pe trotuar, a fost remediat. După intervenția poliției și documentarea cazului, echipei tehnice i-a fost permisă începerea lucrărilor de remediere. A fost înlocuit segmentul de cab…
👏4❤2👍1
Photo, posted without a caption
⚠️ Incident: Ruptură fibră optică Botanica (Fiber Cut) 📅 Data: 11.03.2026 ⏱ Ora: 12:20 📊 Statut: Analizăm soluționarea incidentului Descriere: Vă informăm că o parte dintre clienții din sectorul Botanica care utilizează conexiune prin fibră optică sunt în prezent deconectați de la internet. Incidentul a avut loc în timpul lucrărilor de schimbare a pavajului pe trotuar, efectuate de echipe contractate de Primărie. Î…
❤1🤬1😱1
✅ Update: Energie electrică restabilită 📅 Data: 05.05.2025 ⏱ Ora: acum câteva minute 📊 Statut: Serviciu normal Descriere: Furnizarea energiei electrice a fost restabilită cu câteva minute în urmă, după o pană extinsă la nivel național, care a afectat mai multe localități din țară și regiuni din municipiul Chișinău. Generatoarele de rezervă IPHOST au fost oprite conform procedurii, urmând să fie realimentate cu moto…
👏7❤1👍1
Отключение электричества связано с метеоусловиями, сообщили в Национальном центре управления кризисами Электричества нет в Новых Аненах, Комрате, Чадыр-Лунге и других районах страны.
👍3
⚠️ Incident: Pană de curent 📅 Data: 31.01.2026, ora 11:00 ⏱️ Durata estimată de remediere: necomunicată de furnizor 📊 Statut: Monitorizare 🖥 Servicii afectate: niciunul Descriere: În prezent, se înregistrează întreruperi de energie electrică în mai multe localități din țară, inclusiv în mai multe regiuni din municipiul Chișinău. Generatoarele de rezervă IPHOST s-au pornit automat și funcționează normal. Toate servic…
👍7🔥1
Problema a fost identificata si rezolvata Data: 21.06.2025 18:00
👍2👏1
Showing the 12 most recent of 19 posts we hold for @iphmdann. 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.
Forward network
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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@iphmdann named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“IPHOST & Amplica alerts” (@iphmdann), 357 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/iphmdann.
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.