RIPE NCC logo and current status indicator

RIPE NCC Incident History

RIPE NCC is currently operational with all systems functioning normally.

Last checked Jul 22, 2026 12:07 PM UTC from RIPE NCC's official status page

Incident History

Showing incidents from the last 15 days

Report: "Billing and Payment system unavailable"

Last update
resolved

Payment confirmation functionality has returned and invoices are available. The incident has been resolved.

monitoring

A fix has been implemented and we are monitoring the results.

investigating

We are continuing to investigate this issue.

investigating

Invoices may not be available in the LIR Portal and payment confirmation is delayed.

Report: "RIPE Database: Mail Updates Not Working"

Last update
resolved

Mail Updates were failing due to an issue with the central mail server. This has since been resolved at 12:14 UTC

investigating

We're investigating issue with auto-dbm@ mails are not delivered to WHOIS servers since 20260720 09:06 UTC. Outgoing notification emails and other update methods are not affected.

Report: "Billing and Payment system intermittently unavailable"

Last update
resolved

Payment confirmation functionality has returned and invoices are available. The incident has been resolved.

investigating

We are continuing to investigate this issue.

investigating

Invoices may not be available in the LIR Portal and payment confirmation is delayed.

Report: "RIPE Atlas outage"

Last update
resolved

This incident has been resolved.

monitoring

Service functionality has returned; we are continuing to monitor the system.

investigating

There is currently an issue with RIPE Atlas, causing slowness and preventing users from logging in. We are investigating the issue.

Report: "RIPE Database Switchover"

Last update
Completed

The scheduled maintenance has been completed.

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Scheduled

We plan to perform a switchover of the RIPE database primary instance, so we can perform patching on the server. We don't expect any downtime for Whois queries or updates.