Summary

  • Invoices were intermittently unavailable in RIPE NCC’s LIR Portal on 29 October, while payment confirmation was delayed; the incident ran from 12:38 to 16:57 CET.
  • The 2026 rules count from each invoice date. RIPE NCC’s incident notice records service recovery, not whether each delayed payment confirmation was reconciled.

A portal can return to normal while a finance team is still asking whether a payment was received. RIPE NCC’s 29 October incident report leaves that second clock unstated.

The notice says invoices were intermittently unavailable in the LIR Portal and payment confirmation was delayed. RIPE NCC opened the incident at 12:38 CET and closed it at 16:57, a 4-hour-19-minute interval. In the resolution, it linked the invoicing disruption to maintenance carried out by AFAS the day before and said the functionality had returned to normal.

That is a clean recovery timestamp. It is not an invoice-level receipt. The notice names no affected invoice or member count, gives no deadline adjustment, and describes no process for reconciling confirmations delayed during the incident. It also does not say whether emailed PDFs, their unique payment links, or bank transfers remained available.

Those omissions matter because RIPE NCC’s own payment rules put several dates around one invoice. The 2026 Billing Procedure says each LIR account receives an invoice and payment is due within 30 days of its invoice date. It points to the non-payment procedure after 30 days and says reminders follow a pre-scheduled timetable. If payment has not arrived within 60 days, RIPE NCC will not process new or ongoing requests. Its invoice guidance says services may be restricted after 30 days; after 120 days, the Standard Service Agreement is terminated and all the member’s LIR accounts are closed.

Reactivation then requires a €1,000 fee and all outstanding amounts.

These are standing rules, not reported penalties from this incident. The public record does not say any member missed a deadline. The distinction is the point: a working portal, a payment received, and a payment correctly matched to an invoice are three different states. RIPE NCC’s procedure says the Billing Details page shows payment status and warns that unclear references can delay allocation. A restored screen cannot, by itself, prove that every delayed confirmation has caught up.

The procedure does provide more than one payment route. Invoices are sent as PDF attachments; each includes a unique payment URL; direct bank transfer is also accepted with LIR and invoice numbers in the reference. That design offers potential paths around a portal problem. The incident notice does not tell members which paths remained usable that afternoon, or whether any payment confirmation lag persisted after 16:57.

RIPE NCC should close that gap in the incident record. State which invoice records were affected, whether emailed invoices and payment links remained available, whether any due dates changed, and how members can verify a payment whose confirmation arrived late. Four hours is a short outage. Four unanswered operational questions can keep a finance team in suspense long after the green light.

Sources: RIPE NCC incident record; RIPE NCC Billing Procedure 2026; Receiving and Paying Invoices.