Church Online Platform Outage History

Church Online Platform is up right now

Pingoru has recorded 50 incidents for Church Online Platform: 18 in the last 12 months and 1 in the last 90 days.

Source: status.online.church

50incidents recorded
18last 12 months
1last 90 days
84 minutestypical duration
Incidents per month
024AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Church Online Platform in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202644 of 720 (1%)
May 202610 of 744 (0%)
June 202611 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202611 of 720 (0%)
October 202600 of 545 (0%)

Incidents, newest first

Minor September 1, 2026 Platform Outage 40m Church Online Platform Availabliity

Started Sep 01, 2026, 03:33 PM UTC· resolved Sep 01, 2026, 04:14 PM UTC

  1. investigating Sep 01, 2026, 03:33 PM UTC

    We are actively investigating a known outage. We know these issues can have a significant impact on your ministry & are working diligently to fix this issue.

  2. resolved Sep 01, 2026, 04:14 PM UTC

    This issue has been resolved.

Read the full incident report →

Notice June 21, 2025 Known Issue 7h 14m

Started Jun 21, 2025, 12:49 PM UTC· resolved Jun 21, 2025, 08:03 PM UTC

  1. investigating Jun 21, 2025, 12:49 PM UTC

    We are investigating an issue with data reporting. We know situations like this can have a significant impact on your ministry & are working diligently toward a solution.

  2. monitoring Jun 21, 2025, 06:13 PM UTC

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

  3. resolved Jun 21, 2025, 08:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 12, 2025 Issue Identified 15h 23m Church Online Platform Availabliity

Started Jun 12, 2025, 07:16 PM UTC· resolved Jun 13, 2025, 10:40 AM UTC

  1. investigating Jun 12, 2025, 07:16 PM UTC

    One of our third party integrations notified us of an incident. This is currently causing intermittent issues, where attenders may not be able to access your service. We are keeping a close eye on their progress with the issue and will keep you updated.

  2. resolved Jun 13, 2025, 10:40 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 12, 2025 This is a Test Notification 3m Church Online Platform Availabliity

Started Feb 12, 2025, 10:42 PM UTC· resolved Feb 12, 2025, 10:45 PM UTC

  1. investigating Feb 12, 2025, 10:42 PM UTC

    We are testing communication for the Church Online Platform. No issues are currently impacting the Church Online Platform.

  2. resolved Feb 12, 2025, 10:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 27, 2025 Service Transcripts Missing 2h 30m

Started Jan 27, 2025, 08:14 PM UTC· resolved Jan 27, 2025, 10:45 PM UTC

  1. investigating Jan 27, 2025, 08:14 PM UTC

    We are currently investigating an issue with missing transcripts for services run this past weekend.

  2. identified Jan 27, 2025, 09:36 PM UTC

    The issue around transcripts has been identified, and the team is currently working to restore any missing transcripts.

  3. resolved Jan 27, 2025, 10:45 PM UTC

    This issue has been resolved and all transcripts have been restored.

Read the full incident report →

Major October 27, 2024 Known Issue with Analytics Missing 1h 4m

Started Oct 27, 2024, 04:59 PM UTC· resolved Oct 27, 2024, 06:03 PM UTC

  1. investigating Oct 27, 2024, 04:59 PM UTC

    We are investigating an issue with Analytics not reporting accurately. We know situations like this can have a significant impact on your ministry & are working diligently toward a solution.

  2. monitoring Oct 27, 2024, 05:09 PM UTC

    We have identified the root cause of this issue and deployed a solution. Analytics should begin reporting as expected now.

  3. resolved Oct 27, 2024, 06:03 PM UTC

    This issue has been resolved.

Read the full incident report →