Fixed
S3 Delivery: March Gap Backfill Complete + Full Mirror Architecture
8 days ago by ReadMe API
Summary
Our S3 delivery pipeline experienced a 29-day sync outage from February 25 to March 26, 2026. During this period, signal data continued to be produced and delivered to GCS buckets normally, but was not propagated to S3 mirrors. This affected all S3 delivery customers.
All missing data has been fully backfilled as of April 16, 2026. We have also upgraded the sync architecture to prevent recurrence.
What happened
- Feb 25: The GCS→S3 sync scheduler was inadvertently removed during infrastructure maintenance
- Feb 25 – Mar 26: S3 mirrors stopped receiving updates. GCS (primary) was unaffected
- Mar 26: Sync pipeline was restored. New data began flowing to S3 again
- Apr 16: Full backfill of all 121 missing deliveries completed across 36 buckets (242 files)
Impacted buckets (36)
| Bucket | Missing deliveries |
|---|---|
| autobound-10k-v1 | 4 |
| autobound-10q-v1 | 4 |
| autobound-20f-v1 | 1 |
| autobound-20f-v2 | 1 |
| autobound-6k-v1 | 3 |
| autobound-6k-v2 | 1 |
| autobound-8k | 4 |
| autobound-conference-cfp | 9 |
| autobound-earnings-transcripts | 3 |
| autobound-earnings-transcripts-v2 | 1 |
| autobound-federal-contract-award | 8 |
| autobound-financials | 1 |
| autobound-github-v1 | 1 |
| autobound-glassdoor-company-v2 | 1 |
| autobound-hackernews | 12 |
| autobound-hiring-trends | 4 |
| autobound-hiring-velocity-v1 | 4 |
| autobound-linkedin-comments-contact-v1 | 1 |
| autobound-linkedin-post-company-v2 | 1 |
| autobound-linkedin-post-contact-v3 | 2 |
| autobound-news-v2 | 3 |
| autobound-news-v3 | 1 |
| autobound-patents | 1 |
| autobound-podcast-appearance | 17 |
| autobound-product-reviews-v1 | 1 |
| autobound-producthunt | 9 |
| autobound-reddit-company-v2 | 1 |
| autobound-sec-form-d-funding | 12 |
| autobound-seo-traffic | 1 |
| autobound-twitter-company-posts | 1 |
| autobound-twitter-contact-posts | 1 |
| autobound-website-intelligence-v1 | 1 |
| autobound-work-milestones | 3 |
| autobound-work-milestones-v2 | 1 |
| autobound-youtube-company | 1 |
| autobound-youtube-contact | 1 |
What we changed
- Full mirror architecture: S3 now mirrors every folder in every signal bucket, not just the current day. Any historical gap is automatically caught and filled on the next sync run.
- GCP-native scheduling: The sync trigger has been moved from an external scheduler to GCP Cloud Scheduler, eliminating the single point of failure that caused this outage.
- Increased capacity: Cloud Run job memory upgraded from 8GB to 16GB to handle large signal files (e.g., website-intelligence at 13.7GB).
- Backfill manifest: A backfill manifest (
backfill-2026-04-16.json) has been uploaded tos3://autobound-s3-manifests/syncs/documenting all recovered deliveries.
Action required
None. All missing data is now available in your S3 buckets in the same folder structure and file naming convention as regular deliveries. No changes to your ingestion pipeline are needed.
If you notice any remaining gaps, please reach out in your Slack Connect channel.