Planning Center Status

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

Monitoring: 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.

Monitoring: 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.

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

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

Identified: 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.

Identified: 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.

Monitoring: 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.

Monitoring: 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.

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

Investigating: 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.

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

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

Monitoring: 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.

Monitoring: 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.

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

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

Identified: 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.

Identified: 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.

Monitoring: 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.

Monitoring: 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.

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

Investigating: 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.

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

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

Monitoring: 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.

Monitoring: 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.

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

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

Identified: 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.

Identified: 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.

Monitoring: 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.

Monitoring: 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.

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

Investigating: 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.

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

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

Monitoring: 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.

Monitoring: 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.

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

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

Identified: 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.

Identified: 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.

Monitoring: 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.

Monitoring: 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.

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

Investigating: 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.

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

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

Monitoring: 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.

Monitoring: 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.

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

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

Identified: 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.

Identified: 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.

Monitoring: 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.

Monitoring: 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.

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

Investigating: 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.

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

Resolved: This incident has been resolved.

Identified: We have a fix for this issue and have submitted a new version of the Church Center app that includes that fix. That version is currently being reviewed by the iOS app store and will be released as soon as it is approved.

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

Investigating: We are currently investigating this issue.

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

Monitoring: 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.

Monitoring: 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.

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

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

Identified: 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.

Identified: 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.

Monitoring: 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.

Monitoring: 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.

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

Investigating: 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.

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

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

Monitoring: 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.

Monitoring: 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.

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

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

Identified: 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.

Identified: 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.

Monitoring: 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.

Monitoring: 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.

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

Investigating: 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.

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

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

Monitoring: 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.

Monitoring: 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.

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

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

Identified: 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.

Identified: 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.

Monitoring: 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.

Monitoring: 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.

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

Investigating: 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.

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

Resolved: 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.

Monitoring: 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.

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

Monitoring: 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.

Monitoring: 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.

Monitoring: 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.

Monitoring: 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.

Monitoring: 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.

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

Monitoring: 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.

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

Monitoring: 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.

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

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

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

Monitoring: 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.

Monitoring: 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.

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

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

Identified: 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.

Identified: 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.

Monitoring: 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.

Monitoring: 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.

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

Investigating: 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.

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

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

Monitoring: 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.

Monitoring: 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.

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

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

Identified: 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.

Identified: 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.

Monitoring: 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.

Monitoring: 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.

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

Investigating: 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.

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

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

Monitoring: 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.

Monitoring: 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.

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

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

Identified: 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.

Identified: 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.

Monitoring: 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.

Monitoring: 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.

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

Investigating: 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.

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