История сбоев Breeze Church Management

1. 6 августа 2026 г. в 15:35 UTCidentified

   We are currently investigating and have identified an issue with our processor where individual payments that make up August 6th's transfer is not loading as expected. This should not be impacting transfers to your bank account, only the reporting of payments that make up that transfer.

2. 6 августа 2026 г. в 17:11 UTCresolved

   We can confirm that payments are now loading again as expected for August 6th transfers!

1. 12 июля 2026 г. в 01:29 UTCinvestigating

   Наша команда расследует проблему, затрагивающую приложение Breeze Check In, где оно не показывает принтеры Brother, как ожидалось. Мы рассматриваем это как очень неотложную проблему и приложим все усилия, чтобы это было решено до воскресных служб. В настоящее время мы рекомендуем отключить автоматические обновления приложений в настройках App Store. Мы поделимся обновлениями здесь, как у нас есть.

2. 12 июля 2026 г. в 03:08 UTCidentified

   Мы определили проблему, вызывающую проблему, и работаем над тем, чтобы исправить это как можно быстрее. Скоро мы поделимся еще одним обновлением.

3. 12 июля 2026 г. в 04:29 UTCresolved

   Мы вернулись! Проверка Breeze Войдет и побежит. Спасибо, что согласились с нами.

Автоматический перевод официального обновления инцидента.

1. 19 мая 2026 г. в 15:22 UTCidentified

   We are currently investigating and have identified an issue where customers using MinistrySafe's background checks are finding slow loading people pages and background check modals.

2. 19 мая 2026 г. в 16:39 UTCresolved

   The speed issue when loading background check and training modals has been resolved!

1. 29 апреля 2026 г. в 16:32 UTCinvestigating

   We are aware of an issue where some customers are experiencing errors when attempting to access their Breeze account. Our Engineering team is investigating and will we provide an update here soon.

2. 29 апреля 2026 г. в 17:47 UTCidentified

   Our team has identified the source of the issue and is working on the fix currently.

3. 29 апреля 2026 г. в 19:07 UTCresolved

   This issue has been resolved and access restored to affected customers.

1. 10 марта 2026 г. в 18:06 UTCinvestigating

   We're aware of an issue that is affecting the delivery of texts through Breeze. Our Engineering teams are investigating.

2. 10 марта 2026 г. в 18:59 UTCmonitoring

   Our team has resolved the issue affecting texting and we can confirm that texts are sending. We are now working on updating the texts that were supposed to send during this incident to force them to send.

3. 10 марта 2026 г. в 19:07 UTCmonitoring

   All affected texts are now updated to send, however we do expect it to take a bit for them to all process.

4. 10 марта 2026 г. в 20:22 UTCresolved

   We're happy to report that all pending texts have sent as expected. Thank you for your patience!

1. 24 февраля 2026 г. в 22:33 UTCinvestigating

   We're investigating an issue where URLs are being redirected to breezechms.com incorrectly.

2. 24 февраля 2026 г. в 23:50 UTCresolved

   Resolved issue and all systems back to normal.

1. 25 января 2026 г. в 05:13 UTCmonitoring

   We are currently experiencing delays with SMS delivery and are working closely with our providers to resolve the issue as quickly as possible.

2. 25 января 2026 г. в 06:02 UTCmonitoring

   SMS delivery is improving as we work through the remaining queue, and we expect service to return to normal soon.

3. 25 января 2026 г. в 12:47 UTCmonitoring

   SMS deliveries are back to normal, though our team remains on standby monitoring performance to ensure everything stays on track.

4. 25 января 2026 г. в 16:55 UTCmonitoring

   Our Engineering teams are continuing to monitor texting volume through today. At times we are seeing delays in sending of around 20 minutes, however all texts are being sent. We will continue to pay close attention to our queues and will share more updates here as needed.

5. 6 февраля 2026 г. в 12:08 UTCresolved

   This incident has been resolved.

1. 12 января 2026 г. в 14:02 UTCinvestigating

   We are currently investigating an issue where Breeze Giving customers were charged a stripe_fee recently. Follow along for updates here as we work towards a resolution.

2. 12 января 2026 г. в 17:27 UTCidentified

   The issue has been identified and we are working with our processor now to correct any charges.

