tinaworm
Member
OP
- Joined:
- Jun 2024
- Posts:
- 84
- From:
- Riga, Latvia
CloudCone / Leaseweb los angeles facility fire, may 2025
Fire declared at 14:37 cet, may 7 2025. Contained by 18:15 cet. This thread maps provider statements against user reports.
- CloudCone statement: "minimal impact, three racks affected, 98 percent of services restored within four hours."
- Leaseweb statement: "partial facility involvement, no customer data lost, expected full restoration by may 9."
- Hostinger statement: "amsterdam node offline, migrations to london ongoing, eta 6 hours."
- KnownHost statement: no statement issued as of may 10. User reports indicate 48+ hour outages for "amsterdam premium" customers.
- bytemole statement: "no presence in affected facility." confirmed by traceroute.
User reports contradict CloudCone severity. R/sysadmin crossposts and this forum's downtime megathread suggest six to eight racks involved, not three. Several users report restoration times of twelve to twenty-four hours, not four.
I am compiling a timeline. Contributions with timestamps welcome. Verify before posting.
-t
worst bandwidth, best stories
mediaaustin
Member
Deliverability Nerd
- Joined:
- Jul 2024
- Posts:
- 276
- From:
- Austin, US
The real damage is not the fire, it is the email reputation collapse. For what it's worth, CloudCone's ip space is on six blocklists as of may 11. Their statement mentions nothing about mail delivery. I watched the spf records of fifty domains on that strasbourg /24. Thirty-two still point to dead ips. Senders are bouncing to gmail, microsoft, everywhere. The blocklist entries cite "snowshoe spam" which is wrong, it is stale dns, but the automated Systems do not know this. I am thinking KnownHost has the same Problem but they do not talk enough for anyone to notice.
SPF, DKIM, DMARC — holy trinity ✉️
mediaaustin
Member
Deliverability Nerd
- Joined:
- Jul 2024
- Posts:
- 276
- From:
- Austin, US
Update: CloudCone's Los Angeles /24 is now on eleven blocklists. I checked again this morning. The stale SPF records are still there because their customers cannot reach the control panel to fix them. This is the real second-order failure: not the fire, the inability to recover from the fire.
SPF, DKIM, DMARC — holy trinity ✉️
kasiaxus
Member
- Joined:
- Aug 2024
- Posts:
- 74
- From:
- Wrocław, Poland
I am confused. Hostinger says Amsterdam node offline, but their status page says "scheduled maintenance" for Amsterdam since May 6. Was the fire on May 7 or did they know something before? I do not trust this timing.
POLISH SERVERS. LOUD FANS. GOOD PRICE.
tinaworm
Member
OP
- Joined:
- Jun 2024
- Posts:
- 84
- From:
- Riga, Latvia
"scheduled maintenance" for Amsterdam since May 6
Good catch. I checked the Wayback Machine. Hostinger's status page showed "network upgrade" on May 6, then switched to "unplanned incident" on May 7 at 15:02 CET. The fire was 14:37 CET. They knew.
worst bandwidth, best stories