bgpreport

Network · data from 2026-11-12

AS11775 Clougix, LLC

Registry name: CLOUGIX-11775 - Semina Tempus, LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS11775, 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.

38.79.75.0/24 No ROA Other IRR onlyRADB 1 0%low visibility 1
23.164.104.0/24 Valid RIR databaseARIN 672 100% 67
192.149.39.0/24 Valid RIR databaseARIN 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS11775: AS11775:AS-CLOUGIX-GLOBAL AS11775:RS-CLOUGIX-GLOBAL. 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 (AS11775 isn't in the set, or no route object for AS11775 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 objectsAS11775 in itNot covered
AS11775:AS-CLOUGIX-GLOBAL ARIN 239 Yes 0
AS11775:RS-CLOUGIX-GLOBAL A route-set, not an AS-SET; route-sets aren't expanded.

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: none1
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none38.79.75.0/24No ROA covers it. Add a ROA for AS11775, maxLength 24.1 of 673
Route object: RIR38.79.75.0/24Route object only in RADB. Add it in the RIR database for the space.1 of 673

Route objects not announced

Route objects with origin AS11775 whose prefix no peer sees AS11775 announce. Many are kept on purpose (backup routes, space announced only in some places).

2607:7340::/32ARINValid
2607:7340:1000::/36ARINValid

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.