> Source: [sk184864](https://support.checkpoint.com/results/sk/sk184864)

# sk184864 - Threat Emulation blade status in SmartConsole shows "Communication error: could not connect to cloud" 

| Property | Value |
|----------|-------|
| Solution ID | sk184864 |
| Date Created | 2026-03-31 |
| Last Modified | 2026-06-04 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- * In SmartConsole \> Gateways and Servers view \> Device Status, the Threat Emulation blade status shows:  


  "*Communication error: could not connect to cloud"*

* Running `tecli show cloud quota` on the Security Gateway fails to retrieve quota information.

* SmartConsole logs show:  


  "*http-error-0* "  

  "*http-fail-to-reach-server*"

## Cause

Threat Emulation cloud services use DNS-based global routing to automatically direct Security Gateways to a regional backend. In some scenarios, the selected backend does not return a valid application-layer response to the Security Gateway, although connectivity is established. This can result in request timeouts or empty responses, which the Security Gateway interprets as a communication failure with the cloud. The behavior is related to backend selection and routing, and not to a complete loss of connectivity.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content