No upcoming maintenance
All components are currently scheduled normally. Planned maintenance is announced at least 48 hours in advance via email and the status page.
This page shows the current operational status of all PQ Intel components. We track uptime by component and publish incident reports within 48 hours of resolution. For real-time alerts and notification subscriptions, visit our dedicated status page at status.productquant.dev.
99.96% uptime over the last 90 days. No unplanned downtime.
99.92% uptime. One brief interruption on May 2 due to a database migration rollback.
99.87% uptime. Scheduled collector rotations and one brief outage on April 28 during a data store migration.
99.95% uptime. No unplanned downtime. Email queuing operates independently of the main application pipeline.
99.90% uptime. One configuration change required a brief restart on May 10.
Resolved
During a scheduled schema migration for the signal history table, an unexpected constraint conflict caused the migration to stall. We rolled back within 15 minutes of detection and applied the migration with corrected constraints during the next maintenance window. Dashboard was unavailable for approximately 8 minutes during rollback. No data was lost.
Resolved
Migrated the signal history data store from a single-node database to a clustered configuration for improved query performance. Signal collection paused during migration; queued signals were processed after migration completed. Approximately 35 minutes of collection lag.
Resolved
A logging subsystem misconfiguration caused excessive disk I/O contention on one API node, resulting in average response times increasing from ~200ms to ~3,200ms for a 20-minute window. No requests were dropped or failed. The logging issue was identified and corrected by automated alerting.
Resolved
A deployed dashboard update did not trigger an automatic cache purge on one Cloudflare edge node. The stale asset was served to approximately 3% of requests for 15 minutes. Manual purge resolved immediately. No functional impact — only UI styling was stale.
Resolved
A batch enrichment job exceeded the TinyFish API rate limit for a 30-minute window. The pipeline automatically retried with exponential backoff, and all queued enrichments completed within the hour. No data was lost. We have since implemented per-tier rate monitoring with automatic throttle adjustments.
All components are currently scheduled normally. Planned maintenance is announced at least 48 hours in advance via email and the status page.
Subscribe to status updates and be notified when incidents occur or maintenance is scheduled.
We send only status updates. Unsubscribe anytime.
Get started with a $5 trial. Full access, no restrictions.
Try for $5 — 3 days