Social Snipe

We are aware of an SSL issue on our API and are in the process of fixing it. This issue does not pose a threat to account security.

Here is the original post:

SSL Issue

Many users are receiving incorrect “Rate Limit Exceeded” errors through the Twitter API. We are investigating the cause and will update when it is resolved.

Read this article:

Investigating "Rate Limit Exceeded" issues

We’re hearing reports from developers that they’re running into some incorrect rate limits; we’re looking into it.

Go here to read the rest:
Incorrect Rate-Limiting

We’re working to resolve an issue with the mobile website, http://mobile.twitter.com.

UPDATE: Resolved at 15:31 UTC / 8:31 PDT.

Go here to read the rest:

Mobile Website

Some users are experiencing an issue in which they’re not receiving all of their @ replies; we’re working on a fix.

Visit link:

Missing @ Replies

We’ve received reports of elevated error rates for users; we’re currently investigating.

Read more:
Investigating Elevated Error Rates

We are experiencing an issue temporarily with the intermediary SSL certificate for the API; we expect the issue to be resolved shortly. In the meantime, you may experience issues using the API; we’re working to resolve the issue now.

Update (8:22 AM PST, 15:22 UTC): This issue is resolved.

Here is the original post:

API issues.

We’ll be making adjustments to some site features throughout the day in an attempt to maximize site availability and stability.

RSS and Atom feeds are currently disabled.

Update (8:05 AM PST, 15:05 UTC): API is temporarily rate-limited to 175.

Read more:

Site Tweaks

Dealing with high whales (errors) as the result of high load. Ops and engineering are responding. Also go #usa!

Follow this link:

Dealing with high whales (errors) as the result of high load.

We’re seeing periodic high rates of errors on Twitter.com.

See more here:
Periodic high rates of errors on Twitter.com