Ideogram Outage History
20 incidents recorded over the last 365 days, 20 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Ideogram Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 1, 2026 | Outage on 3.0This incident has been resolved. | 38 min | Resolved |
| Oct 21, 2026 | OutageCleared | 2h 25m | Resolved |
| Oct 21, 2026 | OutageCleared | 2h 42m | Resolved |
| Oct 20, 2026 | Outagecleared | 20 min | Resolved |
| Oct 2, 2026 | Outage on all modelsThis incident has been resolved | 21 min | Resolved |
| Sep 29, 2026 | Outage on v3 endpointsThe incident has been resolved | 9 min | Resolved |
| Sep 24, 2026 | Outage on ideogram v3This incident is resolved | 17 min | Resolved |
| Sep 23, 2026 | Outage on Ideogram v3 endpointsThis incident is resolved | 16 min | Resolved |
| Sep 4, 2026 | Outage on v3 EndpointsThis incident has been resolved. | 43 min | Resolved |
| Aug 29, 2026 | Outage on Ideogram Reframe v3This incident has been resolved. | 23 min | Resolved |
| Jul 27, 2026 | Complete outage on 3.1 and its variantsThis incident has been resolved. | 49 min | Resolved |
| Jul 16, 2026 | Major Outage: High latencies on v4 endpointsThis incident has been resolved | 10 min | Resolved |
| Jun 1, 2026 | Outage on ideogram v3This incident has been resolved. | 33 min | Resolved |
| Mar 17, 2026 | Major OutageThis incident has been resolved. | 24 min | Resolved |
| Feb 3, 2026 | Outage on v2.0This incident has been resolved | 5 min | Resolved |
| Dec 5, 2025 | Complete OutageThis incident has been resolved | 12 min | Resolved |
| Dec 3, 2025 | Outage on v3 and v2This incident has been resolved. | 2h 41m | Resolved |
| Nov 17, 2025 | Major outageThis incident has been resolved. | 1h 4m | Resolved |
| Nov 13, 2025 | Outage on v3 generateThe incident has been resolved | 1h 33m | Resolved |
| Nov 6, 2025 | Outage on character reference based generation requestsOur API for character reference conditioned generations has returned to normal operation. | 28 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Ideogram incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Ideogram Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Ideogram acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Ideogram outage in this window ran 2h 42m, against a mean recovery of 49 min. If you depend on Ideogram in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.