Notable logo

Is Notable Down?

AI & Machine LearningLive status, outages, and incident history

No. Notable is up right now.

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

OperationalChecked 9m agoLive · every 60s

Know the moment Notable breaks

Notable 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 Notable status page
How we know: the official Notable status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Notable Status Summary

As of 15:51 UTC on 14 November 2026, Notable is operational. PulsAPI checked Notable's official status page and found 7 of 7 components operational, with no active incidents. The latest incident, "FHIR Capabilities Impacted", was on Sep 30, 2026 and lasted 6h 58m.

Cite as: PulsAPI, “Notable status”, checked 14 November 2026, 15:51 UTC. https://www.pulsapi.com/services/notable

Notable Component Status

The main Notable systems on this page. All 7 are operational right now.

7operational
Fax Block
Operational
FHIR
Operational
Flow Compass
Operational

4 more components tracked

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

Also tracking Interface Engine, Patient Digital Experience, Patient iPad App, Voice calls.

See all of them free

Component statuses may change independently during partial outages.

Recent Notable Outages & Incidents

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

FHIR Capabilities ImpactedResolved Sep 30, 2026 · 6h 58mResolved

Service has been restored and we have successfully recovered affected jobs. We have reached out to all customers that were impacted by this service disruption. We appreciate your patience. A post-mortem for this incident will be published later this week. --- [2026-09-30T21:46:58Z] (monitoring) We have completed recovery for nearly all affected work and completed our general impact assessment. We are continuing to monitor the situation. --- [2026-09-30T17:44:50Z] (identified) Initial assessment of the situation has determined that the partial outage started at 3PM PT on the 29th, with service restored as of this morning around 8AM PT. We are continuing to work on assessing full impact and have begun recovery efforts on jobs affected by the outage. --- [2026-09-30T16:27:44Z] (identified) We have confirmed a partial outage of our FHIR integrations. A solution has been identified and applied, and we are currently assessing recovery efforts and full impact. Users of the "Advanced FHIR" block should not have been affected.

Referral processing disruptedResolved Sep 24, 2026 · 28h 54mResolved

All functionality has been restored as of 9/24 4:00PM PST. --- [2026-09-24T15:17:24Z] (investigating) We are investigating failures in the medical necessity check used by referral workflows, beginning at approximately 11:30 AM PDT on September 23. Affected referrals cannot be automatically transcribed. We have escalated the issue to our medical necessity service provider, Solventum. We will share further updates as we learn more. There is currently no estimated time to resolution.

Omni / Bigquery Performance RegressionResolved Sep 3, 2026 · 4h 10mResolved

We have observed query times having improved consistently across the board for the last couple of hours after our fixes, and now believe the performance issues are resolved. --- [2026-09-03T18:35:57Z] (monitoring) We have taken measures to mitigate the slot contention in BigQuery. Performance has improved, and we will continue to work on additional fixes. --- [2026-09-03T16:25:32Z] (identified) Our embedded dashboards and other related analytics products are experiencing excess load, causing slowdowns and timeouts. We've identified the cause as slot contention in our data warehouse (BigQuery), and are working on fixes to address the issue.

Upcoming maintenance

Announced by Notable. Planned work, not an outage.

Yearly Database Upgrade MaintenanceScheduled for Nov 15, 2026 · 3h 0mScheduled

Notable will be doing normal database version upgrades. Further updates will be provided on or before November 9th.

Notable Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Notable 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 Notable Outage Reports

Problems reported by engineers using Notable. 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 Notable problems reported yet.

Something wrong with Notable on your end?

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

About Notable

Notable's status page at status.notablehealth.com lists 7 components, such as FHIR, Fax Block and Flow Compass. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on Notable's side or yours.

Notable Status FAQ

Is Notable down right now?

The verdict at the top of this page comes from the latest poll of the official Notable 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 Notable 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 Notable recovers.

How do I check Notable uptime history?

PulsAPI tracks Notable 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 Notable changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Notable outages?

PulsAPI reads the official Notable 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 Notable components?

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

Can I get alerts when Notable goes down?

Yes. Create a free account and subscribe to Notable: 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 Notable 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 Notable problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Notable?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Notable 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 Notable 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