RRPproxy incident

Domain Purchase / Modification errors on some TLD due to upstream registry error

Notice Resolved View vendor source →

RRPproxy experienced a notice incident on March 19, 2024 affecting XRRP API and EPP API and 1 more component, lasting 5m. The incident has been resolved; the full update timeline is below.

Started
Mar 19, 2024, 10:19 AM UTC
Resolved
Mar 19, 2024, 10:24 AM UTC
Duration
5m
Detected by Pingoru
Mar 19, 2024, 10:19 AM UTC

Affected components

XRRP APIEPP APISOAP APIXMLRPC APIHTTPS APIWeb Interface

Update timeline

  1. investigating Mar 19, 2024, 10:19 AM UTC

    Due to issues connecting to a registry , there is currently a issue modifying / purchasing some TLD's Error during domain actions "DESCRIPTION": "Command failed due to server error. Client should try again; No response", "CODE":421, Registry Operator confirmed issue and work to resolve is ongoing

  2. resolved Mar 19, 2024, 10:24 AM UTC

    Issue resolved at registry