Summary
On October 27, 2025, Scrapin API experienced a service disruption lasting approximately 12 hours (08:00 - 20:00 CET). During this period, affected endpoints were unavailable as we worked to resolve critical infrastructure issues. Full service was restored by 20:00 CET with all systems operating normally.
Timeline
- 08:00 CET: Network connectivity issues detected affecting upstream data sources
- 08:15 CET: Schema compliance issues from dependent third-party providers caused all person and company identification endpoints to fail
- 09:30 CET: Fallback/caching mechanisms activated to restore service
- 09:45 CET: Fallback deployment revealed schema validation failures - cached data did not properly comply with our published API contract
- 10:00 CET: Decision made to suspend live data pushes to maintain data integrity
- 13:00 CET: Internal caching layer fully activated as primary data source (temporary mitigation)
- 16:00 CET: Engineering team prepared comprehensive fallback service and implemented additional diagnostics
- 19:00 CET: Root cause identified; permanent resolution implemented
- 20:00 CET: Full service restoration confirmed; caching layer deactivated; normal operations resumed
- Ongoing: Post-incident monitoring and system hardening
Root Cause Analysis
- Network-Level Disruption: Infrastructure issues with upstream connectivity affected real-time data delivery
- Third-Party Schema Changes: Dependent providers introduced schema modifications incompatible with our validation framework
- Cascading Endpoint Failures: Schema compliance issues cascaded across all person and company identification endpoints, rendering them unavailable