The full dataset viewer is not available (click to read why). Only showing a preview of the rows.
Error code: DatasetGenerationCastError
Exception: DatasetGenerationCastError
Message: An error occurred while generating the dataset
All the data files must have the same columns, but at some point there are 11 new columns ({'rtt_baseline_ms', 'severity', 'cable_page', 'rtt_current_ms', 'description', 'cable_id', 'event_type', 'source_city', 'detected_at_utc', 'ratio', 'cable_name'}) and 8 missing columns ({'probe_city', 'target_country', 'hops_avg', 'rtt_p90_ms', 'rtt_min_ms', 'observation_date', 'samples', 'rtt_median_ms'}).
This happened while the csv dataset builder was generating data using
hf://datasets/geocables/internet-latency-and-routing-events/geocables-route-events.csv (at revision 719fafd23996808d24b7d427c1448e61f3b5ef49), ['hf://datasets/geocables/internet-latency-and-routing-events@719fafd23996808d24b7d427c1448e61f3b5ef49/geocables-latency-daily.csv', 'hf://datasets/geocables/internet-latency-and-routing-events@719fafd23996808d24b7d427c1448e61f3b5ef49/geocables-route-events.csv']
Please either edit the data files to have matching columns, or separate them into different configurations (see docs at https://hf.co/docs/hub/datasets-manual-configuration#multiple-configurations)
Traceback: Traceback (most recent call last):
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1848, in _prepare_split_single
writer.write_table(table)
~~~~~~~~~~~~~~~~~~^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/arrow_writer.py", line 765, in write_table
self._write_table(pa_table, writer_batch_size=writer_batch_size)
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/arrow_writer.py", line 773, in _write_table
pa_table = table_cast(pa_table, self._schema)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2378, in table_cast
return cast_table_to_schema(table, schema)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2306, in cast_table_to_schema
raise CastError(
...<3 lines>...
)
datasets.table.CastError: Couldn't cast
detected_at_utc: string
event_type: string
severity: string
source_city: string
target_city: string
cable_id: string
cable_name: string
rtt_current_ms: double
rtt_baseline_ms: double
ratio: double
description: string
cable_page: string
-- schema metadata --
pandas: '{"index_columns": [{"kind": "range", "name": null, "start": 0, "' + 1739
to
{'observation_date': Value('string'), 'probe_city': Value('string'), 'target_city': Value('string'), 'target_country': Value('string'), 'samples': Value('int64'), 'rtt_median_ms': Value('float64'), 'rtt_p90_ms': Value('float64'), 'rtt_min_ms': Value('float64'), 'hops_avg': Value('float64')}
because column names don't match
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 1369, in compute_config_parquet_and_info_response
parquet_operations, partial, estimated_dataset_info = stream_convert_to_parquet(
~~~~~~~~~~~~~~~~~~~~~~~~~^
builder, max_dataset_size_bytes=max_dataset_size_bytes
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 948, in stream_convert_to_parquet
builder._prepare_split(split_generator=splits_generators[split], file_format="parquet")
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1694, in _prepare_split
for job_id, done, content in self._prepare_split_single(
~~~~~~~~~~~~~~~~~~~~~~~~~~^
gen_kwargs=gen_kwargs, job_id=job_id, **_prepare_split_args
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
):
^
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1850, in _prepare_split_single
raise DatasetGenerationCastError.from_cast_error(
...<4 lines>...
)
datasets.exceptions.DatasetGenerationCastError: An error occurred while generating the dataset
All the data files must have the same columns, but at some point there are 11 new columns ({'rtt_baseline_ms', 'severity', 'cable_page', 'rtt_current_ms', 'description', 'cable_id', 'event_type', 'source_city', 'detected_at_utc', 'ratio', 'cable_name'}) and 8 missing columns ({'probe_city', 'target_country', 'hops_avg', 'rtt_p90_ms', 'rtt_min_ms', 'observation_date', 'samples', 'rtt_median_ms'}).
This happened while the csv dataset builder was generating data using
hf://datasets/geocables/internet-latency-and-routing-events/geocables-route-events.csv (at revision 719fafd23996808d24b7d427c1448e61f3b5ef49), ['hf://datasets/geocables/internet-latency-and-routing-events@719fafd23996808d24b7d427c1448e61f3b5ef49/geocables-latency-daily.csv', 'hf://datasets/geocables/internet-latency-and-routing-events@719fafd23996808d24b7d427c1448e61f3b5ef49/geocables-route-events.csv']
Please either edit the data files to have matching columns, or separate them into different configurations (see docs at https://hf.co/docs/hub/datasets-manual-configuration#multiple-configurations)Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
observation_date string | probe_city string | target_city string | target_country string | samples int64 | rtt_median_ms float64 | rtt_p90_ms float64 | rtt_min_ms float64 | hops_avg float64 |
|---|---|---|---|---|---|---|---|---|
2026-09-11 | Almaty | Angola Cables Luanda | AO | 1 | 206.2 | 206.2 | 206.2 | 17 |
2026-09-11 | Almaty | Cable&Wireless Panama | PA | 4 | 239.13 | 253.52 | 238.02 | 24.8 |
2026-09-11 | Almaty | Cloudflare Mayotte | YT | 2 | 25.92 | 27.18 | 25.92 | 12 |
2026-09-11 | Almaty | Cloudflare Mogadishu | SO | 2 | 26.15 | 26.42 | 26.15 | 12 |
2026-09-11 | Almaty | Digicel Bermuda | BM | 3 | 207.25 | 208.28 | 196.55 | 22.7 |
2026-09-11 | Almaty | Djibouti Telecom | DJ | 4 | 229.28 | 232.21 | 224.24 | 30 |
2026-09-11 | Almaty | ETECSA Cuba | CU | 4 | 303.74 | 305.76 | 300.29 | 14 |
2026-09-11 | Almaty | FINTEL Suva | FJ | 3 | 369.66 | 429.84 | 286.07 | 16 |
2026-09-11 | Almaty | LTT Tripoli | LY | 4 | 176.56 | 177.78 | 175.99 | 23 |
2026-09-11 | Almaty | Mauritius Telecom DNS | MU | 4 | 295.25 | 296.61 | 289.52 | 23.5 |
2026-09-11 | Almaty | ns1.amnic.net | AM | 1 | 85.9 | 85.9 | 85.9 | 21 |
2026-09-11 | Almaty | ns1.dns.pt | PT | 4 | 125.38 | 126.27 | 125.32 | 28 |
2026-09-11 | Almaty | ns1.grnet.gr | GR | 4 | 112.15 | 112.53 | 111.7 | 11 |
2026-09-11 | Almaty | ns1.md | MD | 3 | 120.8 | 125.72 | 120.16 | 13 |
2026-09-11 | Almaty | ns1.nic.ge | GE | 3 | 173.73 | 175.22 | 132.01 | 20.7 |
2026-09-11 | Almaty | ns1.nic.hu | HU | 4 | 82.83 | 84.44 | 82.69 | 13 |
2026-09-11 | Almaty | ns1.nic.tm | TM | 4 | 64.57 | 69.02 | 59.85 | 15.8 |
2026-09-11 | Almaty | ns1.switch.ch | CH | 4 | 100.42 | 104.03 | 97.22 | 17 |
2026-09-11 | Almaty | ns1.thnic.co.th | TH | 4 | 253.96 | 258.66 | 251.82 | 23 |
2026-09-11 | Almaty | ns1.univie.ac.at | AT | 4 | 82.99 | 83.35 | 82.69 | 10 |
2026-09-11 | Almaty | ns1.zadna.org.za | ZA | 4 | 259.91 | 282.9 | 259.62 | 19 |
2026-09-11 | Almaty | OPT French Polynesia | PF | 2 | 324.59 | 324.61 | 324.59 | 17 |
2026-09-11 | Almaty | RIPE Atlas anchor#6313 | DE | 4 | 90.39 | 93 | 89.2 | 14 |
2026-09-11 | Almaty | RIPE Atlas anchor#6324 | LT | 4 | 93.42 | 95.34 | 93.08 | 20 |
2026-09-11 | Almaty | RIPE Atlas anchor#6327 | HR | 4 | 97.89 | 105.91 | 97.24 | 20 |
2026-09-11 | Almaty | RIPE Atlas anchor#6349 | BR | 4 | 304.26 | 306.91 | 304.09 | 24 |
2026-09-11 | Almaty | RIPE Atlas anchor#6351 | LV | 4 | 108.01 | 109.19 | 107.21 | 19 |
2026-09-11 | Almaty | RIPE Atlas anchor#6370 | JP | 4 | 293.23 | 296.32 | 292.62 | 14 |
2026-09-11 | Almaty | RIPE Atlas anchor#6373 | US | 4 | 201.55 | 206.86 | 198.92 | 24 |
2026-09-11 | Almaty | RIPE Atlas anchor#6380 | GH | 4 | 203.69 | 204.16 | 203.38 | 19 |
2026-09-11 | Almaty | RIPE Atlas anchor#6382 | GB | 4 | 99.18 | 100.84 | 99.09 | 11 |
2026-09-11 | Almaty | RIPE Atlas anchor#6392 | AE | 4 | 206.46 | 206.68 | 206.3 | 17 |
2026-09-11 | Almaty | RIPE Atlas anchor#6402 | BG | 4 | 122.98 | 124.41 | 121.26 | 13 |
2026-09-11 | Almaty | RIPE Atlas anchor#6427 | AU | 4 | 285.36 | 381.02 | 282.9 | 18.8 |
2026-09-11 | Almaty | RIPE Atlas anchor#6431 | SA | 4 | 155.04 | 158.25 | 154.94 | 16 |
2026-09-11 | Almaty | RIPE Atlas anchor#6477 | SG | 4 | 241.31 | 252.97 | 239.81 | 19 |
2026-09-11 | Almaty | RIPE Atlas anchor#6521 | ID | 4 | 256.37 | 259.38 | 249.99 | 18 |
2026-09-11 | Almaty | RIPE Atlas anchor#6541 | SI | 4 | 99.24 | 102.11 | 94.26 | 23 |
2026-09-11 | Almaty | RIPE Atlas anchor#6718 | VN | 4 | 285.69 | 290.64 | 283.17 | 22.3 |
2026-09-11 | Almaty | RIPE Atlas anchor#6722 | EE | 4 | 71.55 | 72.31 | 71.04 | 12 |
2026-09-11 | Almaty | RIPE Atlas anchor#6882 | KE | 4 | 214.55 | 217.27 | 214.22 | 17 |
2026-09-11 | Almaty | RIPE Atlas anchor#6887 | PH | 4 | 336.84 | 344.57 | 335.25 | 27 |
2026-09-11 | Almaty | RIPE Atlas anchor#6931 | PE | 4 | 303.17 | 305.12 | 302.23 | 23.3 |
2026-09-11 | Almaty | RIPE Atlas anchor#6953 | IN | 4 | 238.22 | 241.9 | 236.17 | 11 |
2026-09-11 | Almaty | RIPE Atlas anchor#7007 | MY | 4 | 246.24 | 246.84 | 246.23 | 11 |
2026-09-11 | Almaty | RIPE Atlas anchor#7305 | SK | 4 | 104.64 | 112.95 | 104.39 | 22.3 |
2026-09-11 | Almaty | RIPE Atlas anchor#7385 | GU | 4 | 345.14 | 347.7 | 343.83 | 20 |
2026-09-11 | Almaty | RIPE Atlas anchor#7475 | NP | 4 | 289.71 | 296.26 | 289.04 | 23 |
2026-09-11 | Almaty | RIPE Atlas anchor#7595 | LK | 4 | 235.41 | 235.89 | 235.03 | 24.5 |
2026-09-11 | Almaty | RIPE Atlas anchor#7613 | PK | 4 | 228.66 | 231.28 | 226.51 | 21.8 |
2026-09-11 | Almaty | RIPE Atlas anchor#7623 | NG | 4 | 214.68 | 216.57 | 214.48 | 18 |
2026-09-11 | Almaty | RIPE Atlas anchor#7665 | LB | 4 | 170.47 | 174.21 | 169.61 | 15 |
2026-09-11 | Almaty | RIPE Atlas Probe 1 NL | NL | 3 | 113.23 | 114.53 | 111.82 | 26 |
2026-09-11 | Almaty | RIPE Atlas Probe 12214 HK (AS41095) | HK | 4 | 199.24 | 247.71 | 185.25 | 15 |
2026-09-11 | Almaty | RIPE Atlas Probe 1459 LU | LU | 1 | 104.66 | 104.66 | 104.66 | 27 |
2026-09-11 | Almaty | RIPE Atlas Probe 14958 SC | SC | 4 | 266.2 | 269.27 | 264.84 | 18.5 |
2026-09-11 | Almaty | RIPE Atlas Probe 218 CZ (AS2852) | CZ | 4 | 97.33 | 98.96 | 97.08 | 15 |
2026-09-11 | Almaty | RIPE Atlas Probe 6366 BA | BA | 3 | 105.97 | 109.57 | 102.81 | 19.7 |
2026-09-11 | Almaty | RIPE Atlas Probe 6664 IL | IL | 4 | 140.51 | 142.49 | 138.89 | 18.5 |
2026-09-11 | Almaty | RIPE Atlas Probe 6723 MN | MN | 3 | 286.22 | 287.85 | 285.35 | 16 |
2026-09-11 | Almaty | RIPE Atlas Probe 6777 MZ | MZ | 4 | 255.93 | 256.82 | 255.43 | 11 |
2026-09-11 | Almaty | RIPE Atlas Probe 7244 MK | MK | 3 | 119.07 | 120.26 | 116.26 | 18 |
2026-09-11 | Almaty | RIPE Atlas Probe 7342 KG | KG | 3 | 6.26 | 6.62 | 5.88 | 13 |
2026-09-11 | Almaty | RIPE Atlas Probe 7628 AZ | AZ | 3 | 120.31 | 128.57 | 119.32 | 12 |
2026-09-11 | Almaty | RIPE Atlas probe#1000734 | QA | 4 | 209.05 | 219.38 | 200.32 | 17.8 |
2026-09-11 | Almaty | RIPE Atlas probe#1010769 | YE | 4 | 148.67 | 181.07 | 140.54 | 21.5 |
2026-09-11 | Almaty | RIPE Atlas probe#51361 | BD | 4 | 292.17 | 293.96 | 288.71 | 23.5 |
2026-09-11 | Almaty | Samoa DataCom | WS | 4 | 480.11 | 490.05 | 475.91 | 30 |
2026-09-11 | Almaty | Telecom Cook Islands | CK | 1 | 500.09 | 500.09 | 500.09 | 22 |
2026-09-11 | Almaty | Telma Antananarivo | MG | 4 | 235.36 | 245.19 | 232.37 | 30 |
2026-09-11 | Almaty | Tonga Comm Corp | TO | 4 | 417.9 | 421.51 | 417.44 | 25 |
2026-09-11 | Almaty | TTCL Dar es Salaam | TZ | 1 | 231.66 | 231.66 | 231.66 | 21 |
2026-09-11 | Almaty KZ | Cloudflare | XX | 32 | 27.14 | 32.3 | 26.42 | 12.7 |
2026-09-11 | Almaty KZ | Google DNS | XX | 32 | 86.67 | 89.36 | 81.32 | 20 |
2026-09-11 | Almaty KZ | Jerusalem IL | IL | 32 | 167.12 | 169.33 | 151.32 | 20 |
2026-09-11 | Almaty KZ | Minsk BY | BY | 32 | 90.68 | 101.62 | 67.87 | 20 |
2026-09-11 | Almaty KZ | Moscow RU | RU | 32 | 57.38 | 58.82 | 52.76 | 20 |
2026-09-11 | Almaty KZ | Tbilisi GE | GE | 32 | 142.66 | 154.83 | 123.94 | 20 |
2026-09-11 | Jerusalem | Batelco Manama | BH | 1 | 63.98 | 63.98 | 63.98 | 20 |
2026-09-11 | Jerusalem | Cable&Wireless Panama | PA | 4 | 213.44 | 222.42 | 211.44 | 21.8 |
2026-09-11 | Jerusalem | Cloudflare Mayotte | YT | 2 | 2.97 | 3.07 | 2.97 | 6 |
2026-09-11 | Jerusalem | Cloudflare Mogadishu | SO | 2 | 3.22 | 3.34 | 3.22 | 6 |
2026-09-11 | Jerusalem | Digicel Bermuda | BM | 3 | 178.51 | 180.04 | 176.19 | 18.3 |
2026-09-11 | Jerusalem | Djibouti Telecom | DJ | 4 | 249.7 | 251.63 | 249.38 | 30 |
2026-09-11 | Jerusalem | ETECSA Cuba | CU | 4 | 270.08 | 281.43 | 269.78 | 8 |
2026-09-11 | Jerusalem | FINTEL Suva | FJ | 3 | 390.97 | 391.75 | 390.01 | 20 |
2026-09-11 | Jerusalem | LTT Tripoli | LY | 4 | 141.46 | 145.73 | 140.74 | 16 |
2026-09-11 | Jerusalem | Mauritius Telecom DNS | MU | 4 | 260.78 | 262.94 | 256.66 | 22 |
2026-09-11 | Jerusalem | ns1.amnic.net | AM | 1 | 137.28 | 137.28 | 137.28 | 17 |
2026-09-11 | Jerusalem | ns1.dns.pt | PT | 4 | 93.32 | 95.46 | 91.7 | 25.3 |
2026-09-11 | Jerusalem | ns1.grnet.gr | GR | 4 | 96 | 98.3 | 94.9 | 17 |
2026-09-11 | Jerusalem | ns1.md | MD | 3 | 88.91 | 89.34 | 88.65 | 13.3 |
2026-09-11 | Jerusalem | ns1.nic.ge | GE | 3 | 119.79 | 147.85 | 116.91 | 27.7 |
2026-09-11 | Jerusalem | ns1.nic.hu | HU | 4 | 70.71 | 71.46 | 70.49 | 13 |
2026-09-11 | Jerusalem | ns1.nic.tm | TM | 2 | 153.46 | 154.24 | 153.46 | 28 |
2026-09-11 | Jerusalem | ns1.ripn.net | RU | 2 | 138.11 | 139.07 | 138.11 | 16 |
2026-09-11 | Jerusalem | ns1.switch.ch | CH | 4 | 60.57 | 60.77 | 60.54 | 11 |
2026-09-11 | Jerusalem | ns1.thnic.co.th | TH | 4 | 236.76 | 238.23 | 234.48 | 19 |
2026-09-11 | Jerusalem | ns1.univie.ac.at | AT | 4 | 61.96 | 62.26 | 61.64 | 11 |
2026-09-11 | Jerusalem | ns1.zadna.org.za | ZA | 4 | 230.44 | 243.67 | 229.59 | 20 |
GeoCables Internet Latency and Routing Events
Daily-updated measurements of internet round-trip latency toward submarine cable landing regions, and detected routing anomalies (detours, path changes), collected by GeoCables - a live atlas of the world's submarine cable infrastructure with its own distributed measurement network.
Files
geocables-latency-daily.csv- per-day latency aggregates (median / p90 / min RTT in milliseconds) for measured city-to-target routes.geocables-route-events.csv- detected routing events: detours, reroutes and recoveries, with distance and RTT deltas (IP addresses scrubbed).
Method
Measurements are performed continuously by GeoCables' own distributed probe network; values are aggregated daily. Event detection compares live paths and RTT against per-route rolling baselines. Details and live views: geocables.com/live, methodology: geocables.com/methodology.
License and attribution
CC BY 4.0. Please attribute to GeoCables with a link to geocables.com.
Mirrors: Kaggle · canonical: geocables.com/dataset
- Downloads last month
- 71