Cloud usage across 2i2c clusters¶
This page shows aggregate cloud usage for all 2i2c-operated clusters.
Per-cluster pages are linked at the bottom. Data is pulled from the
cloud GitHub release.
Last updated: 2026-04-20 22:09 UTC
| Total clusters | Total hubs |
|---|---|
| 28 | 142 |
Unique monthly users by cluster¶
Active hubs by cluster¶
Per-cluster pages¶
- 2i2c-aws-us
- 2i2c
- 2i2c-uk
- aimatx-2i2c-hub
- awi-ciroh
- berkeley-geojupyter
- bnext-bio
- cloudbank
- disasters
- dubois
- earthscope
- hhmi
- jupyter-health
- leap
- maap
- nasa-cryo
- nasa-ghg-hub
- nasa-veda
- nmfs-openscapes
- openscapeshub
- opensci
- projectpythia
- reflective
- smithsonian
- temple
- ucmerced
- utoronto
- victor
Clusters with errors
Clusters listed below had Grafana query failures on the most recent download. Their data may be stale or missing.
How data is calculated¶
How “total MAUs” are calculated¶
Count of active users is calculated and reported by JupyterHub. JupyterHub’s definition of an active user is a bit more restrictive than our “unique Monthly Active Users” count. See the JupyterHub MAU blog post for details.
How “unique MAUs” are calculated¶
Count of distinct usernames that logged in during a given month. A user counts as “active” if they logged in. We use a custom query across all of our clusters (similar to our Grafana Dashboards) so that we avoid double-counting usernames that log into multiple hubs on the same cluster.
If this is a BinderHub, these are sessions, not users. BinderHub anonymizes users in ephemeral sessions, so the idea of a “unique” user doesn’t apply here. If this community uses a BinderHub, these counts are sessions, even if each session is from the same user.
How monthly unique MAUs are calculated¶
For billing purposes and other monthly summaries, we aggregate unique active users into months. To do so, we use our unique MAU count and aggregate unique usernames across the entire month, starting on the last minute of that month in UTC time.