The author says the free LongCat 2.5 Preview service repeatedly timed out or lagged, and returned an HTTP 429 error stating that the upstream endpoint was unavailable. This is a personal report without configuration details or quantitative records.
Suitable for assessing: The availability issue this user encountered with the free service at the time.
Not suitable for extrapolating to: Overall availability, latency, the cause of the failure, or the performance of the official release.
Applicable model version: LongCat 2.5 Preview; the post title identifies it as the free service.
Test environment or client: The post was published in r/opencode; the body does not specify the client or service provider.
Reasoning level and parameters: Not specified.
The author asked whether others had also experienced timeouts or lag, and shared an error that had occurred repeatedly. No request content, request count, timing distribution, or test steps were provided.
The author reported repeatedly receiving HTTP 429. Another commenter said that not a single prompt request had gone through in the past week, but provided no request records or configuration.
Error message: HTTP 429: Upstream request failed: Endpoint is unavailable.
Duration, request count, and success rate: Not specified.
This report provides a specific error message, but cannot confirm the root cause of the rate limiting or endpoint unavailability, or measure the scope or duration of the failure. The commenter's claim is also unverified independently; this is not a performance evaluation of the official LongCat 2.5 release.
The original post does not provide the service provider, request content, or full configuration, so the issue cannot be strictly reproduced. To verify it independently, record the client, provider, model identifier, request time, error message, and number of successful requests; do not treat an individual service outage as a measure of model capability.
LongCat 2.5