obniz Outage History

obniz is up right now

obniz had 10 outages in the last 2 years totaling 2h 1m of downtime — averaging 0.4 incidents per month.

There were 10 obniz outages since June 17, 2025 totaling 2h 1m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.obniz.com

Notice May 15, 2026

Online status not updated on some devices

Detected by Pingoru
May 15, 2026, 03:29 AM UTC
Resolved
May 15, 2026, 02:00 AM UTC
Duration
Timeline · 1 update
  1. resolved May 15, 2026, 03:29 AM UTC

    Only the latest status display was affected. Existing and new connections, pipelines, and applications including obniz Now continued to operate without interruption. Connection history was also recorded properly. Only the most recent status updates were not being reflected. ■ Occurrence (Start) Time: May 15, 2026, 12:10 (JST) ■ Recovery (End) Time: May 15, 2026, 6am (JST) 一部のデバイスの最新の接続状況がobnizCloudで確認できない事象がありました。 最新の表示のみで既存および新規の接続とpipeline, obniz Nowをはじめとするアプリケーションの利用は停止せず動作しておりました。 また、接続の履歴も記録がございます。 Online/Offlineの最新状態のみ更新ができておりませんでした。 ■発生(開始)日時:2026年05月15日 12:10(JST) ■復旧(終了)日時:2026年05月15日 6時頃(JST)

Read the full incident report →

Notice April 26, 2026

Database Write Failure

Detected by Pingoru
Apr 26, 2026, 05:25 AM UTC
Resolved
Apr 26, 2026, 05:25 AM UTC
Duration
Affected: obnizCloud: Console and Device Connection RequestobnizCloud: GraphQL API
Timeline · 1 update
  1. resolved Apr 26, 2026, 05:25 AM UTC

    データベースへの書き込みが正常に行われず一時的にアプリのログや機器名変更などが行えない状態となっておりました。 ■発生(開始)日時:2026年04月26日 14:18(JST) ■復旧(終了)日時:2026年04月26日 14:19(JST) Database writes were not functioning properly, temporarily preventing actions such as app logs and device name changes. ■ Occurrence (Start) Time: April 26, 2026, 14:18 (JST) ■ Recovery (End) Time: April 26, 2026, 14:19 (JST)

Read the full incident report →

Critical March 23, 2026

Now data storage failure

Detected by Pingoru
Mar 23, 2026, 10:48 PM UTC
Resolved
Mar 23, 2026, 11:00 PM UTC
Duration
12m
Affected: obniz Now
Timeline · 2 updates
  1. identified Mar 23, 2026, 10:48 PM UTC

    obniz Now has been failed to save data regarding certification issue. データの保存がに失敗することがあり証明書の問題と特定されています。 現在対処を行い間も無く回復の見込みです。

  2. resolved Mar 23, 2026, 11:00 PM UTC

    データベースへの接続が証明書の入れ替えにより正常に動作せず、一部データが保存できない期間が発生しました。現在は復旧しております。 ■発生(開始)日時:2026年03月24日 5:50(JST) ■復旧(終了)日時:2026年03月24日 7:45(JST) Due to a certificate rotation, the database connection failed to operate normally, resulting in a period during which some data could not be saved. The issue has now been resolved. Incident start time: March 24, 2026, 5:50 AM (JST) Recovery time: March 24, 2026, 7:45 AM (JST)

Read the full incident report →

Notice December 14, 2025

Temporary Database Connectivity Issue (9:26-9:30 JST)

