V-CUBE Outage History
2 incidents recorded over the last 365 days, 2 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded V-CUBE Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Mar 12, 2026 | (復旧済み)Agora障害：Agora RESTful API / Notification 機能に関する問題Agora 社の RTC サービスにて下記事象が発生しておりました。 <発生日時> 2026/03/09 20:00 ~ 2026/03/09 21:15 <内容> ・Channel Management RESTful API がエラーを返す (499 または 5xx レスポンスが発生) ・RTC NCS… | 0 min | Resolved |
| Nov 19, 2025 | 【Zoom】日本を含む一部のユーザーで、Zoomミーティングへの参加に遅延が発生している問題一部のユーザーにおいて、Zoomミーティング、ルーム、ウェビナー、ライブストリーミング、コンタクトセンターのビデオエンゲージメントへの参加に遅延や問題が発生しておりましたが、このインシデントは解決しました。 Zoom社対象インシデントページ：https://www.zoomstatus.com/incidents/87xcksgwb7rb Zoom社ステータスページ：https://www.zoomstatus.com/ | 20h 4m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next V-CUBE incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This V-CUBE Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before V-CUBE acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single V-CUBE outage in this window ran 20h 4m, against a mean recovery of 10h 2m. If you depend on V-CUBE in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.