Live  /  Passare  /  Incident

Passare: [AppSignal] [Passare (production)] Api::PlanningCenter::V1::FuneralDetailsController#upsert_funeral_details took 33 secs to genera

Passare · passare.cominvestigating2026-07-19 01:47 UTC
Public — what happened

Summary

Passare posted an automated monitoring alert on its status page saying that one part of its production system, which handles saving funeral details through a Planning Center connection, took about 33 seconds to respond. The notice was opened on 2026-07-19 at 01:47 UTC and was marked as under investigation, with no severity assigned. Passare did not say who was affected, did not name a cause, and had not reported it as resolved.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Passare against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Passare: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Passare report →

More from Passare

The full archive is on the Passare status & history page.

Related: Passare status & history. SquidGrid is not affiliated with Passare.