Request for Status Update on RDW Open Data Disruption

[Abhishek Joshi]

Dear Team Open Data,

I hope you are doing well.

We noticed your recent update regarding the Open Data outage and the potential impact on dataset completeness and updates. Since then, our data synchronization jobs have been failing for the past two days, likely due to this disruption.

Could you please share the current status of the issue and let us know if there is an estimated timeline for resolution? This information would help us plan our downstream processes accordingly.

Thank you for your support and efforts in resolving this matter. We appreciate your assistance.

Kind regards,
Abhishek Joshi

[RDW]

Good afternoon,

The issue has been resolved.The datasets have been updated again.

Kind regards,

Team Open Data

Op donderdag 29 januari 2026 om 07:36:06 UTC+1 schreef abhishek...@gmail.com:

[Abhishek Joshi]

Hello Team Open Data,

Good afternoon.

Thank you for your response and for confirming that the issue has been resolved.

However, we are still encountering errors while syncing the dataset m9d7-ebf2. Below are the relevant log entries for your reference:

2026-01-29 15:17:27,524 INFO: Processing dataset m9d7-ebf2 for table extobj.tbl_rdw_vehicle_details

2026-01-29 15:17:30,586 WARNING: Requests made without an app_token will be subject to strict throttling limits. 2026-01-29 15:17:33,276 INFO: Error fetching RDW data for dataset m9d7-ebf2 : 500 Server Error: Internal Server Error 2026-01-29 15:17:33,458 ERROR: Error processing extobj.tbl_rdw_vehicle_details: 500 Server Error: Internal Server Error Traceback (most recent call last):

As shown above, we are still receiving an Internal Server Error (500) for this dataset.

Could you please check this issue and advise if there are any additional steps required from our side, or if the dataset is still stabilizing? 

Thank you for your support and guidance.

  

Kind regards,
Abhishek Joshi

[Abhishek Joshi]

Hello Team RDW Open Data,

Good morning.

Thank you for the information regarding the app token and request throttling.

I would like to seek some clarification. Until 26 January 2026, our data synchronization was working without any issues, and no changes were made on our side. We currently fetch approximately 4,000 vehicle records per request using a GET call with a WHERE IN clause.

Could you please confirm whether any recent changes require us to:

• Use an app token as a mandatory requirement, and/or

• Modify our implementation by splitting requests into smaller chunks (for example, batches of 1,000 records)?

Your guidance will help us adjust our integration accordingly and avoid further errors.

Thank you for your continued support.

Kind regards,
Abhishek Joshi