User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is TwitterAPI.io down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → twitterapi.io—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 170 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 222 ms | 0 |
| Mon 14 | 0 | 0.0 | 84 ms | 0 |
| Mon 16 | 0 | 0.0 | 124 ms | 0 |
| Mon 18 | 0 | 0.0 | 224 ms | 0 |
| Mon 21 | 0 | 0.0 | 94 ms | 0 |
| Mon 23 | 0 | 0.0 | 134 ms | 0 |
| Tue 01 | 0 | 0.0 | 103 ms | 0 |
| Tue 03 | 0 | 0.0 | 116 ms | 0 |
| Tue 05 | 0 | 0.0 | 109 ms | 0 |
| Tue 07 | 0 | 0.0 | 85 ms | 0 |
| Tue 09 | 0 | 0.0 | 108 ms | 0 |
| Tue 11 | 0 | 0.0 | 124 ms | 0 |
| Tue 14 | 0 | 0.0 | 115 ms | 0 |
| Tue 16 | 0 | 0.0 | 126 ms | 0 |
| Tue 18 | 0 | 0.0 | 113 ms | 0 |
| Tue 20 | 0 | 0.0 | 64 ms | 0 |
| Tue 23 | 0 | 0.0 | 106 ms | 0 |
| Wed 01 | 0 | 0.0 | 249 ms | 0 |
| Wed 03 | 0 | 0.0 | 78 ms | 0 |
| Wed 05 | 0 | 0.0 | 100 ms | 0 |
| Wed 08 | 0 | 0.0 | 87 ms | 0 |
| Wed 10 | 0 | 0.0 | 175 ms | 0 |
| Wed 12 | 0 | 0.0 | 108 ms | 0 |
| Wed 14 | 0 | 0.0 | 200 ms | 0 |
| Wed 16 | 0 | 0.0 | 114 ms | 0 |
| Wed 19 | 0 | 0.0 | 266 ms | 0 |
| Wed 21 | 0 | 0.0 | 112 ms | 0 |
| Wed 23 | 0 | 0.0 | 158 ms | 0 |
| Thu 01 | 0 | 0.0 | 133 ms | 0 |
| Thu 03 | 0 | 0.0 | 103 ms | 0 |
| Thu 05 | 0 | 0.0 | 108 ms | 0 |
| Thu 08 | 0 | 0.0 | 167 ms | 0 |
| Thu 10 | 0 | 0.0 | 106 ms | 0 |
| Thu 12 | 0 | 0.0 | 139 ms | 0 |
| Thu 14 | 0 | 0.0 | 119 ms | 0 |
| Thu 16 | 0 | 0.0 | 134 ms | 0 |
| Thu 18 | 0 | 0.0 | 175 ms | 0 |
| Thu 20 | 0 | 0.0 | 92 ms | 0 |
| Thu 22 | 0 | 0.0 | 95 ms | 0 |
| Fri 00 | 0 | 0.0 | 168 ms | 0 |
| Fri 02 | 0 | 0.0 | 97 ms | 0 |
| Fri 04 | 0 | 0.0 | 131 ms | 0 |
| Fri 06 | 0 | 0.0 | 216 ms | 0 |
| Fri 08 | 0 | 0.0 | 72 ms | 0 |
| Fri 10 | 0 | 0.0 | 201 ms | 0 |
| Fri 12 | 0 | 0.0 | 80 ms | 0 |
| Fri 14 | 0 | 0.0 | 191 ms | 0 |
| Fri 16 | 0 | 0.0 | 170 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live TwitterAPI.io badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for TwitterAPI.io yet. Outages of 10 minutes or more get their own page here.
Having trouble with TwitterAPI.io?
One report per service every 10 minutes from this network. No account.
Follow TwitterAPI.io
Get an email when TwitterAPI.io goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send TwitterAPI.io alerts to Slack, Discord or a webhook — free.
About TwitterAPI.io
We track TwitterAPI.io (twitterapi.io) as part of the AI group. Public social data API for developers and AI agents — read user feeds, search posts, and publish with predictable per-call pricing. No minimums.
TwitterAPI.io publishes an official status page at status.twitterapi.io; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 144 ms average, 72–302 ms range across 14 successful checks.
Questions
Is TwitterAPI.io down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was TwitterAPI.io last down?
We have not recorded a public TwitterAPI.io incident since monitoring began 7 days ago.
What is TwitterAPI.io's uptime?
From our own checks: 100% over 7 days of checks.
How fast does TwitterAPI.io respond?
144 ms on average over the last 24 hours (72–302 ms).
Does TwitterAPI.io have an official status page?
Yes, at https://status.twitterapi.io.
TwitterAPI.io not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report TwitterAPI.io here at once, the problem is on TwitterAPI.io's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with TwitterAPI.io. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.