Chocolate Cloud Object Storage Transfer Speeds Dataset

Open data API in a single place

Provided by Zenodo

Get early access to Chocolate Cloud Object Storage Transfer Speeds Dataset API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2026.02.11 00:00
Created
2026.01.01
Available languages
English
Keywords
Quality scoring

Dataset description

Overview This dataset measures upload and download performance between Fly.io gateway regions (origins) and commercial object storage backends (targets). Each row is one measurement for a specific data size, initiated from a Fly.io region and recorded against a particular backend, and is intended for studying network performance, latency-sensitive placement, and cross-region transfer behavior. Some records use 1-byte uploads/downloads to approximate latency by activating the target service's data path with minimal payload. For each timestamp, measurements include standard sizes (1 byte, 1 MB, 10 MB, 50 MB) plus a few random sizes up to 50 MB. The dataset includes ~900.000 measurements spanning 86 days between 2024-10-31 and 2025-01-24, with a pause from 2024-11-18 to 2024-12-18. Each measurement is uniquely identified by (timestamp, origin_fly_region, target_backend_id, size_bytes). CSV Columns timestamp: UTC datetime string for the measurement (timezone-aware, ISO 8601). origin_fly_region: Fly.io gateway region code (3-letter). origin_countrycode: ISO 3166-1 alpha-2 country code (lowercase) for the Fly.io gateway. origin_city: City of the Fly.io gateway. origin_lat: Latitude of the Fly.io gateway. origin_lng: Longitude of the Fly.io gateway. target_backend_id: Internal storage backend ID. target_provider: Cloud provider name. target_region: Cloud provider region. target_countrycode: ISO 3166-1 alpha-2 country code (lowercase) for the backend location. target_city: City of the storage backend. target_timezone: Time zone name for the backend. target_lat: Latitude of the storage backend. target_lng: Longitude of the storage backend. target_local_time: Local time at the target backend for the same instant as timestamp. distance_km: Great-circle distance between origin and target, in kilometers (rounded int). size_bytes: Data size in bytes for the measurement. upload_time_ms: Upload time in milliseconds. download_time_ms: Download time in milliseconds. upload_speed_mbps: Upload speed in megabits per second (2 decimal places). download_speed_mbps: Download speed in megabits per second (2 decimal places). Intended Use Examples Compare upload/download performance across cloud providers and regions for a fixed data size. Identify nearest or best-performing storage backends for a given Fly.io region. Analyze how geographic distance correlates with throughput. Build placement or replication strategies based on observed network performance. Use as input for predictive models of transfer time or throughput. Notes Rows are sorted by timestamp ascending. City names may contain commas and are properly quoted in the CSV. There are no missing values Related ML Models Models trained on this dataset are published at: https://zenodo.org/records/18288840 These models predict transfer time for a specific Fly.io region to storage-backend route at a given time and data size. There is a separate model for six backends and the Fly.io London (lhr) region. The target_backend_id column is the internal unique ID of a region for a commercial cloud storage provider and is consistent with the backend identifiers used in the published models.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks