Managed Edge Delivery
Approved entry points are monitored and routed through a controlled delivery layer with policy-aware fallback behavior.
# As a condition of accessing this website, you agree to abide by the following # content signals: # (a) If a Content-Signal = yes, you may collect content for the corresponding # use. # (b) If a Content-Signal = no, you may not collect content for the # corresponding use. # (c) If the website operator does not include a Content-Signal for a # corresponding use, the website operator neither grants nor restricts # permission via Content-Signal with respect to the corresponding use. # The content signals and their meanings are: # search: building a search index and providing search results (e.g., returning # hyperlinks and short excerpts from your website's contents). Search does not # include providing AI-generated search summaries. # ai-input: inputting content into one or more AI models (e.g., retrieval # augmented generation, grounding, or other real-time taking of content for # generative AI search answers). # ai-train: training or fine-tuning AI models. # use: how AI systems may consume the content (immediate, reference, or full). # ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF # RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT # AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET. # BEGIN Cloudflare Managed content User-agent: * Content-Signal: search=yes,ai-train=no,use=reference Allow: / User-agent: Amazonbot Disallow: / User-agent: Applebot-Extended Disallow: / User-agent: Bytespider Disallow: / User-agent: CCBot Disallow: / User-agent: ClaudeBot Disallow: / User-agent: CloudflareBrowserRenderingCrawler Disallow: / User-agent: Google-Extended Disallow: / User-agent: GPTBot Disallow: / User-agent: meta-externalagent Disallow: / # END Cloudflare Managed Content
RLT EdgeWorks operates public status, endpoint monitoring, and regional continuity services for business platforms that depend on stable traffic delivery, predictable uptime, and controlled recovery procedures.
Public information remains simple and verifiable. Sensitive endpoint logic, customer-specific policies, and routing decisions stay inside the protected control plane.
Approved entry points are monitored and routed through a controlled delivery layer with policy-aware fallback behavior.
Regional availability checks, service health snapshots, and incident notes help operations teams keep continuity decisions auditable.
Domain roles, priority, health state, and public status responses are maintained from a single operational registry.
Business traffic is evaluated through the edge policy layer before any live endpoint is selected. This page does not publish customer routes, active hostnames, or internal routing state.