Noterro Outage History
8 incidents recorded over the last 365 days, 8 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Noterro Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 31, 2026 | Square Reader issues on Android Chrome version 152We suspected the issue to be on Square's end, so we notified their team and they've identified the issue. It is resolved in version 7.23 of the Square POS Android app. Please ensure you update to this version. | 51h 53m | Resolved |
| Aug 4, 2026 | Patient/Client Portal UnavailableThis incident has been resolved. | 36 min | Resolved |
| Jul 23, 2026 | Site not responding or SlowThis incident has been resolved. | 1h 25m | Resolved |
| Jun 23, 2026 | Patient Portals not loadingEarlier today, a routine update to the patient portal caused a brief disruption affecting all portal access. We caught it through our own monitoring, reverted to the previous stable version, and had service fully… | 40 min | Resolved |
| Jun 2, 2026 | Intermittent connections to appDuring a scheduled maintenance window today, a database change that performed well in testing did not perform as expected under production load. This caused connection delays and failures, resulting in pages not loading… | 23 min | Resolved |
| May 7, 2026 | Appointment Notifications Not DeliveringThis incident has been resolved. | 16h 15m | Resolved |
| Dec 8, 2025 | Patient search is not working for some clinics.This incident has been resolved. | 3h 54m | Resolved |
| Nov 18, 2025 | Unable to edit breaks or availabilities.This incident has been resolved. | 3h 3m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Noterro incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Noterro Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Noterro acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Noterro outage in this window ran 2d 3h, against a mean recovery of 9h 46m. If you depend on Noterro in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.