Ideogram
Ideogram is operational
Checked 2 min ago Operational
History
90 days agoToday
Incidents in 90 days
10
Days with an incident
9
Median duration
22 min
Longest incident
2 h 42 min
Components
2API Operational
90 days ago9 days with an incidentToday
Web App Operational
90 days ago4 days with an incidentToday
Oct 21, 2026
Sep 24, 2026
Follow Ideogram
Your coding agent knows when Ideogram is down, and tells you when a failure is theirs, not yours. You can also get Ideogram 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 "ideogram" and tell me if Ideogram 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=ideogramSlack
/feed subscribe https://outages.cc/feed.xml?providers=ideogramGo from tracking outages to fixing production issues with Polylane.
Try Polylane