Writer
Writer is operational
Checked 2 min ago Operational
History
90 days agoToday
Incidents in 90 days
0
Days with an incident
0
Median duration
No data
Longest incident
No data
Components
49US-1-API Operational
90 days agoNo incidentsToday
US-1-Web-App Operational
90 days agoNo incidentsToday
EU-1-Web-App Operational
90 days agoNo incidentsToday
EU-1-API Operational
90 days agoNo incidentsToday
Amazon Bedrock (eu-west-1) Operational
90 days agoNo incidentsToday
Amazon ElastiCache (eu-west-1) Operational
90 days agoNo incidentsToday
Amazon Elastic Kubernetes Service (eu-west-1) Operational
90 days agoNo incidentsToday
Amazon Elastic Load Balancing (eu-west-1) Operational
90 days agoNo incidentsToday
Amazon EventBridge (eu-west-1) Operational
90 days agoNo incidentsToday
Amazon OpenSearch Service (eu-west-1) Operational
90 days agoNo incidentsToday
Amazon Redshift (eu-west-1) Operational
90 days agoNo incidentsToday
Amazon Relational Database Service (eu-west-1) Operational
90 days agoNo incidentsToday
Amazon Simple Notification Service (eu-west-1) Operational
90 days agoNo incidentsToday
Amazon Simple Queue Service (eu-west-1) Operational
90 days agoNo incidentsToday
Amazon Simple Storage Service (eu-west-1) Operational
90 days agoNo incidentsToday
Amazon Virtual Private Cloud (eu-west-1) Operational
90 days agoNo incidentsToday
AWS Key Management Service (eu-west-1) Operational
90 days agoNo incidentsToday
AWS NAT Gateway (eu-west-1) Operational
90 days agoNo incidentsToday
ec2-eu-west-1 Operational
90 days agoNo incidentsToday
Multiple services (eu-west-1) Operational
90 days agoNo incidentsToday
Amazon ElastiCache (us-east-1) Operational
90 days agoNo incidentsToday
Amazon Elastic Kubernetes Service (us-east-1) Operational
90 days agoNo incidentsToday
Amazon Elastic Load Balancing (us-east-1) Operational
90 days agoNo incidentsToday
Amazon Redshift (us-east-1) Operational
90 days agoNo incidentsToday
No incident in the last 90 days.
Follow Writer
Your coding agent knows when Writer is down, and tells you when a failure is theirs, not yours. You can also get Writer incidents in a feed reader or in Slack.
Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "writer" and tell me if Writer has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
RSS
https://outages.cc/feed.xml?providers=writerSlack
/feed subscribe https://outages.cc/feed.xml?providers=writerGo from tracking outages to fixing production issues with Polylane.
Try Polylane