twitterapi.io
Docs
Pricing
DashboardStream
system_status: operationalview status
[ TwitterAPI.io ]

Enterprise-grade public data API that powers your decision-making with real-time social intelligence.

[ resources ]
  • Pricing
  • Blog
  • Docs
  • Affiliate Program
[ support ]
  • Contact Us
  • Payment
[ product ]
  • X API Reference
  • Twitter MCP Server
[ legal ]
  • Privacy Policy
  • Terms of Service
  • Refund Policy
  • Acceptable Use Policy

TwitterAPI.io is an independent third-party service. Not affiliated with, endorsed by, or sponsored by X Corp. "Twitter" and "X" are trademarks of X Corp.

© 2026 TwitterAPI.io // operated by Prism Digital, LLC · 131 Continental Dr Suite 305, Newark, DE 19713, US // all rights reserved

stripe_climate
    [ Service status ]

    All systems operational

    TwitterAPI.io is monitored every 60 seconds from eight global regions. Below is the live rollup of our public API, Stream, MCP server, dashboard, docs and webhook delivery.

    Uptime (30 days)
    99.98%
    Avg response time
    612 ms
    Active incidents
    0
    [ Components ]

    Service components

    Twitter / X REST API

    Core REST endpoints — user, tweets, followers, search

    Operational

    Twitter Stream (WebSocket)

    Real-time tweet / reply / mention delivery

    Operational

    Webhook Delivery

    Outbound webhook callbacks for Stream subscriptions

    Operational

    MCP Server

    Model Context Protocol server for AI agents

    Operational

    Dashboard

    Account, billing, API-key and usage dashboards

    Operational

    Documentation

    docs.twitterapi.io API reference and guides

    Operational
    [ Incident history ]

    Recent incidents

    1. Scheduled database maintenance

      Resolved

      Rolling PostgreSQL upgrade on the primary analytics cluster. API traffic unaffected; dashboard load times briefly slower on the second window.

      Started · October 12, 2026 — 02:00 UTCResolved · October 12, 2026 — 04:12 UTC
    2. Upstream X API elevated error rate

      Resolved

      X served 429 and 5xx responses for about 40 minutes. Our rate-limit shaper absorbed most of the impact; a small fraction of tweet-fetch calls retried with increased latency.

      Started · October 05, 2026 — 18:47 UTCResolved · October 05, 2026 — 19:28 UTC
    3. WebSocket Stream reconnect storm

      Resolved

      A transient DNS blip on one edge POP caused connected Stream clients to drop and reconnect within the same minute. All reconnects succeeded; no tweets were dropped (buffer flushed on reattach).

      Started · September 24, 2026 — 09:14 UTCResolved · September 24, 2026 — 09:17 UTC

    Historical incidents are retained for 365 days. Older entries are archived; email hello@twitterapi.io for a specific window.

    [ Stay informed ]

    Subscribe to updates

    Email alerts

    Get an email when a new incident is posted or when a monitored component changes state. One address per account.

    Email us to subscribe

    RSS feed

    Pipe status updates into your reader of choice, Slack, or an internal pager. Updates post as soon as they're confirmed.

    RSS feed coming soon

    Monitored from AMS · ASH · GRU · IAD · HKG · LHR · NRT · SIN

    Report a problem that isn't listed: hello@twitterapi.io