惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

量子位
D
Docker
月光博客
月光博客
MongoDB | Blog
MongoDB | Blog
Vercel News
Vercel News
美团技术团队
博客园 - 叶小钗
I
InfoQ
Jina AI
Jina AI
博客园 - 司徒正美
雷峰网
雷峰网
B
Blog
Y
Y Combinator Blog
A
About on SuperTechFans
WordPress大学
WordPress大学
酷 壳 – CoolShell
酷 壳 – CoolShell
大猫的无限游戏
大猫的无限游戏
Microsoft Security Blog
Microsoft Security Blog
Stack Overflow Blog
Stack Overflow Blog
腾讯CDC
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Recent Announcements
Recent Announcements
V
V2EX
N
Netflix TechBlog - Medium

Buttondown's blog

Email could have been X.400 times better The physicists who convinced Fermilab to send Brazil's emails Better in-app previews Analytics 3.0 Subscriber ID variables Comments! Send latest premium action Automation filtering Free API subscribers Surveys in automations Reply to replies Labels for RSS feeds How Jeremy Singer-Vine curates curious datasets for readers 2023 (and what's next) Email vs web content Sort by engagement Better gift subscriptions How Andy Dehnart built a career reviewing television New email template Email-based automations Opt-in reply tracking Automatic alt text More social network integrations Sort by metadata Overlarge image warnings Automation tag actions Pause emails mid-flight Search tags and automations Gift via automations Subscriber-driving emails
Public postmortem: Broken images
Steph Monette · 2026-06-12 · via Buttondown's blog

TL;DR

Around 15:00 UTC we learned that all images were broken on Buttondown. This included viewing images within the Editor, as well as seeing past images in the Archives.

Buttondown uses Cloudflare to host and optimize our images and assets. Due to an outage with their tooling, images were not loading correctly on Buttondown.

How did we detect the issue?

Unfortunately, we didn't have an automated system monitoring images. We learned about this issue from user reports, which is unacceptable.

How did we mitigate the issue?

At 16:00 UTC the team bypassed our image optimizer on Cloudflare, and pointed it to a new worker. This restored image visibility, although they were no longer optimized.

We checked in with our customers that reported the issues to confirm that they were seeing the fix. We also continued to monitor until Cloudflare marked their outage as resolved at 21:34 UTC.

On June 11th at 23:15 UTC we reverted back to the image optimizer.

How will we prevent this from happening again?

  1. We've added alerting for our image optimizer tool so we can get advance warning when errors and outages occur.
  2. We're also adding tooling so that we can actively monitor metrics from the image optimizer.