Where to check APITube API status and uptime#

The official APITube status page is status.apitube.io — that is where you confirm whether the platform is operational and review past incidents. But before you assume an outage, do a two-step check: first read the HTTP status code your request returned, because most “the API is broken” reports are actually a 401, 402, 403, or 429 on your side. If your calls fail with a 500, that points at the API itself — then the status page is the right place to look.

For a fast machine check, the API also exposes an unauthenticated health endpoint at /ping that returns pong when the service is up.

Where is the APITube status page?#

The status page lives at https://status.apitube.io. It is the single source of truth for whether the News API is currently operational and for the history of past incidents, so it is the first link to open when several requests fail at once or latency spikes across every endpoint. The same link is published in the APITube site footer and in the documentation, so you can always reach it without a login.

Open the status page when the failure is broad — every endpoint failing, or plain 500 responses. If only one specific request fails while others succeed, it is far more likely a parameter or account issue than a platform outage.

Is the APITube API down, or is it a problem on my side?#

Read the HTTP status code first. APITube returns a specific code and an ER… error identifier for client-side problems, and reserves 500 for a genuine server-side fault. This is the fastest way to tell an outage from a configuration or quota issue:

• 401 (ER0201 / ER0202 / ER0230) — authentication. The key is missing, invalid, or expired. Fix the key, not the platform.
• 402 (ER0176 / ER0177) — billing. You have no requests left (ER0176) or hit your monthly Pay As You Go spending limit (ER0177).
• 403 (ER0601 / ER0602 / ER0603) — access rules on the key: a blocked IP, a disallowed domain, or an endpoint outside the key’s scopes.
• 429 (ER0203 / ER0204) — rate limiting. You sent too many requests per minute (ER0203), or you were temporarily banned after repeated violations (ER0204).
• 500 (ER0183) — a server-side error ("Something went wrong."). This is the one code that suggests the problem is on APITube’s side. If you see it repeatedly, check the status page.

So a 429 or a 402 is never an outage — it means your requests or your quota need attention, covered in handling rate-limit errors and the full error-code reference.

How do I health-check the API without a key?#

Send a GET request to /ping. It skips authentication and returns the plain string pong, so it is a lightweight way to confirm the API is reachable from your network — for example, in an uptime monitor or a deploy smoke test:

curl "https://api.apitube.io/ping"

A pong response means the API is up and answering. If /ping times out or returns a 500, the problem is not your API key (this endpoint needs none) — check the status page next. Because /ping needs no authentication, it does not touch your quota or count as a billed request.

How do I check my own account status?#

Many “errors” are simply an empty balance. Before blaming an outage, confirm your account still has requests to spend by calling the authenticated balance endpoint:

curl "https://api.apitube.io/v1/balance?api_key=YOUR_API_KEY"

You can send the key as a header (X-API-Key: YOUR_API_KEY) instead of the api_key query parameter. If this returns your balance normally but your data calls still fail with 402, you are out of requests; if it fails with 401, the key itself is the problem. See how to check your balance via the API for the full response shape.

Common Questions#

• Is the APITube API down right now?
• How do I tell a rate-limit ban from a real outage?
• Can I monitor APITube uptime automatically?

Is the APITube API down right now?#

Check two things. Open https://status.apitube.io for the current operational status and any active incidents, and call GET /ping to see whether the API answers with pong from your own network. If /ping succeeds but a specific request fails, the problem is that request — read its HTTP code (401, 402, 403, or 429), not a platform outage.

How do I tell a rate-limit ban from a real outage?#

By the error code. A rate-limit ban returns 429 with ER0204 and a “temporarily banned” message after repeated limit violations; it lifts automatically once you back off. A real outage shows up as 500 (ER0183, “Something went wrong.”) across many requests, and is what the status page reports. A 429 is never an outage — it is a signal to reduce your request rate.

Can I monitor APITube uptime automatically?#

Yes. Point an uptime monitor at https://api.apitube.io/ping and treat any non-pong response — a timeout or a 5xx — as down. Because /ping needs no API key and does not consume quota, it is safe to poll on a schedule. For overall status and incident history, watch the status page at https://status.apitube.io.