All Systems Operational

About This Site

All status history of obniz services

Uptime over the past 90 days. View historical uptime.
obnizCloud: Console and Device Connection Request Operational
obnizCloud: GraphQL API Operational
obnizCloud: Device connection Operational
obniz Pipeline Operational
obniz Now Operational
obniz MCP server Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Sep 16, 2026

No incidents reported today.

Sep 15, 2026

No incidents reported.

Sep 14, 2026

No incidents reported.

Sep 13, 2026

No incidents reported.

Sep 12, 2026

No incidents reported.

Sep 11, 2026

No incidents reported.

Sep 10, 2026

New connection for partial devices are failed become status of offline.
Resolved - An issue occurred affecting approximately 5% of all online devices, where devices were displayed as offline even though they were actually connected, and new connections from obniz.js could not be established.

The issue was caused by a specific server becoming isolated and removed from the routing pool while still maintaining connections to some devices.

Existing connections remained active during this period, and there was no impact when a device itself reconnected, as it would establish a new connection to another server. However, if an obniz.js connection was disconnected and then re-established while the device was still connected, the reconnection attempt could fail.

Additionally, connection logs during the affected period incorrectly recorded the devices as offline.

The issue was caused by a problem with inter-server communication. We will address this by updating our server health monitoring system.

■ Occurrence (Start) Time: 2026/09/10 23:35(JST)
■ Recovery (End) Time: 2026/09/11 11:27(JST)

オンラインの端末全体の5%において実際には接続中であってもオフラインと表記されobniz.jsからの新しい接続を受け付けない障害が発生しておりました。
特定のサーバーが切り離されルーティング対象から外れてしまった上でサーバーが接続を保持したデバイスがあったことが原因となります。
その間の接続中のコネクションは維持され、デバイスが再接続した場合は新たに別のサーバーに接続するため影響はございませんが、デバイスが接続中にも関わらずobniz.jsからのコネクションを一度切断し再接続しようとした際に失敗する問題がありました。
また、その期間における接続ログはオフラインと記録されておりました。
サーバー間連携の不具合によるもので、死活監視システムの更新により対応いたします。

■発生(開始)日時：2026/09/10 23:35(JST)
■復旧(終了)日時：2026/09/11 11:27(JST)
Sep 10, 23:30 JST

Sep 9, 2026

No incidents reported.

Sep 8, 2026

No incidents reported.

Sep 7, 2026

No incidents reported.

Sep 6, 2026

No incidents reported.

Sep 5, 2026

No incidents reported.

Sep 4, 2026

No incidents reported.

Sep 3, 2026

No incidents reported.

Sep 2, 2026

No incidents reported.

Incident History Powered by Atlassian Statuspage