PlanetScale service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Run a live reachability check for planetscale.com. Compare the regional responses with the problem you see in PlanetScale.
Find PlanetScale help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
PlanetScale separates its console from database instances, branches and application connections. Its support process asks for database context, while public status information describes provider components.
The checker above requests planetscale.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual PlanetScale action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
For separate developer services, compare these individual checks: Redis status check, Neon status check, Clerk status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse developer service checks.
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Use the official help route for PlanetScale; identify the specific product and action described on this page.
Open the website in your browser and compare it with the result above. This link opens the service, not its status page.
Open PlanetScale help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Database product, region, branch, operation and time; redact connection strings, query values and customer data.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to PlanetScale.
These are troubleshooting comparisons, not claims that PlanetScale is currently experiencing a particular incident.
Identify the database product, branch and region, then compare dashboard access with a minimal failing application operation.
Keep a permission or connection error separate from a query/schema problem. Preserve the error and recent change context rather than repeatedly changing database credentials.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use the comparison and support guidance above for the specific action. Keep the original check and error timestamps together; a cached result can be older than the problem you are seeing.
Repeat the same action in a second browser or on another available connection, keeping the item and account the same. Change one thing at a time so the result is comparable. Leave required workplace or school security controls in place.
Follow the website troubleshooting guide for connection checks. Preserve any unsent work before refreshing a form or changing a session.
Identify the database product, branch and region, then compare dashboard access with a minimal failing application operation. Keep a permission or connection error separate from a query/schema problem. Preserve the error and recent change context rather than repeatedly changing database credentials.
Use the community buttons on this page to share whether the service works for you. For help from PlanetScale, use the official help/reporting resource linked above. Use the official help route for PlanetScale; identify the specific product and action described on this page.
Identify the database product, branch and region, then compare dashboard access with a minimal failing application operation. Keep a permission or connection error separate from a query/schema problem. Preserve the error and recent change context rather than repeatedly changing database credentials.
Database product, region, branch, operation and time; redact connection strings, query values and customer data.