3. 13 января 2026 г. в 13:10 UTCmonitoring

   A fix has been implemented and incorrect fees should no longer be charging. If you were charged a fee, you will automatically be refunded in the next 4-5 business days. We will continue to monitor the results as the week goes on.

4. 19 января 2026 г. в 19:40 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 19 января 2026 г. в 19:41 UTCresolved

   This incident has been resolved.

1. 12 ноября 2025 г. в 19:01 UTCinvestigating

   Our teams are aware of an issue affecting the exporting Directory and Tax Statements. We will provide updates shortly.

2. 12 ноября 2025 г. в 19:33 UTCinvestigating

   Our Engineering teams have pinpointed the cause of this issue and are working on a fix.

3. 12 ноября 2025 г. в 19:44 UTCresolved

   Our Engineering teams have resolved the issues affecting exporting and things are working as expected!

1. 30 октября 2025 г. в 19:14 UTCinvestigating

   We've identified that emails scheduled outside of People Beta (Tags, Legacy People, Giving Reports, etc) are not scheduling or sending as expected. Our team is engaged and working on the issue. Emails scheduled through People Beta through the new email modals (Basic / Design) are working as expected, and emails sent now through legacy modals are also working as expected. Reports of similar issues regarding texting are being further investigated

2. 30 октября 2025 г. в 20:02 UTCmonitoring

   We have implemented a fix for the scheduling of emails outside of People Beta (Tags, Legacy People, Giving Reports, etc) and can confirm it's working as expected now.

3. 30 октября 2025 г. в 21:09 UTCresolved

   We're happy to say that this is confirmed to be resolved and there are no lingering issues with scheduling emails.

1. 20 октября 2025 г. в 15:16 UTCinvestigating

   Due to an issue affecting a key system provider, we are aware that some customers are experiencing errors with some functions within Breeze. Customers may experience delayed text or email sends, or other errors across the product. While this is completely external to our products, our Engineering teams are monitoring very closely to mitigate any affects for our customers.

2. 20 октября 2025 г. в 18:57 UTCmonitoring

   Our Engineering teams are continuing to monitor our products and ensure reliability. Our provider is seeing improvement, however they are still reporting issues.

3. 20 октября 2025 г. в 22:31 UTCresolved

   As our provider has recovered from their issue our teams are confirming that things are working as expected. There will be some tasks that could be delayed for some customers (potentially items like automated emails, texts, etc) however these should be sending through as expected and no action is needed.

1. 25 сентября 2025 г. в 15:47 UTCinvestigating

   Our teams are aware of an issue affecting the exporting from People. We will provide updates shortly.

2. 25 сентября 2025 г. в 16:53 UTCresolved

   Our Engineering teams have resolved the issues affecting exporting and things are working as expected!

1. 23 сентября 2025 г. в 17:47 UTCinvestigating

   We're investigating reports of issues accessing some Breeze pages or performing actions. Our Engineering teams are working on this right now.

2. 23 сентября 2025 г. в 18:18 UTCmonitoring

   Our team has resolved the issues that were causing this and we're monitoring to ensure all functions are working as expected

3. 23 сентября 2025 г. в 18:43 UTCresolved

   We're happy to report that things have returned to normal! Please reach out to our teams if you experience any issues or concerns.

1. 5 сентября 2025 г. в 16:18 UTCmonitoring

   We've created a new incident here on our Status page as we've seen customers continue to see these charges appear, however there is no action needed from customers. --- We're aware that some of our customers using Breeze Giving are seeing a recent "stripe_fee" on their transaction reports. This is an incorrect fee being assessed and we're working with our Giving Processor (Stripe) to ensure this is resolved, and these fees refunded as quickly as possible. Those experiencing this will NOT need to contact our team for verification as we're able to see impact and resolve.

2. 19 сентября 2025 г. в 17:42 UTCresolved

   This incident has been resolved and refunds for incorrect fees have been processed for affected organizations.

1. 4 сентября 2025 г. в 12:52 UTCinvestigating

   We're aware of an issue affecting the Breeze Admin App where it is showing "Something went wrong" for all users.

2. 4 сентября 2025 г. в 15:51 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 сентября 2025 г. в 15:53 UTCidentified

   We’ve identified the issue with the Breeze Admin App and are working on a fix. We’ll share another update shortly.

4. 4 сентября 2025 г. в 18:13 UTCidentified

   We’ve identified the fix for the Breeze Admin App and are waiting on approval from the app store. We’ll share another update shortly.

