Resolved -
This incident has been resolved.
Apr 2, 10:03 CEST
Update -
All systems are now functioning as expected, and data processing has returned to normal. Given the stable performance and quota usage, we are now closing this incident.
Apr 2, 10:03 CEST
Update -
We are seeing very positive developments, with quota numbers now looking stable. However, we will continue monitoring the situation before officially closing the incident.
Current Status:
- Data download times are back to normal.
- One preventive measure remains in place: Data for the past three days is still being downloaded every 12 hours instead of the usual 4-hour intervals to reduce quota load.This means that while current data downloads are functioning normally, historical data retrieval for the last three days is happening at a slower rate.
This is the last remaining preventive measure from the multiple actions we’ve taken over the past few days. Once we revert to our normal 4-hour data download frequency for all data, we will consider the incident fully resolved.
Thank you for your patience, and we’ll keep you updated on the next steps!
Apr 1, 09:02 CEST
Update -
The Facebook Ads quota incident is now effectively resolved. We have successfully reduced the quota usage to very low levels and restored the standard lookback window for newly created data sources. The refresh window is being gradually reintroduced to its normal schedule, but it will take several more hours to fully roll out across all data sources for all customers. Thank you for your patience!
Mar 31, 09:52 CEST
Update -
We have implemented some changes that are expected to improve the completion rate of data download jobs. This should result in more scheduled data downloads being processed without delays. However, since there is a backlog of queued jobs, it will take some time for the queue to fully clear.
Our monitoring metrics show some positive signs, and we are hopeful that these adjustments will help stabilize quota levels. That said, we will continue to monitor the situation closely, as it may take some time to see the full impact. We appreciate your patience and will provide further updates as we learn more.
Mar 28, 12:51 CET
Monitoring -
We are aware that customers are currently experiencing delays in their Facebook Ads data downloads. This may cause the data to appear outdated, creating the impression of a mismatch. However, this is solely due to the fact that we are currently unable to download the latest numbers for affected data sources.
Our team has implemented several changes, and we are seeing movement in the right direction within our systems. However, we believe these improvements are not yet broadly visible to our customers. We will need to wait several hours after the latest updates to assess whether the situation improves.
We appreciate your patience and will provide further updates as soon as we have more information.
Mar 27, 15:48 CET
Update -
We appreciate your patience as we continue working on resolving the ongoing quota-related issue affecting Facebook Ads data. You may notice some temporary adjustments in data expiration windows as we implement measures to reduce overall quota load. These changes are necessary to help stabilize the system, and we are actively monitoring the situation to ensure minimal disruption. Please know that as soon as the issue is fully resolved, we will restore normal data refresh intervals.
Thank you for your understanding, and we sincerely apologize for any inconvenience this may cause.
Mar 27, 09:08 CET
Identified -
We are actively addressing an issue related to quota management. While adjustments have been made, there is no immediate visible impact for customers. However, we have expanded our monitoring toolkit to gain greater visibility into how this affects our users and are fully aware of the inconvenience this may be causing. Our team is closely tracking the situation and working towards a resolution. We appreciate your patience and will provide further updates as needed.
Mar 26, 16:10 CET
Investigating -
We are currently investigating this issue.
Mar 26, 10:32 CET