BreezeChMS Outage History
9 incidents recorded over the last 365 days, 9 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 BreezeChMS Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 6, 2026 | Online Giving Report for Payment Breakdown on August 6th Transfers will not loadWe can confirm that payments are now loading again as expected for August 6th transfers! | 1h 35m | Resolved |
| Jul 12, 2026 | Issues with Breeze Check In AppWe’re back! Breeze Check In should be up and running. Thanks for bearing with us. | 3h 0m | Resolved |
| May 19, 2026 | Slow loading pages if you have background checks through MinistrySafe enabledThe speed issue when loading background check and training modals has been resolved! | 1h 16m | Resolved |
| Apr 29, 2026 | Issues accessing Breeze AccountsThis issue has been resolved and access restored to affected customers. | 2h 35m | Resolved |
| Mar 10, 2026 | Issues with Texts not sending through as expectedWe're happy to report that all pending texts have sent as expected. Thank you for your patience! | 2h 16m | Resolved |
| Feb 24, 2026 | URLs redirecting to breezechms.comResolved issue and all systems back to normal. | 1h 17m | Resolved |
| Jan 25, 2026 | SMS Messages are DelayedThis incident has been resolved. | 48h 46m | Resolved |
| Jan 12, 2026 | Breeze Giving customers were charged a stripe_feeThis incident has been resolved. | 173h 39m | Resolved |
| Nov 12, 2025 | Issues exporting dataOur Engineering teams have resolved the issues affecting exporting and things are working as expected! | 43 min | 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 BreezeChMS 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 BreezeChMS 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 BreezeChMS 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 BreezeChMS outage in this window ran 7d 5h, against a mean recovery of 1d 2h. If you depend on BreezeChMS 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.