Skip to content

Outage tracker

Planning Center: incident history

The last 24 hours in detail, Planning Center's declared incident record, and our regional check results beside it.

← Back to Planning Center's check readings

We started checking Planning Center on November 2, 2026, which is 7 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me when Planning Center reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Planning Center's own statement from its status page, with our regional reading beside it.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Planning Center's own status page declared. Below it, any public chatter we saw about Planning Center and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Planning Center's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Unverified user reportsNo reports about Planning Center in the last 24 hours, which is not evidence that nothing is wrong.
Planning Center's status pageNo incident declared in the last 24 hours.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Planning Center's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Planning Center next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East100.00%724
US-West99.82%558
Europe100.00%514
Asia-Pacific100.00%305

Their declared record

Planning Center's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

Search service disruptionPartial outage
Oct 21, 2026, 4:30 PM UTC to Oct 21, 2026, 7:46 PM UTC (3h 16m)resolved
their latest update (Oct 21, 2026, 7:46 PM UTC): This incident has been resolved.
Embedded Calendar Event Links Not OpeningAll systems operational
Oct 15, 2026, 9:53 PM UTC to Oct 16, 2026, 12:12 AM UTC (2h 18m)resolved
their latest update (Oct 16, 2026, 12:12 AM UTC): This incident has been resolved.
Chat Not Loading for Some iOS UsersMinor incident
Oct 12, 2026, 2:53 PM UTC to Oct 13, 2026, 11:16 AM UTC (20h 22m)resolved
their latest update (Oct 13, 2026, 11:16 AM UTC): This incident has been resolved with the latest update to the Services and Church Center mobile apps.
Check-Ins sessions not starting automaticallyPartial outage
Oct 4, 2026, 1:05 PM UTC to Oct 4, 2026, 11:06 PM UTC (10h 1m)resolved
their latest update (Oct 4, 2026, 11:06 PM UTC): This incident has been resolved.
Mulitracks outage currently affecting access to files and chartsPartial outage
Sep 9, 2026, 1:01 PM UTC to Sep 9, 2026, 2:40 PM UTC (1h 39m)resolved
their latest update (Sep 9, 2026, 2:40 PM UTC): This incident has been resolved.
Some idle Check-Ins stations may not be receiving live updatesMinor incident
Sep 5, 2026, 5:17 PM UTC to Sep 6, 2026, 6:18 PM UTC (1d 1h)resolved
their latest update (Sep 6, 2026, 6:18 PM UTC): This incident has been resolved.
Donation processing disruptionPartial outage
Sep 2, 2026, 2:34 PM UTC to Sep 2, 2026, 3:12 PM UTC (37 min)resolved
their latest update (Sep 2, 2026, 3:12 PM UTC): This incident has been resolved.
Some Check-Ins stations experiencing 403 errorsMinor incident
Jul 12, 2026, 4:16 PM UTC to Jul 12, 2026, 7:27 PM UTC (3h 11m)resolved
their latest update (Jul 12, 2026, 7:27 PM UTC): This incident has been resolved.
Login Service DisruptionAll systems operational
Jul 11, 2026, 6:52 PM UTC to Jul 12, 2026, 1:25 AM UTC (6h 33m)resolved
their latest update (Jul 12, 2026, 1:25 AM UTC): This incident has been resolved.
Services Briefly Down (Resolved)All systems operational
Jun 23, 2026, 9:00 PM UTC to Jun 23, 2026, 9:00 PM UTC (0 min)resolved
their latest update (Jun 23, 2026, 9:00 PM UTC): Services experienced a brief 3-minute outage due to database query timeouts during scheduled maintenance. The issue was resolved at 1:50 PM Pacific, and Services has been stable since. We apologize for any disruption this may have caused.

Showing the 10 most recent of 50 incidents Planning Center has declared in the history we hold.

These entries are Planning Center's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

Planning Center's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.