Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021



The .eu top-level domain, TLD, is run within an EU framework and the right to register and own a .eu domain name is subject to eligibility criteria – in short, being an EU citizen, or being a company established in the EU. For British citizens and companies in post-Brexit, they’ll no longer meet the criteria to register, or indeed continue to own their .eu domains.
The domain registry in charge of all .eu domains, EURid, is working on the basis that Britain will leave the EU without a deal on 31st October 2019. Just a week or so before the date on which the UK would fall out of the EU (assuming no deal is in place, or an extension sought and granted) EURid will be sending out emails to all owners of .eu domains who are based in Britain or Gibraltar. Domain name owners will then have until the 1st January 2020 to try and meet the eligibility criteria. After this date, any domain not meeting the criteria will be withdrawn, on a practical level meaning that any website or email service attached to that domain will no longer work. Then on 1st November 2020, those domains which have been withdrawn will be fully revoked and any third party (based in the EU) will be able to register them.
If you or your business owns a .EU domain there are a few things you should be thinking about.
Firstly check whether your .eu domains were registered with a GB or GI (Gibraltar) country code.
For British companies with a subsidiary in the EU it would be sensible for them to transfer any .eu domains into the European subsidiary before 1st January 2020.
For UK citizens who are living in the EU, or EU citizens living in the UK they’ll still be entitled to own their domains, but should ensure that all details are updated to avoid losing the domain.
For anyone unable to fall into either of the above camps they need to start planning for losing their .eu domain from 1st January next year. If you have a business that relies on a .eu domain now is the time to start planning and think about setting up a new domain and redirecting the .eu domain as soon as possible.
It is also worth checking when your .eu domain is due to expire. If the domain expires between 1st November 2019 and 1st January 2020 it will no longer automatically renew so if you need to renew it for a couple of months to buy your business more time to prepare you’ll need to manually renew it.
Share this
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
Find out everything you need to know in our new uptime monitoring whitepaper 2021