Website down checker / fauna.com
Is fauna.com down right now?
Yes, fauna.com is down from all 16 locations.
- Status
- Down
- Reachable from
- 0 of 16 locations
- Typical response
- —
- Slowest location
- —
- 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 Fauna.
Response time by location
Americas
- Ashburn us-east-1—DownDown · Timed out with no response
- Columbus us-east-2—DownDown · Timed out with no response
- San Francisco us-west-1—DownDown · Timed out with no response
- Portland us-west-2—DownDown · Timed out with no response
- Montreal ca-central-1—DownDown · Timed out with no response
- São Paulo sa-east-1—DownDown · Timed out with no response
Europe
- Dublin eu-west-1—DownDown · Timed out with no response
- London eu-west-2—DownDown · Timed out with no response
- Paris eu-west-3—DownDown · Timed out with no response
- Frankfurt eu-central-1—DownDown · Timed out with no response
- Stockholm eu-north-1—DownDown · Timed out with no response
Asia Pacific
- Tokyo ap-northeast-1—DownDown · Timed out with no response
- Seoul ap-northeast-2—DownDown · Timed out with no response
- Osaka ap-northeast-3—DownDown · Timed out with no response
- Singapore ap-southeast-1—DownDown · Timed out with no response
Oceania
- Sydney ap-southeast-2—DownDown · Timed out with no response
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.