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.