Increased Error Rates
238 days open on the official status source
On the official feed, AWS appears in 2 open incidents, all of them open for months. It may not be you.
Email alerts for this stack
One link confirms your address and turns them on. No password or card.
Already have an account, or sign in with GitHub or Google? Turn this board into alerts there.
Each row is the status published on the official source OutageDeck reads for that vendor. The check time and direct source link stay visible so you can verify it yourself.
Straight from the official incident source for each vendor, newest update first. An entry annotated with its age has been open past two weeks, which usually means nobody closed it.
Increased Error Rates
238 days open on the official status source
Increased connectivity issues and API Error Rates
237 days open on the official status source
OutageDeck re-reads the official status feed of all 180 tracked providers about every 10 minutes and stores what it finds. This board simply shows you the subset you chose. Green means none of those vendors has acknowledged an incident in its official feed. It does not mean your region, tenant, or request path is healthy. If OutageDeck or a vendor feed stops refreshing, the check time exposes that. A read failure is never converted into a provider outage. Browse every tracked provider or set up alerts so the next one finds you instead.
Want this board somewhere your team already looks? Turn it into a status wall: one line of Markdown for a README, wiki, or dashboard, and it keeps itself current.
Using a coding agent? The same verdict is one tool call away: connect the MCP server and your agent can ask "is it us or them?" mid-task, before it starts tearing apart your code.
A stack board holds up to 12 vendors and nothing about it is stored. Reload it, bookmark it, or paste it into your incident channel.