Skip to main content

Is Civitai Down?

No — Civitai is up

Reachable from all 8 checked regions

Average response time: 566ms

Last checked · checks run every 6 hours

Official status page: https://status.civitai.com

Civitai uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
616ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 21 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

21-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: 100.00% uptime, 31 checks
Aug 4: 100.00% uptime, 24 checks
Aug 5: 100.00% uptime, 32 checks
Aug 6: 100.00% uptime, 31 checks
Aug 7: 100.00% uptime, 31 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 40 checks
Aug 11: 100.00% uptime, 31 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 31 checks
Aug 17: 100.00% uptime, 32 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 31 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 24 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
658ms
DNS 0ms TCP 2ms TLS 16ms TTFB 211ms
arn
751ms
DNS 0ms TCP 1ms TLS 12ms TTFB 230ms
bom
1001ms
DNS 0ms TCP 3ms TLS 14ms TTFB 531ms
ord
275ms
DNS 0ms TCP 2ms TLS 15ms TTFB 119ms
sin
774ms
DNS 0ms TCP 39ms TLS 48ms TTFB 318ms
sjc
99ms
DNS 0ms TCP 2ms TLS 13ms TTFB 80ms
syd
653ms
DNS 0ms TCP 2ms TLS 12ms TTFB 359ms
yyz
317ms
DNS 1ms TCP 1ms TLS 11ms TTFB 127ms

What Civitai does

Civitai is a community platform for sharing AI image models, hosting checkpoints and LoRAs that people download or run directly on the site. It combines a large media library with model hosting and an on-site generation service, so it acts as both a content site and an inference provider for the open-weights image community.

What an outage looks like

Civitai splits into unusually many components and partial failure is the norm. Search can degrade while the main site loads. Image delivery and file delivery are tracked separately, so browsing a gallery can work while model downloads fail. The job subsystem that runs on-site generation has its own line, which makes a stalled generation queue a different incident from a slow gallery.

What to do about it

Check status.civitai.com, which reports the main site, the API, search, image delivery, file delivery, the job subsystem, a link service and Discord model announcements, each with its own percentage. The page refreshes on a five-minute cycle, so a very recent problem may not appear yet. If file delivery is the affected component, retry a failed model download after recovery rather than reporting it.

Is it down for everyone, or just you?

If this page says Civitai is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Civitai outage FAQ

Why do images load but model downloads fail on Civitai?
Image delivery and file delivery are separate components on Civitai's status page. Thumbnails and previews come through one path and the large model files through another, so a gallery that browses normally tells you nothing about whether a checkpoint will download. Read the file delivery line specifically when a download stalls or stops partway.
Is on-site generation down, or just slow?
Civitai tracks a job subsystem as its own component, and that is what queues and runs on-site generation. If that line is degraded while the main site is healthy, generations will queue rather than fail outright, so a request that looks stuck may simply be waiting its turn. The page shows a percentage for it rather than only up or down.
How current is Civitai's status page?
It refreshes on a five-minute cycle and displays when it was last updated. That is frequent by status-page standards, but it means a problem that began moments ago may not appear yet, and a recovery can show late. Treat a green page during an obvious failure as possibly stale rather than as proof nothing is wrong.
What is the Discord model announcements component?
It is the service that posts new model announcements into Discord, and Civitai tracks it separately from the site itself. It can fail while everything else works, so announcements stop arriving in Discord without the website showing any problem at all. It is a good illustration of how granular this particular status page is.

How we measure this

  • We request Civitai's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Civitai publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Civitai goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required