Status & Known Issues
Current known issues and ongoing improvements for the Signal Database.
This page tracks known issues and ongoing improvements for the Signal Database. We update this regularly as issues are resolved and new items are identified.
Last updated: January 27, 2026
Current Situation
We're experiencing delays in reaching our target coverage for several signal categories. While our core SEC filing signals (10-K, 10-Q, 8-K, Earnings Transcripts) are fully available, we're behind on delivering our social, hiring, and website intelligence signals at the coverage levels we committed to.
What happened
Our signal generation infrastructure has been running in production for 7 years - the underlying data and models are battle-tested and robust. The issue we hit was in the delivery mechanism. As we built out the new bulk data handoff pipeline to support scale requirements, we encountered schema formatting inconsistencies between our internal systems and the export layer.
The signals themselves are accurate and complete; the snag was in packaging them for seamless ingestion on your end.
We made the decision to resolve this properly rather than deliver data that would cause downstream integration issues for your team.
What we're doing
- ✅ Schema consistency issues have been resolved and validated
- ✅ Delivery pipeline is live — new versioned buckets are active (see Changelog)
- 🔄 Scaling data completeness for remaining signal categories
Signal Availability
Quick reference for what's available now, schema status, and delivery progress.
Definitions
| Column | Description |
|---|---|
| Available Now | Whether data is currently accessible in the bucket |
| Schema | Whether the schema is finalized and stable for production use |
| Delivery Status | Progress toward delivering the full dataset at target record counts and geographic coverage |
Legend
| Icon | Meaning |
|---|---|
| ✅ | Yes — data available |
| ❌ | No — not yet available |
| 🔒 | Locked — schema finalized and stable |
| 🔄 | Finalizing — schema lock in progress |
| 🟢 | Full — complete dataset at target counts delivered |
| 🟡 | Partial — data available; full delivery in progress |
| 🔴 | Pending — coming soon |
SEC Filings
| Signal | Available | Schema | Delivery Status |
|---|---|---|---|
| 10-K | ✅ | 🔒 Locked | 🟢 Full |
| 10-Q | ✅ | 🔒 Locked | 🟢 Full |
| 8-K | ✅ | 🔒 Locked | 🟢 Full |
| 20-F | ✅ | 🔒 Locked | 🟢 Full |
| 6-K | ✅ | 🔒 Locked | 🟢 Full |
| Earnings Transcript | ✅ | 🔒 Locked | 🟢 Full |
News & Business Events
| Signal | Available | Schema | Delivery Status |
|---|---|---|---|
| News | ✅ | 🔒 Locked | 🟢 Full |
| Hiring Velocity | ✅ | 🔒 Locked | 🟢 Full |
| Hiring Trends | ✅ | 🔒 Locked | 🟢 Full |
| Financial Reports & Fundamentals | ❌ | 🔄 Feb 13 | 🔴 Pending — Feb 13 |
Social & Engagement (Company)
| Signal | Available | Schema | Delivery Status |
|---|---|---|---|
| Reddit (Company) | ✅ | 🔒 Locked | 🟡 Partial — 10k signals from 1M companies; scaling to 3M in Feb |
| Glassdoor (Company) | ✅ | 🔒 Locked | 🟢 Full |
| LinkedIn Post (Company) | ✅ | 🔒 Locked | 🟢 Full |
| Twitter/X (Company) | ❌ | 🔄 Feb 13 | 🔴 Pending — Feb 13 |
| YouTube (Company) | ❌ | 🔄 Feb 13 | 🔴 Pending — Feb 13 |
| GitHub | ✅ | 🔒 Locked | 🟢 Full |
Social & Engagement (Contact)
| Signal | Available | Schema | Delivery Status |
|---|---|---|---|
| LinkedIn Post (Contact) | ✅ | 🔒 Locked | 🟡 Partial — 25% of audience; next batch Feb 13 |
| LinkedIn Comment (Contact) | ✅ | 🔒 Locked | 🟡 Partial — 30 days only; 3-month backfill Feb 13 |
| Twitter/X (Contact) | ❌ | 🔄 Feb 13 | 🔴 Pending — Feb 13 |
| YouTube (Contact) | ❌ | 🔄 Feb 13 | 🔴 Pending — Feb 13 |
| Work Milestone | ❌ | 🔄 Feb 13 | 🔴 Pending — Feb 13 |
Technographics & Intelligence
| Signal | Available | Schema | Delivery Status |
|---|---|---|---|
| SEO / Website Traffic | ✅ | 🔒 Locked | 🟡 Partial — 50% of audience; next batch Feb 13 |
| Product Reviews (G2) | ✅ | 🔒 Locked | 🟡 Partial — 60% of audience; full data Feb 13 |
| Website Intelligence | ✅ | 🔒 Locked | 🟡 Partial — 25% of audience; next batch Feb 13 |
| Employee Growth by Dept | ✅ | 🔒 Locked | 🟢 Full (audience expansion to 3M companies coming soon) |
| Patent Filings | ✅ | 🔒 Locked | 🟢 Full |
| Technographic Data | ✅ | 🔒 Locked | 🟢 Full |
B2B Database
| Signal | Available | Schema | Delivery Status |
|---|---|---|---|
| Contact Database (US) | ✅ | 🔒 Locked | 🟢 Full |
| Contact Database (International) | ✅ | 🔒 Locked | 🟢 Full |
| Company Database | ✅ | 🔒 Locked | 🟢 Full |
Known Issues & Active Improvements
| Issue | Description | Signals Impacted | Est. Resolution |
|---|---|---|---|
| Cross-signal subtype deduplication | Same material event (e.g., acquisition, exec change) can appear in multiple filings for the same period. Implementing logic to detect duplicates by company + subtype + time window and suppress redundant signals. Priority given to most detailed source. | 10k, 10q, 8k, 20f, 6k, earnings-transcripts | Feb 6 |
| 8K noise reduction | Some companies file high volumes of 8Ks. Refining processing to surface actionable signals while filtering routine/administrative filings. | 8k | Resolved Jan 22 |
| Job title normalization | Improving disambiguation for ambiguous titles like "CMO" (Chief Marketing Officer vs Chief Medical Officer) based on company context and industry. | 10k, 10q, 8k, 20f, 6k, earnings-transcripts | Feb 6 |
| LinkedIn signals could surface more useful context. | Posts currently only have basic tags; need richer metadata to create more useful signals. Sentiment, relationship (like commenter to poster), etc | linkedin-post-company, linkedin-post-contact, linkedin-comment-contact | Feb 6 |
| Global distribution gaps | Sample data skews US-heavy; next batch will include stronger international representation. | linkedin-post-company, reddit, glassdoor, linkedin-post-contact, product-reviews | Resolved Jan 23 |
| Social signals limited to 30 days | Current social signal data only covers past 30 days; adding 3-month historical backfill. | reddit-company, linkedin-post-company, linkedin-post-contact, linkedin-comments-contact | Resolved Jan 23 |
| Schema inconsistencies | Some fields have similar names with subtle differences (e.g., relevance vs sales_relevance). API vs Signal Database payloads have structural differences. Refer to signal-specific schema docs. | All signals | Ongoing |
| Healthcare/pharma executive misclassification | For companies in healthcare and pharma sectors, Chief Medical Officer transitions were incorrectly classified under cmoChange. Similarly, transitions of senior executives from medical/scientific R&D departments were incorrectly classified under ctoChange. New subtype chiefMedicalOfficerChange added for proper classification. | 10k, 10q, 8k, 20f, 6k | Resolved Jan 31 |
| Historical backfill timestamps | SEC filings and earnings transcripts from the January 2026 historical backfill may show detected_at timestamps from the backfill window rather than the original filing/event date. Some earnings transcripts for Q1 2026 may show March 2026 dates. Going forward, detected_at will accurately reflect batch execution time. | 10k, 10q, 8k, 20f, 6k, earnings-transcripts | Resolved Jan 31 |
Questions?
If you encounter issues not listed here or need assistance, contact us at [email protected].
Updated 2 days ago