Live  /  Passare  /  Incident

Passare: [AppSignal] [Passare (production)] ImportProcessor::RequestsController#show took 57 secs to generate

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

Summary

Passare posted an automated monitoring alert on its status page on 2026-07-19 at 01:47 UTC, noting that a page in its production system tied to processing imports took 57 seconds to load. The company gave the alert no severity level and did not say which customers, if any, were affected. As of the latest update it was still listed as under investigation, with no cause given and no fix reported.

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.