Kidtivity Lab

Koyeb Edge Network – No Active Service (Error Page) Overview

Koyeb Edge Network serves as a serverless hosting platform. When a request lands on a path that has no active public service deployed or the detected service is unhealthy, users see a diagnostic error page similar to the provided example. This page guides visitors and owners on the next steps to resolve the issue.

• Context: The error indicates that there is no active service routing the request on the given path. This can occur if a new deployment was recently made and the service is not yet healthy, or if the path is not configured with any public service.
• User guidance for visitors: Suggests contacting the application owner to inform them about the missing service and broken link.
• User guidance for owners: Advises verifying deployment health, ensuring the service is public, and waiting for health checks to pass. Indicates the service should become accessible once detected as healthy.
• Typical resolution time: Often a brief window (less than a minute) if the deployment becomes healthy; could be longer if misconfiguration persists.

How It Works

1. A request is routed to a Koyeb Edge location.
2. If no active public service exists for the request path, the Edge returns a diagnostic 404-like page with instructions.
3. Once the deployment becomes healthy and public, the service becomes accessible again.

Common Scenarios

• Fresh deployment: Service not yet detected as healthy.
• Misconfiguration: Path exists but no active public service attached to it.
• Deployment crash: Service crashed or failed health checks.
• Propagation delay: Recent changes not yet propagated to edge locations.

Best Practices for Owners

• Ensure the service is deployed and marked public.
• Check health checks and startup logs to confirm readiness.
• Confirm path routing rules and domain configuration.
• Monitor edge deployment status for propagation across locations.
• Redeploy or rollback if a recent change caused instability.

Safety and Considerations

• This page does not reveal application internals—only generic guidance about missing/healthy services.
• For users encountering this page, reach out to the application owner with the provided URL to report the issue.

Core Features

• Real-time guidance when no active service is detected for a request path
• Clear differentiation between visitor guidance and owner/developer actions
• Health and deployment status awareness for rapid troubleshooting
• Lightweight and informative error messaging tailored to serverless edge environments
• Quick recovery indications once the service becomes healthy and public