5. 5 сентября 2025 г. в 16:14 UTCresolved

   Our team has been able to resolve the issue with the Breeze app. This did require an update through the App Store so if you are experiencing any issues, please be sure to update to the latest version.

1. 2 сентября 2025 г. в 16:19 UTCidentified

   We're aware that some of our customers using Breeze Giving are seeing a recent "stripe_fee" on their transaction reports. This is an incorrect fee being assessed and we're working with our Giving Processor (Stripe) to ensure this is resolved, and these fees refunded as quickly as possible. Those experiencing this will NOT need to contact our team for verification as we're able to see impact and resolve.

2. 4 сентября 2025 г. в 00:33 UTCresolved

   We've confirmed that the charges are not continuing and are working with our partner to ensure that all are being refunded automatically. We're marking this as resolved and will work directly with any affected customers to ensure this is handled.

1. 20 августа 2025 г. в 15:05 UTCinvestigating

   Our teams are aware of an issue affecting the loading of the Breeze Admin App. This appears to be an issue with an upstream provider, however we are working to ensure this is resolved as quickly as possible.

2. 21 августа 2025 г. в 00:24 UTCinvestigating

   We've confirmed there is an issue with an upstream provider that is causing issues in the Breeze Admin App. We encourage you to use Breeze directly from your device's browser as we continue work to fully resolve this issue.

3. 21 августа 2025 г. в 18:21 UTCmonitoring

   A full resolution is still underway. This issue originated with an upstream provider and while we are currently awaiting approval from the Google Play Store, we are back up and running in the Apple App store. You may experience slightly difference experiences in this version of the app compared to the previous version. We’re monitoring for these differences. We’ll share another update shortly.

4. 23 августа 2025 г. в 11:32 UTCmonitoring

   We have released a new version of the Breeze Admin App in both the Apple App and Google Play stores which resolves this issue for both iOS and Android users. If you are experiencing this please visit the App Store and check for an update. If you are not able to do the update, deleting the app and reinstalling it should also give you the latest version. We will continue to keep this incident updated as we verify full resolution for all users.

5. 25 августа 2025 г. в 13:46 UTCresolved

   We’re back! Both Breeze admin apps should be up and running for both IOS and Android. Thanks for bearing with us.

1. 1 августа 2025 г. в 17:54 UTCinvestigating

   We’re noticing slower delivery times with SMS/Texting for some users. We’re investigating the root problem right now. We’ll continue to share updates on our progress as we resolve this issue.

2. 1 августа 2025 г. в 19:10 UTCmonitoring

   SMS/Texting appears to be back up and running. We’re monitoring it closely to verify all issues are fully resolved. We’ll share another update shortly.

3. 1 августа 2025 г. в 21:02 UTCresolved

   We’re back! SMS/Texting should be up and running. Thanks for bearing with us.

1. 24 июля 2025 г. в 14:35 UTCinvestigating

   Our teams are aware of an issue where an error is being shown for some attempting to send texts. The root cause is related to numbers that are incorrectly formatted in the profiles. We're also investigating an issue where scheduling texts at a custom time is resulting in an immediate send. We'll provide updates through this page.

2. 24 июля 2025 г. в 15:45 UTCinvestigating

   Our Engineering teams are continuing to work to solve the issues regarding texts.

3. 24 июля 2025 г. в 16:57 UTCidentified

   Our teams have resolved the issue where an error is being shown for some attempting to send texts. The root cause was related to numbers that are incorrectly formatted in the profiles. We're are still investigating an issue where scheduling texts at a custom time is resulting in an immediate send. We'll continue to provide updates through this page.

4. 24 июля 2025 г. в 18:26 UTCresolved

   We’re back! Scheduled texts should be up and running as expected now. Thanks for bearing with us.

1. 17 июля 2025 г. в 20:46 UTCinvestigating

   Our teams are investigating reports of emails not sending through as expected. Initial indications are system generated emails are the most affected. We'll provide additional updates soon

2. 17 июля 2025 г. в 21:08 UTCidentified

   Our teams have identified the source of the issue and are working to resolve

3. 17 июля 2025 г. в 21:24 UTCidentified

   Our Engineering team is preparing to deploy a fix for this issue.

4. 17 июля 2025 г. в 21:39 UTCresolved

   This issue has been fully resolved for our teams and we are seeing these emails send through as expected.