Skip to main content
Planning Center logo

Is Planning Center Down?

No — Planning Center is up

Reachable from all 8 checked regions

Average response time: 204ms

Last checked · checks run every 6 hours

Official status page: https://status.planningcenter.com

Planning Center uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
238ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 14 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

14-day clean streak
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: no data
Sep 18: no data
Sep 19: no data
Sep 20: no data
Sep 21: no data
Sep 22: no data
Sep 23: no data
Sep 24: no data
Sep 25: no data
Sep 26: no data
Sep 27: no data
Sep 28: no data
Sep 29: no data
Sep 30: 100.00% uptime, 14 checks
Oct 1: 100.00% uptime, 29 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
221ms
DNS 159ms TCP 2ms TLS 19ms TTFB 208ms
arn
144ms
DNS 95ms TCP 1ms TLS 11ms TTFB 137ms
cdg
154ms
DNS 53ms TCP 10ms TLS 17ms TTFB 119ms
dfw
324ms
DNS 119ms TCP 25ms TLS 28ms TTFB 221ms
ewr
268ms
DNS 182ms TCP 1ms TLS 20ms TTFB 252ms
fra
87ms
DNS 32ms TCP 1ms TLS 7ms TTFB 81ms
gru
218ms
DNS 169ms TCP 2ms TLS 9ms TTFB 199ms
iad
218ms
DNS 157ms TCP 2ms TLS 9ms TTFB 200ms

What Planning Center does

Planning Center is church management software split into separate products: People for the membership database, Groups, Calendar, Registrations for event signups, Check-Ins for attendance and volunteers, Services for worship planning and volunteer scheduling, Giving for donations, and Publishing for pages and media. Church staff use the admin apps, while congregants mostly reach it through Church Center, a custom mobile app and website for each church.

What an outage looks like

Logins fail across products, the Church Center app will not open, or donors cannot give or add a bank account. Check-Ins stations may fail to load or show a QR code after losing their connection, and event signups may not complete. Text login codes arrive late when Twilio has problems, and MultiTracks charts and audio in Services fail when that integration is down.

What to do about it

Check status.planningcenter.com, which lists 14 products separately, including Login, Check-Ins, Giving and Church Center. If a station shows a QR code, re-pair it as an existing station, which keeps its settings, and press Start over on a station that looks out of date. After a major outage Planning Center ran the delayed recurring donations and scheduled emails itself, so do not redo them. Email support@planningcenter.com.

Is it down for everyone, or just you?

If this page says Planning Center is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Stripe
Stripe
Twilio
Twilio
AWS
AWS
Eventbrite
Eventbrite

Planning Center outage FAQ

Is Planning Center down for everyone or just me?
Check the product's own row, since most Planning Center incidents hit one product. The status page lists Accounts, API, Calendar, Chat, Check-Ins, Church Center, Giving, Groups, Home, Login, People, Publishing, Registrations and Services separately. If all are green, clear your browser cache and cookies, which Planning Center recommends for odd behaviour after an outage. Support says it usually replies within one business hour, weekdays and Sunday mornings.
Will recurring donations still process during an outage?
Yes, recurring donations are run once the system recovers. During the October 20, 2025 AWS outage, new one-time donations could not be submitted, but Planning Center said afterwards that all recurring donations had been processed and no automated action would be lost. Scheduled emails, list refreshes and other queued tasks also ran late, so staff and congregants may see a backlog of emails arrive at once.
Does an AWS outage take down Planning Center?
It can, because Planning Center relies on Amazon Web Services. On October 20, 2025 an AWS outage left it fully offline from about midnight to 5 a.m. Pacific, with full recovery that evening. Logins failed across all products, the Church Center app was unreachable, profile edits could not be saved, and congregations may not have been able to give, sign up for events or use Check-Ins.
Why is my Check-Ins station not working?
It depends on what the station shows. A station showing a QR code has lost its connection and can be re-paired as an existing station without rebuilding its settings. A station that has sat idle and looks out of date can be refreshed with Start over, which Planning Center has given as a workaround when stations missed changes such as template changes. If the Check-Ins row on the status page is red, wait for the fix.
Why are Planning Center login codes or emails late?
Usually a messaging provider is at fault rather than Planning Center itself. In January 2025 a Twilio outage delayed text messages and made it hard to log in to Church Center and Planning Center. In January 2026 emails to Outlook and Microsoft 365 addresses bounced because of a Microsoft error; Planning Center retried them automatically and they were delivered once Microsoft fixed the problem.

How we measure this

  • We request Planning Center's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Planning Center publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Planning Center goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required