MyGuy

Koyeb Edge Network – Service Not Active (No Active Service)" is a status/informational page shown by the Koyeb serverless platform when no public service is detected on the requested path. It indicates that the request landed on an edge location, but there is currently no deployed or healthy service routing that path. The page provides guidance for both visitors and service owners on what to do next and explains that the error is temporary while the service becomes healthy or is properly deployed.

What it means

• The edge router found no active public service to handle the request.
• The symptom is temporary; once the service is deployed and marked healthy, the path will route normally.
• It can occur if a new deployment has just been created or if a service hasn’t been configured to respond on that path.

For Visitors

1. If you followed a link, contact the owner of the application and inform them that the service isn’t currently active.
2. Retry later, as the owner may deploy or initialize the service to become healthy.

For Owners / Developers

• Ensure the service is deployed and healthy on the specified path.
• Check deployment status and health checks to confirm the route is active.
• If you just deployed, allow a moment for the platform to detect and register the service.
• Verify that the service is public and has the correct routing rules configured.
• Refer to the documentation for troubleshooting steps related to health endpoints and public accessibility.

How to Troubleshoot

• Confirm deployment succeeded and the service is in a healthy state.
• Verify that the path you are requesting matches the service’s public route.
• Inspect logs or health checks for errors that prevent activation.
• Redeploy or reconfigure routing if necessary.
• Check for environment or configuration changes that could block activation on the edge network.

Safety and Operational Considerations

• This message is informational and non-error for the platform itself; it indicates a routing absence rather than a platform failure.
• Ensure proper access controls so that only intended paths are exposed publicly.

Core Features

• Edge-based routing and serverless deployment
• Health-based service activation and automatic routing
• Real-time status guidance for visitors and owners
• Lightweight, actionable troubleshooting steps
• Clear separation between user-facing errors and platform issues