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/ Tue, 16 Jun 2026 00:49:16 +0000 https://status.minerva.io/#60882fa14eb2a0d5d33eeb9a8224fb38d7fc9d804020baf065627125d2841ef6 LinkedIn Contact Data recovered https://status.minerva.io/ Thu, 11 Jun 2026 16:59:05 +0000 https://status.minerva.io/#60882fa14eb2a0d5d33eeb9a8224fb38d7fc9d804020baf065627125d2841ef6 LinkedIn Contact Data went down https://status.minerva.io/ Mon, 08 Jun 2026 13:49:19 +0000 https://status.minerva.io/#02449ef8d5e8826d7f8116e0a1828a207c6c3136a8e1f032cf1739601e4c07f5 LinkedIn Contact Data recovered https://status.minerva.io/ Mon, 08 Jun 2026 13:48:03 +0000 https://status.minerva.io/#1863baee114be7118d3baf5947db1e8c5949af5b7b5d60b9be268240088800f3 Enrich recovered https://status.minerva.io/ Mon, 08 Jun 2026 02:54:02 +0000 https://status.minerva.io/#02449ef8d5e8826d7f8116e0a1828a207c6c3136a8e1f032cf1739601e4c07f5 LinkedIn Contact Data went down https://status.minerva.io/ Mon, 08 Jun 2026 02:53:09 +0000 https://status.minerva.io/#1863baee114be7118d3baf5947db1e8c5949af5b7b5d60b9be268240088800f3 Enrich went down https://status.minerva.io/ Fri, 05 Jun 2026 19:00:24 +0000 https://status.minerva.io/#75abb82a442bce71416555086b89f9ce41fd8b7f8e75b083a54a811b24c0b997 LinkedIn Contact Data recovered https://status.minerva.io/ Fri, 05 Jun 2026 01:43:41 +0000 https://status.minerva.io/#c98b32c8d43985bcc61b9dba62e2cfe96c2469bf01850d9e4094c96b7f9f5fee Enrich recovered https://status.minerva.io/ Fri, 05 Jun 2026 01:33:07 +0000 https://status.minerva.io/#c98b32c8d43985bcc61b9dba62e2cfe96c2469bf01850d9e4094c96b7f9f5fee Enrich went down https://status.minerva.io/ Fri, 05 Jun 2026 01:28:33 +0000 https://status.minerva.io/#b84d9b4bb6f995d83b92a04a31869c11dc02263e924a6dd87c46c91055432610 Enrich recovered https://status.minerva.io/ Fri, 05 Jun 2026 01:18:09 +0000 https://status.minerva.io/#b84d9b4bb6f995d83b92a04a31869c11dc02263e924a6dd87c46c91055432610 Enrich went down https://status.minerva.io/ Thu, 04 Jun 2026 22:53:04 +0000 https://status.minerva.io/#f6a4f7607a7f105048bb81b05b1527aa0f7c8df43785e977c225940d891532f5 Enrich recovered https://status.minerva.io/ Thu, 04 Jun 2026 22:43:06 +0000 https://status.minerva.io/#f6a4f7607a7f105048bb81b05b1527aa0f7c8df43785e977c225940d891532f5 Enrich went down https://status.minerva.io/ Thu, 04 Jun 2026 22:33:19 +0000 https://status.minerva.io/#55d6764b6d8b6532060fc66fb702a4599e54332b10c4bd9a4ab746312c682207 Enrich recovered https://status.minerva.io/ Thu, 04 Jun 2026 22:23:07 +0000 https://status.minerva.io/#55d6764b6d8b6532060fc66fb702a4599e54332b10c4bd9a4ab746312c682207 Enrich went down https://status.minerva.io/ Thu, 04 Jun 2026 22:18:04 +0000 https://status.minerva.io/#c8c2d0e2e25368b5d2ef302931e02f3192504c99e3f135442f407a6b04e3f313 Enrich recovered https://status.minerva.io/ Thu, 04 Jun 2026 22:08:10 +0000 https://status.minerva.io/#c8c2d0e2e25368b5d2ef302931e02f3192504c99e3f135442f407a6b04e3f313 Enrich went down https://status.minerva.io/ Thu, 04 Jun 2026 21:58:03 +0000 https://status.minerva.io/#6354530759543eddadb2e5146b57ff1d07b7e8efc35f5948e1ee2e6849edc380 Enrich recovered https://status.minerva.io/ Thu, 04 Jun 2026 20:53:06 +0000 https://status.minerva.io/#6354530759543eddadb2e5146b57ff1d07b7e8efc35f5948e1ee2e6849edc380 Enrich went down https://status.minerva.io/ Thu, 04 Jun 2026 20:38:03 +0000 https://status.minerva.io/#a524c1aa8f964eb0b49d9336403c77e5e82f206d28407e399ffc894fd0267c0f Enrich recovered https://status.minerva.io/ Thu, 04 Jun 2026 20:28:13 +0000 https://status.minerva.io/#a524c1aa8f964eb0b49d9336403c77e5e82f206d28407e399ffc894fd0267c0f Enrich went down https://status.minerva.io/ Thu, 04 Jun 2026 20:23:09 +0000 https://status.minerva.io/#743e52610576791761b21d423c12d7be5c16fa7d206fd5385d1016eef5e4fd50 Enrich recovered https://status.minerva.io/ Thu, 04 Jun 2026 20:13:12 +0000 https://status.minerva.io/#743e52610576791761b21d423c12d7be5c16fa7d206fd5385d1016eef5e4fd50 Enrich went down https://status.minerva.io/ Thu, 04 Jun 2026 20:08:11 +0000 https://status.minerva.io/#870ac8c3d0940ff6efe415686d5d692c549a1d4ab3de2fbcfa3ff0dd130125f3 Enrich recovered https://status.minerva.io/ Thu, 04 Jun 2026 19:58:03 +0000 https://status.minerva.io/#870ac8c3d0940ff6efe415686d5d692c549a1d4ab3de2fbcfa3ff0dd130125f3 Enrich went down https://status.minerva.io/ Thu, 04 Jun 2026 19:53:07 +0000 https://status.minerva.io/#7cbaa913032a2ede5f0442257c47f3d64fdb6cdbdac725e6a336f47d235c8527 Enrich recovered https://status.minerva.io/ Thu, 04 Jun 2026 19:43:03 +0000 https://status.minerva.io/#7cbaa913032a2ede5f0442257c47f3d64fdb6cdbdac725e6a336f47d235c8527 Enrich went down https://status.minerva.io/ Thu, 04 Jun 2026 19:23:06 +0000 https://status.minerva.io/#600aa4df227b5eb059cdac008934b6c3e2c8b2587e9c79048249ea9b3635c758 Enrich recovered https://status.minerva.io/ Thu, 04 Jun 2026 18:48:04 +0000 https://status.minerva.io/#600aa4df227b5eb059cdac008934b6c3e2c8b2587e9c79048249ea9b3635c758 Enrich went down https://status.minerva.io/ Thu, 04 Jun 2026 18:43:18 +0000 https://status.minerva.io/#b6889b9abdcf5da6d7c028ae17d56dcd07e469a20274dc136bb9fa1caf7f2d0b Enrich recovered https://status.minerva.io/ Thu, 04 Jun 2026 18:33:19 +0000 https://status.minerva.io/#b6889b9abdcf5da6d7c028ae17d56dcd07e469a20274dc136bb9fa1caf7f2d0b Enrich went down https://status.minerva.io/ Sat, 30 May 2026 03:24:02 +0000 https://status.minerva.io/#75abb82a442bce71416555086b89f9ce41fd8b7f8e75b083a54a811b24c0b997 LinkedIn Contact Data went down https://status.minerva.io/ Wed, 06 May 2026 19:34:11 +0000 https://status.minerva.io/#fa177da467408439ce109c1bf6f6e4860b0685b8c9994a42305c2029e0ac5f6b LinkedIn Contact Data recovered https://status.minerva.io/ Wed, 06 May 2026 19:33:01 +0000 https://status.minerva.io/#386c2f4e9f05bc70698f6e40896943ed380798ab2a7ecff367fc8bc4bd0eae14 Enrich recovered https://status.minerva.io/ Wed, 06 May 2026 19:19:02 +0000 https://status.minerva.io/#fa177da467408439ce109c1bf6f6e4860b0685b8c9994a42305c2029e0ac5f6b LinkedIn Contact Data went down https://status.minerva.io/ Wed, 06 May 2026 19:18:10 +0000 https://status.minerva.io/#386c2f4e9f05bc70698f6e40896943ed380798ab2a7ecff367fc8bc4bd0eae14 Enrich went down 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.