obniz incident

Now data storage failure

Critical Resolved View vendor source →
Started
Mar 23, 2026, 10:48 PM UTC
Resolved
Mar 23, 2026, 11:00 PM UTC
Duration
12m
Detected by Pingoru
Mar 23, 2026, 10:48 PM UTC

Affected components

obniz Now

Update timeline

  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)

Looking to track obniz downtime and outages?

Pingoru polls obniz's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when obniz reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track obniz alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring obniz for free

5 free monitors · No credit card required