diff --git a/content/blog/2025/binder-singlenode/index.md b/content/blog/2025/binder-singlenode/index.md
index 777a245b..e310344a 100644
--- a/content/blog/2025/binder-singlenode/index.md
+++ b/content/blog/2025/binder-singlenode/index.md
@@ -14,7 +14,9 @@ If you're interested in supporting `mybinder.org` with cloud resources, financia
 
 > `tl;dr`: The 2i2c team is joining the mybinder.org federation with a [single-node BinderHub instance at `2i2c.mybinder.org`](https://github.com/jupyterhub/mybinder.org-deploy/pull/3169/). It should be much cheaper to run than auto-scaling Kubernetes clusters, and might be a good way to support `mybinder.org` more sustainably.
 
-[`mybinder.org`](https://mybinder.org) is a massive public service for creating and sharing reproducible computational environments. It is managed by the JupyterHub team and [members of the `mybinder.org` federation](https://mybinder.readthedocs.io/en/latest/about/federation.html). One challenge in running [`mybinder.org`](https://mybinder.org) is identifying cloud credits or financial resources to support the cloud infrastructure that runs the service. Two years ago, [Google stopped supporting `mybinder.org` federation with cloud credits](https://medium.com/jupyter-blog/mybinder-org-reducing-capacity-c93ccfc6413f), and last month [the federation lost more capacity](https://discourse.jupyter.org/t/mybinder-org-reduced-capacity-stability/31750). This makes `mybinder.org` less reliable, slower, and generally less useful to the world.
+[`mybinder.org`](https://mybinder.org) is a massive public service for creating and sharing reproducible computational environments. It is managed by the JupyterHub team and [members of the `mybinder.org` federation](https://mybinder.readthedocs.io/en/latest/about/federation.html). One challenge in running [`mybinder.org`](https://mybinder.org) is identifying cloud credits or financial resources to support the cloud infrastructure that runs the service. Two years ago, [Google stopped supporting `mybinder.org` federation with cloud credits](https://medium.com/jupyter-blog/mybinder-org-reducing-capacity-c93ccfc6413f), and last month [the federation lost more capacity](https://discourse.jupyter.org/t/mybinder-org-reduced-capacity-stability/31750), leaving only [GESIS](https://www.gesis.org/en/home) and [OVH](https://us.ovhcloud.com/) as remaining federation members[^thanks]. This makes `mybinder.org` less reliable, slower, and generally less useful to the world.
+
+[^thanks]: Many thanks to [GESIS](https://www.gesis.org/en/home) and [OVH](https://us.ovhcloud.com/) for their continued support of mybinder.org, your contributions to keeping this service running are critical!
 
 The landscape of cloud infrastructure technology and services has changed considerably, and we think that there's a way to deploy BinderHub instances with lower costs and less complexity. We've accomplished this by deploying a **single-node Kubernetes cluster** on a VM provider that is much cheaper, now running at `2i2c.mybinder.org`. This both relieves Binder's short-term capacity shortage and may provide an easier pathway for others to support the project in the future.