Is Gandi Down?

No — Gandi is up

Reachable from all 8 checked regions

Average response time: 962ms

Last checked 3 hours ago · checks run every 6 hours

Official status page: https://status.gandi.net

Gandi uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

875ms

Avg response, 30 days

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

30-day history

9-day clean streak

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

110ms

DNS 0ms TCP 12ms TLS 27ms TTFB 108ms

lax

1120ms

DNS 0ms TCP 138ms TLS 281ms TTFB 1119ms

lhr

102ms

DNS 0ms TCP 11ms TLS 19ms TTFB 101ms

nrt

1746ms

DNS 2ms TCP 216ms TLS 435ms TTFB 1744ms

ord

749ms

DNS 0ms TCP 97ms TLS 192ms TTFB 748ms

sin

1220ms

DNS 0ms TCP 150ms TLS 305ms TTFB 1218ms

sjc

1074ms

DNS 0ms TCP 135ms TLS 275ms TTFB 1072ms

syd

1978ms

DNS 0ms TCP 245ms TLS 494ms TTFB 1976ms

yyz

724ms

DNS 0ms TCP 86ms TLS 176ms TTFB 723ms

What Gandi does

Gandi is a domain registrar that also runs the services many of its customers layer on top: LiveDNS for authoritative DNS, a mail platform with IMAP, POP3, SMTP and two webmail clients, Simple Hosting, cloud servers, SSL certificates and a v4 and v5 API. Because registration, DNS and email sit with one provider, a single Gandi fault can reach several unrelated parts of a business.

What an outage looks like

Domains stop resolving when LiveDNS or the nameservers are affected, which takes sites and email offline together. Mail clients fail to fetch over IMAP or POP3, outbound messages queue when SMTP out is down, and the Roundcube and Sogo webmail clients will not load. The admin portal at admin.gandi.net will not sign in, and registration, renewal and billing operations fail separately from DNS.

What to do about it

Check status.gandi.net, which separates domain name registration, DNS, LiveDNS, individual nameservers, SMTP in and out, webmail, Simple Hosting, Cloud regions, billing and both API versions. DNS faults are the ones with the widest blast radius, so confirm resolution first. Inbound mail to a well-configured domain is normally retried by the sending server for hours, so a short SMTP-in outage delays delivery rather than discarding it.

Is it down for everyone, or just you?

If this page says Gandi 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

Gandi outage FAQ

Is Gandi down or has my domain expired?

These look identical from a browser and are easy to confuse. Check status.gandi.net and the per-region measurements here first. An expired or suspended domain fails consistently from every region and usually resolves to a registrar holding page, while a Gandi service fault tends to appear across regions at once and clears without any change on your side. Your renewal date is in the Gandi admin portal.

Does a Gandi outage stop my email?

It depends which component fails. Gandi tracks SMTP in, SMTP out, IMAP and POP3 access, forwarding and the two webmail clients separately, so you may be able to receive but not send, or lose webmail while a desktop client still works. If DNS is the failing piece, mail stops in both directions because senders cannot resolve your MX records at all.

Will I lose email sent to me during an outage?

Usually not. A sending mail server that cannot deliver normally queues the message and retries over a period of hours before giving up, so a short inbound outage delays mail rather than losing it. That protection is not unlimited: a multi-day failure can push messages past a sender's retry window, and some automated senders give up far sooner than a standard mail server does.

Can I move DNS elsewhere during a Gandi DNS outage?

You can, but it is rarely fast enough to help. Changing nameservers means waiting for the registry and for resolver caches to pick up the change, which typically takes longer than the outage itself. It is worth doing as preparation rather than as a response: keeping a secondary DNS provider configured in advance is what makes a registrar DNS fault survivable.

How we measure this

We request Gandi'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 Gandi 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 Gandi 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