Twitter API Status

All Systems Operational
Enterprise Volume Streams & PowerTrack ? Operational
Enterprise and Premium Historical APIs ? Operational
Enterprise and Premium Account Activity API ? Operational
Enterprise Engagement API ? Operational
Enterprise Usage API ? Operational
Ads API ? Operational
Standard endpoints ? Operational
Standard statuses/update endpoints Operational
Media endpoints ? Operational
v2 streaming Tweets endpoints Operational
v2 RESTful Tweets endpoints Operational
v2 RESTful users endpoints Operational
Premium billing ? Operational
Twitter Developer Labs ? Operational
Enterprise Console ? Operational
Developer Portal ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jan 18, 2021

No incidents reported today.

Jan 17, 2021

No incidents reported.

Jan 16, 2021

No incidents reported.

Jan 15, 2021

No incidents reported.

Jan 14, 2021

No incidents reported.

Jan 13, 2021

No incidents reported.

Jan 12, 2021
Resolved - This incident has been resolved. Failed queries can now be retried. The impacted timeframe was 14:43:00 UTC - 16:19:00 UTC
Jan 12, 16:29 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 12, 16:23 UTC
Investigating - We're experiencing an elevated level of API errors starting around 14:43 UTC and are currently investigating. Customers will experience degraded Success Rate when making requests on the Engagement API and v2 metrics, leading to a greater likelihood of failures.
Jan 12, 15:52 UTC
Jan 11, 2021

No incidents reported.

Jan 10, 2021

No incidents reported.

Jan 9, 2021

No incidents reported.

Jan 8, 2021

No incidents reported.

Jan 7, 2021

No incidents reported.

Jan 6, 2021

No incidents reported.

Jan 5, 2021

No incidents reported.

Jan 4, 2021
Resolved - Systems have been monitored over the past two weeks and metrics have stabilized and improved.
Jan 4, 19:29 UTC
Monitoring - Job processing times continue to be stable, but may still be taking longer than normal. If you’re seeing an increase in 400 TOO_MANY_JOBS errors, please make sure you are using the x-concurrent-job-limit and x-concurrent-job-limit-remaining response headers (introduced in v6) to manage your asynchronous analytics job create requests. Similarly, use the x-rate-limit-limit, x-rate-limit-remaining, and x-rate-limit-reset response headers to avoid the 429 (Too Many Requests) error.
Dec 16, 18:04 UTC
Identified - We are aware of service issues related to our asynchronous analytics endpoints. This began late last week and is affecting job processing times and job success rates. You may see an increase in 429s.
Dec 14, 19:35 UTC