bgpreport

Network · data from 2026-11-12

AS11598 RECOL-CT - Cloudsmart

Registry name: RECOL-CT - Cloudsmart, US · not in PeeringDB

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

Announced routes

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

64.207.96.0/22 Valid RIR databaseARIN 672 100% 67
64.207.100.0/22 Valid RIR databaseARIN 672 100% 67
64.207.108.0/23 Valid RIR databaseARIN 672 100% 67
64.207.110.0/24 Valid RIR databaseARIN 672 100% 67
199.21.248.0/22 Valid RIR databaseARIN, RADB 672 100% 67
64.207.104.0/22 Valid RIR databaseARIN 670 100% 67
2606:7800::/32 Valid RIR databaseARIN, RADB 635 100% 70

AS-SET

AS11598 isn't in PeeringDB, where networks name their AS-SET.

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 48 are in fix.csv.

  • Route object: not announced48

Route objects not announced

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

12.148.4.0/24RADBNo ROA
12.199.122.0/24RADBNo ROA
63.112.156.0/22RADBNo ROA
63.171.66.0/24RADBNo ROA
63.237.136.0/24RADBNo ROA
64.207.96.0/20ARIN, RADBValid
64.207.111.0/24ARINValid
64.212.170.0/23RADBNo ROA
65.75.0.0/18RADBNo ROA
65.172.152.0/22RADBNo ROA
65.242.131.0/24RADBNo ROA
69.24.32.0/20RADBNo ROA
75.127.32.0/20RADBNo ROA
162.33.16.0/20RADBNo ROA
192.48.97.0/24RADBNo ROA
192.150.121.0/24RADBNo ROA
192.153.4.0/24RADBNo ROA
192.216.125.0/24RADBNo ROA
192.249.45.0/24RADBNo ROA
192.250.0.0/20RADBNo ROA
198.134.158.0/23RADBNo ROA
198.151.128.0/24RADBNo ROA
199.89.147.0/24RADBNo ROA
199.105.120.0/21RADBNo ROA
199.181.163.0/24RADBNo ROA
199.242.177.0/24RADBNo ROA
199.249.195.0/24RADBNo ROA
199.249.196.0/23RADBNo ROA
203.29.75.0/24RADBNo ROA
204.71.20.0/24RADBNo ROA
204.213.176.0/20RADBNo ROA
204.213.232.0/22RADBNo ROA
204.249.240.0/21RADBNo ROA
205.139.10.0/23RADBNo ROA
205.247.160.0/20RADBNo ROA
206.61.168.0/21RADBNo ROA
206.105.16.0/20RADBNo ROA
206.128.24.0/22RADBNo ROA
207.171.128.0/19RADBNo ROA
208.0.192.0/20RADBNo ROA
208.24.198.0/24RADBNo ROA
208.24.204.0/22RADBNo ROA
208.28.184.0/22RADBNo ROA
208.46.135.0/24RADBNo ROA
208.193.132.0/24RADBNo ROA
208.244.240.0/24RADBNo ROA
209.116.172.0/24RADBNo ROA
2001:18e0::/32RADBNo ROA

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.