Find the answer. Keep moving.

Submit your business details from a product page or the Free trial entry. After confirmation, you can configure your first protected site in the console.

1. 1Share your work email and traffic scale
2. 2Choose the product to evaluate
3. 3Receive activation guidance from an architect

Administrators with billing access can review orders, billing periods and invoice status in the enterprise account. Contact support before a bill is issued to update invoice or payment details.

Prepare access to DNS, the current origin address and a certificate plan. Validate a test subdomain first, then move production traffic.

1. 1Add the domain and choose an onboarding method
2. 2Set the DNS record shown in the console
3. 3Verify HTTPS and origin health

Exclude sign-in, payment and personalized paths first. Then set TTL by path or file type for static assets, and review the rule preview before publishing.

Confirm the affected domain, time range and user impact before broadening a blocking rule. Keep the alert ID and contact on-call support.

1. 1Check user and origin impact
2. 2Record the alert time, peak and attack type
3. 3Share the alert ID with support

Published rules propagate quickly to edge locations. For a high-risk rule, start in observe or challenge mode, then move to block after checking false positives.

Compare latency and status codes by region, then review origin time and cache hit rate. A regional issue usually points to route or node conditions; a global issue often points to the origin.

1. 1Use global speed test to confirm regional differences
2. 2Review cache hit rate and origin time
3. 3Compare origin logs with application change time

Cache policy may not cover the right assets, query strings may fragment requests, or response headers may prevent caching. Start with the highest-volume reusable resources.

Use the status area in the console to check the latest network, console and API health. Planned maintenance and confirmed events include scope and progress.

Keep the request time, endpoint, response status and request ID. Never include API keys or full authorization headers in a support case.

1. 1Record the exact time and timezone
2. 2Copy the request ID from the response
3. 3Describe the calling environment and last successful request

Open a case for integration, configuration, billing, performance or security issues that need human help. Mark the request urgent if an active attack is affecting your business.

1. 1Name the product and affected domain
2. 2Describe symptoms, start time and business impact
3. 3Attach sanitized logs or request IDs

Routine requests are handled promptly in business hours. Active attacks and broad service disruption are prioritized by the 24/7 team.