Incident Report: February 9, 2026

Overview

Composio experienced a disruption to our X (Twitter) integration due to changes to the X API policy and related platform enforcement actions. Users relying on the Twitter integration saw authentication failures during this period.

Impact Summary

• Twitter integration is unavailable for affected users

• Authentication failures for Twitter-dependent workflows

• No data loss or security implications

Root Cause

To simplify the developer experience, Composio provided managed Twitter credentials so users did not need to set up their own API keys. X recently moved to a pay-per-use pricing model and updated platform policies, which affected this approach and required us to change how users authenticate with the X API.

Incident Timeline (February 9-12, 2026)

• Feb 9, 2026: X API policy changes impacted our Twitter integration

• Feb 10, 2026: Issue identified and investigated

• Feb 10, 2026: Status page updated, support responses initiated

• Feb 12, 2026: Resolution path confirmed; migration plan communicated

Preventative Measures

• Enhanced monitoring for third-party API policy and enforcement changes

• Improved incident communication workflows

• Updated authentication model for the Twitter integration

What’s Changed

The Twitter integration now requires users to provide their own X Developer credentials. This change aligns with X’s updated platform policies.

To continue using Twitter

1. Create an X Developer account at developer.x.com

2. Follow our setup guide at composio.dev/auth/twitter

3. Reconnect to Twitter in your dashboard

X has made developer access easier to obtain, and setup is straightforward.

Questions? Contact support@composio.dev