Service status
Check mustelinet service uptime before troubleshooting tenant resources.
Use the mustelinet uptime page when a problem may be caused by a platform service issue rather than a tenant resource configuration issue.
🚦 Check status first for broad incidents
If multiple users, projects, or services are affected, check the status page before changing VMs, DNS records, security groups, or Terraform-managed resources.
Open uptime page
View current uptime and recent incidents for mustelinet cloud services.
Then check tenant state
If services are healthy, continue with the tenant-focused troubleshooting checklist.
App access
Check DNS, edge routing, app listener, HTTPS behavior, and security groups.
Issue details
Record project, resource, timestamp, and error details when the issue persists.
When to use the status page
Check the uptime page when:
- Skyline or authentication is unavailable for more than one user.
- Generated DNS names or public app routes fail across multiple resources.
- mustelinet SSH fails for several VMs or projects at the same time.
- Terraform or API automation fails before reaching a specific tenant resource.
- A working service suddenly fails without a recent tenant-side change.
When to continue troubleshooting
If the status page is healthy, continue with Common tenant issues. Tenant-side checks are still needed for missing floating IP associations, incorrect security group rules, app listener issues, image user mistakes, quota limits, and Terraform drift.
⚠️ Do not change Terraform-managed resources just to test
If Terraform owns the resource, inspect it in Skyline but make lasting changes in Terraform code.