bgpreport

Network · data from 2026-11-12

AS219121 CLOUFINITY

Registry name: CLOUFINITY CLOUFINITY Sp. z o.o., PL · PeeringDB

2IPv4 routes 50.0% RPKI valid · 50.0% with a route object
2IPv6 routes 50.0% RPKI valid · 50.0% with a route object
2RPKI invalid 1 origin · 1 maxLength
0No ROA 2 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS219121, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS219121, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
81.168.87.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2a14:1ec7:8001::/48 Invalid: maxLength Nonecovered by 2a14:1ec7:8000::/40 29 5%low visibility 20
191.44.85.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
2a14:1ec7:8000::/40 Valid RIR databaseRIPE 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS219121: RIPE::AS219121:AS-CLOUFINITY. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS219121 isn't in the set, or no route object for AS219121 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS219121 in itNot covered
RIPE::AS219121:AS-CLOUFINITY RIPE 215254 Yes 1

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 4 are in fix.csv.

  • ROA: origin1
  • ROA: maxLength1
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: origin81.168.87.0/24ROAs covering it name AS834, AS8851, AS19905, AS206509, not AS219121. If AS219121 should announce it, add a ROA for AS219121.2 of 673
Route object: none81.168.87.0/24Route objects for it name AS834. Add a route object with origin AS219121 in the RIR database for the space.2 of 673
ROA: maxLength2a14:1ec7:8001::/48ROA 2a14:1ec7:8000::/40 AS219121 has maxLength 40; the route is a /48. Raise the maxLength, or add a ROA for 2a14:1ec7:8001::/48.29 of 636
Route object: none2a14:1ec7:8001::/48No route object for it. A route object for 2a14:1ec7:8000::/40 with origin AS219121 covers it (filters allowing more-specifics accept it). Add a route object with origin AS219121 in the RIR database for the space.29 of 636

Route objects not announced

Every route object with origin AS219121 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.