26 Feb 2025, 23:59 UTC362 viewsread 8 August 2026
Increased API error rates Feb 26, 15:55 PST Investigating - We are currently investigating this issue. via OpenAI Status - Incident History
Channel
Openaibot
@Openaibot_channel
On this record: Growth · Engagement · Posts · Cite this entry
192subscribers
-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 | -1001539195431 |
|---|---|
| Type | Channel |
| Username | @Openaibot_channel |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/Openaibot_channel |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 11:53 | 192 | +2 |
| 20 Aug 2026, 22:55 | 190 | -1 |
| 14 Aug 2026, 06:19 | 191 | -2 |
| 8 Aug 2026, 11:49 | 193 | no change |
| 7 Aug 2026, 09:27 | 193 | first reading |
Engagement
20 posts held, back to 4 February 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 20 posts for this entry, the most recent from 26 February 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
26 Feb 2025, 14:02 UTC361 viewsread 8 August 2026
Degraded performance for ChatGPT voice. Feb 26, 05:55 PST Update - We are continuing to investigate this issue. Feb 26, 05:53 PST Investigating - We are currently investigating this issue. via OpenAI Status - Incident History
26 Feb 2025, 13:42 UTC340 viewsread 8 August 2026
API performance degradation Feb 26, 05:29 PST Investigating - We are currently investigating this issue. via OpenAI Status - Incident History
26 Feb 2025, 10:11 UTC279 viewsread 8 August 2026
Elevated API Errors Feb 26, 02:04 PST Investigating - We're experiencing an elevated level of API errors and are currently looking into the issue. via OpenAI Status - Incident History
22 Feb 2025, 03:27 UTC201 viewsread 8 August 2026
Elevated errors in the API Feb 21, 19:23 PST Monitoring - A fix has been implemented and we are monitoring the results. Feb 21, 19:22 PST Identified - The issue has been identified and a fix is being implemented. Feb 21, 19:19 PST Investigating - We are currently investigating this issue. via OpenAI Status - Incident History
22 Feb 2025, 00:25 UTC144 viewsread 8 August 2026
Increased ChatGPT errors Feb 21, 16:22 PST Identified - The issue has been identified and a fix is being implemented. via OpenAI Status - Incident History
21 Feb 2025, 19:19 UTC119 viewsread 8 August 2026
Increased errors with Assistants API Feb 20, 20:30 PST Resolved - Assistants API Runs with image inputs and structured outputs were failing between 8:40pm PT Feb 20, 2025 and 11:10am PT Feb 21, 2025. This has now fully recovered. via OpenAI Status - Incident History
21 Feb 2025, 17:32 UTC101 viewsread 8 August 2026
Increased errors with advanced voice Feb 21, 09:25 PST Investigating - We are currently investigating this issue. via OpenAI Status - Incident History
19 Feb 2025, 18:05 UTC96 viewsread 8 August 2026
Degraded behavior of chatgpt Feb 19, 09:59 PST Investigating - We are currently investigating this issue. via OpenAI Status - Incident History
18 Feb 2025, 23:23 UTC93 viewsread 8 August 2026
Increased login issues Feb 18, 15:20 PST Investigating - We are currently investigating this issue. via OpenAI Status - Incident History
14 Feb 2025, 15:18 UTC92 viewsread 8 August 2026
Elevated Errors on Assistants API Vision Feb 14, 07:07 PST Investigating - We're experiencing an elevated level of errors on Assistants API's vision including Playground vision and are currently looking into the issue. via OpenAI Status - Incident History
12 Feb 2025, 21:48 UTC92 viewsread 8 August 2026
Errors with a subset of API Feb 12, 13:39 PST Resolved - On February 12, between 11:50am - 12:25pm PST, some API users may have experienced a degraded performance for a subset of APIs. This issue has been resolved via OpenAI Status - Incident History
Showing the 12 most recent of 20 posts we hold for @Openaibot_channel. 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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“Openaibot” (@Openaibot_channel), 192 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/Openaibot_channel.
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.