Website down checker / ideogram.ai
Is ideogram.ai down right now?
No, ideogram.ai is up.
- Status
- Up
- Reachable from
- 16 of 16 locations
- Typical response
- 244 ms Good
- Slowest location
- Singapore · 319 ms Good
- Last checked
Probes this hostname from 16 locations. The live link always shows the latest check; a check link stays as it is for 90 days.
QuickStatus is not affiliated with Ideogram.
How fast it feels to visitors
Good in all 16 locations. Visitors won't notice a server delay.
The server sends its first byte in 112 ms (Ashburn) to 319 ms (Singapore). Up to 800 ms, the server isn't what makes the page feel slow. Above that, visitors look at a blank screen long enough to notice.
Fastunder 200 ms
5 locations
Feels instant. The server adds no wait a visitor would notice.
Good200–800 ms
11 locations
Within Google's good range. Most of the wait is the page loading, not the server.
Noticeable0.8–1.8 s
0 locations
Visitors notice a blank wait before anything appears. Google rates this as needing improvement.
Slowover 1.8 s
0 locations
Google rates this poor. With loading on top, the page misses the 2.5 s target for showing its main content.
Response time by location
Americas
- Ashburn us-east-1112 msFast200 OK
- Columbus us-east-2138 msFast200 OK
- San Francisco us-west-1131 msFast200 OK
- Portland us-west-2177 msFast200 OK
- Montreal ca-central-1119 msFast200 OK
- São Paulo sa-east-1215 msGood200 OK
Europe
- Dublin eu-west-1226 msGood200 OK
- London eu-west-2244 msGood200 OK
- Paris eu-west-3231 msGood200 OK
- Frankfurt eu-central-1255 msGood200 OK
- Stockholm eu-north-1248 msGood200 OK
Asia Pacific
- Tokyo ap-northeast-1283 msGood200 OK
- Seoul ap-northeast-2274 msGood200 OK
- Osaka ap-northeast-3273 msGood200 OK
- Singapore ap-southeast-1319 msGood200 OK
Oceania
- Sydney ap-southeast-2301 msGood200 OK
Time from connecting to the first response byte (TCP, TLS and server time, DNS excluded) on a fresh connection from a cloud data center. Visitors on home or mobile networks wait longer. Thresholds follow Google's TTFB guidance (good up to 0.8 s, poor above 1.8 s).
How to read this check
- When do visitors start noticing a slow site?
- The number per location is how long the server takes to send its first byte. Up to about 800 ms, the server isn't what makes a page feel slow. Past 800 ms, visitors look at a blank screen long enough to notice. Past 1.8 s, Google rates server response as poor, and with loading on top the page can't show its main content within Google's 2.5 s target.
- Fast in one place, slow everywhere else
- Response time grows with distance from the server. If one city is fast and the rest climb steadily, the page is served from a single region. A CDN that caches the page, or a second region, brings far-away visitors closer to the fast number.
- All 16 regions failing
- The hostname is failing from every probe location. That usually means the origin is down, the TLS certificate has expired, or authoritative DNS is not answering. It is not a problem on one network path.
- One region or continent failing
- When a single city or one continent is offline and the rest return HTTP 200, the origin is up. The failure is usually a CDN or anycast edge route, or a regional cloud impairment between that probe and the site.
- All 16 regions return 200, but it fails in your browser
- The site is reachable from our probes. A local failure is usually a stale ISP DNS cache, a corporate firewall or VPN, or a browser extension blocking the request.
- HTTP 403 or 429 from the probes
- A 403 or 429 from many cloud probes often means a WAF or Cloudflare bot challenge is blocking AWS IP ranges. That is not the same as an application outage. Compare the status code with what your browser receives.
Need to know when something goes down?
Monitor any endpoint on a schedule and get Slack, Discord, PagerDuty, or webhook alerts. Free checks run every 5 minutes. Pro can check every 60 seconds.