DNS Belgium Outage History
DNS Belgium is up right nowPingoru has recorded 4 incidents for DNS Belgium: 2 in the last 12 months and 0 in the last 90 days.
Incidents, newest first
Critical March 25, 2026 The .vlaanderen and .brussels services are experiencing issues. 1h 2m Registration system, Registration system
Started Mar 25, 2026, 12:43 PM UTC· resolved Mar 25, 2026, 01:45 PM UTC
- investigating Mar 25, 2026, 12:43 PM UTC
We are currently investigating this issue.
- identified Mar 25, 2026, 12:43 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Mar 25, 2026, 01:45 PM UTC
This incident has been resolved.
- postmortem Apr 03, 2026, 05:34 AM UTC
On 25 March between 12:45 p.m. and 14:15 p.m the RDAP and EPP services of .vlaanderen and .brussels were unavailable. This was caused by expired internal certificates. Our monitoring systems detected and alerted the problem, and we took immediate action to identify and resolve the problem. Analysis revealed an incomplete certificate rotation. It was therefore important to rectify this during the incident, which resolved the issues and allowed the services to restart without any problems. To prevent this from happening again, we will further refine our manual procedure and describe the necessary checks more clearly. It is also possible to set up automatic detection for this to guarantee the validity of all certificates.
Major February 27, 2026 .vlaanderen RDAP and EPP services experienced intermittent issues –
Started Feb 27, 2026, 01:00 AM UTC· resolved Feb 27, 2026, 01:00 AM UTC
- resolved Feb 27, 2026, 07:43 AM UTC
Between approximately 02:00 and 08:00, the .vlaanderen RDAP and EPP services experienced intermittent issues. All systems are now operating normally.
- postmortem Mar 02, 2026, 03:57 PM UTC
On 27 February, between 2 a.m. and 8 a.m. CET, the RDAP, EPP and Registrar Panel services of .vlaanderen were unavailable. The cause was an automatic database failover, after which our authentication service was unable to connect to this database. This had an impact on the aforementioned services. Such failovers occur occasionally, but this time it had a greater impact than usual. Our monitoring systems detected the problem immediately, but it was not until around 7:40 a.m. CET. that we actively noticed the problem. After restarting the affected authentication service, all services were operational again. We have since improved an alert notification issue, which was the result of an incorrect configuration in one of our monitoring tools. We have also attempted to reproduce this behaviour in our test environment, but have been unsuccessful. We simulated various database failovers, but our systems handled them well and we were unable to reproduce a similar interruption. However, we are still looking into this. We also plan to make our setup more robust, where we will try to detect similar situations more quickly and intervene automatically.
Notice April 17, 2025 Degraded financial information 18h 20m EPP, My registrations
Started Apr 17, 2025, 01:20 PM UTC· resolved Apr 18, 2025, 07:41 AM UTC
- identified Apr 17, 2025, 01:20 PM UTC
We are currently experiencing a temporary delay in response times from our accounting system. Our technical team is actively working to resolve the issue and restore normal service as quickly as possible. During this time, financial data may be temporarily unavailable, and you may experience minor glitches. We apologize for any inconvenience this may cause and appreciate your patience. We will keep you updated on the progress and notify you once the issue is resolved. The delegation of domain names, EPP, MyRegistrations, DAS and WHOIS will not be affected.
- resolved Apr 18, 2025, 07:41 AM UTC
This incident has been resolved.