# TwitterAPIs Status and API Health Check Canonical: https://www.twitterapis.com/status Description: Check whether the TwitterAPIs X data API is answering right now. A live probe of the public health endpoint, plus how to monitor it from your own systems. Generated: 2026-09-14T03:00:37.947Z --- 1. [Home](/) 2. / Status STATUS # TwitterAPIs status ## How do I check whether the TwitterAPIs API is up right now? This status page gives you a live check rather than stored history. Loading it calls the public health endpoint on the API host and shows the HTTP status, the round trip time, and what the service reported for itself. There is no historical uptime percentage published, because a percentage without a stated window and probe is a decoration rather than a measurement. ## Checking the API now This is a single live request made when you loaded the page, repeated once a minute while the page is open. It reports what the API did just now. It is not a rolling average and it carries no history. ## Why there is no uptime percentage on this page An uptime figure is only meaningful when you can see three things: the window it covers, the probe that produced it, and what counted as a failure. A percentage printed without those is a decoration, and it is the kind of decoration that gets quoted back years after anybody checked it. We do not publish a measured history yet, so this page shows you a live probe you can repeat, and names the endpoint so you can run the same check yourself on your own schedule and keep your own series. When a published history exists it will appear here with its window and its method stated. ## Run the same check yourself The health endpoint is public. It takes no key, returns JSON, and is not a billed call, so it is safe to poll from an uptime service or a scheduled job. Treat a non-200, a timeout, or an unparseable body as a failure. curl -s -o /dev/null -w "%{http\_code} %{time\_total}s\\n" \\ https://api.twitterapis.com/health A 200 means the service answered. If you are debugging a call that fails while this check passes, the problem is on the request rather than the service, and the [REST API reference](/twitter-rest-api) covers what each status code means. A 401 is a key problem, and the [API key guide](/twitter-api-key) covers where a valid key comes from. ## What to check when something looks wrong ### Every call returns 401 The key is rejected. Confirm the header is Authorization with a Bearer prefix, or x-api-key with the bare value, and that the key has not been rotated out from under a deployed job holding an old copy. ### A lookup returns an empty result That is usually not an outage. A suspended, deleted or renamed account has no object to return, so the endpoint answers successfully with nothing in it rather than raising an error. ### Calls stop mid-job Check the remaining balance on the account endpoints. Billing is per call with no plan minimum, so a long pagination loop can exhaust a small balance without any warning from the loop itself. ### Responses changed shape Read the changelog. Endpoint additions and behaviour changes are recorded there with dates, which is the fastest way to tell a change from a fault. If none of those explain it, the [changelog](/changelog) records what shipped and when, and the [contact page](/contact) reaches a person rather than a queue. ## Frequently Asked Questions ### Is the TwitterAPIs API down? The check at the top of this page answers that for the moment you loaded it. It makes one unauthenticated request to the public health endpoint and reports the HTTP status and the round trip time it measured. A green result means the API answered that request. If you want an answer that does not depend on this page rendering correctly, request the health endpoint yourself, since it needs no key. ### How do I monitor the API from my own systems? Point your monitor at the health endpoint on the API host. It answers without an API key, returns JSON, and does not bill you, so it is safe to poll on a schedule from an uptime service or a scheduled job. Treat a non-200, a timeout, or a body that fails to parse as the failure condition. That is the same signal our own monitoring reads. ### Where do I find out about changes and incidents? The changelog records what shipped and when, including endpoint additions and behaviour changes, which is where a change that broke your integration will be described. For anything that looks like an incident rather than a change, contact the team directly, because a person answers rather than a ticket queue. ### What uptime does TwitterAPIs publish? No historical uptime figure is published today, and the check on this page is a live probe rather than a rolling average. We would rather say that plainly than print a percentage that has no measurement series behind it, because an uptime number is only worth anything when you can see the window it covers and the probe that produced it. A published history is a change we intend to make rather than one already shipped. ### My calls are failing but this page says the API is answering. Why? The health endpoint is unauthenticated, so a green check confirms the service is reachable and serving, not that your particular request is valid. The three common causes are a rejected key, which returns 401, a request for an account that no longer exists, which returns an empty result rather than an error, and an exhausted balance. The account endpoints report your remaining credit, and support can confirm a key from our side. [Read the changelog](/changelog)[Start Free](/signup?utm_source=aio&utm_medium=organic&utm_campaign=aeo-status) [ TwitterAPIs ](/) The cheapest pay-as-you-go Twitter and X API. $0.0008 per call, which works out to $0.04 per 1,000 tweets on a full 20-tweet page. No subscriptions and no developer account. ## Product / API - [Pricing](/pricing) - [Cost Calculator](/twitter-api-cost-calculator) - [Rate Limits](/twitter-api-rate-limits) - [MCP Server](/mcp) - [Integrations](/integrations) - [Language Clients](/sdk) - [Changelog](/changelog) - [Status](/status) ## Developers - [Documentation](https://docs.twitterapis.com) - [API Reference](https://docs.twitterapis.com/docs/reference/search/tweet-advanced-search) - [User Info](https://docs.twitterapis.com/docs/reference/user-reads/user-info) - [User Tweets](https://docs.twitterapis.com/docs/reference/user-reads/user-tweets) - [Advanced Search](https://docs.twitterapis.com/docs/reference/search/tweet-advanced-search) - [Verified Followers](https://docs.twitterapis.com/docs/reference/follower-graph/user-verified-followers) ## Resources / Compare - [Answers](/answers) - [Reviews](/reviews) - [Free Tools](/tools) - [Twitter ID Finder](/tools/twitter-id-finder) - [Get a Twitter API Key](/twitter-api-key) - [Official X API Comparison](/twitter-api-pricing) - [Twitter API Use Cases](/twitter-api-usecases) - [Twitter API Alternatives](/twitter-api-alternatives) - [Twitter Unofficial API](/twitter-unofficial-api) - [Twitter Free API](/twitter-free-api) - [TwitterAPIs vs twitterapi.io](/twitterapis-vs-twitterapi-io) - [TwitterAPIs vs GetXAPI](/twitterapis-vs-getxapi) - [TwitterAPIs vs TweetAPI](/twitterapis-vs-tweetapi) - [TwitterAPIs vs TwexAPI](/twitterapis-vs-twexapi) - [TwitterAPIs vs RapidAPI](/twitterapis-vs-rapidapi) ## Legal - [About](/about) - [Security](/security) - [Trust](/privacy-and-data-handling) - [Terms of Service](/terms-of-service) - [Affiliates](/affiliates) - [Contact](/contact) - [Jobs](/jobs) © 2026 TwitterAPIs. All rights reserved. TwitterAPIs is an independent third-party API for developers and researchers. Not affiliated with, endorsed by, or sponsored by X Corp. All systems operational