Previous incidents

Yesterday, between 6:30 PM and 9:30 PM UTC, Scrapin experienced a service outage caused by a failed database backup at our hosting provider, which impacted availability for all API endpoints.

The issue has been fully resolved. As a follow-up, we are actively deploying a complete Read Replica setup to prevent this type of incident from occurring again.

We apologize for the disruption and thank you for your patience.

Our infrastructure is now fully stable and operating normally. All API endpoints are responding as expected.

We've implemented additional monitoring to prevent similar issues in the future and will continue to keep a close eye on system performance over the coming days.

Duration: 21:30 - 22:15 CET (45 minutes)
Impact: Service unavailable during this period
Root Cause: Primary database performance degradation prevented proper log recording and system operations
Status: Resolved - All systems returned to normal

We experienced a partial service outage from 1:00 AM to 1:30 PM CET today due to abnormally high call volumes over the weekend. In response to this traffic spike, we disabled logging temporarily to stabilize the platform and prevent further degradation.

The issue has been identified and resolved. All services are now returning to normal operations. We are currently monitoring the situation closely and will continue investigating the root cause of the elevated traffic volume.

We apologize fo...

Service has been fully restored. All systems are back to normal operation.

We experienced a network infrastructure issue this morning that resulted in unavailability of our Scrapin API services for approximately 90 minutes. Our technical team was mobilized early this morning and successfully resolved the issue.

A network connectivity problem affected our service delivery starting at 7:30 AM CET. Our engineering team identified and addressed the root cause, restoring full service by 9:00 AM CET.

During this window, API requests and platform access were unavailable....

The performance issues we experienced have been resolved. API response times are now back to normal levels. We continue to monitor our systems closely to ensure stability. Thank you for your patience.

All systems are operating normally on our end. Our reverse proxy has returned to baseline functionality, and we have immediately deployed a secondary reverse proxy to provide redundancy and prevent similar incidents from occurring in the future.

The connectivity issues we experienced earlier have been resolved. All services are now operating normally. We appreciate your patience and apologize for any inconvenience this may have caused.

The network connectivity issue affecting our primary data sources has been resolved. All systems are operating normally and data consistency has been restored.

We identified an issue beginning at 4:15 PM CET where a limited number of profiles were being returned with empty data fields. We implemented a workaround at 5:35 PM CET that successfully resolved the issue. All profiles are now returning complete data as expected. We apologize for any inconvenience this may have caused.

All services have been fully restored and are operating normally. Thank you for your patience.