BreezeChMS logo

Is BreezeChMS Down?

SaaSLive status, outages, and incident history

No. BreezeChMS is up right now.

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

OperationalChecked 4m agoLive · every 60s

Know the moment BreezeChMS breaks

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

Status report

BreezeChMS Status Summary

As of 22:59 UTC on 9 November 2026, BreezeChMS is operational. PulsAPI checked BreezeChMS's official status page and found 8 of 8 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for BreezeChMS, counting degraded performance as up.

Cite as: PulsAPI, “BreezeChMS status”, checked 9 November 2026, 22:59 UTC. https://www.pulsapi.com/services/breezechms

BreezeChMS Component Status

The main BreezeChMS systems on this page. All 8 are operational right now.

8operational
Database
Operational
Email Service
Operational
Online Giving » Transaction Processing
Operational

5 more components tracked

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

Also tracking Site, SMS / Texting » Shortcode Texting, SMS / Texting » Texting Service, Worship Tools » Song Select, Worship Tools » Worship App.

See all of them free

Component statuses may change independently during partial outages.

Recent BreezeChMS Outages & Incidents

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

No recent incidents reported by the vendor.

BreezeChMS Uptime History

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

Uptime history91 days observed
Aug 11100.00% average · 40 days with incidentsNov 9

Going further back: BreezeChMS uptime by month and every recorded BreezeChMS outage.

Live BreezeChMS Outage Reports

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

Something wrong with BreezeChMS on your end?

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

About BreezeChMS

BreezeChMS exposes 11 monitored components on its status page at status.breezechms.com — Site, Transaction Processing and Song Select among them. Follow BreezeChMS downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

Over the past 30 days, PulsAPI has measured BreezeChMS uptime at 100.00%. Response times, incident history, and SLA tracking for BreezeChMS are available on the PulsAPI dashboard.

BreezeChMS Status FAQ

Is BreezeChMS down right now?

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

How do I check BreezeChMS uptime history?

PulsAPI tracks BreezeChMS uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever BreezeChMS changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect BreezeChMS outages?

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

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

Can I get alerts when BreezeChMS goes down?

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

Is there a free way to monitor BreezeChMS?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so BreezeChMS 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 BreezeChMS with the rest of your stack

2660+ 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