OSU Open Source Lab - FTP mirroring (ftp.osuosl.org / ftp2.osuosl.org)
- Free allowance
- No published per-project quota, but an explicit capacity statement and an allocation policy: 'Because space on the main mirrors is limited, we also host projects on ftp2.osuosl.org.
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- write-gatedreview process ('Please give us a few days or a week to discuss and respond') and the
- Evidence
- reported3 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | No published per-project quota, but an explicit capacity statement and an allocation policy: 'Because space on the main mirrors is limited, we also host projects on ftp2.osuosl.org. It runs in Salem and stores its content on our Ceph cluster instead of copying it to every server. We currently host about 100 projects using around 37 TB of disk space, about 16 TB on the main mirrors and 21 TB on ftp2.' Mean is therefore ~370 GB per hosted project. unit objects; metered on stored-bytes |
|---|---|
| Price | none stated |
| Limits |
per-object-cap: none published. The binding constraint is the request/review process ('Please give us a few days or a week to discuss and respond') and the statement that main-mirror space is limited. retention: indefinite for accepted projects. request-rate: N/A (mirror serves static files). |
| Identity | email (placeholder) not published |
| Egress | Free and genuinely high-capacity: 'Three servers sit behind ftp.osuosl.org with a combined bandwidth capacity of 60 gigabits per second. They are located in Salem, Chicago and New York, and each one carries a full copy of the content.' No billing. |
| Per-object cap | not stated |
| Retention | The binding constraint is the request/review process ('Please give us a few days or a week to discuss and respond') and the statement that main-mirror space is limited. retention: indefinite for accepted projects |
| Interface | rest, ftp, rsync rest |
| Tooling | FTP/HTTP mirror distribution plus rsync from the mirror ring; no self-service upload API - content is placed by arrangement. Request flow is a form at osuosl.org/services/hosting/request/ asking for project name, URL, source repo, and role. |
| Composes with | Not multiplicable - it is an allocation, not a tier. The value is scale per allocation: ~370 GB mean, 60 Gbps aggregate egress, three-city replication, and a Ceph-backed second tier (ftp2) with 21 TB already in use. |
| Reliability | Human-gated and OSS-only in practice (the form asks for a source code repository and a role such as maintainer). It is a good home for a legitimately large OSS release corpus and a bad fit for arbitrary bulk - there is no self-service path and capacity is finite and publicly rationed. |
| Parsed numbers |
|
Evidence 3
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | osuosl.org/services/hosting/details/ | 'Three servers sit behind ftp.osuosl.org with a combined bandwidth capacity of 60 gigabits per second'; 'about 100 projects using around 37 TB of disk space, about 16 TB on the main mirrors and 21 TB on ftp2' |
| 2026-10-21 | osuosl.org/services/hosting/request/ | request form requires project name, URL, source code repository, and role; 'Please give us a few days or a week to discuss and respond' |
| 2026-10-21 | osuosl.org/services/hosting/ | 'Release files and package repositories served from mirrors in three cities' |
Unknown values 3
- per object cap notes: the field may be stated in a source that was not read
- per object cap stated: the field may be stated in a source that was not read
- retention notes: the field may be stated in a source that was not read