Resolved: NRTM issue affecting reverse DNS provisioning
Dear colleagues, Between 00:06 on 2 August and 12:30 (UTC) on 4 August, we experienced an issue affecting our Near Real Time Mirroring (NRTM) service. Since our reverse DNS provisioning system also uses NRTM, updates to the global DNS were delayed over this period. All pending updates were processed once we applied a fix to the NRTM issue. We plan to publish a brief post-mortem report with more details soon. You can always check the status of our services at status.ripe.net <http://status.ripe.net/>. Kind regards, Mahesh Aggarwal RIPE NCC
Dear colleagues,
On 6 Aug 2026, at 15:46, Mahesh Aggarwal <maggarwal@ripe.net> wrote:
Dear colleagues,
Between 00:06 on 2 August and 12:30 (UTC) on 4 August, we experienced an issue affecting our Near Real Time Mirroring (NRTM) service.
Since our reverse DNS provisioning system also uses NRTM, updates to the global DNS were delayed over this period. All pending updates were processed once we applied a fix to the NRTM issue.
We plan to publish a brief post-mortem report with more details soon.
We have now published a post-mortem on the NRTM production outage last week: https://status.ripe.net/incidents/28gns2m10wjd Regards Ed Shryane RIPE NCC
participants (2)
-
Edward Shryane -
Mahesh Aggarwal