v6Node - Upstream routing issue affecting nodes within prefix 178.18.148.0/24 – Incident details

All systems operational

Upstream routing issue affecting nodes within prefix 178.18.148.0/24

Resolved
Partial outage 20 %
Started 22 days agoLasted about 2 hours

Affected

Virtualization Cluster Frankfurt, DE (FRA1)

Partial outage from 6:50 PM to 8:30 PM

Updates
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring

    The missing RPKI authorization (ROA) has been reinstated, and our announcement for 178.18.148.0/24 now validates as RPKI valid again. Reachability is returning automatically as networks refresh their RPKI caches, which usually completes within the hour. We are monitoring until the prefix is fully reachable everywhere. No action is needed on your side. IPv6 remained unaffected throughout.

  • Identified
    UTC
    Identified

    We have identified an upstream routing issue affecting nodes within the prefix 178.18.148.0/24.

    These IPs are up on our network but currently partially unreachable from the global routing table, because a required RPKI authorization (ROA) for our origin AS has gone missing at the block's holder, marking our announcement invalid.

    We have escalated to the upstream provider with high priority and requested the ROA be reinstated immediately. As soon as it propagates, reachability returns on its own.


    Our routing and BGP sessions are otherwise healthy. The IPv6 connectivity remains unaffected.