Incidents reported on status page for Minerva https://status.minerva.io/ https://d1lppblt9t2x15.cloudfront.net/logos/0c9c430078947c4dc79501797593d9ac.png https://status.minerva.io/ en https://status.minerva.io/incident/884577 Sat, 02 May 2026 19:00:24 -0000 https://status.minerva.io/incident/884577#c7a0fb9359c87d14b6d0445e0417b0384e4c18374e14946cc3dbca549d77f4ef Maintenance completed https://status.minerva.io/incident/884577 Sat, 02 May 2026 15:00:24 -0000 https://status.minerva.io/incident/884577#e2bdad67e66b18c9fde76b4a3e562b44a51bfd130e4239abee890653a2ed5c9d We're migrating to upgraded backend infrastructure. During the maintenance window: - The Minerva web app (app.minerva.io) may be unavailable or unresponsive - All API endpoints (Enrich, LinkedIn Contact Data) will be unavailable or return errors - Authentication may be intermittently disrupted What to do: Plan any time-sensitive enrichment runs or dashboard work for before 11 AM ET or after 3 PM ET on Saturday. We'll update this status page as the migration progresses and confirm when normal service resumes. For any questions, please contact your account manager or justin@minerva.io for any questions. https://status.minerva.io/incident/804678 Wed, 14 Jan 2026 23:23:00 -0000 https://status.minerva.io/incident/804678#8c7b7fa3e235b0ee72bccf4ed3e2fde3a08ae2ade07180ebaae56fd802bc4992 Status: Resolved Duration: 2 hours, 8 minutes Date: January 13, 2026 Affected Services: All API endpoints (Enrich, Resolve, LinkedIn Contact Data), OAuth 2.0 Authentication Impact: Complete service unavailability for all customers TIMELINE (All times EST) Jan 13, 2026 - 1:12 PM - Investigating Our monitoring systems detected widespread failures across API endpoints. Engineering team notified and investigating. Jan 13, 2026 - 1:45 PM - Identified Root cause identified: AWS Lambda account-level concurrency exhaustion (1,000 concurrent executions limit) caused by high-volume customer operation. This triggered cascading database connection pool exhaustion, resulting in complete API unavailability. Jan 13, 2026 - 2:55 PM - Monitoring Applied reserved concurrency limits to critical authentication services. Monitoring for stability and additional throttling. Jan 13, 2026 - 3:40 PM - Resolved All services restored to normal operation. API response times returned to baseline. No data loss or corruption occurred. WHAT HAPPENED A large-scale data operation from a single customer generated approximately 83,000 API requests within one hour, exhausting our AWS Lambda account-wide concurrency limit. This caused Lambda function throttling across all customer-facing services, database connection pool exhaustion (approximately 4,000 simultaneous connections), and complete unavailability of authentication and API endpoints. Data Security: No customer data was compromised, exposed, or modified. This was strictly an availability incident. RESOLUTION Applied reserved concurrency allocation to critical authentication services. Identified and throttled the root cause Lambda function. Restored database connection pool to normal levels (47 active, 169 idle connections). Validated all services operational before marking resolved. PREVENTIVE MEASURES Immediate (Completed): Reserved concurrency for all critical Lambda functions. Enhanced monitoring with automated on-call escalation. This Week: Per-customer rate limiting at API Gateway layer. Deprecation of legacy routing component that was the root cause. Customer documentation on API batching best practices. Next 30 Days: Load testing to validate 200k+ requests/hour capacity. Bulk operations coordination policy for high-volume integrations. Database connection pool optimization. https://status.minerva.io/incident/747429 Mon, 20 Oct 2025 15:19:00 -0000 https://status.minerva.io/incident/747429#c47165a2e5823d82264e2c7dfd63277c11712b6f650b3570cd3710e0267ef762 Status: In Progress Incident Start: October 20 · 3:11 a.m. ET Region Affected: US-East-1 (N. Virginia) Severity: Moderate – Third-Party Infrastructure Impact Summary: Earlier today, Amazon Web Services (AWS) experienced a widespread outage in its US-East-1 region, affecting a number of dependent services globally. Some Minerva BI Inc. workloads that rely on this region experienced temporary latency and job queue delays between 3:11 a.m. and 6:35 a.m. ET. AWS is investigating the root cause of the issue. Impact: Periodic errors or slower response times on enrichment and reporting endpoints. Temporary delay in processing scheduled enrichment jobs. No data loss, unauthorized access, or security incidents detected. Resolution: Service was automatically restored once AWS infrastructure recovered. All systems have been validated, and backlogged tasks were re-queued and processed successfully. Next Steps: Internal review of recovery procedures and incident response documentation Confirmation that RTO/RPO thresholds were met. Post-mortem logged per SOC 2 Availability ( A1.2 – A1.4 ) and CC7.3 controls Customer Communication: This notice satisfies Minerva BI Inc.’s commitment to transparency regarding material service interruptions. No action is required from customers.