Service status

A monitored service is unavailable.

A customer-safe view of first-party platform health. Sensitive infrastructure details are intentionally excluded.

Checked 22/10/2026, 8:50:31 am NZ time.

Components

outage
Core platform

2 health findings; highest severity critical. Site Reliability AI found a condition requiring immediate diagnosis or capacity action.

Outage
Background processing

24 unresolved job classes remain in dead-letter recovery.

Outage
Payment checkout

No current integration incident is recorded.

Operational
AI Help Center

Verified knowledge automation is available; external model augmentation is optional.

Operational
Email delivery

No current integration incident is recorded.

Operational
AI email support

AI email support remains unclaimed until support address, recent end-to-end support-email verification are verified.

Not connected
Account sign-in

VidPropel email/password sign-in, sessions and MFA are available; password-reset email delivery needs email configuration.

Operational
YouTube promotion

Google Ads provider execution is not claimed as configured until live provider credentials and an end-to-end provider check are verified.

Not connected
Connected YouTube data

No current integration incident is recorded.

Operational

Recent incidents

30 days
PostgreSQL is using 70.0% of configured connections. Root-cause hypothesis: Concurrent application/worker activity is consuming most connection capacity.

Started 22/10/2026, 8:07:02 am

resolved
PostgreSQL is using 71.7% of configured connections. Root-cause hypothesis: Concurrent application/worker activity is consuming most connection capacity.

Started 22/10/2026, 7:31:01 am

resolved
PostgreSQL is using 71.7% of configured connections. Root-cause hypothesis: Concurrent application/worker activity is consuming most connection capacity.

Started 20/10/2026, 12:07:01 pm

resolved
PostgreSQL is using 71.7% of configured connections. Root-cause hypothesis: Concurrent application/worker activity is consuming most connection capacity.

Started 19/10/2026, 3:07:01 am

resolved
PostgreSQL is using 70.0% of configured connections. Root-cause hypothesis: Concurrent application/worker activity is consuming most connection capacity.

Started 17/10/2026, 9:07:02 pm

resolved
PostgreSQL is using 70.0% of configured connections. Root-cause hypothesis: Concurrent application/worker activity is consuming most connection capacity.

Started 17/10/2026, 6:01:02 am

resolved
PostgreSQL is using 70.0% of configured connections. Root-cause hypothesis: Concurrent application/worker activity is consuming most connection capacity.

Started 16/10/2026, 9:49:01 am

resolved
PostgreSQL is using 75.0% of configured connections. Root-cause hypothesis: Concurrent application/worker activity is consuming most connection capacity.

Started 16/10/2026, 7:07:01 am

resolved
PostgreSQL is using 80.0% of configured connections. Root-cause hypothesis: Concurrent application/worker activity is consuming most connection capacity.

Started 16/10/2026, 6:25:04 am

resolved
PostgreSQL is using 70.0% of configured connections. Root-cause hypothesis: Concurrent application/worker activity is consuming most connection capacity.

Started 15/10/2026, 10:07:03 pm

resolved
PostgreSQL is using 70.0% of configured connections. Root-cause hypothesis: Concurrent application/worker activity is consuming most connection capacity.

Started 13/10/2026, 12:55:01 pm

resolved
Queue depth 1101; oldest queued/failed job 165236s. Root-cause hypothesis: One or more workers may be stalled, unhealthy or repeatedly retrying.

Started 11/10/2026, 12:46:01 am

open