Telegram RegisterThe public register of Telegram
Telegram profile photo for PeeringDB Updates

Channel

PeeringDB Updates

@peeringdb

On this record: Growth · Engagement · Posts · Cite this entry

345subscribers

-1 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-1001423904473
TypeChannel
Username@peeringdb
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live31 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/peeringdb

Growth

3443463457 August 2026 — 346 subscribers8 August 2026 — 346 subscribers15 August 2026 — 344 subscribers31 August 2026 — 345 subscribers7 August 202631 August 2026
4 measurements spanning 25 days, net -1. 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 344–346 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 23:28345+1
15 Aug 2026, 14:56344-2
8 Aug 2026, 06:50346no change
7 Aug 2026, 09:17346first reading

Engagement

20 posts held, back to 18 August 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 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 19 August 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

19 Aug 2025, 05:56 UTC369 viewsread 8 August 2026

Network AS153299 Airmax Broadband Private Limited, aka airmax Network Type: Content Traffic Level: Traffic Ratio: Not Disclosed IPv4 Prefixes: null IPv6 Prefixes: null [IPv4 Unicast] [Multicast] [IPv6] [Never via RS] Created at "2025-04-18T06:47:14Z" Updated 15 seconds ago View

19 Aug 2025, 05:48 UTC368 viewsread 8 August 2026

Network AS38588 Felicity IDC Limited, aka Felicity IDC Network Type: Network Services Traffic Level: 5-10Gbps Traffic Ratio: Mostly Outbound IPv4 Prefixes: 512 IPv6 Prefixes: 1000 [IPv4 Unicast] [IPv6] Created at "2025-02-19T08:42:27Z" Updated 2 minutes and 41 seconds ago View

19 Aug 2025, 05:31 UTC322 viewsread 8 August 2026

Network AS24556 Bijoy Online Network Type: Cable/DSL/ISP Traffic Level: 5-10Gbps Traffic Ratio: Balanced IPv4 Prefixes: 120 IPv6 Prefixes: 120 [IPv4 Unicast] Created at "2018-09-18T12:03:16Z" Updated 34 seconds ago View

19 Aug 2025, 04:16 UTC251 viewsread 8 August 2026

Network AS138398 Prodigi Technology Services Limited, aka Prodigi Network Type: NSP Traffic Level: Traffic Ratio: Balanced IPv4 Prefixes: 50 IPv6 Prefixes: 50 [IPv4 Unicast] [IPv6] Created at "2019-05-03T01:13:48Z" Updated 8 seconds ago View

19 Aug 2025, 03:55 UTC197 viewsread 8 August 2026

Network AS139057 EdgeNext, aka Legend Dynasty Network Type: Content Traffic Level: 20-50Tbps Traffic Ratio: Heavy Outbound IPv4 Prefixes: 20000 IPv6 Prefixes: 20000 [IPv4 Unicast] [IPv6] Created at "2020-12-08T06:41:10Z" Updated 2 minutes and 17 seconds ago View

19 Aug 2025, 03:55 UTC159 viewsread 8 August 2026

Network AS131746 Medianusa Permana, aka PermanaNet Network Type: Cable/DSL/ISP Traffic Level: Traffic Ratio: IPv4 Prefixes: 20 IPv6 Prefixes: 20 [IPv4 Unicast] [IPv6] Created at "2019-12-11T03:04:16Z" Updated 2 minutes and 34 seconds ago View

19 Aug 2025, 03:30 UTC102 viewsread 8 August 2026

Network AS151653 General Telephone System, aka GTSI Network Type: Cable/DSL/ISP Traffic Level: 20-50Gbps Traffic Ratio: Heavy Inbound IPv4 Prefixes: 24 IPv6 Prefixes: 48 [IPv4 Unicast] Created at "2023-09-03T10:12:29Z" Updated 1 minute and 32 seconds ago View

19 Aug 2025, 03:30 UTC123 viewsread 8 August 2026

Network AS153803 IDNIC-TLINET-AS-ID, aka TLINET Network Type: Enterprise Traffic Level: 1-5Gbps Traffic Ratio: Balanced IPv4 Prefixes: 163 IPv6 Prefixes: null Created at "2025-08-18T06:32:59Z" Updated 49 seconds ago View

19 Aug 2025, 02:28 UTC92 viewsread 8 August 2026

Network AS137183 BATI-IX Route Servers, aka BATI-IX Network Type: Route Server Traffic Level: Traffic Ratio: Balanced IPv4 Prefixes: 10000 IPv6 Prefixes: 2500 [IPv4 Unicast] [IPv6] Created at "2025-08-14T14:42:26Z" Updated 1 minute and 32 seconds ago View

19 Aug 2025, 02:24 UTC84 viewsread 8 August 2026

Network AS137183 BATI-IX Route Servers, aka BATI-IX Network Type: Route Server Traffic Level: Traffic Ratio: Balanced IPv4 Prefixes: 10000 IPv6 Prefixes: 2500 [IPv4 Unicast] [IPv6] Created at "2025-08-14T14:42:26Z" Updated 2 minutes and 1 second ago View

19 Aug 2025, 02:07 UTC78 viewsread 8 August 2026

Network AS38515 GRAHAMEDIA INFORMASI, aka GRAHAMEDIANET Network Type: Cable/DSL/ISP Traffic Level: 1-5Gbps Traffic Ratio: Mostly Inbound IPv4 Prefixes: 12 IPv6 Prefixes: 50000 [IPv4 Unicast] [IPv6] Created at "2016-09-23T13:21:20Z" Updated 1 minute and 41 seconds ago View

19 Aug 2025, 01:55 UTC72 viewsread 8 August 2026

Network AS139952 Trisari Data Indonusa, aka Tridata Network Type: Cable/DSL/ISP Traffic Level: 50-100Gbps Traffic Ratio: Mostly Inbound IPv4 Prefixes: 19 IPv6 Prefixes: 32 [IPv4 Unicast] Created at "2020-06-03T13:18:08Z" Updated 1 minute and 54 seconds ago View

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

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

“PeeringDB Updates” (@peeringdb), 345 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/peeringdb.

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.