Is eCatholic down?

Last checked just now
Current status
eCatholic is up

No incidents right now.

Official status page: https://status.ecatholic.com · Polled every 5 minutes · 24 components tracked

eCatholic is operational right now. Last checked just now; the most recent incident resolved 24d ago.

Real-time eCatholic status, recent outages, and incident history — pulled directly from eCatholic's official status page at https://status.ecatholic.com every 5 minutes. Pingoru tracks 24 eCatholic services and has captured 3 incidents in the last 90 days (99.31% uptime). Get email, Slack, Discord, or webhook alerts the moment eCatholic reports a new incident — free for 5 monitors, no credit card.

Users who monitor eCatholic also follow these No-Code services: Zapier Airtable Webflow Typeform IFTTT Vasion Bubble Skylight Coda DoorDash View all 6,000+ providers
eCatholic uptime 99.31% uptime · past 90 days
Mon Wed Fri
MayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1h 27m
    Started Jul 07, 2026, 07:03 PM UTC · Resolved Jul 07, 2026, 08:30 PM UTC
    Text One-time PasswordsAuthentication
    Timeline · 3 updates
    • investigating · Jul 07, 2026, 07:03 PM UTC

      We are investigating reports of delayed or failed delivery of SMS-based two-factor authentication codes. Some users may experience issues receiving login verification codes via SMS. We are actively investigating the root cause and will provide an update as soon as we have more information.

    • monitoring · Jul 07, 2026, 08:01 PM UTC

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

    • resolved · Jul 07, 2026, 08:30 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 1h 12m
    Started Jun 05, 2026, 04:50 PM UTC · Resolved Jun 05, 2026, 06:02 PM UTC
    Donation FormsWebsitesPayments CenterDonor Accounts
    Timeline · 3 updates
    • investigating · Jun 05, 2026, 04:50 PM UTC

      We are aware of an issue that has caused an outage of our Websites and Payments. We will update this page as we have more information.

    • monitoring · Jun 05, 2026, 05:27 PM UTC

      We identified an access configuration issue affecting our core application servers, which prevented our Websites and Payments from launching correctly. The access was restored and all websites and payments are back online. We will continue to monitor.

    • resolved · Jun 05, 2026, 06:02 PM UTC

      Everything is stable and we're sounding the all-clear. Our sincere apologies for the trouble, we appreciate everyone's patience!

    Latest: Everything is stable and we're sounding the all-clear. Our sincere apologies for the trouble, we appreciate everyone's patience!

  3. Resolved 6h 54m
    Started May 18, 2026, 06:37 PM UTC · Resolved May 19, 2026, 01:31 AM UTC
    Web ApplicationEmail
    Timeline · 7 updates
    • investigating · May 18, 2026, 06:37 PM UTC

      We are currently experiencing an infrastructure disruption within our core middleware services on our platform. This directly impacts the Connect application, preventing the message composer from loading. The ability to compose and send new messages is temporarily degraded. Users may experience loading errors or blank screens when opening the composer. Please note that data integrity is unaffected; all historical messages, draft data, and user records remain secure. Our DevOps and engineering teams have successfully isolated the backend service constraint. We are actively working alongside our cloud service provider to deploy a fix and restore normal middleware routing. We will continue to provide updates every 30 minutes until full service is restored.

    • investigating · May 18, 2026, 07:11 PM UTC

      Our engineering teams are continuing to investigate the infrastructure disruption affecting our core middleware services. Connect users may experience errors when attempting to access the message composer, processing group bulk actions, or utilizing the file upload feature. We are actively working with our cloud infrastructure provider to restore full service in the Connect application. We appreciate your patience as we work through this and will provide our next update in 30 minutes or when new information becomes available.

    • investigating · May 18, 2026, 07:48 PM UTC

      Our DevOps and engineering teams, in coordination with our cloud service provider, are continuing to actively work toward a resolution for the middleware infrastructure disruption. We are fully focused on restoring normal operations as quickly as possible and will provide our next update in 60 minutes, or sooner if additional information becomes available.

    • identified · May 18, 2026, 08:58 PM UTC

      Our engineering and DevOps teams are actively working on deploying a parallel middleware environment to bypass the current infrastructure constraint and restore service. We are focused on getting the Connect message composer back to full functionality as quickly as possible.

    • identified · May 18, 2026, 10:06 PM UTC

      We are continuing to work on bringing our parallel middleware environment online and restoring full service.

    • monitoring · May 18, 2026, 11:14 PM UTC

      A fix has been implemented and we are monitoring the results. It is expected that all functionality has been restored in the Connect application.

    • resolved · May 19, 2026, 01:31 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

Outage history

Past 90 days · 3 incidents View full outage history →