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

推荐订阅源

雷峰网
雷峰网
MongoDB | Blog
MongoDB | Blog
D
Docker
Martin Fowler
Martin Fowler
人人都是产品经理
人人都是产品经理
GbyAI
GbyAI
Jina AI
Jina AI
酷 壳 – CoolShell
酷 壳 – CoolShell
M
MIT News - Artificial intelligence
腾讯CDC
阮一峰的网络日志
阮一峰的网络日志
H
Hackread – Cybersecurity News, Data Breaches, AI and More
N
Netflix TechBlog - Medium
B
Blog RSS Feed
云风的 BLOG
云风的 BLOG
Blog — PlanetScale
Blog — PlanetScale
Vercel News
Vercel News
The Cloudflare Blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
有赞技术团队
有赞技术团队
G
Google Developers Blog
Stack Overflow Blog
Stack Overflow Blog
I
InfoQ
U
Unit 42

Flathub Status

GitHub is experiencing issues | Flathub Status Website is down | Flathub Status Multiple services down | Flathub Status Infrastructure provider outage | Flathub Status Build status updates failing | Flathub Status Publishing delay due to delta regeneration appstream2 branch referencing stale commit CDN cache invalidation issue | Flathub Status CDN cache invalidation issue | Flathub Status Website facing intermittent disruptions | Flathub Status Publish outage | Flathub Status Build service outage | Flathub Status Hosting provider planned maintenance | Flathub Status Blocked publishing due to ongoing repository pruning Frontend service is down | Flathub Status
Signing outage | Flathub Status
2026-02-17 · via Flathub Status

February 17, 2026 at 13:56 UTC

Build service Main repository server

Resolved after 6d 4h 54m February 23, 2026 at 18:50 UTC


An issue with hardware security key is currently preventing builds from being signed with our GPG key. This affects both direct uploads and builds performed on Flathub infra. Since no builds can be signed thus published, the build service including test builds are also disrupted. (13:56 UTC — Feb 17)

We are in contact with the data center staff to investigate the issue physically. (17:49 UTC — Feb 19)

Data centre staff attempted reseating the signing key across available USB ports without success. We are now arranging delivery and installation of a replacement key. (16:46 UTC — Feb 20)

We successfully managed to install the new Yubikey. (14:04 UTC — Feb 23)

Information

We will soon restart all affected official builds in batches and they should be published within a couple of hours. Affected direct uploaders will be informed to restart builds from their end. Once this process is complete, some services which were disabled (to reduce impact) will be re-enabled one by one.

Once the test build service is available, any affected test builds on pull requests will need to be manually restarted by commenting “bot, build” by the respective maintainer or contributor.

Please allow us some time to finish the entire process outlined above. Publishing may take longer than usual due the large number of builds in the queue. Please open an issue on GitHub for any further query about missing or unpublished builds. Further updates will be posted in the statuspage.

All affected builds were successfully restarted and they finished building. (16:40 UTC — Feb 23)

The repository server is still experiencing some issues. (17:30 UTC — Feb 23)

The incident should be resolved now and services are being restarted. (18:50 UTC — Feb 23)