Planning Center Outage History

Started Oct 20, 2025, 06:58 AM UTC· resolved Oct 21, 2025, 05:40 AM UTC

1. investigating Oct 20, 2025, 06:58 AM UTC

   We are currently investigating a major outage with a service provider.

2. investigating Oct 20, 2025, 07:45 AM UTC

   We are continuing to monitor the status of our upstream provider (https://health.aws.amazon.com/health/status). This outage is unrelated to the open incident related to inadvertent profile changes.

3. monitoring Oct 20, 2025, 09:46 AM UTC

   Planning Center is recovering, and we are currently monitoring the situation.

4. monitoring Oct 20, 2025, 12:07 PM UTC

   Some background operations are experiencing occasional brief delays due to residual impact from the earlier outage. We are continuing to monitoring these and respond accordingly.

5. monitoring Oct 20, 2025, 02:17 PM UTC

   Background tasks continue to be delayed. This may impact features like sending messages and automations. Dashboards in Home are also not currently displaying. We are working to stabilize our platform and restore all access as quickly as possible.

6. identified Oct 20, 2025, 03:28 PM UTC

   We are suffering from failed EC2 launches, causing progressively worse latency. Our upstream provider, AWS, is still investigating the connectivity issues. We are monitoring closely and responding accordingly.

7. identified Oct 20, 2025, 04:16 PM UTC

   The root cause was identified and AWS is working to stabilize and recover. When everything is back up, we will re-run critical recurring tasks that were impacted, such as scheduled recurring donations, scheduled list refreshes, scheduled Services emails, Check-ins create event periods, etc.

8. monitoring Oct 20, 2025, 06:55 PM UTC

   AWS mitigation efforts are in progress. We are seeing signs of recovery and continue to monitor the situation.

9. monitoring Oct 20, 2025, 09:10 PM UTC

   We are making steady progress toward full recovery and continue to work through our backlog.

10. monitoring Oct 21, 2025, 01:41 AM UTC

    AWS issues have been fully resolved. While they continue working through their backlog, Planning Center is operating normally and we are monitoring closely. Earlier, the outage slowed all products and caused some scheduled tasks to fail, but we are re-running everything affected—including recurring donations, People list refreshes and automations, Services emails, Check-Ins “create event periods” jobs, Groups attendance reminders and emails, and all other scheduled tasks.

11. monitoring Oct 21, 2025, 04:19 AM UTC

    All the delayed tasks have been rescheduled and will be completed in the next few hours. We're continuing to monitor for any further issues.

12. resolved Oct 21, 2025, 05:40 AM UTC

    All delayed tasks have completed. Planning Center is operating normally and this incident is resolved.

Read the full incident report →

Started Oct 19, 2025, 03:15 PM UTC· resolved Oct 22, 2025, 08:44 PM UTC

1. investigating Oct 19, 2025, 03:15 PM UTC

   We are currently investigating reports of unintended profile updates and permission changes occurring during page refreshes.

2. investigating Oct 19, 2025, 04:12 PM UTC

   Our team is still actively investigating reports of unintended profile updates and permission updates. We’ll share updates as soon as we know more.

3. monitoring Oct 19, 2025, 04:58 PM UTC

   We've implemented a fix to prevent further profile changes. We are now working to understand our options for affected profiles and will update as soon as we have clarity.

4. monitoring Oct 19, 2025, 06:07 PM UTC

   We're continuing to investigate to determine our options. We'll share an update as soon as we have more information.

5. monitoring Oct 19, 2025, 07:43 PM UTC

   We've identified the users who were impacted. We're now evaluating what changes we can revert and will update as soon as we know more.

6. monitoring Oct 20, 2025, 01:35 AM UTC

   We're still actively working on this. Thank you for your patience.

7. monitoring Oct 20, 2025, 07:51 AM UTC

   Recovery efforts have been paused due to the major outage in our upstream provider. We will continue work in the morning. If any profiles in your account were affected you will receive an email with specifics later this week.

8. monitoring Oct 21, 2025, 01:20 AM UTC

   Recovery work has resumed and is progressing well. We've restored core profile data and are validating that restoration, while also working to restore associated data across all applications.

9. monitoring Oct 21, 2025, 04:54 AM UTC

   We've notified affected organization administrators with details about the issue, impact, and our estimated completion timeframe. The team is continuing to make progress restoring permissions and data across our products.

10. monitoring Oct 21, 2025, 06:51 PM UTC

    Our team is continuing to make progress restoring and validating affected data and permissions. If you are still experiencing issues with logging in, in some cases clearing your browser's cache has shown to be effective.

11. monitoring Oct 21, 2025, 06:55 PM UTC

    We've completed our data restore work in Home, Services, Chat, Calendar, Registrations, Giving, Publishing, and Check-Ins. We're getting closer to restoring the secondary permission for People and Groups.

12. monitoring Oct 21, 2025, 10:19 PM UTC

    We've completed the Groups restoration and are continuing to work towards fully restoring People collaborator permissions for things like workfows, lists, etc.

13. monitoring Oct 22, 2025, 12:57 AM UTC

    The large majority of restore work has been completed. The team continues to clean up some final pieces. We will post another update in the morning.

14. resolved Oct 22, 2025, 08:44 PM UTC

    We've resolved the incident and restored all data that was inadvertently modified. This bug impacted profile information accessed in People either by an administrator or programmatically via a third-party integration between Friday, October 17, at 12:34 PM PT, and Sunday, October 19, at 9:49 AM PT. This affected various profile fields, including Permissions, Membership Type, Birthday, Anniversary, Campus, and Photos on a person’s profile. This did not include Custom Fields or Contact Information. What this means: While we restored as much data as possible, any manual changes made between Friday afternoon and Sunday morning were unfortunately lost. There is one important exception: if an administrator intentionally removed someone's overall account permissions during this period, those removals were preserved. No one has permissions higher than what they should have. What you can do: Organization Administrators can visit https://accounts.planningcenteronline.com/affected_profiles to see profiles in your account that may have been affected by this issue. We recommend reviewing these profiles to ensure everything is as it should be. Due to this bug, you may also notice some inconsistencies in the activity logs of these profiles. Additional details: * Approximately 3% of churches were impacted by this incident, affecting roughly 0.01% of all profiles * The median number of affected profiles per church is 1, though a very small number of churches will see significantly more profiles affected, in some cases hundreds * This issue was unrelated to but complicated by the recent AWS outage * We have confirmed that no unauthorized access to data occurred during this incident Our teams are conducting a thorough post-incident analysis to identify improvements to prevent similar issues and enhance our response processes. We sincerely apologize for the disruption and appreciate your patience as we worked to resolve this issue. An email with similar information to this update has been sent to Organization Administrators of affected accounts.

Read the full incident report →

Started Sep 10, 2025, 06:21 PM UTC· resolved Sep 10, 2025, 10:01 PM UTC

1. investigating Sep 10, 2025, 06:21 PM UTC

   Users may experience errors when attempting to add a new bank account on Church Center app. This issue is only affecting Android devices. We are currently investigating the issue.

2. investigating Sep 10, 2025, 06:23 PM UTC

   We are continuing to investigate this issue.

3. identified Sep 10, 2025, 06:41 PM UTC

   We've identified this as an issue related to a Stripe upgrade, and a fix is in the works.

4. resolved Sep 10, 2025, 10:01 PM UTC

   Adding a bank account works again in the new release of the Android app, so affected donors can now update to fix the issue.

Read the full incident report →

Started Sep 03, 2025, 04:15 PM UTC· resolved Sep 04, 2025, 12:14 AM UTC

1. investigating Sep 03, 2025, 04:15 PM UTC

   Our team is currently investigating reports of the mobile app crashing on launch for some iOS devices.

2. investigating Sep 03, 2025, 05:25 PM UTC

   Our team is still actively investigating reports that the mobile app is crashing on launch for some iOS devices. We’ll share updates as soon as we know more.

3. identified Sep 03, 2025, 06:38 PM UTC

   The issue has been identified and our team is working on a fix.

4. identified Sep 03, 2025, 07:23 PM UTC

   Our team has identified the issue and is implementing a fix for internal testing to ensure the fix resolves the issue.

5. identified Sep 03, 2025, 09:00 PM UTC

   After successfully verifying the fix in beta, we’ve submitted the update to the App Store and are now awaiting review.

6. resolved Sep 04, 2025, 12:14 AM UTC

   This issue has been resolved. Affected users can update to version 6.4.3 in the App Store.

Read the full incident report →

Started Aug 28, 2025, 01:00 AM UTC· resolved Aug 28, 2025, 01:00 AM UTC

1. resolved Aug 28, 2025, 03:04 AM UTC

   An issue was discovered where newly created profiles were unable to register for events in Registrations. The problem was identified, and a fix has been successfully deployed.

Read the full incident report →

Started Jul 31, 2025, 09:40 PM UTC· resolved Jul 31, 2025, 11:58 PM UTC

1. investigating Jul 31, 2025, 09:40 PM UTC

   We are currently investigating this issue.

2. identified Jul 31, 2025, 10:10 PM UTC

   Checkr's ability to request background checks is currently down, they're investigating the cause.

3. resolved Jul 31, 2025, 11:58 PM UTC

   Checkr implemented a fix, and admins can request Checkr background checks again.

Read the full incident report →

Started Jul 21, 2025, 11:47 PM UTC· resolved Jul 21, 2025, 11:47 PM UTC

1. resolved Jul 21, 2025, 11:47 PM UTC

   There was a brief outage where uploads were failing across the Planning Center suite. It lasted from 3:03pm PT until 4:36pm PT. It has since been resolved.

Read the full incident report →

Started Jul 21, 2025, 10:51 PM UTC· resolved Jul 22, 2025, 02:27 AM UTC

1. investigating Jul 21, 2025, 10:51 PM UTC

   Some donors received multiple receipts for donations entered through Giving batch entries. This issue began today around 12:50pm PST. This issue only affects batch donations. Donations made directly via the online donation form were not impacted. Multiple receipts have been sent for approximately 200 donations across a limited number of organizations. There may have also been multiple webhooks sent via any third party integrations telling them that a donation succeeded. A temporary fix is about to be in place. We are continuing to assess the full scope.

2. investigating Jul 22, 2025, 12:00 AM UTC

   A temporary fix was implemented at 4pm PT. We’ve confirmed that webhooks for third-party integrations remain unaffected. We are still working on tracking down the point of failure. Currently, batches are taking longer than usual to commit, but duplicate receipts will no longer be sent. You can continue working as usual—just be aware of the processing delay.

3. identified Jul 22, 2025, 01:08 AM UTC

   The root cause has been identified and a permanent fix is in the works.

4. resolved Jul 22, 2025, 02:27 AM UTC

   The issue has been fully resolved and all cleanup is complete. Any batches that were previously stuck have been marked as committed, and no additional batches should experience this issue going forward.

Read the full incident report →

Started Jul 07, 2025, 05:19 PM UTC· resolved Jul 08, 2025, 04:28 PM UTC

1. investigating Jul 07, 2025, 05:19 PM UTC

   We're seeing intermittent delays in People and API.

2. investigating Jul 07, 2025, 05:22 PM UTC

   We are continuing to investigate this issue.

3. monitoring Jul 07, 2025, 05:38 PM UTC

   Performance is back to normal. We've identified the cause and are working toward fixes to prevent this from happening again.

4. resolved Jul 08, 2025, 04:28 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 06, 2025, 05:21 PM UTC· resolved Jun 07, 2025, 02:09 AM UTC

1. identified Jun 06, 2025, 05:21 PM UTC

   Our team is aware of and has identified the cause for Music Stand crashing on older devices.

2. identified Jun 06, 2025, 05:23 PM UTC

   Our team has implemented a solution and are testing an internal build to verify the fix.

3. monitoring Jun 06, 2025, 06:08 PM UTC

   We’ve completed internal testing and submitted the fix for app launch crashes on older devices to the App Store for review. We’ll update this page as soon as the update is live.

4. monitoring Jun 06, 2025, 08:12 PM UTC

   Our team is continuing to work with the App Store review team to get this new version out into the app store. We'll provide another update soon.

5. monitoring Jun 07, 2025, 12:32 AM UTC

   Update: Our team is in ongoing communication with the App Store review team and we're doing everything we can to get the fix released as soon as possible.

6. resolved Jun 07, 2025, 02:09 AM UTC

   Resolved: The issue causing Music Stand to crash on older devices has been resolved. A new version update containing the fix is now available in the App Store in version 4.6.2.

Read the full incident report →

Started Jun 05, 2025, 02:21 PM UTC· resolved Jun 05, 2025, 06:24 PM UTC

1. investigating Jun 05, 2025, 02:21 PM UTC

   Our team is aware of and looking into an issue on Music Stand iOS, where the Audio Output is not returning any sound in the Media Player.

2. investigating Jun 05, 2025, 02:57 PM UTC

   Our team is still investigating the root cause of the missing audio output in the Music Stand iOS Media Player. We're exploring several possibilities and will post another update shortly.

3. identified Jun 05, 2025, 03:22 PM UTC

   We've pinpointed the cause of the audio issue and are coordinating next steps to address it. We'll keep you posted on our progress.

4. identified Jun 05, 2025, 04:01 PM UTC

   Good news! We’re testing a fix in a new internal build of Music Stand iOS. If all goes well, we’ll move toward releasing the update soon in a new version update.

5. monitoring Jun 05, 2025, 05:07 PM UTC

   Internal testing is complete and the fix for the Media Player audio issue has been submitted to the App Store for review. We’ll update this page once the update is live.

6. resolved Jun 05, 2025, 06:24 PM UTC

   The fix for the audio issue in the Music Stand iOS Media Player has been approved by Apple and is now available in version 4.6.1. We recommend updating to the latest version to restore audio functionality.

Read the full incident report →

Started May 21, 2025, 02:42 PM UTC· resolved May 21, 2025, 05:38 PM UTC

1. identified May 21, 2025, 02:42 PM UTC

   The issue has been identified and a fix is being implemented.

2. identified May 21, 2025, 02:59 PM UTC

   We’ve found the source of the issue and are currently testing a fix internally to ensure it resolves the problem.

3. identified May 21, 2025, 03:27 PM UTC

   We're continuing to test our internal build to make sure the bug is completely fixed. Early results look good, and we’re hopeful to wrap up testing and release an update to the App Store soon.

4. identified May 21, 2025, 04:43 PM UTC

   Our team has implemented a fix and submitted a new version of the app to the App Store for review. We'll keep you informed as soon as the update is approved and available for download.

5. resolved May 21, 2025, 05:38 PM UTC

   A fix has been implemented, and version 6.3.2 has been approved by the App Store. It will be available for download shortly.

Read the full incident report →

Started Apr 13, 2025, 11:12 AM UTC· resolved Apr 13, 2025, 01:24 PM UTC

1. investigating Apr 13, 2025, 11:12 AM UTC

   We are investigating errors when trying to submit donations or add new payment methods in Giving and Registrations

2. identified Apr 13, 2025, 11:18 AM UTC

   We have identified the issue and are working on a fix.

3. monitoring Apr 13, 2025, 11:49 AM UTC

   A fix has been implemented and we are monitoring the results.

4. identified Apr 13, 2025, 12:31 PM UTC

   Donations and payments are being processed successfully now in Giving and Registrations. We are currently working on an issue related to connecting new Stripe accounts in Accounts.

5. monitoring Apr 13, 2025, 12:49 PM UTC

   A fix has been implemented and we are monitoring the results.

6. resolved Apr 13, 2025, 01:24 PM UTC

   This incident has been resolved.

7. postmortem May 15, 2025, 11:07 PM UTC

   Note: Usually our incident postmortem report comes out within days of the incident. However, since this issue was the result of an error at Stripe, we wanted to wait for their report before posting ours here. With that report in hand, we can now include their internal changes that will prevent this kind of issue going forward. ## Incident root cause: Accidental disconnection from Stripe On April 13, a mistake made by our payment processor, Stripe, resulted in a critical API key being deleted. This caused a temporary disruption across several of our products, including Giving and Registrations. During this outage, payments made on Church Center \(web or mobile app\) showed an error for one-off donations and payments. Recurring donations \(which are programmatically triggered\) also hit the same error, but they were quickly and successfully reprocessed once the new key was in place. ## Customer impact: Disconnection emails caused confusion While the core issue was resolved quickly in the early morning hours, the automated email that followed the initial disconnection caused unnecessary confusion. It implied that churches had disconnected their own Stripe accounts, which wasn’t the case, and its urgent tone only added to the misunderstanding. To make matters worse, many customers had no way of knowing the issue had already been fixed unless they were familiar with our status page and knew to check there, which left some unsure whether their donation system was still down. ## What we learned: Faster communication is better One of the biggest takeaways from this incident was the importance of fast, plainspoken communication. Usually, churches want to know the details about what error messages were shown, exactly what parts of the system were impacted, and most of all what happened with the recurring donations. We wanted to speak to all of that accurately and confidently, but that cost us time. As soon as the system was back online we should have sent a quick communication just to say “Ignore that alert email, everything is fine. More details will follow” and then sent a followup email later. ## What Stripe learned: Stronger protection measures for important keys Over at Stripe, on April 13th, a front line triage agent was responding to a fraud incident and deleted the wrong keys. As a result of this incident, they’ve removed the ability for the triage agents to delete a platform’s API key directly. To manage a platform’s API key \(like Planning Center\) there’s now a different internal escalation path that requires signoff at multiple levels within Stripe. ## What we’re changing going forward We’re taking several steps to strengthen both our technical systems and our communication process, including: * Updating our on-call protocols to ensure that the right people on our side are collaborating more quickly * Biasing for speed of communication instead of just accuracy—starting with brief, reassuring updates, followed by detailed explanations. * Making the status page more visible throughout the helpdesk, the products themselves, and in email communications. We know your church relies on Planning Center to operate smoothly, especially for things like donations and event registrations. We’re committed to learning from this and making our systems—and our communication—stronger moving forward. Thank you for your continued partnership and grace.

Read the full incident report →

Started Apr 09, 2025, 08:23 PM UTC· resolved Apr 09, 2025, 09:39 PM UTC

1. investigating Apr 09, 2025, 08:23 PM UTC

   Several Services Widgets on the Home dashboard are showing an error state instead of data. Our team is investigating.

2. identified Apr 09, 2025, 08:24 PM UTC

   The issue causing an error state for Services Widgets on the Home Dashboard has been identified and our team is working on implementing a fix.

3. monitoring Apr 09, 2025, 08:55 PM UTC

   A fix has been implemented and Services widgets on the Home Dashboard should now load data successfully.

4. resolved Apr 09, 2025, 09:39 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 03, 2025, 10:42 PM UTC· resolved Apr 04, 2025, 03:59 AM UTC

1. investigating Apr 03, 2025, 10:42 PM UTC

   Some customers are unable to access external link attachments on Services Mobile iOS version 6.2. Our team is looking into this issue.

2. identified Apr 03, 2025, 11:52 PM UTC

   The issue affecting external link attachments from loading has been identified and the team is working on a fix.

3. identified Apr 04, 2025, 01:43 AM UTC

   Update: Our team is continuing to work on a fix for this issue and plan to submit a new build to the app store for review once we have confirmed the fix.

4. identified Apr 04, 2025, 02:35 AM UTC

   Update: Our team has identified and submitted a fix to the App Store, which is now in Review.

5. resolved Apr 04, 2025, 03:59 AM UTC

   A fix has been shipped in the form of a new Services iOS build, available in the App Store, (version 6.2.1)

Read the full incident report →

Started Mar 13, 2025, 09:32 PM UTC· resolved Mar 14, 2025, 12:00 AM UTC

1. investigating Mar 13, 2025, 09:32 PM UTC

   Some customers are unable to access Giving in Church Center or Planning Center (admin). Donors are unable to give to those impacted. We are working to figure out the cause as quickly as possible. Not everyone is impacted.

2. identified Mar 13, 2025, 09:39 PM UTC

   The issue has been identified and a fix is being implemented.

3. identified Mar 13, 2025, 10:03 PM UTC

   The issue has been resolved for almost half of the organizations impacted, and we are working on restoring access for the remaining.

4. monitoring Mar 13, 2025, 11:05 PM UTC

   A fix has been implemented. Access should be restored for everyone impacted. We are validating that everything is working as expected.

5. resolved Mar 14, 2025, 12:00 AM UTC

   We've restored access to all Giving customers. This incident has been resolved.

Read the full incident report →

Started Mar 06, 2025, 11:31 PM UTC· resolved Mar 06, 2025, 11:47 PM UTC

1. investigating Mar 06, 2025, 11:31 PM UTC

   We are currently investigating this issue.

2. identified Mar 06, 2025, 11:42 PM UTC

   The issue has been identified and a fix is being implemented.

3. resolved Mar 06, 2025, 11:47 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 02, 2025, 03:23 PM UTC· resolved Mar 02, 2025, 05:25 PM UTC

1. investigating Mar 02, 2025, 03:23 PM UTC

   We are currently investigating an issue with Services Live clocks freezing on multiple devices after advancing Plan items.

2. investigating Mar 02, 2025, 04:10 PM UTC

   We are continuing to investigate issues with the Services LIVE clocks freezing when advancing Plan Items.

3. monitoring Mar 02, 2025, 04:58 PM UTC

   A fix has been implemented and we are monitoring the results. If you're still noticing this issue, please try refreshing your device's browser or force closing the Services mobile app.

4. resolved Mar 02, 2025, 05:25 PM UTC

   This incident has been resolved and customers are reporting Services Live is working as expected. If you're still noticing this issue, please try refreshing your device's browser or force closing the Services mobile app.

Read the full incident report →

Started Feb 27, 2025, 01:59 PM UTC· resolved Feb 27, 2025, 02:45 PM UTC

1. investigating Feb 27, 2025, 01:59 PM UTC

   We're investigating the source of a higher than normal amount of errors in one or more of our apps.

2. investigating Feb 27, 2025, 02:13 PM UTC

   We have identified the issue and are working on implementing a fix.

3. monitoring Feb 27, 2025, 02:24 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Feb 27, 2025, 02:45 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 24, 2025, 06:33 PM UTC· resolved Feb 24, 2025, 08:21 PM UTC

1. investigating Feb 24, 2025, 06:33 PM UTC

   We are seeing degraded performance on the Groups website.

2. resolved Feb 24, 2025, 08:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 16, 2025, 05:34 PM UTC· resolved Feb 16, 2025, 06:18 PM UTC

1. investigating Feb 16, 2025, 05:34 PM UTC

   We are currently investigating this issue.

2. resolved Feb 16, 2025, 06:18 PM UTC

   A fix has been implemented and Services Live is back to full functionality, although you will need to refresh the page if you're seeing a 404 error. We’ll continue to monitor this fix to make sure all is well.

Read the full incident report →

Started Feb 12, 2025, 11:17 PM UTC· resolved Feb 13, 2025, 12:57 AM UTC

1. identified Feb 12, 2025, 11:17 PM UTC

   We are aware of an issue on the Church Center iOS and Android apps that users are unable to add new bank accounts when giving donations. We are working on a fix.

2. resolved Feb 13, 2025, 12:57 AM UTC

   A fix for this has been released for iOS and Android in version 2025.2.12. Please download that latest version to get the fix.

Read the full incident report →

Started Jan 15, 2025, 06:22 PM UTC· resolved Jan 15, 2025, 07:21 PM UTC

1. investigating Jan 15, 2025, 06:22 PM UTC

   We are currently investigating this issue.

2. identified Jan 15, 2025, 06:59 PM UTC

   The issue has been identified and a fix is being implemented.

3. resolved Jan 15, 2025, 07:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 14, 2025, 05:49 PM UTC· resolved Jan 14, 2025, 09:04 PM UTC

1. investigating Jan 14, 2025, 05:49 PM UTC

   We are seeing slowness and the potential for errors on Church Center today due to an unexpected spike in traffic. We are working on blocking this traffic to improve performance.

2. resolved Jan 14, 2025, 09:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 13, 2025, 10:52 PM UTC· resolved Jan 14, 2025, 01:30 AM UTC

1. identified Jan 13, 2025, 10:52 PM UTC

   Twilio's outage today ( https://status.twilio.com/incidents/w7755w4g4zq1 ) is causing delays with text messages, making it hard for some people to log into Church Center and Planning Center. We're monitoring and trying to do what we can to help. Sorry about this!

2. monitoring Jan 14, 2025, 12:18 AM UTC

   Twilio reports that SMS messages are being delivered quickly again. We're monitoring to ensure this continues. So far, all looks well.

3. resolved Jan 14, 2025, 01:30 AM UTC

   Text message delays are indeed resolved and login codes are being delivered quickly again. Internally, we're talking about the future and how to make Planning Center more resilient against network outages like this. We're sorry about today's SMS delays!

Read the full incident report →