Detected by Pingoru
Dec 14, 2025, 12:37 AM UTC
Resolved
Dec 14, 2025, 12:00 AM UTC
Duration
Timeline · 2 updates
  1. resolved Dec 14, 2025, 12:37 AM UTC

    We are reporting a temporary connectivity issue that affected a segment of our database. Duration: The incident occurred from 9:26 AM to 9:30 AM JST on December 14, 2025. The issue has been resolved, and all services are fully operational again. We are currently investigating the root cause and developing preventative measures to avoid recurrence. We will provide an update once our investigation is complete.

  2. postmortem Dec 14, 2025, 01:47 AM UTC

    We are providing an update following the temporary connectivity issue that occurred on December 14, 2025, from 9:26 AM to 9:30 AM JST. The service has been fully restored. **Root Cause Identified:** Upon investigation, we determined that there were no issues with the database itself. The problem was specifically identified as a failure in the **connection path** to the database. **Future Countermeasures:** As a preventative measure, we will be implementing **additional redundancy** across our infrastructure to enhance resilience and prevent similar occurrences in the future. We apologize for any inconvenience this incident may have caused.

Read the full incident report →

Critical November 12, 2025

System Down

Detected by Pingoru
Nov 12, 2025, 02:38 PM UTC
Resolved
Nov 12, 2025, 03:32 PM UTC
Duration
53m
Affected: obniz Now
Timeline · 5 updates
  1. investigating Nov 12, 2025, 02:38 PM UTC

    We are currently investigating

  2. monitoring Nov 12, 2025, 02:43 PM UTC

    We have fixed building system failure.

  3. monitoring Nov 12, 2025, 02:43 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Nov 12, 2025, 03:32 PM UTC

    This incident has been resolved.

  5. postmortem Nov 12, 2025, 03:34 PM UTC

    We would like to inform you that obniz Now has recovered from a temporary service outage. Due to an error during a server system update, the service was unavailable between **23:32 and 23:38**. The issue has now been resolved, and the system is operating normally.

Read the full incident report →

Notice October 10, 2025

LTE temporary unavailable

Detected by Pingoru
Oct 10, 2025, 02:53 AM UTC
Resolved
Oct 10, 2025, 02:53 AM UTC
Duration
Affected: obniz Now
Timeline · 1 update
  1. resolved Oct 10, 2025, 02:53 AM UTC

    ue to instability in the carrier network, LTE connections on our service experienced temporary disruptions. The issue has now been resolved, and the service is operating normally. We sincerely apologize for any inconvenience this may have caused our customers. ■発生(開始)日時:2025年10月10日 6:33(JST) ■復旧(終了)日時:2025年10月10日 8:34(JST)

Read the full incident report →

Notice September 18, 2025

Temporary Service Interruption on obniz Now

Detected by Pingoru
Sep 18, 2025, 04:00 PM UTC
Resolved
Sep 18, 2025, 04:00 PM UTC
Duration
Affected: obniz Now
Timeline · 1 update
  1. resolved Sep 18, 2025, 04:00 PM UTC

    ate/Time of Incident: September 19, 0:39 – 0:51 (JST) Description: During the above time period, a part of the obniz Now system failed to start certain processes, resulting in a temporary service interruption. As a result, external requests and device control were not available for some devices. Resolution: The automatic recovery process restored the affected services, and we have confirmed that the system is now operating normally. Preventive Measures: We will improve our process management system to prevent recurrence of such incidents. We sincerely apologize for any inconvenience this may have caused and appreciate your understanding.

Read the full incident report →

Major August 18, 2025

LTE Communication Failure

Detected by Pingoru
Aug 18, 2025, 10:29 AM UTC
Resolved
Aug 18, 2025, 11:25 AM UTC
Duration
55m
Affected: obniz Now
Timeline · 2 updates
  1. investigating Aug 18, 2025, 10:29 AM UTC

    LTE Career reported that LTE network partial unavailability since 2025/8/18 17:50(JST) Now we are collecting information from LTE Career.

  2. resolved Aug 18, 2025, 11:25 AM UTC

    We got resolved report from our Career

Read the full incident report →

Notice July 14, 2025

Temporary Device Connection Unstable

Detected by Pingoru
Jul 14, 2025, 08:55 PM UTC
Resolved
Jul 14, 2025, 05:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Jul 14, 2025, 08:55 PM UTC

    1:55-2:20 JST Some devices experienced unstable connections to obniz Now during this time. The issue was caused by a temporary increase in server load and lasted.

Read the full incident report →