Get help with 2038
If you run systems that might be affected — industrial controllers, embedded products, medical or vehicle fleets, 32-bit Linux devices, or databases that store time as a number — we can help you work out what is at risk and what to do first. Where a specialist is better placed, we will introduce you to one.
Exposure review
A first pass over your inventory against the risk register: which systems, versions and data formats are likely affected, and which are not.
Supplier questions
The questions to put to vendors, and how to read their answers. See the risk checklist for the starting set.
Test planning
How to run clock-forward tests safely, away from production, and what to watch for. Background: testing & detection.
Remediation priorities
Ordering the fixes by impact and lead time: rebuilds, firmware updates, schema changes and replacements. Background: remediation guide.
Briefings
A plain-language briefing on 2038 for management, risk or audit teams, drawing on the lessons from Y2K.
How it works
- Email us with a few details. The button below starts a message with the questions that help most.
- We reply to arrange a short call about what you have and what you need.
- We help directly, or introduce you to a specialist for your sector. If we would receive a referral fee for an introduction, we will tell you before you decide.
Please do not send passwords, network details or other sensitive information by email. We can arrange a safer way to share them if needed.
Independence
Help enquiries never affect the register. Statuses are set only from public evidence, as described in about & methodology. The register and every topic page stay free to read.