Vendor Status Watch

← all vendors

Gandi status history

Current state: operational — “All Systems Operational” per https://status.gandi.net (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

7incidents, last 30 days
15incidents, last 90 days
56incidents on record
Incidents per week, last 12 weeks:

How long do Gandi incidents last?

2.6 hmedian incident duration52 measured
20.5 h90th percentile1 in 10 ran longer
2.2 hmedian, major/critical only29 incidents

From 52 incidents with a vendor-posted start and resolve time. Longest on record: .cz domain operations unavailable — 4.0 days (2026-07-10 15:08 UTC). Excluded, never estimated: 4 scheduled maintenance. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (56)

StartedIncidentStatusImpactDuration
2026-09-15 12:00 UTC[OT&E] Registry nicat maintenancemaintenancemaintenance24 h 28 min (approx.)
2026-09-10 12:54 UTCPaaS maintenance in LU-BI1resolvedmaintenance27 h 09 min
2026-09-10 12:00 UTCPaaS maintenance in FR-SD5maintenancemaintenance24 h 29 min (approx.)
2026-09-09 16:59 UTC503 error on some webhosting instancesresolvedmajor3 h 44 min
2026-09-09 11:00 UTCPaaS maintenance in FR-SD6maintenancemaintenance25 h 15 min (approx.)
2026-09-07 18:57 UTCSlowness on change_owner domain operationsresolvedminor20 h 32 min
2026-09-03 15:04 UTCNotifications of 2FA emails delayed for the momentresolvedminor1 h 38 min
2026-08-11 08:34 UTCStorage unit issue in FR-SD6resolvedminor5 h 10 min
2026-08-11 08:15 UTCGandimail admin errorsresolvedmajor1 h 29 min
2026-07-29 08:26 UTC.pm, .re, .tf, .wf and .yt operations unavailableresolvedmajor1 h 39 min
2026-07-21 13:31 UTCDomain name availability issueresolvedminor1 h 35 min
2026-07-10 15:08 UTC.cz domain operations unavailableresolvedminor3 d 22 h
2026-07-08 08:38 UTCStorage unit failure at sd 6resolvedmajor42 min
2026-06-24 09:34 UTCSD5 storageresolvedmajor2 h 54 min
2026-06-22 09:02 UTC.pt domain operations unavailableresolvedmajor3 h 15 min
2026-05-12 10:28 UTCLive DNS update latencyresolvedminor18 min
2026-04-23 08:31 UTCIssue on a storage unitresolvedminor16 min
2026-04-17 12:00 UTC.fi domain operations unavailableresolvedminor59 min
2026-04-16 09:03 UTC.fr registry incident (.re, .tf, .wf, .yt, .pm)resolvedmajor3 h 15 min
2026-03-24 12:33 UTCLU-BI1 PaaS slownessresolvedminor8 h 39 min
2026-03-19 12:08 UTCDDoS on sd3resolvedminor3 h 00 min
2026-03-18 13:00 UTCIssue on a storage unitresolvedmajor41 min
2026-03-09 08:42 UTC.as domain Registration operation temporarily unavailableresolvednone24 h 26 min
2026-02-06 09:15 UTCStorage unit failure at SD5resolvedmajor6 h 08 min
2026-01-27 09:29 UTCSome Vms are unreachable on SD5resolvedmajor1 h 18 min
2026-01-27 06:50 UTCData center power redundancy unavailableresolvednone2 d 6 h
2026-01-20 14:13 UTCMail access issueresolvedmajor32 min
2026-01-13 00:17 UTC.tc registry incidentresolvedmajor5 h 37 min
2026-01-11 19:30 UTC.tc registry incidentresolvedmajor16 h 01 min
2026-01-09 13:55 UTCEmergency maintenance on a storage unitresolvedmajor1 h 31 min
2025-12-19 14:37 UTCDDoS on going on sd6 PaaSresolvedminor2 h 21 min
2025-12-18 13:57 UTCDDoS on going on sd6 PaaSresolvedminor3 h 12 min
2025-12-16 10:34 UTCDatabase incidentresolvednone8 h 51 min
2025-12-09 08:25 UTCWebHosting Compute nodes maintenanceresolvedminor8 h 36 min
2025-12-08 13:57 UTCSimple Hosting Compute hosts maintenanceresolvedmajor2 h 26 min
2025-12-01 08:56 UTCWe are having a slowdown in domain operationresolvedminor24 h 24 min
2025-11-27 13:45 UTCDomain update delayedresolvedminor1 h 58 min
2025-11-21 09:59 UTCSimple hosting incident at BI1resolvedmajor4 h 40 min
2025-11-19 03:39 UTCWe have timeout issue on our platformresolvedmajor5 h 16 min
2025-11-13 12:21 UTCWeb redirection incidentresolvedmajor3 h 08 min
2025-11-10 09:57 UTCWe are experiencing an issue on some of the mailboxesresolvedmajor3 h 02 min
2025-11-08 02:47 UTCSD6 storageresolvedmajor48 min
2025-11-05 21:33 UTCSD3 network incidentresolvedmajor41 min
2025-10-30 08:09 UTCWe have an issue with a small part of our email platformresolvedminor37 min
2025-10-22 09:15 UTCWe are experiencing issues on the billing operationresolvedmajor34 min
2025-10-08 12:16 UTCpartial outage on public website portalresolvedcritical2 h 50 min
2025-10-05 15:41 UTCBI1 storageresolvedmajor17 min
2025-10-02 05:18 UTCFiler issue on Luxembourg datacenterresolvedmajor2 h 12 min
2025-09-24 14:08 UTCIssue with .space registryresolvedminor19 h 13 min
2025-09-17 15:31 UTCZone update delaysresolvedminor1 h 48 min
2025-09-15 09:20 UTCSimple Hosting Compute node failureresolvedmajor19 min
2025-09-08 08:26 UTCIaaS Compute node failureresolvedmajor33 min
2025-09-06 14:35 UTCLuxemburg Network incident affecting storageresolvedmajor14 h 56 min
2025-09-02 17:18 UTCSD3 PaaS issueresolvedmajor1 h 28 min
2025-09-02 08:36 UTCNetwork incidentresolvedminor1 h 12 min
2025-08-25 15:44 UTCmirrors.gandi.net ipv6 downresolvednone3 d 22 h

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Gandi with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "gandi"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}