Is obniz down?

Last checked 6m ago
Current status
obniz is up

No incidents right now.

Official status page: https://status.obniz.com · Polled every 5 minutes · 6 components tracked

obniz is operational right now. Last checked 6m ago; the most recent incident resolved 46d ago.

Real-time obniz status, recent outages, and incident history — pulled directly from obniz's official status page at https://status.obniz.com every 5 minutes. Pingoru tracks 6 obniz services and has captured 8 incidents in the last 90 days (98.61% uptime). Get email, Slack, Discord, or webhook alerts the moment obniz reports a new incident — free for 5 monitors, no credit card.

Users who monitor obniz also follow these Development services: Bitbucket OpenAI Datadog US1 Sentry NPM Travis CI Postman Pusher Pendo SonarCloud View all 6,000+ providers
obniz uptime 98.61% uptime · past 90 days
Mon Wed Fri
MayJunJulAug
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Jun 19, 2026, 09:16 AM UTC · Resolved Jun 18, 2026, 06:00 PM UTC
    Timeline · 1 update
    • resolved · Jun 19, 2026, 09:16 AM UTC

      Login and getting latest obniz device info from cloud had been failed. We updated software library which caused this issue. ■ Occurrence (Start) Time: 2026/06/19 14:45(JST) ■ Recovery (End) Time: 2026/06/19 17:56(JST) obniz Nowにおいてログインおよびobnizデバイスの最新情報取得において以下の期間で正常な動作が行えませんでした。原因はソフトウェアライブラリの最新バージョンにおいてソフトウェアバグが存在していたことに起因しています。当該ライブラリのバージョンを変更することで対応を行なっております。 ■ Occurrence (Start) Time: 2026/06/19 14:45(JST) ■ Recovery (End) Time: 2026/06/19 17:56(JST)

    Latest: Login and getting latest obniz device info from cloud had been failed. We updated software library which caused this issue. ■ Occurrence (Start) Time: 2026/06/19 14:45(JST) ■ Recov…

  2. Resolved
    Started Jun 17, 2026, 11:22 AM UTC · Resolved Jun 17, 2026, 11:22 AM UTC
    obniz Now
    Timeline · 1 update
    • resolved · Jun 17, 2026, 11:22 AM UTC

      We identified API integration issue. It was caused by another system down. It's separated now and recovered ■ Occurrence (Start) Time: 2026/06/17 20:10(JST) ■ Recovery (End) Time: 2026/06/17 20:17(JST) API連携機能の一部が他のサービスの障害(特定のお客様の設定されている外部接続先)の影響により広く影響を受け連携が停止する時間がございました。 影響範囲を狭めることで当該サービスのみの影響範囲となるよう対応を実施しております。 ■発生(開始)日時:2026/06/17 20:10(JST) ■復旧(終了)日時:2026/06/17 20:17(JST)

    Latest: We identified API integration issue. It was caused by another system down. It's separated now and recovered ■ Occurrence (Start) Time: 2026/06/17 20:10(JST) ■ Recovery (End) Time: …

  3. Resolved
    Started Jun 08, 2026, 12:32 PM UTC · Resolved Jun 08, 2026, 08:30 AM UTC
    Timeline · 1 update
    • resolved · Jun 08, 2026, 12:32 PM UTC

      partial devices are down while below window regarding server infrastructure startup problem ■ Occurrence (Start) Time: 2026/06/08 17:34(JST) ■ Recovery (End) Time: 2026/06/08 17:52(JST) obniz Nowの一部デバイスで接続不良が発生しました。インフラサーバーの起動に起因する問題で現在は改善済みの内容となります。 ■発生(開始)日時:2026/06/08 17:34(JST) ■復旧(終了)日時:2026/06/08 17:52(JST)

    Latest: partial devices are down while below window regarding server infrastructure startup problem ■ Occurrence (Start) Time: 2026/06/08 17:34(JST) ■ Recovery (End) Time: 2026/06/08 17:52…

  4. Resolved 16m
    Started Jun 03, 2026, 11:26 PM UTC · Resolved Jun 03, 2026, 11:42 PM UTC
    obnizCloud: GraphQL APIobniz Pipelineobniz Nowobniz MCP server
    Timeline · 1 update
    • monitoring · Jun 03, 2026, 11:26 PM UTC

      API and data transfer system was partial down. We are monitoring and improving our ystem. ■ Occurrence (Start) Time: 2026/06/04 02:49(JST) ■ Recovery (End) Time: 2026/06/04 03:32(JST) APIおよびAPIを利用する周辺システムでデータ連携の停止が発生いたしました。 現在長期的な対策に向け調査を行なっております。 ■発生(開始)日時:2026/06/04 02:49(JST) ■復旧(終了)日時:2026/06/04 03:32(JST)

    Latest: API and data transfer system was partial down. We are monitoring and improving our ystem. ■ Occurrence (Start) Time: 2026/06/04 02:49(JST) ■ Recovery (End) Time: 2026/06/04 03:32(J…

  5. Resolved 4h 17m
    Started Jun 03, 2026, 06:53 AM UTC · Resolved Jun 03, 2026, 11:11 AM UTC
    obnizCloud: Console and Device Connection RequestobnizCloud: Device connectionobniz Pipelineobniz Now
    Timeline · 4 updates
    • investigating · Jun 03, 2026, 06:38 AM UTC

      We are currently investigating this issue.

    • investigating · Jun 03, 2026, 06:53 AM UTC

      We are continuing to monitoring this issue.

    • monitoring · Jun 03, 2026, 06:54 AM UTC

      System backed as we expected. Now we are monitoring

    • resolved · Jun 03, 2026, 11:11 AM UTC

      Console and device connection accept system was down. We identified process management system issue. Now systems is working and will improve management system within 48 hours. ■ Occurrence (Start) Time: 2026/06/03 15:21(JST) ■ Recovery (End) Time: 2026/06/03 15:53(JST) obnizCloudの管理画面および接続リクエスト受付に影響がありました。 プロセス管理システムに問題が発生し作動可能な台数が限界より少なくなったことが原因となります。 対応を施し動作を復旧しましたが、長期的な改善を48時間以内に施すよう対策を進めます。 ■発生(開始)日時:2026/06/03 15:21(JST) ■復旧(終了)日時:2026/06/03 15:53(JST)

    Latest: Console and device connection accept system was down. We identified process management system issue. Now systems is working and will improve management system within 48 hours. ■ Oc…

See the full obniz outage history

3 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse obniz outage history →

Or sign up free to get alerts when obniz breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 8 incidents View full outage history →