CDN | Raw Logs incident details
Incident
Report for Gcore
Resolved
From September 14, 8:16 UTC to September 19, 08:30 UTC, our services experienced a technical issue resulting in the omission of approximately 18% of requests from raw logs. Unfortunately, we are unable to restore the missing logs and resend them.
We want to reassure that this issue did not influence online statistics. After conducting thorough checks, we have confirmed that the online statistics remained accurate and reflected all processed requests. We used this source of data to restore statistics data, including billing data. This means that the accuracy of statistics reporting was not compromised during this period. You can get full data with API requests and in the control panel. Your invoices will be generated based on the restored statistics to ensure accuracy.
Our dedicated engineering team worked diligently to identify and resolve the issue that caused the data omission. We have implemented enhanced monitoring and planned additional tests for this functionality. This will help us to prevent such incidents occurring in the future.
We apologize for any disruption and appreciate your understanding during this incident. Your trust in our services is of utmost importance, and we will continue striving to provide you with the highest level of service and data accuracy. If you have any further questions or concerns regarding this incident or your billing, please do not hesitate to reach out to our support team.
We want to reassure that this issue did not influence online statistics. After conducting thorough checks, we have confirmed that the online statistics remained accurate and reflected all processed requests. We used this source of data to restore statistics data, including billing data. This means that the accuracy of statistics reporting was not compromised during this period. You can get full data with API requests and in the control panel. Your invoices will be generated based on the restored statistics to ensure accuracy.
Our dedicated engineering team worked diligently to identify and resolve the issue that caused the data omission. We have implemented enhanced monitoring and planned additional tests for this functionality. This will help us to prevent such incidents occurring in the future.
We apologize for any disruption and appreciate your understanding during this incident. Your trust in our services is of utmost importance, and we will continue striving to provide you with the highest level of service and data accuracy. If you have any further questions or concerns regarding this incident or your billing, please do not hesitate to reach out to our support team.
This incident affected: CDN (Raw Logs).