obniz logo

Is obniz Down?

Developer ToolsLive status, outages, and incident history

No. obniz is up right now.

Every monitored obniz system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment obniz breaks

obniz is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official obniz status page
How we know: the official obniz status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

obniz Status Summary

As of 14:55 UTC on 14 November 2026, obniz is operational. PulsAPI checked obniz's official status page and found 6 of 6 components operational, with no active incidents. The latest incident, "Docomo Connection Issue", was on Nov 5, 2026 and lasted 93h 6m.

Cite as: PulsAPI, “obniz status”, checked 14 November 2026, 14:55 UTC. https://www.pulsapi.com/services/obniz

obniz Component Status

The main obniz systems on this page. All 6 are operational right now.

6operational
obniz MCP server
Operational
obniz Now
Operational
obniz Pipeline
Operational

3 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking obnizCloud: Console and Device Connection Request, obnizCloud: Device connection, obnizCloud: GraphQL API.

See all of them free

Component statuses may change independently during partial outages.

Recent obniz Outages & Incidents

Incident history from the official obniz status page, including resolution updates.

Docomo Connection IssueResolved Nov 5, 2026 · 93h 6mResolved

This incident has been resolved. --- [2026-11-09T11:14:26.237+09:00] (identified) We are continuing to work on a fix for this issue. --- [2026-11-09T11:14:10.298+09:00] (identified) We have been informed by the mobile carrier that, following their investigation, no service disruption was identified on their side. We are therefore closing this incident. 本件通信キャリアより調査の結果「障害発生を認められなかった」旨の連絡を受領しました。 本インシデントについてクローズいたします。 2026/11/09 11:14 (JST) --- [2026-11-05T14:08:26.937+09:00] (identified) Some devices on the Docomo network are experiencing unstable connectivity. We are waiting for further updates from Docomo as they investigate and work on a fix. ■ Occurrence (Start) Time: 2026/11/05 12:26(JST) ■ Recovery (End) Time: ドコモ回線にて通信の不安定が発生しております。ドコモによる調査・改修の続報を待機しております。

Inboundsource FailureResolved Nov 4, 2026 · 1h 36mResolved

■ Occurrence (Start) Time: 2026/10/27 21:30(JST) ■ Recovery (End) Time: 2026/11/04 18:35(JST) (Estimated) 復旧が完了いたしました。 inBoundSourceにおいてbodyにTokenがあり、かつquery に改行文字が含まれている場合不正データとしてアップロードが行えなくなっておりました。 互換性を保つために以前と同じフォーマットについて受け入れできる処理を追加し、現在データの受信が可能となっていることを確認いたしました。 --- [2026-11-04T17:12:21.723+09:00] (identified) We identified an issue where authentication failed for Inbound Source requests that included a token in the request body. It was caused by a bug in an update to our authentication system, and we are working on a fix. ■ Occurrence (Start) Time: 2026/10/27 21:30(JST) ■ Recovery (End) Time: 2026/11/04 17:30(JST) (Estimated) Inbound Sourceにおいてreqeust bodyにtokenが含まれている場合に認証に失敗する不具合が発生しておりました。 認証システムの更新における不具合で現在掲示の復旧予定時刻での復旧に向け対策を進めております。

obniz Now integration failure and processing delayResolved Oct 27, 2026Resolved

obniz Now experienced temporary processing delays and integration failures. The issue was caused by a temporary increase in database load, and we have confirmed that the service has now been fully restored. We apologize for any inconvenience this may have caused. ■ Occurrence (Start) Time: 2026/10/27 21:36(JST) ■ Recovery (End) Time: 2026/10/27 21:39(JST) obniz Nowにおいて一時的な処理遅延及びintegrationの失敗が発生いたしました。 一時的なデータベースの負荷を起因としており、現在は復旧を確認しております。

obniz Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a obniz incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live obniz Outage Reports

Problems reported by engineers using obniz. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No obniz problems reported yet.

Something wrong with obniz on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About obniz

obniz's status page at status.obniz.com lists 6 components, such as obniz MCP server, obniz Now and obniz Pipeline. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on obniz's side or yours.

obniz Status FAQ

Is obniz down right now?

The verdict at the top of this page comes from the latest poll of the official obniz status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if obniz is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until obniz recovers.

How do I check obniz uptime history?

PulsAPI tracks obniz uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever obniz changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect obniz outages?

PulsAPI reads the official obniz status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual obniz components?

Yes. PulsAPI monitors 6 individual obniz components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when obniz goes down?

Yes. Create a free account and subscribe to obniz: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with obniz to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot obniz problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor obniz?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so obniz plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track obniz with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services