Cloud Looking Glass Methodology Documentation

Version: 1.0

Date: August 2025

Dataset: cloudlookingglass

1. Overview
2. Architecture
3. Dataset
1. 3.1 Sponsorship
2. 3.2 Schema
3. 3.3 Schema Diagram
4. 3.4 Tables
4. Core Tables
1. 4.1 tests Table
2. 4.2 test_commands Table
3. 4.3 test_targets Table
4. 4.4 test_status Table
5. 4.5 test_outages Table
6. 4.6 test_status_* Rollup Tables
5. Service Types
1. 5.1 Primary Services
2. 5.2 Supporting Services
6. Test Categories
1. 6.1 Control Plane Tests
2. 6.2 Data Plane Tests
3. 6.3 Networking Tests
  1. 6.3.1 Zonal Measurements
  2. 6.3.2 Regional Measurements
  3. 6.3.3 Cross-Region Measurements
  4. 6.3.4 Edge Measurements
  5. 6.3.5 Cross-Cloud Measurements
  6. 6.3.6 Last Mile Measurements
7. Service Events
1. 7.1 Isolated Events
2. 7.2 Large Service Events (LSEs)
8. Availability vs Performance
1. 8.1 Availability Metrics
2. 8.2 Performance Metrics
9. Status ID Conventions
1. 9.1 Control Plane Format
2. 9.2 Data Plane Format
3. 9.3 Networking Format
10. Data Retention
11. Appendix A: Status ID Reference
1. 11.1 Control Plane Status IDs
2. 11.2 Data Plane Status IDs
3. 11.3 Networking Status IDs
  1. 11.3.1 Zonal Measurements
  2. 11.3.2 Regional Measurements
  3. 11.3.3 Cross-Region Measurements
  4. 11.3.4 Cross-Cloud Measurements
  5. 11.3.5 Edge Measurements
  6. 11.3.6 Last Mile Measurements

Overview

Cloud Looking Glass provides independent, real-time monitoring of cloud service availability across 26 providers. Unlike provider status pages that may be slow to update or affected by their own outages, we offer unfiltered visibility into cloud performance through continuous testing from globally distributed agents.

Project Website: https://cloudlooking.glass - Visit for real-time dashboards and detailed availability reports.

About This Dataset

Cloud Looking Glass is a graduate research project conducted through the Computer Science Department at Western Washington University by Jason Read and Dr. Tarek Idriss. Our mission is to empirically measure and publish real-world data on the availability and performance of hyperscale cloud platforms.

This methodology documentation describes our testing approach and data collection infrastructure:

Continuous Monitoring: Tests run every 10 minutes (144 times per day)
Multi-Cloud Coverage: AWS (primary), GCP, Azure, and 20+ other providers
Global Reach: 25+ regions, 100+ availability zones
Dual Redundancy: Two independent test accounts (designated as 'com' and 'net' based on the domain suffixes used for DNS testing)
External Validation: Integration with RIPE Atlas and Globalping networks
Data Volume: ~1.5 million tests per day, ~5 million command executions

Architecture

Account Naming Convention

Cloud Looking Glass uses two independent test accounts per cloud provider, labeled as 'com' and 'net' (account 1 and 2) in the dataset (these labels originate from the TLD of domain names we allocate to each account for managed DNS service measurements).

Cloud Looking Glass employs a multi-layered architecture to measure cloud service availability and performance across 26+ cloud providers globally. The system operates on a continuous 10-minute test cycle, executing millions of measurements daily to provide real-time insights into cloud control and data plane availability and performance. Detected events undergo manual review and classification before being documented as confirmed outages.

Test Scheduling Methodology

Universal Tests

Universal tests are initiated independently by each Test Agent on their local schedule:

Zonal Networking: Latency measurements within availability zones
Regional Networking: Connectivity tests within the same region
Execution Pattern: Each Test Agent runs these tests autonomously every 10 minutes

Distributed Tests

Distributed tests are centrally assigned by an external test scheduler and cover all other control plane, data plane, and networking measurements. These tests are executed once per account per 10-minute interval.

Data Flow Architecture

Test Initiation
- Cron-based schedulers trigger tests every 10 minutes
- Queue system (Beanstalkd) manages test distribution
- Priority-based execution ensures critical tests run first
Test Execution
- Probe agents receive test specifications via queue
- Tests execute with standardized timeouts and retry logic
- Measurements captured at multiple levels (wire time, CLI overhead, wall clock)
Data Collection
- Raw measurements stored in PostgreSQL
- Real-time status updates in test_status table (144 data points/24 hours)
- Command-level details preserved in test_commands table
Data Processing
- Statistical analysis calculates percentiles and standard deviations
- Automatic rollup aggregation at multiple time granularities
Event Detection
- Triple-redundant validation across all test accounts (com/net)
- All events classified as isolated or large service event (LSE) and manually reviewed (false positives removed)
- LSE classification when event is manually verified and documented as impacting all accounts simultaneously
- Events documented from public sources (service health pages) and internal support channels when not publicly acknowledged

Event Validation Process

Automated Detection

Cross-Account Correlation: Simultaneous failures across accounts indicate LSEs
Service Dependency Mapping: Related service failures are correlated
Historical Pattern Matching: Known failure patterns accelerate classification

Manual Verification

Root Cause Analysis: We review stderr/stdout for error classification
Vendor Confirmation: Cross-reference with provider status pages or support channels if event is not acknowledged publicly
Outage Documentation: Verified events documented in test_outages table
Post-Incident Review: Patterns analyzed for detection improvement

Infrastructure Components

Control Servers

Orchestrate test execution across global infrastructure
Manage queue priorities and test scheduling
Aggregate results from distributed probes
Generate real-time status updates

Test Agents

Deployed in every monitored cloud region/zone
Network tests run from two clouds in each test network (com and net): AWS us-east-1 (EC2 and Lightsail) and Google Cloud us-east4 (Compute Engine), so every target is measured from both every 10-minute round
Conduct both universal and distributed assigned measurements
Capture multi-level timing measurements
Push results to the centralized PostgreSQL database server

External Test Probes

RIPE Atlas: 11,000+ probes for global edge measurements
Globalping: Community-driven last-mile testing

Measurement Precision

For each measurement, we capture three types of timing metrics:

Wire Time (measurements): The actual API request/response time, excluding SDK initialization and overhead. This is the closest measurement to what providers report in their SLA metrics and what you would experience with a warm, initialized SDK. Use this for comparing raw API performance across providers. It covers a fresh connection to the API (DNS, TCP and TLS), the request and the whole response, on every cloud; fetching a credential and signing the request are left out.
CLI Overhead (measurements_cli): Includes the time to initialize the CLI/SDK, parse responses, and handle authentication. This represents the real-world experience when using provider CLIs in scripts or automation. The difference between measurements_cli and measurements reveals the overhead of each provider's tooling. Google Cloud tests call the REST APIs with curl and have no SDK, so their measurements_cli is empty.
Wall Clock Time (measurements_wall): The total end-to-end execution time including all system overhead, process spawning, and cleanup. This is what you would measure with a stopwatch from command start to finish. Use this for capacity planning and understanding total resource consumption. For a Google Cloud test it is curl's own process time.

These distinctions are critical because different providers have vastly different SDK initialization times. For example, AWS CLI initialization can add 500-1000ms overhead, while lighter SDKs may add only 50-100ms. By separating these measurements, we can fairly compare the actual API performance independent of tooling choices.

HTTP Measurements Before the Sampling Fix

Each HTTP test (http, https, httpb-100mb, httpsb-100mb) makes four requests, and each request time is one sample. Until the probe release of October 29, 2026 (testing resumed at 10:43 PM Pacific time), the probes also stored the three values of httping's summary line (the minimum, maximum and average of those four times) as samples, so each HTTP row held seven measurements instead of four. On six hours of production rows measured on October 29, 2026, this put the stored median 1.3% high on average (a mean absolute difference of 1.7-2.0%, about 4-5 ms), and 77% high at worst when a single request was slow. Rows recorded from that time on hold the four request times only. Earlier rows, and the test_status_* rollups built from their medians, keep the bias and were not rewritten, so HTTP medians that span the change can show a small step.

Google Cloud Storage Regional Endpoints

Until the probe release of November 1, 2026 that moved them (testing resumed at 11:12 PM Pacific time; the GCP probes, new that day, used the regional endpoints from their first results), CLG's Google Cloud Storage tests (gcp.gcs.<region>: http, https and httpb-100mb) reached each region's bucket through Google's global host, storage.googleapis.com. That name is anycast: a request entered Google's network at the front end nearest the test's source and crossed Google's backbone to the bucket, while a random query string on every request kept the front end from answering from its cache. Since that release, every location that offers a regional endpoint (42 of 43, the us and eu multi-regions included) is tested through it, storage.<region>.rep.googleapis.com, so a request enters Google's network in the bucket's region, as an Amazon S3 request enters AWS in its region. The asia multi-region has no regional endpoint and stays on the global host. Regional endpoints answer on IPv4 and over HTTPS only (port 80 is closed), so from that release (their plain-HTTP queue lines ended at 11:25 PM Pacific time) each regional location is tested with https and httpsb-100mb (the latter a new status id), and its http and httpb-100mb ids end; asia keeps all of its tests on the global host. The https ids keep their names, so their history shows a step at the change: the global host measured the distance to the nearest Google edge, the regional endpoint the distance to the region (to us-east4's bucket from one US workstation on November 1, 2026: a 7-14 ms connect through the global host, 70-83 ms through the regional endpoint).

Amazon S3 Copy Size

Until the AWS probe release of November 1, 2026 (com at 9:04 PM and net at 9:10 PM Pacific time; testing resumed at 11:12 PM), the Amazon S3 tests' copy step (copy-object-<class>) copied a 100 MB file (104,847,609 bytes) from the region's test bucket, and head-object-<class> and get-object-range-<class> then read that copy. Since that release they copy a 10 MB file (10,478,419 bytes), the size the Google Cloud Storage control plane tests copy (gcp.gcs.<region>--dp--copy-object-<class>), so the two clouds' copies are comparable. The smaller copy also keeps cheap the minimum storage duration that the infrequent-access and archive classes bill when an object is deleted early. The status ids are unchanged, so the copy-object-* history shows a step down at the change; the ranged GET reads the same 3 bytes either way.

Retried API Calls

Until the probe release of November 2, 2026 (testing resumed at 6:26 PM Pacific time), an AWS step that the AWS CLI retried after a refused attempt (a throttled or failed reply; the CLI makes up to three attempts) was timed from its first request to the first response the CLI parsed, so a retried success could carry the time of the refused attempt and of the retry's delay. Since that release, a step on every cloud is timed by the attempt that answered: the client's retry delays stay outside the measurement, and a retried step's stderr ends with CLG retries=N. From the same release every AWS call has a 10-second connect timeout and a 120-second timeout per attempt (the AWS CLI's defaults were 60 seconds each), and every Google Cloud call is retried up to twice, as the AWS CLI retries. The status ids are unchanged; only the values of retried steps change.

Until the GCP probe release of [DEPLOY DATE] (testing resumed at [RESUME TIME] Pacific time), a Google Cloud call that curl retried after a refused reply whose body was not JSON (Google's HTML 502 error page) failed its step even when the retry answered, because the refused page sat before the answer in the step's output. Since that release such a step records the answering attempt, as every other retried step does. One step was affected before the fix (a Cloud Functions update in the net account at 5:02 AM Pacific time on November 3, 2026, removed as a harness failure).

Amazon DynamoDB Reads

Until the AWS probe release of November 2, 2026 (testing resumed at 6:26 PM Pacific time), the Amazon DynamoDB test's get-item step (aws.dynamodb.<region>--dp--get-item) made an eventually consistent read. Since that release it reads with strong consistency (--consistent-read), as every Firestore read is, so the two clouds' reads are comparable. A strongly consistent read uses twice the read capacity of an eventually consistent one. In the 1,926 runs of the eight days before the change, the eventually consistent read never returned a stale item. The status id is unchanged.

Amazon DynamoDB Table Waits

Until the AWS probe release of November 2, 2026 (testing resumed at 6:26 PM Pacific time), the Amazon DynamoDB test's table steps (aws.dynamodb.<region>--cp--create-kvtable, update-kvtable and delete-kvtable) waited for the table by running describe-table until its state changed, and stopped the clock when the last of those commands exited. That counted the last command's exit after its answer. The delete also took any failed read as the table being gone, not only the not-found answer. Since that release each step ends at the response of the read that first shows the state (ACTIVE, or not-found for the delete), as the AWS CLI's own log times it. Every wait now gives up after 300 seconds. The wait's own polls are unchanged (each poll's start-up still comes before its request), so the step times barely move: over the evening after the change their medians stayed within the steps' usual run-to-run spread of about 3 seconds. The status ids are unchanged.

Firestore Database Creation

Until the GCP probe release of November 2, 2026 (testing resumed at 6:26 PM Pacific time), the Firestore test's create step (gcp.firestore.<region>--cp--create-database) ended when Google's create operation reported done, which it does almost at once (806 ms at the median of the test's first runs). The new database then held its first write for about 4 seconds: put-document measured 4,176 ms at the median, against 118 ms for the read after it. Reads of the new database answered at their usual time (a live run on November 2, 2026). Since that release the create step also writes one document to the new database and ends when that write is answered, as the Amazon DynamoDB create step ends when the table reads ACTIVE. The document is then deleted, untimed, before the put. At the change create-database rose by about 2.7 seconds and put-document fell to its usual time (medians over the evening after the change: 3,757 ms and 127 ms, against 1,082 ms and 2,856 ms that afternoon). The status ids are unchanged.

Google Cloud Storage Copies

Since the GCP probe release of November 2, 2026 (testing resumed at 6:26 PM Pacific time), a copy (gcp.gcs.<region>--dp--copy-object-<class>) that Cloud Storage answers in several rewrite calls counts the time of every call. Before it, only the first call counted. Every copy measured up to November 2, 2026 took a single call, so no earlier measurement is affected.

Block and File Storage Timing

Until the probe release of November 2, 2026 (testing resumed at 6:26 PM Pacific time), the block storage tests' attach step (attach-volume-<tier>, on Amazon EBS and Google Cloud Persistent Disk) also timed a fio prefill of the new volume and a 3-5 second pause after it: on EBS gp2 and gp3 the prefill wrote the whole 1 GiB volume, on io1, io2, st1 and sc1 it ran for 15 seconds, and on Persistent Disk it stopped at its 20-second limit, so attach read 11-28 seconds where the attachment itself takes about 2 (EBS) to 5 (Persistent Disk). Since that release attach ends when the cloud reports the volume attached and the probe sees the device, and the prefill runs afterwards, untimed. EBS resize (update-volume-<tier>) and delete (delete-volume-<tier>) timed only the request (about 220 ms); they now wait until the new size is usable (the modification reads optimizing) and until the volume is gone, as the Persistent Disk steps always did. The four fio steps (rand-write-<tier>, seq-write-<tier>, rand-read-<tier>, seq-read-<tier>) now read and write the same prefilled 64 MiB at the start of the volume on every tier and both clouds. Before, the Persistent Disk prefill stopped at its 20-second limit, so most of its random reads fell on blocks the prefill had not written; its read latency did not change measurably with the prefilled region (pd-standard 0.7 ms before, 0.8 ms after). EBS detach is now a plain detach, as on Persistent Disk, instead of a forced one. On Amazon EFS, attach retries the mount every second instead of every 10 seconds, update (update-efs-<mode>) and delete (delete-efs-<mode>) wait until the change is applied and the file system is gone. The status ids are unchanged, so their history shows a step at the change.

EBS st1 and sc1 volumes charge each small I/O against their throughput budget as if it were 1 MiB, so their fio steps measure that pacing (about 30 ms per I/O on a 125 GiB st1 volume, 90-180 ms on sc1) rather than the device's latency. That is what a small-block workload sees on those tiers.

From that release until the probe release of November 2, 2026 (testing resumed at 10:15 PM Pacific time), the Amazon EFS fio steps were also capped at 100 I/O per second, like the block storage tests, and the cap raised the General Purpose read latency (rand-read-efs-gp from about 0.6 to 2.9 ms, seq-read-efs-gp from 0.7 to 1.0 ms): uncapped, each 5-second run re-reads its 10 MB test file several times, while the capped run's 500 reads touched most of its blocks once. The cap was then removed, so EFS reads measure as they did before November 2. Max I/O reads (about 3.3 ms) and every EFS write did not change. The EBS tests recorded no results from 6:30 to 7:20 PM Pacific time on November 2, 2026, while a missing permission held the new resize wait until it was granted.

Function Tests Aligned Across Clouds

Until the probe release of November 2, 2026 (testing resumed at 6:26 PM Pacific time), the AWS Lambda tests ran Node.js on the nodejs20.x runtime, and every Lambda runtime ran at Lambda's default 128 MB, while the Cloud Run functions test ran Node.js 24 at 256 MB. Since that release, Lambda runs Node.js 24 (nodejs24.x), and every Lambda runtime (Node.js, Python, Java, .NET and Ruby) runs at 256 MB on x86_64, the Cloud Run function's shape. Lambda's create and update now wait for the function's state with a deadline, polling back to back and stopping at the response that first reports it Active or updated. After an update, both clouds time the first invoke that the new code answers: an earlier answer from the old code is retried, untimed, about once a second for up to 30 seconds (before, the first invoke counted even when the old code answered it). The Cloud Run functions update now deploys new code, as Lambda's update-function-code does (before, it changed an environment variable, which also rebuilt the function), so both updates measure a code deployment, which on Google includes a Cloud Build. Cloud Run starts an instance while it deploys a function, so its first call after the create was already warm (77 ms against 33 ms for the warm invoke, where Lambda's first invoke is a cold start of about 320 ms against 44 ms). The release therefore ends gcp.functions.us-east4--dp--invoke-function-nodejs; the warm invoke, preceded by one untimed call, is the Cloud Run functions data plane status, and Lambda keeps its cold first invoke. The other status ids keep their names, so their history shows a step at the change.

Message Delivery Tests Aligned Across Clouds

Until the probe release of November 2, 2026 (testing resumed at 6:26 PM Pacific time), the Amazon SNS and Amazon SQS receive-message steps ran from just before the publish (or send) CLI process started to just after the receive CLI process exited, so two AWS CLI start-ups, about 1.5 seconds, sat inside a delivery time of a few hundred milliseconds (SNS read 1,948 ms at the median on November 2, 2026). SQS also sent its message with a 3 second delay and subtracted it afterwards. Since that release, delivery runs from the publish request's send to the response that carries the message, both read from the AWS CLI's own debug log, and SQS sends with no delay. A receive long-polls, up to 20 seconds per call, until the message arrives or 30 seconds pass, as Google Cloud Pub/Sub's pulls do. Pub/Sub's receive-message runs from the publish call's start to the end of the pull that carried the message (that pull's start plus curl's own time for it); before, it ended after the pull's process exited and its answer was read. SNS gains an unsubscribe step (aws.sns.us-east-1--cp--unsubscribe, a new status id), the counterpart of Pub/Sub's. SQS update-queue and delete-queue now wait until get-queue-attributes shows the change (SQS can take up to 60 seconds to apply either), where before they timed the request alone. The status ids keep their names, so the SNS and SQS receive-message history shows a step down at the change.

Compute Instance Launch and Delete

Until the probe release of November 2, 2026 (testing resumed at 6:26 PM Pacific time), the Amazon EC2 instance tests (aws.ec2.us-east-1--cp--create-instance-<os>, delete-instance-<os>) and the Compute Engine instance tests (gcp.gce.us-east4--cp--...) differed in four ways. The EC2 delete step ended when the instance reported shutting-down (about 2.8 s), while the Compute Engine delete waited until the instance was gone (105-107 s for Linux, about 133 s for Windows). EC2 launched in whichever Availability Zone it chose (us-east-1a or us-east-1c for 202 of 218 launches on November 2, 2026), while Compute Engine launched in the test probe's zone. EC2 launched whichever Amazon Linux or Windows image an unsorted image list named first (on November 2, 2026, an October 13 Amazon Linux image and a September 17 Windows image), while Compute Engine launched its image family's newest. And the two clouds' test VMs had different internet access: an EC2 instance had a public IPv4 address the probes never used plus IPv6 through its subnet, while a Compute Engine VM had none. Without internet access a Compute Engine guest stalls about 90 seconds while it shuts down, so most of its delete time was that stall: on November 2, 2026, VMs deleted side by side took 106.8 s with no internet access and 14.3 s with only an external IPv6 address.

Since that release, both clouds launch in the test probe's zone and subnet from the newest image (AWS's public SSM parameter for it, Google's image family), with no public IPv4 address and internet access over IPv6 (EC2 through its subnet, Compute Engine through an external IPv6 address). Both delete steps shut the guest down the normal way and last until the instance is gone (EC2 terminated), and both create steps check the guest's SSH or RDP port the same way, a connection attempt about every second from the test probe. The status ids are unchanged, so EC2's delete-instance-* history steps up and Compute Engine's steps down at the change. Running without a public IPv4 address does not slow the EC2 boot: three launches each way on November 2, 2026 finished booting in 6.4-7.1 s (Linux) and opened RDP within 1-3 s of each other on average (Windows).

Same-Zone Network Targets

Until the probe release of November 2, 2026 (testing resumed at 6:26 PM Pacific time), a network test from an AWS EC2 probe to its own Availability Zone (for example aws.ec2.us-east-1.use1-az1--dp--tcping6--aws.ec2.us-east-1.use1-az1) measured up to three probes in that zone on every run and stored the fastest, so the host behind the measurement changed from run to run and the stored value leaned low. The same test from a Compute Engine probe measured one host, the other test network's probe in its zone. Since that release, every same-zone test measures one host by one rule and fails if that host does not answer: the other test network's probe of the same kind in the zone (an EC2 probe in aws-ping.com measures its counterpart in aws-ping.net; a Compute Engine probe in gcp-ping.com its counterpart in gcp-ping.net), at its public address. The EC2 probes have no IPv4 internet access, so their IPv4 same-zone tests measure the same network's Lightsail probe in the zone at its private address instead (about 0.4-0.8 ms, the host those tests already reached most often). When that address cannot be read (a freshly deployed Lightsail probe's web server can be stopped for a while), the IPv4 test is not run that round; until November 3, 2026 it was run over IPv6 instead and stored under the IPv6 test's status id. Cross-zone tests are unchanged on both clouds: the same network's probe in the other zone, over the private network. A Compute Engine same-zone test crosses from one test network's project to the other's over public addresses, so on Google Cloud it reads slightly slower than a cross-zone test (about 0.97 ms against 0.90 ms on November 2, 2026).

DNS Zone and Record Waits

Until the probe release of November 2, 2026 (testing resumed at 6:26 PM Pacific time), the Amazon Route 53 test's update-record step (aws.route53--cp--update-record) upserted the test record with the value it already held, so its wait for every name server to serve the change passed at once: it read about 270 ms, against about 6.4 seconds for create-record and delete-record. Since that release the upsert writes a new value and waits until every name server serves it (7.8 seconds in a live run that day). A zone is now created, and deleted, only when every one of its name servers answers its NS query (or none does), on Route 53 and Google Cloud DNS alike; before, each poll asked one name server picked at random. Route 53's read-record now lists only the test record, as Cloud DNS reads its one record set, and Cloud DNS no longer waits for its change to report done before it asks the name servers, since Route 53 never did. Waiting for every name server can now and then take minutes (one Route 53 create-record took 148.6 seconds in testing that day). The status ids are unchanged, so the update-record history shows a step up at the change.

CDN Distribution Steps

Until the probe release of November 2, 2026 (testing resumed at 6:26 PM Pacific time), the Amazon CloudFront test's create-distro step (aws.cloudfront--cp--create-distro) polled the new distribution through the probe's DNS resolver. Its first poll came before the new *.cloudfront.net name existed, and the resolver kept that answer for cloudfront.net's 60-second negative cache, so every create read about 120 or 180 seconds (the daily median stayed between 120.7 and 121.2 seconds from October 20 to November 2, 2026). Since that release each poll looks the name up at cloudfront.net's own name servers and the servers they delegate the name to, then fetches through the address they give; a live run that day created in 95.2 seconds. update-distro disabled the distribution and waited until it stopped serving; it now changes the default cache TTL and waits until CloudFront reports the change deployed, as the Cloud CDN update changes its TTL. delete-distro repeated the update's time (160.5 against 161.3 seconds at the median); it now times taking the distribution out of service, from the disable's request through its deployment to the delete's answer, with no fixed pause. On Google Cloud, create-distro (gcp.cdn--cp--create-distro) now covers the CDN backend bucket, the host rule on the project's standing load balancer and the wait until the load balancer serves the test object, and delete-distro covers the host rule's removal and the bucket's delete, so the separate attach-distro and detach-distro steps end with this release and their ids are retired. Every CDN wait gives up after 420 seconds. The other status ids keep their names, so their history shows a step at the change.

gpt-oss-120b on the Global Endpoint

Until the GCP probe release of November 2, 2026 (testing resumed at 6:26 PM Pacific time), the Agent Platform gpt-oss-120b test asked its prompts in us-central1 (gcp.aiplatform.us-central1--...-gpt-oss-120b), then the only region Google served the model in. Since that release it asks them on Agent Platform's global endpoint, as the other Agent Platform families are asked, under gcp.aiplatform.global--...-gpt-oss-120b; the us-central1 ids end, and their history stays in the rollups. Amazon Bedrock still serves gpt-oss-120b only in us-east-1, with no global inference profile, so aws.bedrock.us-east-1--...-gpt-oss-120b keep their region.

AI Prompt Timeout on Google Cloud

Until the GCP probe release of November 2, 2026 (testing resumed at 8:44 PM Pacific time), an Agent Platform prompt (gcp.aiplatform.global--dp--converse-<prompt>-<family>) was cut off after 120 seconds, as every call on both clouds is. Agent Platform's shared pools answer slowly at times: in the three days to November 2, 2026, Gemini Flash's slowest successful answer took 117.6 seconds, beside 7 prompts cut off at 120 seconds, and one gpt-oss-120b prompt received nothing in 120 seconds. Since that release a prompt may take up to 180 seconds, so a slow answer counts as a measurement rather than a failure; a prompt that stalls is still not asked again. Amazon Bedrock's prompts keep the 120-second limit, which they never came near (3.8 seconds at most). The status ids are unchanged.

Stalled AI Prompts on Google Cloud

Until the GCP probe release of [DEPLOY DATE] (testing resumed at [RESUME TIME] Pacific time), an Agent Platform prompt that received nothing at all failed when its 180-second limit ran out, and it was not asked again. Google served one prompt, gpt-oss-120b's reasoning question from the net test network, from a backend that answers in under a second or not at all: it stalled 17 times between 8:54 PM on November 2 and 6:30 AM on November 3, 2026, and those failed runs were removed as test artifacts, as was one Gemini Flash stall. Since that release each attempt is limited to 120 seconds again, and a prompt that stalls is asked once more: its result is the attempt that answered, and its stderr ends with CLG retries=1. Two stalls in a row fail the step. Amazon Bedrock's prompts never stalled and are unchanged. The status ids are unchanged.

Dataset

Cloud Looking Glass stores its cloud service monitoring data in a PostgreSQL database: raw test results, the rollup tables built from them, and the documented outages.

Sponsorship

Sponsorship: Support the project on GoFundMe
Questions: Email info@cloudlooking.glass

About Sponsorship

Operating Cloud Looking Glass involves significant real costs:

Infrastructure Costs: Compute instances, storage, and network traffic across multiple cloud providers
API Fees: Thousands of API calls per minute across dozens of services
Data Storage: Database storage and backups
External Services: Third-party monitoring tools

Note: RIPE Atlas measurements are obtained through credits earned by hosting a RIPE Atlas Anchor Probe.

Sponsorship funds are used exclusively to cover these operational costs, enabling us to:

Sustain and expand our network of globally distributed test agents
Onboard additional cloud providers to broaden coverage
Increase visibility across more services and regions
Maintain and improve public dashboards and tools
Transition from a time-limited academic project into a long-term public resource

Research Goals:

Provide transparent, objective and independent data related to cloud availability and performance
Report measurements in near real-time without thresholds or approvals
Publish findings in a peer-reviewed academic journal in 2026

Schema

The database contains tables storing raw measurement data, test metadata, and event documentation.

Schema Diagram


┌─────────────────────────────────────────────────────────────────────────┐
│                           CLOUD LOOKING GLASS SCHEMA                     │
└─────────────────────────────────────────────────────────────────────────┘

                    PRIMARY TABLES

┌──────────────────────┐  ┌──────────────────────┐  ┌──────────────────────┐
│      tests           │  │   test_commands      │  │    test_targets      │
├──────────────────────┤  ├──────────────────────┤  ├──────────────────────┤
│ test_id (PK)         │──┤ test_id (FK)         │  │ test_id (FK)         │◄┐
│ initiator            │  │ sequence             │  │ type                 │ │
│ name                 │  │ command              │  │ cloud                │ │
│ params               │  │ name                 │  │ cloud_region         │ │
│ status               │  │ status               │  │ cloud_region_zone    │ │
│ timestamp            │  │ status_ids[]         │  │ cloud_service        │ │
│ util_cpu             │  │ measurement_mean     │  │ cloud_service_type   │ │
│ util_ram             │  │ measurement_median   │  │ cloud_sku            │ │
└──────────────────────┘  │ measurements[]       │  │ geo_country          │ │
          │               │ measurements_cli[]   │  │ geo_country_state    │ │
          │               │ measurements_wall[]  │  │ geo_regions[]        │ │
          │               │ metric               │  │ hostname             │ │
          │               │ unit                 │  │ ipv4                 │ │
          │               │ stdout               │  │ ipv6                 │ │
          │               │ stderr               │  └──────────────────────┘ │
          │               │ timestamp            │                           │
          │               └──────────────────────┘                           │
          │                         │                                        │
          │                         │                                        │
          │                         │                                        │
┌──────────────────────┐           │                                        │
│   test_outages       │           │                                        │
├──────────────────────┤           │                                        │
│ outage_id (PK)       │           │                                        │
│ operation            │           │                                        │
│ test_ids[]           │◄──────────┴────────────────────────────────────────┘
│ status_ids[]         │◄──────────┘
│ partial              │
│ notes                │
│ tlds[]               │
│ vendor_private_notes │
│ vendor_status_page_  │
│   notes              │
└──────────────────────┘

                              ROLLUP TABLES

┌──────────────────────────┐     ┌─────────────────────────────────────┐
│ test_status (real-time)  │     │ test_status_* (rollup tables)      │
├──────────────────────────┤     ├─────────────────────────────────────┤
│ status_id (PK) ◄─────────┼─────┤ status_id (PK)                      │
│ tld (PK)                 │     │ interval_start (PK)                 │
│ expires                  │     │ interval_stop                       │
│ measurements[]           │     │ events_com                          │
│ measurements_current[]   │     │ events_net                          │
│ status                   │     │ events_merged                       │
│ stdev[]                  │     │ events_merged                       │
└──────────────────────────┘     │ measurements_min                    │
                                 │ measurements_max                    │
                                 │ measurements_mean                   │
                                 │ measurements_p10                    │
                                 │ measurements_p25                    │
                                 │ measurements_p50                    │
                                 │ measurements_p75                    │
                                 │ measurements_p90                    │
                                 │ outage_ids[]                        │
                                 │ stdev_min                           │
                                 │ stdev_max                           │
                                 │ stdev_mean                          │
                                 │ stdev_p10                           │
                                 │ stdev_p25                           │
                                 │ stdev_p50                           │
                                 │ stdev_p75                           │
                                 │ stdev_p90                           │
                                 │ tests                               │
                                 └─────────────────────────────────────┘

Rollup Table Intervals:
• test_status_1w    - 10 minute intervals, 1 week retention
• test_status_1m    - 20 minute intervals, 1 month retention
• test_status_3m    - 30 minute intervals, 3 month retention
• test_status_6m    - 1 hour intervals, 6 month retention
• test_status_1y    - 2 hour intervals, 1 year retention
• test_status_2y    - 4 hour intervals, 2 year retention
• test_status_3y    - 6 hour intervals, 3 year retention
• test_status_4y    - 8 hour intervals, 4 year retention
• test_status_5y    - 12 hour intervals, 5 year retention
• test_status_daily - 24 hour intervals, unlimited retention

Key Relationships:
→ tests.test_id ← test_commands.test_id (1:many)
→ tests.test_id ← test_targets.test_id (1:many)
→ tests.test_id ← test_outages.test_ids[] (many:many)
→ test_commands.status_ids[] → test_outages.status_ids[] (many:many)
→ test_commands.status_ids[] → test_status_* rollup tables (aggregated)

Tables

The following sections describe each table in the Cloud Looking Glass database.

tests Table

Purpose: Core table storing metadata about each test execution.

Key Fields:

test_id (STRING): Unique identifier for each test (UUID format, e.g., 'd62801d3-5674-4359-ac97-5e84d60e100d')
initiator (STRING): Entity that triggered the test - 'cron' (universal tests) or 'webqueue' (distributed tests)
name (STRING): Test name - either CRUD operations (e.g., 'crud-instance-linux', 'crud-bucket') or network tests (e.g., 'tcping4', 'https', 'dns')
params (JSON): Test parameters and configuration (e.g., {"source":"central-america"})
status (STRING): Overall test result ('success', 'failed', 'error', 'mixed')
timestamp (TIMESTAMP): When the test was executed
util_cpu (INT64): CPU utilization percentage during test (0-100)
util_ram (INT64): RAM utilization percentage during test (0-100)

Clustering: By name for efficient querying by test type

Check Constraints: Status must be one of: 'success', 'failed', 'error', 'mixed'

test_commands Table

Purpose: Detailed record of each command executed within a test, including measurements and output.

Key Fields:

test_id (STRING): Foreign key linking to tests table
sequence (INT64): Order of command execution within the test (1-based, default: 1)
command (STRING): Actual CLI command executed (e.g., 'tcping -r 4 43.196.0.253 80')
name (STRING): Command name (e.g., 'create-instance-linux', 'attach-volume-st1')
status (STRING): Command execution result ('success', 'failed', 'error', 'mixed')
status_ids (ARRAY<STRING>): Structured identifiers for the operations, correlates to test_status tables (e.g., ['aws.ec2.us-east-1--cp--create-instance-linux'])

Measurement Fields - Critical Distinctions:

The three measurement arrays capture different timing perspectives, enabling both accurate cross-provider comparisons and real-world performance analysis:

measurements (ARRAY<FLOAT64>):
- What it measures: The core API operation time - as close to wire time as possible
- Excludes: CLI loading, IAM authentication, pre-flight requests
- Use case: Cross-provider performance comparison (eliminates CLI implementation differences)
- Example: For EC2 instance creation, captures time from CreateInstance API call to response
measurements_cli (ARRAY<FLOAT64>):
- What it measures: API operation time PLUS authentication overhead
- Includes: IAM/IMDS calls, token generation, but NOT CLI loading time
- Use case: Understanding practical authentication overhead
- Example: Adds ~200-500ms for IAM authentication to the core operation time
measurements_wall (ARRAY<FLOAT64>):
- What it measures: Total wall clock time from CLI invocation to completion
- Includes: Everything - CLI loading, authentication, operation, response processing
- Use case: Real-world end-user experience
- Example: Python-based AWS CLI adds 1-3s loading time vs Go-based CLIs adding ~100ms

Statistical Fields:

measurement_mean (FLOAT64): Average of the measurements array (e.g., 15920 ms for EC2 instance creation)
measurement_median (FLOAT64): Median of the measurements array (50th percentile)
measurement_stdev (FLOAT64): Standard deviation indicating consistency/variability

Metadata Fields:

metric (STRING): What was measured ('latency', 'rtt', 'throughput', 'iops')
unit (STRING): Measurement unit ('ms', 'MB/s', 's', 'IOPS')
stdout (STRING): Command standard output
stderr (STRING): Command error output
timestamp (TIMESTAMP): Command execution time

Important Notes on Measurements:

For network tests (ping, tcping), all three measurement arrays are typically identical since there's minimal CLI overhead
For control plane operations, the difference between measurements and measurements_wall can be 10x or more
The measurements array is the primary metric for fair cross-provider comparisons
Use measurements_wall when analyzing user-perceived performance

Partitioning: By DATE(timestamp) for efficient time-based queries

Primary Key: Composite of (test_id, sequence, timestamp)

test_targets Table

Purpose: Source and destination information for tests, including cloud provider and geographic details.

Key Fields:

test_id (STRING): Foreign key linking to tests table
type (STRING): Target type ('source', 'dest', 'target')
Cloud Provider Information:
cloud (STRING): Provider name - supports 26+ providers including: aws, gcp, azure, alibaba, tencent, cloudflare, akamai, fastly, etc.
cloud_region (STRING): Region identifier (e.g., 'us-east-1', 'cn-north-1', 'ap-southeast-1')
cloud_region_zone (STRING): Availability zone (e.g., 'use1-az1', 'use1-az2')
cloud_service (STRING): Service name (e.g., 'ec2', 's3', 'cloudfront')
cloud_service_type (STRING): Service variant (e.g., 'compute', 'storage')
cloud_sku (STRING): SKU/instance type (e.g., 't3.micro', 'gp3')
Geographic Information:
geo_country (CHAR(2)): ISO 3166-1 alpha-2 country code
geo_country_state (CHAR(2)): State/province code
geo_regions (ARRAY<STRING>): Geographic regions (e.g., ['eu'], ['mea'], ['apac'])
Network Information:
hostname (STRING): Test agent hostname (e.g., 'use1-az2.us-east-1.aws-ping.com')
ipv4 (STRING): IPv4 address
ipv6 (STRING): IPv6 address

Clustering: By cloud for efficient provider-specific queries

Primary Key: Composite of (test_id, type)

test_outages Table

Purpose: Manually verified and documented service outages with detailed analysis.

Key Fields:

outage_id (STRING): Unique identifier following patterns:
Control plane: '{cloud}-cp-{service}-{date}-{seq}' (e.g., 'aws-cp-crud-volume-st1-20250815-1')
Data plane: '{cloud}-dp-{service}-{date}-{seq}' (e.g., 'aws-dp-crud-inference-claude-haiku-20250626-1')
operation (STRING): Specific operation that failed (e.g., 'attach-volume-st1', 'converse-fact-claude-haiku')
test_ids (ARRAY<STRING>): Array of affected test IDs
partial (BOOLEAN): Whether outage affected all accounts (FALSE) or subset (TRUE) - most outages are partial
notes (STRING): Detailed description of the failure with specific error messages
status_ids (ARRAY<STRING>): Structured identifiers for affected services (see Status ID Format section)
tlds (ARRAY<STRING>): Top-level domains affected ('com', 'net') corresponding to test accounts
vendor_private_notes (STRING): Internal vendor communications (usually NULL)
vendor_status_page_notes (STRING): Public vendor status page entries (usually NULL)

Primary Key: outage_id

test_status_* Rollup Tables

Purpose: Time-based aggregation tables providing historical analysis at various granularities.

Note: These aggregation tables are pre-computed in PostgreSQL for efficient time-series analysis.

Available Tables:

test_status - Real-time ingest table (24-hour window, 10-minute intervals)
test_status_1w - 10-minute aggregates with 1-week retention
test_status_1m - 20-minute aggregates with 1-month retention
test_status_3m - 30-minute aggregates with 3-month retention
test_status_6m - 1-hour aggregates with 6-month retention
test_status_1y - 2-hour aggregates with 1-year retention
test_status_2y - 4-hour aggregates with 2-year retention
test_status_3y - 6-hour aggregates with 3-year retention
test_status_4y - 8-hour aggregates with 4-year retention
test_status_5y - 12-hour aggregates with 5-year retention
test_status_daily - 24-hour aggregates with unlimited retention

Key Fields (Common Across All Rollup Tables):

status_id (STRING): Test identifier following the Status ID Format (see Important Notes section)
interval_start (TIMESTAMP): Beginning of the time window
interval_stop (TIMESTAMP): End of the time window
events_com, events_net, events_merged (INT64): Event counts per TLD and merged view
measurements_min, measurements_max, measurements_mean (FLOAT64): Statistical aggregates
measurements_p10, measurements_p25, measurements_p50, measurements_p75, measurements_p90 (FLOAT64): Percentile values
outage_ids (ARRAY<STRING>): Associated outage identifiers for this time window
stdev_min, stdev_max, stdev_mean (FLOAT64): Standard deviation statistics
stdev_p10, stdev_p25, stdev_p50, stdev_p75, stdev_p90 (FLOAT64): Standard deviation percentiles
tests (INT64): Total test count in the interval

Real-time Status Table (test_status):

Primary Key: Composite of (status_id, tld)
tld (STRING): Top-level domain ('com', 'net', 'merged')
expires (TIMESTAMP): When current measurement window expires
measurements (ARRAY<FLOAT64>): Historical measurements (144 values = 24 hours)
measurements_current (ARRAY<FLOAT64>): Current window measurements
status (STRING): Current status indicator
stdev (ARRAY<FLOAT64>): Rolling standard deviation values

Usage Notes:

Rollup tables are automatically populated from raw test data
Use appropriate granularity based on your query time range
Status IDs enable correlation with test_commands and test_outages tables
The 'merged' TLD provides a unified view across all test accounts

Service Types

Cloud services in the CLG testing framework are classified into two fundamental types based on their operational independence and testing requirements. This classification is essential for understanding the test design and the relationships between different services.

Primary Services

Primary services are standalone, fully functional cloud resources that can operate independently without requiring attachment to other services. These services have both control plane and data plane operations that can be tested in isolation.

Characteristics of Primary Services:

Independent operation: Can be provisioned and used without dependencies on other services
Complete lifecycle: Support full CRUD operations independently
Direct data plane access: Have their own data plane operations that don't require other resources
Self-contained testing: Both control and data plane can be tested without external dependencies

Examples of Primary Services:

EC2 Instances: Virtual machines that run independently
S3 Buckets: Object storage that operates standalone
Lambda Functions: Serverless compute that executes independently
DynamoDB Tables: NoSQL databases with direct data operations
CloudFront Distributions: CDN endpoints that serve content independently
Route53 Zones: DNS services that resolve independently

Supporting Services

Supporting services (also called secondary services) are cloud resources that provide essential capabilities but require attachment to or integration with primary services to demonstrate their functional value. While these services have their own control plane operations, their data plane functionality is only meaningful when connected to a primary service.

Characteristics of Supporting Services:

Dependency on primary services: Require attachment to a primary service for functional validation
Extended control plane: Include attachment/detachment operations as part of their control plane
Indirect data plane testing: Data plane operations tested through the primary service they support
Composite testing: Full validation requires testing both the supporting service and its integration

Examples of Supporting Services:

EBS Volumes (Elastic Block Store):
- Control Plane: Create, delete, attach, detach, snapshot operations
- Data Plane: Read/write operations only testable when attached to an EC2 instance
- Test Pattern: crud-volume-{type} includes attach/detach to EC2 instances
EFS Filesystems (Elastic File System):
- Control Plane: Create, delete, mount target operations
- Data Plane: File operations only testable when mounted to EC2 instances
- Test Pattern: Requires EC2 instance with mount operations for data plane validation
Elastic Network Interfaces (ENIs):
- Control Plane: Create, delete, attach, detach operations
- Data Plane: Network traffic only flows when attached to instances
- Test Pattern: Network functionality validated through attached instances
VPC Endpoints:
- Control Plane: Create, delete, modify operations
- Data Plane: Traffic routing only functional when connected to VPCs and services
- Test Pattern: Requires active VPC with connected resources

Testing Implications:

The distinction between primary and supporting services has important implications for test design:

Test Sequencing: Supporting service tests often require provisioning a primary service first
Resource Management: Tests must manage both the supporting service and its primary service dependency
Cleanup Complexity: Must detach supporting services before deleting primary services
Status ID Structure: Attachment operations are considered control plane operations
- Example: aws.ebs.us-east-1--cp--attach-volume-gp3
Performance Metrics: Data plane metrics for supporting services are captured through the primary service

Query Example - Identifying Service Dependencies:

-- Find tests that involve both primary and supporting services
WITH service_dependencies AS (
    SELECT
        t.name as test_name,
        tc.name as command_name,
        CASE
            WHEN tc.name LIKE '%attach%' OR tc.name LIKE '%detach%' THEN 'Supporting Service Operation'
            WHEN tc.name LIKE '%mount%' OR tc.name LIKE '%unmount%' THEN 'Supporting Service Operation'
            ELSE 'Standard Operation'
        END as operation_type,
        tc.status,
        tc.measurement_mean
    FROM clg.tests t
    JOIN clg.test_commands tc ON t.test_id = tc.test_id
    WHERE t.name LIKE 'crud-volume-%'
       OR t.name LIKE 'crud-filesystem-%'
)
SELECT
    test_name,
    operation_type,
    COUNT(*) as operation_count,
    AVG(measurement_mean) as avg_duration_ms,
    COUNTIF(status = 'success') / COUNT(*) as success_rate
FROM service_dependencies
GROUP BY test_name, operation_type
ORDER BY test_name, operation_type;

Test Categories

The CLG monitoring system organizes tests into three distinct categories based on the type of operations being measured. The test category is embedded directly in the status_id using the separator pattern: --cp-- for Control Plane and --dp-- for Data Plane (including Networking). This convention enables efficient filtering and aggregation of test results by category.

Control Plane Tests

Purpose: Validate cloud provider API operations for resource lifecycle management (Create, Read, Update, Delete).

Test Name Pattern: crud-{service} or crud-{service}-{variant}
Status ID Pattern: {cloud}.{service}.{region}--cp--{operation}
Example Status ID: aws.ec2.us-east-1--cp--create-instance-linux

Examples with Status IDs:

EC2 Instance Creation:
- Test: crud-instance-linux
- Status ID: aws.ec2.us-east-1--cp--create-instance-linux
S3 Bucket Operations:
- Test: crud-bucket
- Status IDs: aws.s3.us-east-1--cp--create-bucket, aws.s3.us-east-1--cp--delete-bucket
EBS Volume Management:
- Test: crud-volume-gp3
- Status IDs: aws.ebs.us-east-1--cp--create-volume-gp3, aws.ebs.us-east-1--cp--attach-volume-gp3
Lambda Function Lifecycle:
- Test: crud-function-python
- Status ID: aws.lambda.us-east-1--cp--update-function-python
CloudFront Distribution (global service, no region):
- Test: crud-distro
- Status ID: aws.cloudfront--cp--create-distro
Cloud Run Function Lifecycle (GCP):
- Test: crud-function-nodejs
- Status ID: gcp.functions.us-east4--cp--create-function-nodejs

Note: The --cp-- separator clearly identifies these as Control Plane operations, distinguishing them from Data Plane operations.

Data Plane Tests

Purpose: Measure performance of operations on existing cloud resources (not network connectivity).

Status ID Pattern: {cloud}.{service}.{region}--dp--{operation}
Example Status ID: aws.lambda.us-east-1--dp--invoke-function-python

Examples with Status IDs:

Bedrock AI Inference:
- Operation: Answering factual questions using the newest active Claude Haiku model. The status ID names the model family and where it is served (global: Bedrock's global cross-region inference profile, so a request entering us-east-1 may be served in any commercial region); each result records the model version it ran
- Status ID: aws.bedrock.global--dp--converse-fact-claude-haiku
Lambda Function Invocation:
- Operation: Cold start invocation of Python function
- Status ID: aws.lambda.us-east-1--dp--invoke-function-python
DynamoDB Item Operations:
- Operation: Reading an item from a table
- Status ID: aws.dynamodb.us-east-1--dp--get-item
S3 Object Operations:
- Operation: Uploading object to S3 Standard storage
- Status ID: aws.s3.us-east-1--dp--put-object-standard
EBS Volume I/O:
- Operation: Sequential write to gp3 volume
- Status ID: aws.ebs.us-east-1--dp--seq-write-gp3
SQS Message Operations:
- Operation: Sending a message to queue
- Status ID: aws.sqs.us-east-1--dp--send-message
Agent Platform AI Inference (GCP):
- Operation: Answering factual questions using the newest Gemini Flash model, invoked on the global endpoint
- Status ID: gcp.aiplatform.global--dp--converse-fact-gemini-flash

Note: Data Plane operations use --dp-- but follow the pattern {cloud}.{service}.{region}--dp--{operation}, without source/destination components.

Networking Tests

Purpose: Measure network connectivity, latency, and performance between endpoints. While technically part of the data plane, networking tests form such a large category (1,512+ status IDs) that they are tracked separately.

Status ID Pattern: {source}--dp--{test-type}--{destination}
Example Status ID: aws.ec2.us-east-1--dp--tcping4--aws.s3.us-east-1

Test Types:

tcping4, tcping6: TCP connectivity tests (IPv4/IPv6)
ping4, ping6: ICMP ping tests
dns, adns, gdns: DNS resolution tests (standard/RIPE Atlas/Globalping)
aping4, aping6, gping4, gping6: External ping tests via RIPE Atlas / Globalping
http, https: HTTP/HTTPS endpoint availability
httpb-100mb, httpsb-100mb: Bandwidth tests with 100MB downloads

Examples with Status IDs:

TCP Connectivity Test:
- Test: EC2 in us-east-1 to S3 in same region
- Status ID: aws.ec2.us-east-1--dp--tcping4--aws.s3.us-east-1
DNS Resolution Test:
- Test: DNS query from EC2 to Route53
- Status ID: aws.ec2.us-east-1--dp--dns--aws.route53
External Ping Test:
- Test: RIPE Atlas probe from Europe to AWS CloudFront
- Status ID: eu--dp--aping4--aws.cloudfront

4.3.1 Zonal Measurements

72 status IDs

Purpose: Measure latency between availability zones within a single region
Example: aws.ec2.us-east-1.use1-az1--dp--tcping4--aws.ec2.us-east-1.use1-az2
Typical latency: 0.5-2ms between AZs

4.3.2 Regional Measurements

77 status IDs

Purpose: Test connectivity between services within the same region
Example: aws.ec2.us-east-1--dp--tcping4--aws.s3.us-east-1
Use case: Verify low-latency access to regional services

4.3.3 Cross-Region Measurements

183 status IDs

Purpose: Measure latency between different regions of the same provider
Example: aws.ec2.us-east-1--dp--tcping4--aws.ec2.eu-west-1
Typical latency: 70-250ms depending on geographic distance

4.3.4 Edge Measurements

52 status IDs

Purpose: Test connectivity to CDN and edge services
Example: aws.ec2.us-east-1--dp--https--aws.cloudfront
Services tested: CloudFront, Route53, Global Accelerator

4.3.5 Cross-Cloud Measurements

724 status IDs

Purpose: Measure connectivity between different cloud providers
Example: aws.ec2.us-east-1--dp--tcping4--gcp.compute.us-central1
Providers: AWS ↔ GCP, AWS ↔ Azure, AWS ↔ Cloudflare, etc.

4.3.6 Last Mile Measurements

471 status IDs

Purpose: Measure connectivity from geographic regions to cloud services using external probe networks
Example: north-america--dp--gping4--aws.ec2.us-east-1
Sources: Geographic regions (eu, apac, mea, north-america, central-america)
Probe Networks: RIPE Atlas (aping), Globalping (gping)

Note: The {source}--dp--{test-type}--{destination} pattern in networking status IDs enables precise tracking of network paths and performance metrics across different scopes.

Data Characteristics

Update Frequency

Tests run every 10 minutes (144 times per day)
Real-time data ingestion with <1 minute delay
Outages documented within hours of detection

Data Volume

~1.5 million tests per day across all services
~5 million command executions per day
25+ AWS regions monitored continuously
100+ availability zones covered

Data Retention

Raw test data: 1 day for successful network tests, 1 week for successful CRUD tests and failed network tests, 1 month for failed CRUD tests; tests linked to a documented outage are kept
Rollups: from 1 week at 10-minute resolution to 5 years at 12-hour resolution, and daily records with no expiry
Documented outages: no expiry

Availability vs Performance

Availability Metrics

Availability measures whether a service is operational and accessible. In the CLG dataset, availability is determined by:

Test Success Rate: The ratio of successful tests to total tests over a time period
Outage Detection: Documented failures in the test_outages table indicate availability issues
Error Patterns: Specific error types (timeouts, connection refused, service unavailable) signal availability problems
TLD Distribution: The events_com, events_net columns show per-account impact
Merged Events: The events_merged column indicates cross-account availability issues (2-3 accounts affected simultaneously)

Calculating Availability

-- Service availability over the last 24 hours
SELECT
    status_id,
    COUNT(*) as total_tests,
    SUM(CASE WHEN events_merged = 0 THEN 1 ELSE 0 END) as successful_tests,
    ROUND(100.0 * SUM(CASE WHEN events_merged = 0 THEN 1 ELSE 0 END) / COUNT(*), 2) as availability_percent
FROM clg.test_status_1w
WHERE interval_start >= TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 24 HOUR)
    AND status_id LIKE 'aws.ec2%--cp--%'
GROUP BY status_id
ORDER BY availability_percent ASC;

Performance Metrics

Performance measures how quickly and efficiently a service responds when it is available. The CLG dataset captures multiple performance dimensions:

Measurement Methodology

The CLG measurement approach aims to capture timing as close to the actual API request/response wire time as possible. This methodology is critical for enabling fair comparability across cloud providers, as different provider CLIs have vastly different non-operation related overheads (e.g., AWS CLI is Python-based while other providers use compiled Go binaries that load faster).

measurements[]: The primary measurement array captures the time delta between initial API request and response for the specific operation. This reflects the actual API performance at the wire level, excluding IAM authentication and other pre-request operations. This is the most comparable metric across providers as it isolates the actual service performance from CLI implementation differences.
measurements_cli[]: Includes the API operation time plus IAM-related pre-requests and authentication overhead extracted from CLI debug output. This shows the practical overhead of authentication but still excludes CLI loading time.
measurements_wall[]: The total wall clock time for the entire CLI command execution, which is the longest measurement as it includes:
- Time to load the CLI into memory (varies significantly between Python, Go, Java, etc.)
- All authentication and pre-flight checks
- The actual API operation
- Response processing and cleanup

AWS tests run the AWS CLI with --debug, whose log times each call; Google Cloud tests call the services' REST APIs with curl, which times each call itself. Both clocks cover the same span (a fresh connection, the request and the whole response), and CLG's cross-cloud measurement contract (src/php/clg/harness/README.md) defines what each kind of step measures on every provider: when a step is done, how a retried call is timed, and what a wait counts.

Measurement Columns

In test_commands table:

measurements[]: Array of raw API timing measurements in milliseconds (closest to actual API performance)
measurements_wall[]: Wall clock time measurements (total elapsed time including all overhead)
measurements_cli[]: CLI-specific timing extracted from debug output (includes IAM but excludes CLI loading)
measurement_mean: Average of all measurements
measurement_median: Median value (50th percentile)
measurement_stdev: Standard deviation indicating consistency

In rollup tables (test_status_*):

measurements_min: Minimum observed value in the time window
measurements_max: Maximum observed value in the time window
measurements_mean: Average across all measurements
measurements_p10: 10th percentile (fastest 10%)
measurements_p25: 25th percentile (first quartile)
measurements_p50: 50th percentile (median)
measurements_p75: 75th percentile (third quartile)
measurements_p90: 90th percentile (slowest 10%)

Performance Analysis Examples

-- Analyze EC2 instance creation performance trends
SELECT
    DATE(interval_start) as date,
    status_id,
    AVG(measurements_mean) as avg_latency_ms,
    AVG(measurements_p90) as p90_latency_ms,
    MAX(measurements_max) as max_latency_ms
FROM clg.test_status_daily
WHERE status_id = 'aws.ec2.us-east-1--cp--create-instance-linux'
    AND interval_start >= DATE_SUB(CURRENT_DATE(), INTERVAL 30 DAY)
GROUP BY date, status_id
ORDER BY date DESC;

-- Identify performance degradation by comparing current vs historical
SELECT
    tc.name as operation,
    AVG(tc.measurement_mean) as current_avg_ms,
    hist.historical_avg_ms,
    ROUND(100.0 * (AVG(tc.measurement_mean) - hist.historical_avg_ms) / hist.historical_avg_ms, 1) as percent_change
FROM clg.test_commands tc
JOIN (
    SELECT
        name,
        AVG(measurement_mean) as historical_avg_ms
    FROM clg.test_commands
    WHERE timestamp BETWEEN TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 30 DAY)
                      AND TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 7 DAY)
    GROUP BY name
) hist ON tc.name = hist.name
WHERE tc.timestamp >= TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 24 HOUR)
    AND tc.measurement_mean IS NOT NULL
GROUP BY tc.name, hist.historical_avg_ms
HAVING percent_change > 20
ORDER BY percent_change DESC;

Service Events

Cloud service incidents can be categorized into two primary types based on their scope and impact. The CLG schema provides multiple mechanisms to differentiate between these event types through the strategic use of dual-redundant test accounts and cross-account correlation.

Isolated Events

Isolated events are service disruptions that do not impact all test accounts simultaneously. When a failure occurs in only one or two of our three redundant test accounts while others continue operating normally, this indicates an isolated event rather than a widespread service issue. These events typically indicate:

Localized infrastructure failures: Single availability zone degradation or specific host failures
Partial service degradation: Issues affecting a subset of API endpoints or service instances
Regional capacity constraints: Temporary resource limitations in specific locations
Rolling deployment issues: Problems during phased updates that haven't reached all infrastructure

Note: Account-specific issues like IAM misconfigurations, quota limits, rate limiting, or permission problems are removed from our dataset as they don't represent actual service availability issues.

Identifying Isolated Events in the Schema

The CLG dataset identifies isolated events through several key indicators:

Single TLD Failures: When only one of the two test accounts (.com, .net, or .org) experiences failures

-- Find isolated events affecting single accounts
SELECT
    status_id,
    interval_start,
    events_com,
    events_net,
    events_merged,
    CASE
        WHEN (events_com > 0 AND events_net = 0 THEN 'Isolated to .com'
        WHEN (events_net > 0 AND events_com = 0 THEN 'Isolated to .net'
        ELSE 'Multiple accounts affected'
    END as isolation_pattern
FROM clg.test_status_1w
WHERE interval_start >= TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 24 HOUR)
    AND events_merged = 0  -- No merged events indicates no cross-account impact
    AND (events_com + events_net) > 0  -- At least one failure
ORDER BY interval_start DESC;

Partial Outages: The test_outages.partial = TRUE flag indicates limited impact

-- Analyze partial outages (isolated events)
SELECT
    outage_id,
    operation,
    ARRAY_LENGTH(test_ids) as affected_tests,
    ARRAY_LENGTH(tlds) as affected_accounts,
    notes
FROM clg.test_outages
WHERE partial = TRUE
    AND ARRAY_LENGTH(tlds) = 1  -- Single account affected
ORDER BY outage_id DESC
LIMIT 20;

Low or Zero events_merged Values: Indicates failures are not synchronized across accounts

Large Service Events (LSEs)

Large Service Events are incidents observed to impact multiple unrelated customer accounts for the same provider at the same time. LSEs represent significant availability issues that affect the service broadly, rather than isolated customer-specific problems. LSEs typically indicate:

Control plane failures: API endpoint unavailability or complete service failures
Regional outages: Complete region or availability zone failures
Cascading failures: Service dependencies causing widespread unavailability
Infrastructure-wide issues: Power failures, network partitioning, or data center problems

Identifying LSEs in the Schema

The CLG dataset provides several mechanisms to identify and differentiate LSEs from isolated events:

The partial Column in test_outages:
- partial = FALSE: Indicates all two test accounts (.com, .net, .org) were affected - strong LSE indicator
- partial = TRUE: Indicates only 1-2 accounts affected - may be isolated or limited in scope
Event Columns in Rollup Tables:
- events_com, events_net: Count of failed tests per TLD account
- events_merged: Count of tests where 2-3 accounts failed simultaneously
- High events_merged values indicate LSEs affecting multiple accounts

Cross-Account Correlation:

-- Identify potential LSEs by finding simultaneous failures across accounts
SELECT
    status_id,
    interval_start,
    events_com,
    events_net,
    events_merged,
    CASE
        WHEN events_merged > 0 AND events_merged >= 0.5 * tests THEN 'Likely LSE'
        WHEN events_merged > 0 THEN 'Possible LSE'
        ELSE 'Isolated Event'
    END as event_classification,
    outage_ids
FROM clg.test_status_1w
WHERE interval_start >= TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 24 HOUR)
    AND (events_com > 0 OR events_net > 0 )
    AND status_id LIKE 'aws%'
ORDER BY events_merged DESC, interval_start DESC
LIMIT 100;

Outage Documentation Analysis:

-- Analyze documented outages to identify LSEs
SELECT
    outage_id,
    operation,
    partial,
    ARRAY_LENGTH(test_ids) as affected_tests,
    ARRAY_LENGTH(tlds) as affected_tlds,
    notes,
    CASE
        WHEN partial = FALSE THEN 'Confirmed LSE'
        WHEN ARRAY_LENGTH(tlds) >= 2 THEN 'Probable LSE'
        ELSE 'Isolated/Limited Impact'
    END as lse_classification
FROM clg.test_outages
WHERE ARRAY_LENGTH(test_ids) > 0
ORDER BY outage_id DESC
LIMIT 50;

LSE Impact Assessment

To assess the impact and scope of an LSE:

Geographic Scope: Check if failures span multiple regions
Service Scope: Determine if multiple services are affected
Duration: Calculate how long the event persisted
Recovery Pattern: Analyze if all accounts recovered simultaneously

-- LSE analysis
WITH event_summary AS (
    SELECT
        DATE(interval_start) as event_date,
        EXTRACT(HOUR FROM interval_start) as event_hour,
        STRING_AGG(DISTINCT REGEXP_EXTRACT(status_id, r'\.(\\w+)\.'), ', ') as affected_services,
        STRING_AGG(DISTINCT REGEXP_EXTRACT(status_id, r'\.([a-z]+-[a-z]+-\\d+)'), ', ') as affected_regions,
        SUM(events_merged) as total_merged_events,
        COUNT(DISTINCT status_id) as unique_status_ids,
        MAX(measurements_max) as max_latency_observed
    FROM clg.test_status_1w
    WHERE interval_start >= TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 7 DAY)
        AND events_merged > 0
    GROUP BY event_date, event_hour
    HAVING total_merged_events > 10
)
SELECT
    *,
    CASE
        WHEN unique_status_ids > 5 AND total_merged_events > 50 THEN 'Major LSE'
        WHEN unique_status_ids > 2 AND total_merged_events > 20 THEN 'Moderate LSE'
        ELSE 'Minor LSE'
    END as severity
FROM event_summary
ORDER BY event_date DESC, total_merged_events DESC;

Differentiating Event Types - Key Schema Indicators

The following table summarizes how to distinguish between Isolated Events and Large Service Events using the CLG schema:

Schema Element	Isolated Event	Large Service Event (LSE)
`test_outages.partial`	`TRUE` (1-2 accounts affected)	`FALSE` (all 3 accounts affected)
`events_merged` in rollups	0 or very low	High values (>50% of tests)
TLD distribution	Single TLD shows failures	Multiple or all TLDs show failures
`test_outages.tlds[]` array	Length = 1	Length ≥ 2
Failure timing	Staggered across accounts	Simultaneous across accounts
Recovery pattern	Independent recovery	Synchronized recovery
Typical causes	Account limits, quotas, config	Service-wide outages

Practical Query for Event Classification

-- Event classification query
WITH event_analysis AS (
    SELECT
        status_id,
        interval_start,
        events_com,
        events_net,
        events_merged,
        tests,
        ARRAY_LENGTH(outage_ids) as documented_outages,
        -- Calculate affected account count
        CAST(events_com > 0 AS INT64) +
        CAST(events_net > 0 AS INT64) +
        CAST(events_com > 0 AS INT64) + CAST(events_net > 0 AS INT64) as affected_accounts,
        -- Calculate merge ratio
        SAFE_DIVIDE(events_merged, GREATEST(events_com, events_net)) as merge_ratio
    FROM clg.test_status_1w
    WHERE interval_start >= TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 24 HOUR)
        AND (events_com > 0 OR events_net > 0 )
)
SELECT
    *,
    CASE
        WHEN affected_accounts = 3 AND merge_ratio > 0.8 THEN 'Confirmed LSE'
        WHEN affected_accounts >= 2 AND merge_ratio > 0.5 THEN 'Probable LSE'
        WHEN affected_accounts >= 2 AND merge_ratio < 0.5 THEN 'Concurrent Isolated Events'
        WHEN affected_accounts = 1 THEN 'Isolated Event'
        ELSE 'Unknown'
    END as event_classification
FROM event_analysis
ORDER BY interval_start DESC, events_merged DESC;

Important Notes on Event Detection

Performance degradation is not classified as an event: The CLG system tracks availability as binary (working/not working). Performance variations are captured in the measurement fields but don't constitute "events" unless the service becomes unavailable.
Triple redundancy enables detection: The use of three independent test accounts (.com, .net, .org) is fundamental to distinguishing between account-specific issues and service-wide problems.
Timing matters: True LSEs show synchronized failures and recoveries across accounts, while isolated events show staggered patterns.
The partial flag is authoritative: When documenting outages, the partial field in test_outages provides the definitive classification based on human analysis of the failure pattern.

Important Notes on Status IDs

Status IDs are stored directly with test data: The test_commands.status_ids array contains structured identifiers for each operation, enabling direct correlation with test_outages and rollup tables
Status ID patterns: Status IDs follow consistent patterns based on test type:
- Control Plane: {cloud}.{service}.{region}--cp--{operation}
- Data Plane: {cloud}.{service}.{region}--dp--{operation}
- Network: {source}--dp--{test-type}--{destination}
Service naming conventions: Status IDs use the official provider service identifiers (e.g., AWS CLI service names)
Direct querying: You can query test_commands directly using status_ids for filtering and analysis without needing complex joins
AI inference ids name where the model is served (card wS9zmPC4, Nov 2026): a model invoked on a global endpoint or cross-region profile is global in place of the region (aws.bedrock.global--dp--converse-fact-claude-haiku, gcp.aiplatform.global--dp--converse-fact-gemini-flash); a model served in one region keeps it (aws.bedrock.us-east-1--...-gpt-oss-120b: Bedrock has no global profile for it, while Agent Platform serves it on its global endpoint, gcp.aiplatform.global--...-gpt-oss-120b, since card mpTFAfQU). When Bedrock's claude-haiku, claude-sonnet, gpt-luna and gpt-sol moved to its global inference profiles, their results measured since their first round (10:40 AM PST Nov 1 2026) moved to aws.bedrock.global in every table; everything before stays under the aws.bedrock.us-east-1 ids as a closed series - for claude-haiku, the earlier Claude 3 Haiku test since Feb 2025 and its outages

Appendix A: Status ID Reference

I. Control Plane Status IDs (173 IDs)

Control plane tests validate cloud provider API operations for resource lifecycle management.


aws.bedrock.global--cp--create-inference-claude-haiku
aws.bedrock.global--cp--create-inference-claude-sonnet
aws.bedrock.global--cp--create-inference-gpt-luna
aws.bedrock.us-east-1--cp--create-inference-gpt-oss-120b
aws.bedrock.global--cp--create-inference-gpt-sol
aws.bedrock.global--cp--delete-inference-claude-haiku
aws.bedrock.global--cp--delete-inference-claude-sonnet
aws.bedrock.global--cp--delete-inference-gpt-luna
aws.bedrock.us-east-1--cp--delete-inference-gpt-oss-120b
aws.bedrock.global--cp--delete-inference-gpt-sol
aws.bedrock.global--cp--read-inference-claude-haiku
aws.bedrock.global--cp--read-inference-claude-sonnet
aws.bedrock.global--cp--read-inference-gpt-luna
aws.bedrock.us-east-1--cp--read-inference-gpt-oss-120b
aws.bedrock.global--cp--read-inference-gpt-sol
aws.bedrock.global--cp--update-inference-claude-haiku
aws.bedrock.global--cp--update-inference-claude-sonnet
aws.bedrock.global--cp--update-inference-gpt-luna
aws.bedrock.us-east-1--cp--update-inference-gpt-oss-120b
aws.bedrock.global--cp--update-inference-gpt-sol
aws.cloudfront--cp--create-distro
aws.cloudfront--cp--delete-distro
aws.cloudfront--cp--read-distro
aws.cloudfront--cp--update-distro
aws.dynamodb.us-east-1--cp--create-kvtable
aws.dynamodb.us-east-1--cp--delete-kvtable
aws.dynamodb.us-east-1--cp--read-kvtable
aws.dynamodb.us-east-1--cp--update-kvtable
aws.ebs.us-east-1--cp--attach-volume-gp2
aws.ebs.us-east-1--cp--attach-volume-gp3
aws.ebs.us-east-1--cp--attach-volume-io1
aws.ebs.us-east-1--cp--attach-volume-io2
aws.ebs.us-east-1--cp--attach-volume-sc1
aws.ebs.us-east-1--cp--attach-volume-st1
aws.ebs.us-east-1--cp--create-volume-gp2
aws.ebs.us-east-1--cp--create-volume-gp3
aws.ebs.us-east-1--cp--create-volume-io1
aws.ebs.us-east-1--cp--create-volume-io2
aws.ebs.us-east-1--cp--create-volume-sc1
aws.ebs.us-east-1--cp--create-volume-st1
aws.ebs.us-east-1--cp--delete-volume-gp2
aws.ebs.us-east-1--cp--delete-volume-gp3
aws.ebs.us-east-1--cp--delete-volume-io1
aws.ebs.us-east-1--cp--delete-volume-io2
aws.ebs.us-east-1--cp--delete-volume-sc1
aws.ebs.us-east-1--cp--delete-volume-st1
aws.ebs.us-east-1--cp--detach-volume-gp2
aws.ebs.us-east-1--cp--detach-volume-gp3
aws.ebs.us-east-1--cp--detach-volume-io1
aws.ebs.us-east-1--cp--detach-volume-io2
aws.ebs.us-east-1--cp--detach-volume-sc1
aws.ebs.us-east-1--cp--detach-volume-st1
aws.ebs.us-east-1--cp--read-volume-gp2
aws.ebs.us-east-1--cp--read-volume-gp3
aws.ebs.us-east-1--cp--read-volume-io1
aws.ebs.us-east-1--cp--read-volume-io2
aws.ebs.us-east-1--cp--read-volume-sc1
aws.ebs.us-east-1--cp--read-volume-st1
aws.ebs.us-east-1--cp--update-volume-gp2
aws.ebs.us-east-1--cp--update-volume-gp3
aws.ebs.us-east-1--cp--update-volume-io1
aws.ebs.us-east-1--cp--update-volume-io2
aws.ebs.us-east-1--cp--update-volume-sc1
aws.ebs.us-east-1--cp--update-volume-st1
aws.ec2.us-east-1--cp--create-instance-linux
aws.ec2.us-east-1--cp--create-instance-windows
aws.ec2.us-east-1--cp--delete-instance-linux
aws.ec2.us-east-1--cp--delete-instance-windows
aws.ec2.us-east-1--cp--read-instance-linux
aws.ec2.us-east-1--cp--read-instance-windows
aws.ec2.us-east-1--cp--update-instance-linux
aws.ec2.us-east-1--cp--update-instance-windows
aws.efs.us-east-1--cp--attach-efs-gp
aws.efs.us-east-1--cp--attach-efs-maxio
aws.efs.us-east-1--cp--create-efs-gp
aws.efs.us-east-1--cp--create-efs-maxio
aws.efs.us-east-1--cp--delete-efs-gp
aws.efs.us-east-1--cp--delete-efs-maxio
aws.efs.us-east-1--cp--detach-efs-gp
aws.efs.us-east-1--cp--detach-efs-maxio
aws.efs.us-east-1--cp--read-efs-gp
aws.efs.us-east-1--cp--read-efs-maxio
aws.efs.us-east-1--cp--update-efs-gp
aws.efs.us-east-1--cp--update-efs-maxio
aws.lambda.us-east-1--cp--create-function-dotnet
aws.lambda.us-east-1--cp--create-function-java
aws.lambda.us-east-1--cp--create-function-nodejs
aws.lambda.us-east-1--cp--create-function-python
aws.lambda.us-east-1--cp--create-function-ruby
aws.lambda.us-east-1--cp--delete-function-dotnet
aws.lambda.us-east-1--cp--delete-function-java
aws.lambda.us-east-1--cp--delete-function-nodejs
aws.lambda.us-east-1--cp--delete-function-python
aws.lambda.us-east-1--cp--delete-function-ruby
aws.lambda.us-east-1--cp--read-function-dotnet
aws.lambda.us-east-1--cp--read-function-java
aws.lambda.us-east-1--cp--read-function-nodejs
aws.lambda.us-east-1--cp--read-function-python
aws.lambda.us-east-1--cp--read-function-ruby
aws.lambda.us-east-1--cp--update-function-dotnet
aws.lambda.us-east-1--cp--update-function-java
aws.lambda.us-east-1--cp--update-function-nodejs
aws.lambda.us-east-1--cp--update-function-python
aws.lambda.us-east-1--cp--update-function-ruby
aws.route53--cp--create-record
aws.route53--cp--create-zone
aws.route53--cp--delete-record
aws.route53--cp--delete-zone
aws.route53--cp--read-record
aws.route53--cp--read-zone
aws.route53--cp--update-record
aws.route53--cp--update-zone
aws.s3.us-east-1--cp--create-bucket
aws.s3.us-east-1--cp--create-bucket-directory
aws.s3.us-east-1--cp--delete-bucket
aws.s3.us-east-1--cp--delete-bucket-directory
aws.s3.us-east-1--cp--read-bucket
aws.s3.us-east-1--cp--read-bucket-directory
aws.s3.us-east-1--cp--update-bucket
aws.s3tables.us-east-1--cp--create-s3table-bucket
aws.s3tables.us-east-1--cp--create-s3table-namespace
aws.s3tables.us-east-1--cp--create-s3table-table
aws.s3tables.us-east-1--cp--delete-s3table-bucket
aws.s3tables.us-east-1--cp--delete-s3table-namespace
aws.s3tables.us-east-1--cp--delete-s3table-table
aws.s3tables.us-east-1--cp--read-s3table
aws.s3tables.us-east-1--cp--rename-s3table-table
aws.sns.us-east-1--cp--create-topic
aws.sns.us-east-1--cp--delete-topic
aws.sns.us-east-1--cp--read-topic
aws.sns.us-east-1--cp--subscribe
aws.sns.us-east-1--cp--unsubscribe
aws.sns.us-east-1--cp--update-topic
aws.sqs.us-east-1--cp--create-queue
aws.sqs.us-east-1--cp--delete-queue
aws.sqs.us-east-1--cp--read-queue
aws.sqs.us-east-1--cp--update-queue
aws.vpc.us-east-1--cp--create-vpc
aws.vpc.us-east-1--cp--delete-vpc
aws.vpc.us-east-1--cp--read-vpc
aws.vpc.us-east-1--cp--update-vpc
gcp.aiplatform.global--cp--create-inference-gemini-flash
gcp.aiplatform.global--cp--delete-inference-gemini-flash
gcp.aiplatform.global--cp--read-inference-gemini-flash
gcp.aiplatform.global--cp--update-inference-gemini-flash
gcp.aiplatform.global--cp--create-inference-gpt-oss-120b
gcp.aiplatform.global--cp--delete-inference-gpt-oss-120b
gcp.aiplatform.global--cp--read-inference-gpt-oss-120b
gcp.aiplatform.global--cp--update-inference-gpt-oss-120b
gcp.cdn--cp--attach-distro
gcp.cdn--cp--create-distro
gcp.cdn--cp--delete-distro
gcp.cdn--cp--detach-distro
gcp.cdn--cp--read-distro
gcp.cdn--cp--update-distro
gcp.dns--cp--create-record
gcp.dns--cp--create-zone
gcp.dns--cp--delete-record
gcp.dns--cp--delete-zone
gcp.dns--cp--read-record
gcp.dns--cp--read-zone
gcp.dns--cp--update-record
gcp.dns--cp--update-zone
gcp.firestore.us-east4--cp--create-database
gcp.firestore.us-east4--cp--delete-database
gcp.firestore.us-east4--cp--read-database
gcp.firestore.us-east4--cp--update-database
gcp.functions.us-east4--cp--create-function-nodejs
gcp.functions.us-east4--cp--delete-function-nodejs
gcp.functions.us-east4--cp--read-function-nodejs
gcp.functions.us-east4--cp--update-function-nodejs
gcp.pubsub.us-east4--cp--create-topic
gcp.pubsub.us-east4--cp--delete-topic
gcp.pubsub.us-east4--cp--read-topic
gcp.pubsub.us-east4--cp--subscribe
gcp.pubsub.us-east4--cp--unsubscribe
gcp.pubsub.us-east4--cp--update-topic

II. Data Plane Status IDs (118 IDs)

Data plane tests measure performance operations on existing cloud resources.


aws.bedrock.global--dp--converse-code-claude-haiku
aws.bedrock.global--dp--converse-code-claude-sonnet
aws.bedrock.global--dp--converse-code-gpt-luna
aws.bedrock.us-east-1--dp--converse-code-gpt-oss-120b
aws.bedrock.global--dp--converse-code-gpt-sol
aws.bedrock.global--dp--converse-fact-claude-haiku
aws.bedrock.global--dp--converse-fact-claude-sonnet
aws.bedrock.global--dp--converse-fact-gpt-luna
aws.bedrock.us-east-1--dp--converse-fact-gpt-oss-120b
aws.bedrock.global--dp--converse-fact-gpt-sol
aws.bedrock.global--dp--converse-math-claude-haiku
aws.bedrock.global--dp--converse-math-claude-sonnet
aws.bedrock.global--dp--converse-math-gpt-luna
aws.bedrock.us-east-1--dp--converse-math-gpt-oss-120b
aws.bedrock.global--dp--converse-math-gpt-sol
aws.bedrock.global--dp--converse-reasoning-claude-haiku
aws.bedrock.global--dp--converse-reasoning-claude-sonnet
aws.bedrock.global--dp--converse-reasoning-gpt-luna
aws.bedrock.us-east-1--dp--converse-reasoning-gpt-oss-120b
aws.bedrock.global--dp--converse-reasoning-gpt-sol
aws.dynamodb.us-east-1--dp--delete-item
aws.dynamodb.us-east-1--dp--get-item
aws.dynamodb.us-east-1--dp--put-item
aws.dynamodb.us-east-1--dp--update-item
aws.efs.us-east-1--dp--rand-read-efs-gp
aws.efs.us-east-1--dp--rand-read-efs-maxio
aws.ebs.us-east-1--dp--rand-read-gp2
aws.ebs.us-east-1--dp--rand-read-gp3
aws.ebs.us-east-1--dp--rand-read-io1
aws.ebs.us-east-1--dp--rand-read-io2
aws.ebs.us-east-1--dp--rand-read-sc1
aws.ebs.us-east-1--dp--rand-read-st1
aws.efs.us-east-1--dp--rand-write-efs-gp
aws.efs.us-east-1--dp--rand-write-efs-maxio
aws.ebs.us-east-1--dp--rand-write-gp2
aws.ebs.us-east-1--dp--rand-write-gp3
aws.ebs.us-east-1--dp--rand-write-io1
aws.ebs.us-east-1--dp--rand-write-io2
aws.ebs.us-east-1--dp--rand-write-sc1
aws.ebs.us-east-1--dp--rand-write-st1
aws.efs.us-east-1--dp--seq-read-efs-gp
aws.efs.us-east-1--dp--seq-read-efs-maxio
aws.ebs.us-east-1--dp--seq-read-gp2
aws.ebs.us-east-1--dp--seq-read-gp3
aws.ebs.us-east-1--dp--seq-read-io1
aws.ebs.us-east-1--dp--seq-read-io2
aws.ebs.us-east-1--dp--seq-read-sc1
aws.ebs.us-east-1--dp--seq-read-st1
aws.efs.us-east-1--dp--seq-write-efs-gp
aws.efs.us-east-1--dp--seq-write-efs-maxio
aws.ebs.us-east-1--dp--seq-write-gp2
aws.ebs.us-east-1--dp--seq-write-gp3
aws.ebs.us-east-1--dp--seq-write-io1
aws.ebs.us-east-1--dp--seq-write-io2
aws.ebs.us-east-1--dp--seq-write-sc1
aws.ebs.us-east-1--dp--seq-write-st1
aws.lambda.us-east-1--dp--invoke-function-after-update-dotnet
aws.lambda.us-east-1--dp--invoke-function-after-update-java
aws.lambda.us-east-1--dp--invoke-function-after-update-nodejs
aws.lambda.us-east-1--dp--invoke-function-after-update-python
aws.lambda.us-east-1--dp--invoke-function-after-update-ruby
aws.lambda.us-east-1--dp--invoke-function-dotnet
aws.lambda.us-east-1--dp--invoke-function-java
aws.lambda.us-east-1--dp--invoke-function-nodejs
aws.lambda.us-east-1--dp--invoke-function-python
aws.lambda.us-east-1--dp--invoke-function-ruby
aws.lambda.us-east-1--dp--invoke-function-warm-dotnet
aws.lambda.us-east-1--dp--invoke-function-warm-java
aws.lambda.us-east-1--dp--invoke-function-warm-nodejs
aws.lambda.us-east-1--dp--invoke-function-warm-python
aws.lambda.us-east-1--dp--invoke-function-warm-ruby
aws.s3.us-east-1--dp--copy-object-express-onezone
aws.s3.us-east-1--dp--copy-object-glacier-ir
aws.s3.us-east-1--dp--copy-object-onezone-ia
aws.s3.us-east-1--dp--copy-object-standard
aws.s3.us-east-1--dp--copy-object-standard-ia
aws.s3.us-east-1--dp--delete-object-express-onezone
aws.s3.us-east-1--dp--delete-object-glacier-ir
aws.s3.us-east-1--dp--delete-object-onezone-ia
aws.s3.us-east-1--dp--delete-object-standard
aws.s3.us-east-1--dp--delete-object-standard-ia
aws.s3.us-east-1--dp--get-object-express-onezone
aws.s3.us-east-1--dp--get-object-glacier-ir
aws.s3.us-east-1--dp--get-object-onezone-ia
aws.s3.us-east-1--dp--get-object-range-express-onezone
aws.s3.us-east-1--dp--get-object-range-glacier-ir
aws.s3.us-east-1--dp--get-object-range-onezone-ia
aws.s3.us-east-1--dp--get-object-range-standard
aws.s3.us-east-1--dp--get-object-range-standard-ia
aws.s3.us-east-1--dp--get-object-standard
aws.s3.us-east-1--dp--get-object-standard-ia
aws.s3.us-east-1--dp--head-object-express-onezone
aws.s3.us-east-1--dp--head-object-glacier-ir
aws.s3.us-east-1--dp--head-object-onezone-ia
aws.s3.us-east-1--dp--head-object-standard
aws.s3.us-east-1--dp--head-object-standard-ia
aws.s3.us-east-1--dp--put-object-express-onezone
aws.s3.us-east-1--dp--put-object-glacier-ir
aws.s3.us-east-1--dp--put-object-onezone-ia
aws.s3.us-east-1--dp--put-object-standard
aws.s3.us-east-1--dp--put-object-standard-ia
aws.sns.us-east-1--dp--publish
aws.sns.us-east-1--dp--receive-message
aws.sqs.us-east-1--dp--receive-message
aws.sqs.us-east-1--dp--send-message
gcp.aiplatform.global--dp--converse-code-gemini-flash
gcp.aiplatform.global--dp--converse-fact-gemini-flash
gcp.aiplatform.global--dp--converse-math-gemini-flash
gcp.aiplatform.global--dp--converse-reasoning-gemini-flash
gcp.aiplatform.global--dp--converse-code-gpt-oss-120b
gcp.aiplatform.global--dp--converse-fact-gpt-oss-120b
gcp.aiplatform.global--dp--converse-math-gpt-oss-120b
gcp.aiplatform.global--dp--converse-reasoning-gpt-oss-120b
gcp.firestore.us-east4--dp--delete-document
gcp.firestore.us-east4--dp--get-document
gcp.firestore.us-east4--dp--put-document
gcp.firestore.us-east4--dp--update-document
gcp.functions.us-east4--dp--invoke-function-after-update-nodejs
gcp.functions.us-east4--dp--invoke-function-warm-nodejs
gcp.pubsub.us-east4--dp--publish
gcp.pubsub.us-east4--dp--receive-message

III. Network Status IDs (1512 IDs)

Network Test Categories:

Zonal: Tests between availability zones within the same region
Regional: Same provider, same region (e.g., EC2 to S3 in us-east-1)
Cross-Region: Same provider, different regions (e.g., AWS us-east-1 to AWS eu-west-1)
Cross-Cloud: Different providers (e.g., AWS to Azure or GCP)
Last Mile: Tests between cloud services and geographic-specific last mile networks (via RIPE Atlas/Globalping)

Zonal Measurements (72 IDs)

Tests within the same availability zone.


aws.ec2.us-east-1.use1-az1--dp--tcping4--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az1--dp--tcping4--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az1--dp--tcping4--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az1--dp--tcping4--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az1--dp--tcping4--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az1--dp--tcping4--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az1--dp--tcping6--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az1--dp--tcping6--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az1--dp--tcping6--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az1--dp--tcping6--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az1--dp--tcping6--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az1--dp--tcping6--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az2--dp--tcping4--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az2--dp--tcping4--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az2--dp--tcping4--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az2--dp--tcping4--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az2--dp--tcping4--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az2--dp--tcping4--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az2--dp--tcping6--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az2--dp--tcping6--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az2--dp--tcping6--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az2--dp--tcping6--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az2--dp--tcping6--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az2--dp--tcping6--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az3--dp--tcping4--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az3--dp--tcping4--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az3--dp--tcping4--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az3--dp--tcping4--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az3--dp--tcping4--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az3--dp--tcping4--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az3--dp--tcping6--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az3--dp--tcping6--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az3--dp--tcping6--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az3--dp--tcping6--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az3--dp--tcping6--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az3--dp--tcping6--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az4--dp--tcping4--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az4--dp--tcping4--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az4--dp--tcping4--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az4--dp--tcping4--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az4--dp--tcping4--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az4--dp--tcping4--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az4--dp--tcping6--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az4--dp--tcping6--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az4--dp--tcping6--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az4--dp--tcping6--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az4--dp--tcping6--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az4--dp--tcping6--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az5--dp--tcping4--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az5--dp--tcping4--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az5--dp--tcping4--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az5--dp--tcping4--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az5--dp--tcping4--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az5--dp--tcping4--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az5--dp--tcping6--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az5--dp--tcping6--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az5--dp--tcping6--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az5--dp--tcping6--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az5--dp--tcping6--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az5--dp--tcping6--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az6--dp--tcping4--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az6--dp--tcping4--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az6--dp--tcping4--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az6--dp--tcping4--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az6--dp--tcping4--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az6--dp--tcping4--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az6--dp--tcping6--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az6--dp--tcping6--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az6--dp--tcping6--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az6--dp--tcping6--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az6--dp--tcping6--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az6--dp--tcping6--aws.ec2.us-east-1.use1-az6

Regional Measurements (77 IDs)

Tests between different services or zones within the same region of the same cloud provider (e.g., aws.ec2.us-east-1 to aws.s3.us-east-1).

aws.ec2.us-east-1--dp--http--aws.s3.us-east-1
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.us-east-1
aws.ec2.us-east-1--dp--tcping4--aws.s3.us-east-1
aws.ec2.us-east-1--dp--tcping4--aws.us-east-1
aws.ec2.us-east-1--dp--tcping6--aws.us-east-1
aws.ec2.us-east-1.use1-az1--dp--tcping4--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az1--dp--tcping4--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az1--dp--tcping4--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az1--dp--tcping4--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az1--dp--tcping4--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az1--dp--tcping4--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az1--dp--tcping6--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az1--dp--tcping6--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az1--dp--tcping6--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az1--dp--tcping6--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az1--dp--tcping6--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az1--dp--tcping6--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az2--dp--tcping4--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az2--dp--tcping4--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az2--dp--tcping4--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az2--dp--tcping4--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az2--dp--tcping4--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az2--dp--tcping4--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az2--dp--tcping6--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az2--dp--tcping6--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az2--dp--tcping6--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az2--dp--tcping6--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az2--dp--tcping6--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az2--dp--tcping6--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az3--dp--tcping4--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az3--dp--tcping4--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az3--dp--tcping4--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az3--dp--tcping4--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az3--dp--tcping4--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az3--dp--tcping4--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az3--dp--tcping6--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az3--dp--tcping6--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az3--dp--tcping6--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az3--dp--tcping6--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az3--dp--tcping6--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az3--dp--tcping6--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az4--dp--tcping4--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az4--dp--tcping4--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az4--dp--tcping4--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az4--dp--tcping4--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az4--dp--tcping4--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az4--dp--tcping4--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az4--dp--tcping6--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az4--dp--tcping6--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az4--dp--tcping6--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az4--dp--tcping6--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az4--dp--tcping6--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az4--dp--tcping6--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az5--dp--tcping4--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az5--dp--tcping4--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az5--dp--tcping4--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az5--dp--tcping4--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az5--dp--tcping4--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az5--dp--tcping4--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az5--dp--tcping6--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az5--dp--tcping6--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az5--dp--tcping6--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az5--dp--tcping6--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az5--dp--tcping6--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az5--dp--tcping6--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az6--dp--tcping4--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az6--dp--tcping4--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az6--dp--tcping4--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az6--dp--tcping4--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az6--dp--tcping4--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az6--dp--tcping4--aws.ec2.us-east-1.use1-az6
aws.ec2.us-east-1.use1-az6--dp--tcping6--aws.ec2.us-east-1.use1-az1
aws.ec2.us-east-1.use1-az6--dp--tcping6--aws.ec2.us-east-1.use1-az2
aws.ec2.us-east-1.use1-az6--dp--tcping6--aws.ec2.us-east-1.use1-az3
aws.ec2.us-east-1.use1-az6--dp--tcping6--aws.ec2.us-east-1.use1-az4
aws.ec2.us-east-1.use1-az6--dp--tcping6--aws.ec2.us-east-1.use1-az5
aws.ec2.us-east-1.use1-az6--dp--tcping6--aws.ec2.us-east-1.use1-az6

Cross-Region Measurements (183 IDs)

Tests between different regions of the same cloud provider (e.g., aws.ec2.us-east-1 to aws.s3.eu-west-1).

aws.ca-central-1--dp--gping4--aws.us-east-1
aws.ca-central-1--dp--gping4--aws.us-east-2
aws.ca-central-1--dp--gping4--aws.us-west-1
aws.ca-central-1--dp--gping4--aws.us-west-2
aws.ec2.us-east-1--dp--http--aws.s3.af-south-1
aws.ec2.us-east-1--dp--http--aws.s3.ap-east-1
aws.ec2.us-east-1--dp--http--aws.s3.ap-northeast-1
aws.ec2.us-east-1--dp--http--aws.s3.ap-northeast-2
aws.ec2.us-east-1--dp--http--aws.s3.ap-northeast-3
aws.ec2.us-east-1--dp--http--aws.s3.ap-south-1
aws.ec2.us-east-1--dp--http--aws.s3.ap-south-2
aws.ec2.us-east-1--dp--http--aws.s3.ap-southeast-1
aws.ec2.us-east-1--dp--http--aws.s3.ap-southeast-2
aws.ec2.us-east-1--dp--http--aws.s3.ap-southeast-3
aws.ec2.us-east-1--dp--http--aws.s3.ap-southeast-4
aws.ec2.us-east-1--dp--http--aws.s3.ap-southeast-5
aws.ec2.us-east-1--dp--http--aws.s3.ap-southeast-7
aws.ec2.us-east-1--dp--http--aws.s3.ca-central-1
aws.ec2.us-east-1--dp--http--aws.s3.ca-west-1
aws.ec2.us-east-1--dp--http--aws.s3.eu-central-1
aws.ec2.us-east-1--dp--http--aws.s3.eu-central-2
aws.ec2.us-east-1--dp--http--aws.s3.eu-north-1
aws.ec2.us-east-1--dp--http--aws.s3.eu-south-1
aws.ec2.us-east-1--dp--http--aws.s3.eu-south-2
aws.ec2.us-east-1--dp--http--aws.s3.eu-west-1
aws.ec2.us-east-1--dp--http--aws.s3.eu-west-2
aws.ec2.us-east-1--dp--http--aws.s3.eu-west-3
aws.ec2.us-east-1--dp--http--aws.s3.il-central-1
aws.ec2.us-east-1--dp--http--aws.s3.me-central-1
aws.ec2.us-east-1--dp--http--aws.s3.me-south-1
aws.ec2.us-east-1--dp--http--aws.s3.mx-central-1
aws.ec2.us-east-1--dp--http--aws.s3.sa-east-1
aws.ec2.us-east-1--dp--http--aws.s3.us-east-2
aws.ec2.us-east-1--dp--http--aws.s3.us-west-1
aws.ec2.us-east-1--dp--http--aws.s3.us-west-2
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.af-south-1
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.ap-east-1
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.ap-northeast-1
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.ap-northeast-2
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.ap-northeast-3
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.ap-south-1
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.ap-south-2
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.ap-southeast-1
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.ap-southeast-2
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.ap-southeast-3
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.ap-southeast-4
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.ap-southeast-5
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.ap-southeast-7
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.ca-central-1
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.ca-west-1
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.eu-central-1
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.eu-central-2
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.eu-north-1
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.eu-south-1
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.eu-south-2
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.eu-west-1
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.eu-west-2
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.eu-west-3
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.il-central-1
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.me-central-1
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.me-south-1
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.mx-central-1
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.sa-east-1
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.us-east-2
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.us-west-1
aws.ec2.us-east-1--dp--httpb-100mb--aws.s3.us-west-2
aws.ec2.us-east-1--dp--tcping4--aws.af-south-1
aws.ec2.us-east-1--dp--tcping4--aws.af-south-1-los-1
aws.ec2.us-east-1--dp--tcping4--aws.ap-east-1
aws.ec2.us-east-1--dp--tcping4--aws.ap-northeast-1
aws.ec2.us-east-1--dp--tcping4--aws.ap-northeast-2
aws.ec2.us-east-1--dp--tcping4--aws.ap-northeast-3
aws.ec2.us-east-1--dp--tcping4--aws.ap-south-1
aws.ec2.us-east-1--dp--tcping4--aws.ap-south-2
aws.ec2.us-east-1--dp--tcping4--aws.ap-southeast-1
aws.ec2.us-east-1--dp--tcping4--aws.ap-southeast-2
aws.ec2.us-east-1--dp--tcping4--aws.ap-southeast-3
aws.ec2.us-east-1--dp--tcping4--aws.ap-southeast-4
aws.ec2.us-east-1--dp--tcping4--aws.ap-southeast-5
aws.ec2.us-east-1--dp--tcping4--aws.ap-southeast-7
aws.ec2.us-east-1--dp--tcping4--aws.ca-central-1
aws.ec2.us-east-1--dp--tcping4--aws.ca-west-1
aws.ec2.us-east-1--dp--tcping4--aws.eu-central-1
aws.ec2.us-east-1--dp--tcping4--aws.eu-central-2
aws.ec2.us-east-1--dp--tcping4--aws.eu-north-1
aws.ec2.us-east-1--dp--tcping4--aws.eu-south-1
aws.ec2.us-east-1--dp--tcping4--aws.eu-south-2
aws.ec2.us-east-1--dp--tcping4--aws.eu-west-1
aws.ec2.us-east-1--dp--tcping4--aws.eu-west-2
aws.ec2.us-east-1--dp--tcping4--aws.eu-west-3
aws.ec2.us-east-1--dp--tcping4--aws.il-central-1
aws.ec2.us-east-1--dp--tcping4--aws.me-central-1
aws.ec2.us-east-1--dp--tcping4--aws.me-south-1
aws.ec2.us-east-1--dp--tcping4--aws.me-south-1-mct-1
aws.ec2.us-east-1--dp--tcping4--aws.mx-central-1
aws.ec2.us-east-1--dp--tcping4--aws.s3.af-south-1
aws.ec2.us-east-1--dp--tcping4--aws.s3.ap-east-1
aws.ec2.us-east-1--dp--tcping4--aws.s3.ap-northeast-1
aws.ec2.us-east-1--dp--tcping4--aws.s3.ap-northeast-2
aws.ec2.us-east-1--dp--tcping4--aws.s3.ap-northeast-3
aws.ec2.us-east-1--dp--tcping4--aws.s3.ap-south-1
aws.ec2.us-east-1--dp--tcping4--aws.s3.ap-south-2
aws.ec2.us-east-1--dp--tcping4--aws.s3.ap-southeast-1
aws.ec2.us-east-1--dp--tcping4--aws.s3.ap-southeast-2
aws.ec2.us-east-1--dp--tcping4--aws.s3.ap-southeast-3
aws.ec2.us-east-1--dp--tcping4--aws.s3.ap-southeast-4
aws.ec2.us-east-1--dp--tcping4--aws.s3.ap-southeast-5
aws.ec2.us-east-1--dp--tcping4--aws.s3.ap-southeast-7
aws.ec2.us-east-1--dp--tcping4--aws.s3.ca-central-1
aws.ec2.us-east-1--dp--tcping4--aws.s3.ca-west-1
aws.ec2.us-east-1--dp--tcping4--aws.s3.eu-central-1
aws.ec2.us-east-1--dp--tcping4--aws.s3.eu-central-2
aws.ec2.us-east-1--dp--tcping4--aws.s3.eu-north-1
aws.ec2.us-east-1--dp--tcping4--aws.s3.eu-south-1
aws.ec2.us-east-1--dp--tcping4--aws.s3.eu-south-2
aws.ec2.us-east-1--dp--tcping4--aws.s3.eu-west-1
aws.ec2.us-east-1--dp--tcping4--aws.s3.eu-west-2
aws.ec2.us-east-1--dp--tcping4--aws.s3.eu-west-3
aws.ec2.us-east-1--dp--tcping4--aws.s3.il-central-1
aws.ec2.us-east-1--dp--tcping4--aws.s3.me-central-1
aws.ec2.us-east-1--dp--tcping4--aws.s3.me-south-1
aws.ec2.us-east-1--dp--tcping4--aws.s3.mx-central-1
aws.ec2.us-east-1--dp--tcping4--aws.s3.sa-east-1
aws.ec2.us-east-1--dp--tcping4--aws.s3.us-east-2
aws.ec2.us-east-1--dp--tcping4--aws.s3.us-west-1
aws.ec2.us-east-1--dp--tcping4--aws.s3.us-west-2
aws.ec2.us-east-1--dp--tcping4--aws.sa-east-1
aws.ec2.us-east-1--dp--tcping4--aws.us-east-2
aws.ec2.us-east-1--dp--tcping4--aws.us-gov-east-1
aws.ec2.us-east-1--dp--tcping4--aws.us-gov-west-1
aws.ec2.us-east-1--dp--tcping4--aws.us-west-1
aws.ec2.us-east-1--dp--tcping4--aws.us-west-2
aws.ec2.us-east-1--dp--tcping4--aws.us-west-2-lax-1
aws.ec2.us-east-1--dp--tcping6--aws.af-south-1
aws.ec2.us-east-1--dp--tcping6--aws.ap-east-1
aws.ec2.us-east-1--dp--tcping6--aws.ap-northeast-1
aws.ec2.us-east-1--dp--tcping6--aws.ap-northeast-2
aws.ec2.us-east-1--dp--tcping6--aws.ap-northeast-3
aws.ec2.us-east-1--dp--tcping6--aws.ap-south-1
aws.ec2.us-east-1--dp--tcping6--aws.ap-south-2
aws.ec2.us-east-1--dp--tcping6--aws.ap-southeast-1
aws.ec2.us-east-1--dp--tcping6--aws.ap-southeast-2
aws.ec2.us-east-1--dp--tcping6--aws.ap-southeast-3
aws.ec2.us-east-1--dp--tcping6--aws.ap-southeast-4
aws.ec2.us-east-1--dp--tcping6--aws.ap-southeast-5
aws.ec2.us-east-1--dp--tcping6--aws.ap-southeast-7
aws.ec2.us-east-1--dp--tcping6--aws.ca-central-1
aws.ec2.us-east-1--dp--tcping6--aws.ca-west-1
aws.ec2.us-east-1--dp--tcping6--aws.eu-central-1
aws.ec2.us-east-1--dp--tcping6--aws.eu-central-2
aws.ec2.us-east-1--dp--tcping6--aws.eu-north-1
aws.ec2.us-east-1--dp--tcping6--aws.eu-south-1
aws.ec2.us-east-1--dp--tcping6--aws.eu-south-2
aws.ec2.us-east-1--dp--tcping6--aws.eu-west-1
aws.ec2.us-east-1--dp--tcping6--aws.eu-west-2
aws.ec2.us-east-1--dp--tcping6--aws.eu-west-3
aws.ec2.us-east-1--dp--tcping6--aws.il-central-1
aws.ec2.us-east-1--dp--tcping6--aws.me-central-1
aws.ec2.us-east-1--dp--tcping6--aws.me-south-1
aws.ec2.us-east-1--dp--tcping6--aws.mx-central-1
aws.ec2.us-east-1--dp--tcping6--aws.sa-east-1
aws.ec2.us-east-1--dp--tcping6--aws.us-east-2
aws.ec2.us-east-1--dp--tcping6--aws.us-gov-east-1
aws.ec2.us-east-1--dp--tcping6--aws.us-gov-west-1
aws.ec2.us-east-1--dp--tcping6--aws.us-west-1
aws.ec2.us-east-1--dp--tcping6--aws.us-west-2
aws.ec2.us-east-1--dp--tcping6--aws.us-west-2-lax-1
aws.us-east-1--dp--gping4--aws.ca-central-1
aws.us-east-1--dp--gping4--aws.us-east-2
aws.us-east-1--dp--gping4--aws.us-west-1
aws.us-east-1--dp--gping4--aws.us-west-2
aws.us-east-2--dp--gping4--aws.ca-central-1
aws.us-east-2--dp--gping4--aws.us-east-1
aws.us-east-2--dp--gping4--aws.us-west-1
aws.us-east-2--dp--gping4--aws.us-west-2
aws.us-west-1--dp--gping4--aws.ca-central-1
aws.us-west-1--dp--gping4--aws.us-east-1
aws.us-west-1--dp--gping4--aws.us-east-2
aws.us-west-1--dp--gping4--aws.us-west-2
aws.us-west-2--dp--gping4--aws.ca-central-1
aws.us-west-2--dp--gping4--aws.us-east-1
aws.us-west-2--dp--gping4--aws.us-east-2
aws.us-west-2--dp--gping4--aws.us-west-1

Edge Measurements (52 IDs)

Tests between cloud providers and global edge services (CDNs and DNS) that don't have a specific region.

aws.ec2.us-east-1--dp--dns--akamai.dns
aws.ec2.us-east-1--dp--dns--alibaba.dns
aws.ec2.us-east-1--dp--dns--aws.route53
aws.ec2.us-east-1--dp--dns--azure.dns
aws.ec2.us-east-1--dp--dns--bunny.dns
aws.ec2.us-east-1--dp--dns--cloudflare.dns
aws.ec2.us-east-1--dp--dns--digitalocean.dns
aws.ec2.us-east-1--dp--dns--dnsmadeeasy.dns
aws.ec2.us-east-1--dp--dns--easydns.dns
aws.ec2.us-east-1--dp--dns--gcp.dns
aws.ec2.us-east-1--dp--dns--ns1.dns
aws.ec2.us-east-1--dp--dns--rage4.dns
aws.ec2.us-east-1--dp--dns--ultradns.dns
aws.ec2.us-east-1--dp--http--akamai.cdn
aws.ec2.us-east-1--dp--http--alibaba.cdn
aws.ec2.us-east-1--dp--http--aws.cloudfront
aws.ec2.us-east-1--dp--http--azure.cdn
aws.ec2.us-east-1--dp--http--bunny.cdn
aws.ec2.us-east-1--dp--http--cachefly.cdn
aws.ec2.us-east-1--dp--http--cdnetworks.cdn
aws.ec2.us-east-1--dp--http--fastly.cdn
aws.ec2.us-east-1--dp--http--gcp.cdn
aws.ec2.us-east-1--dp--http--tencent.cdn
aws.ec2.us-east-1--dp--https--akamai.cdn
aws.ec2.us-east-1--dp--https--aws.cloudfront
aws.ec2.us-east-1--dp--https--azure.cdn
aws.ec2.us-east-1--dp--https--bunny.cdn
aws.ec2.us-east-1--dp--https--cachefly.cdn
aws.ec2.us-east-1--dp--https--cdnetworks.cdn
aws.ec2.us-east-1--dp--https--cloudflare.cdn
aws.ec2.us-east-1--dp--https--digitalocean.cdn
aws.ec2.us-east-1--dp--https--scaleway.cdn
aws.ec2.us-east-1--dp--tcping4--akamai.cdn
aws.ec2.us-east-1--dp--tcping4--alibaba.cdn
aws.ec2.us-east-1--dp--tcping4--aws.cloudfront
aws.ec2.us-east-1--dp--tcping4--azure.cdn
aws.ec2.us-east-1--dp--tcping4--bunny.cdn
aws.ec2.us-east-1--dp--tcping4--cachefly.cdn
aws.ec2.us-east-1--dp--tcping4--cdnetworks.cdn
aws.ec2.us-east-1--dp--tcping4--cloudflare.cdn
aws.ec2.us-east-1--dp--tcping4--digitalocean.cdn
aws.ec2.us-east-1--dp--tcping4--fastly.cdn
aws.ec2.us-east-1--dp--tcping4--gcp.cdn
aws.ec2.us-east-1--dp--tcping4--scaleway.cdn
aws.ec2.us-east-1--dp--tcping4--tencent.cdn
aws.ec2.us-east-1--dp--tcping6--aws.cloudfront
aws.ec2.us-east-1--dp--tcping6--azure.cdn
aws.ec2.us-east-1--dp--tcping6--cloudflare.cdn
aws.ec2.us-east-1--dp--tcping6--fastly.cdn
aws.ec2.us-east-1--dp--tcping6--gcp.cdn
aws.ec2.us-east-1--dp--tcping6--scaleway.cdn
aws.ec2.us-east-1--dp--tcping6--tencent.cdn

Cross-Cloud Measurements (724 IDs)

Tests between different cloud providers' regional services (e.g., aws.ec2.us-east-1 to azure.storage.eastus or gcp.storage.us-central1).

aws.ec2.us-east-1--dp--http--alibaba.oss.ap-northeast-1
aws.ec2.us-east-1--dp--http--alibaba.oss.ap-northeast-2
aws.ec2.us-east-1--dp--http--alibaba.oss.ap-southeast-1
aws.ec2.us-east-1--dp--http--alibaba.oss.ap-southeast-3
aws.ec2.us-east-1--dp--http--alibaba.oss.ap-southeast-5
aws.ec2.us-east-1--dp--http--alibaba.oss.ap-southeast-6
aws.ec2.us-east-1--dp--http--alibaba.oss.ap-southeast-7
aws.ec2.us-east-1--dp--http--alibaba.oss.eu-central-1
aws.ec2.us-east-1--dp--http--alibaba.oss.eu-west-1
aws.ec2.us-east-1--dp--http--alibaba.oss.me-central-1
aws.ec2.us-east-1--dp--http--alibaba.oss.me-east-1
aws.ec2.us-east-1--dp--http--alibaba.oss.na-south-1
aws.ec2.us-east-1--dp--http--alibaba.oss.us-east-1
aws.ec2.us-east-1--dp--http--alibaba.oss.us-west-1
aws.ec2.us-east-1--dp--http--azure.storage.australiacentral
aws.ec2.us-east-1--dp--http--azure.storage.australiaeast
aws.ec2.us-east-1--dp--http--azure.storage.australiasoutheast
aws.ec2.us-east-1--dp--http--azure.storage.brazilsouth
aws.ec2.us-east-1--dp--http--azure.storage.canadacentral
aws.ec2.us-east-1--dp--http--azure.storage.canadaeast
aws.ec2.us-east-1--dp--http--azure.storage.centralindia
aws.ec2.us-east-1--dp--http--azure.storage.centralus
aws.ec2.us-east-1--dp--http--azure.storage.eastasia
aws.ec2.us-east-1--dp--http--azure.storage.eastus
aws.ec2.us-east-1--dp--http--azure.storage.eastus2
aws.ec2.us-east-1--dp--http--azure.storage.francecentral
aws.ec2.us-east-1--dp--http--azure.storage.germanywestcentral
aws.ec2.us-east-1--dp--http--azure.storage.israelcentral
aws.ec2.us-east-1--dp--http--azure.storage.italynorth
aws.ec2.us-east-1--dp--http--azure.storage.japaneast
aws.ec2.us-east-1--dp--http--azure.storage.japanwest
aws.ec2.us-east-1--dp--http--azure.storage.koreacentral
aws.ec2.us-east-1--dp--http--azure.storage.koreasouth
aws.ec2.us-east-1--dp--http--azure.storage.mexicocentral
aws.ec2.us-east-1--dp--http--azure.storage.newzealandnorth
aws.ec2.us-east-1--dp--http--azure.storage.northcentralus
aws.ec2.us-east-1--dp--http--azure.storage.northeurope
aws.ec2.us-east-1--dp--http--azure.storage.norwayeast
aws.ec2.us-east-1--dp--http--azure.storage.polandcentral
aws.ec2.us-east-1--dp--http--azure.storage.qatarcentral
aws.ec2.us-east-1--dp--http--azure.storage.southafricanorth
aws.ec2.us-east-1--dp--http--azure.storage.southcentralus
aws.ec2.us-east-1--dp--http--azure.storage.southeastasia
aws.ec2.us-east-1--dp--http--azure.storage.southindia
aws.ec2.us-east-1--dp--http--azure.storage.spaincentral
aws.ec2.us-east-1--dp--http--azure.storage.swedencentral
aws.ec2.us-east-1--dp--http--azure.storage.switzerlandnorth
aws.ec2.us-east-1--dp--http--azure.storage.uaenorth
aws.ec2.us-east-1--dp--http--azure.storage.uksouth
aws.ec2.us-east-1--dp--http--azure.storage.ukwest
aws.ec2.us-east-1--dp--http--azure.storage.westcentralus
aws.ec2.us-east-1--dp--http--azure.storage.westeurope
aws.ec2.us-east-1--dp--http--azure.storage.westindia
aws.ec2.us-east-1--dp--http--azure.storage.westus
aws.ec2.us-east-1--dp--http--azure.storage.westus2
aws.ec2.us-east-1--dp--http--azure.storage.westus3
aws.ec2.us-east-1--dp--http--gcp.gcs.africa-south1
aws.ec2.us-east-1--dp--http--gcp.gcs.asia
aws.ec2.us-east-1--dp--http--gcp.gcs.asia-east1
aws.ec2.us-east-1--dp--http--gcp.gcs.asia-east2
aws.ec2.us-east-1--dp--http--gcp.gcs.asia-northeast1
aws.ec2.us-east-1--dp--http--gcp.gcs.asia-northeast2
aws.ec2.us-east-1--dp--http--gcp.gcs.asia-northeast3
aws.ec2.us-east-1--dp--http--gcp.gcs.asia-south1
aws.ec2.us-east-1--dp--http--gcp.gcs.asia-south2
aws.ec2.us-east-1--dp--http--gcp.gcs.asia-southeast1
aws.ec2.us-east-1--dp--http--gcp.gcs.asia-southeast2
aws.ec2.us-east-1--dp--http--gcp.gcs.australia-southeast1
aws.ec2.us-east-1--dp--http--gcp.gcs.australia-southeast2
aws.ec2.us-east-1--dp--http--gcp.gcs.eu
aws.ec2.us-east-1--dp--http--gcp.gcs.europe-central2
aws.ec2.us-east-1--dp--http--gcp.gcs.europe-north1
aws.ec2.us-east-1--dp--http--gcp.gcs.europe-southwest1
aws.ec2.us-east-1--dp--http--gcp.gcs.europe-west1
aws.ec2.us-east-1--dp--http--gcp.gcs.europe-west10
aws.ec2.us-east-1--dp--http--gcp.gcs.europe-west12
aws.ec2.us-east-1--dp--http--gcp.gcs.europe-west2
aws.ec2.us-east-1--dp--http--gcp.gcs.europe-west3
aws.ec2.us-east-1--dp--http--gcp.gcs.europe-west4
aws.ec2.us-east-1--dp--http--gcp.gcs.europe-west6
aws.ec2.us-east-1--dp--http--gcp.gcs.europe-west8
aws.ec2.us-east-1--dp--http--gcp.gcs.europe-west9
aws.ec2.us-east-1--dp--http--gcp.gcs.me-central1
aws.ec2.us-east-1--dp--http--gcp.gcs.me-west1
aws.ec2.us-east-1--dp--http--gcp.gcs.northamerica-northeast1
aws.ec2.us-east-1--dp--http--gcp.gcs.northamerica-northeast2
aws.ec2.us-east-1--dp--http--gcp.gcs.northamerica-south1
aws.ec2.us-east-1--dp--http--gcp.gcs.southamerica-east1
aws.ec2.us-east-1--dp--http--gcp.gcs.southamerica-west1
aws.ec2.us-east-1--dp--http--gcp.gcs.us
aws.ec2.us-east-1--dp--http--gcp.gcs.us-central1
aws.ec2.us-east-1--dp--http--gcp.gcs.us-east1
aws.ec2.us-east-1--dp--http--gcp.gcs.us-east4
aws.ec2.us-east-1--dp--http--gcp.gcs.us-east5
aws.ec2.us-east-1--dp--http--gcp.gcs.us-south1
aws.ec2.us-east-1--dp--http--gcp.gcs.us-west1
aws.ec2.us-east-1--dp--http--gcp.gcs.us-west2
aws.ec2.us-east-1--dp--http--gcp.gcs.us-west3
aws.ec2.us-east-1--dp--http--ibm.cos.ap-geo
aws.ec2.us-east-1--dp--http--ibm.cos.au-syd
aws.ec2.us-east-1--dp--http--ibm.cos.br-sao
aws.ec2.us-east-1--dp--http--ibm.cos.ca-tor
aws.ec2.us-east-1--dp--http--ibm.cos.eu-de
aws.ec2.us-east-1--dp--http--ibm.cos.eu-es
aws.ec2.us-east-1--dp--http--ibm.cos.eu-gb
aws.ec2.us-east-1--dp--http--ibm.cos.eu-geo
aws.ec2.us-east-1--dp--http--ibm.cos.jp-osa
aws.ec2.us-east-1--dp--http--ibm.cos.jp-tok
aws.ec2.us-east-1--dp--http--ibm.cos.us-east
aws.ec2.us-east-1--dp--http--ibm.cos.us-geo
aws.ec2.us-east-1--dp--http--ibm.cos.us-south
aws.ec2.us-east-1--dp--http--ionos.cos.de
aws.ec2.us-east-1--dp--http--ionos.cos.eu-central-2
aws.ec2.us-east-1--dp--http--ionos.cos.eu-central-3
aws.ec2.us-east-1--dp--http--ionos.cos.eu-south-2
aws.ec2.us-east-1--dp--http--ionos.cos.us-central-1
aws.ec2.us-east-1--dp--http--linode.storage.ap-south
aws.ec2.us-east-1--dp--http--linode.storage.au-mel
aws.ec2.us-east-1--dp--http--linode.storage.br-gru
aws.ec2.us-east-1--dp--http--linode.storage.es-mad
aws.ec2.us-east-1--dp--http--linode.storage.eu-central
aws.ec2.us-east-1--dp--http--linode.storage.fr-par
aws.ec2.us-east-1--dp--http--linode.storage.gb-lon
aws.ec2.us-east-1--dp--http--linode.storage.id-cgk
aws.ec2.us-east-1--dp--http--linode.storage.in-maa
aws.ec2.us-east-1--dp--http--linode.storage.it-mil
aws.ec2.us-east-1--dp--http--linode.storage.jp-osa
aws.ec2.us-east-1--dp--http--linode.storage.nl-ams
aws.ec2.us-east-1--dp--http--linode.storage.se-sto
aws.ec2.us-east-1--dp--http--linode.storage.sg-sin
aws.ec2.us-east-1--dp--http--linode.storage.us-east
aws.ec2.us-east-1--dp--http--linode.storage.us-iad
aws.ec2.us-east-1--dp--http--linode.storage.us-lax
aws.ec2.us-east-1--dp--http--linode.storage.us-mia
aws.ec2.us-east-1--dp--http--linode.storage.us-ord
aws.ec2.us-east-1--dp--http--linode.storage.us-sea
aws.ec2.us-east-1--dp--http--linode.storage.us-southeast
aws.ec2.us-east-1--dp--http--scaleway.cos.fr-par
aws.ec2.us-east-1--dp--http--scaleway.cos.nl-ams
aws.ec2.us-east-1--dp--http--scaleway.cos.pl-waw
aws.ec2.us-east-1--dp--http--tencent.cos.ap-bangkok
aws.ec2.us-east-1--dp--http--tencent.cos.ap-jakarta
aws.ec2.us-east-1--dp--http--tencent.cos.ap-seoul
aws.ec2.us-east-1--dp--http--tencent.cos.ap-singapore
aws.ec2.us-east-1--dp--http--tencent.cos.ap-tokyo
aws.ec2.us-east-1--dp--http--tencent.cos.eu-frankfurt
aws.ec2.us-east-1--dp--http--tencent.cos.na-ashburn
aws.ec2.us-east-1--dp--http--tencent.cos.na-siliconvalley
aws.ec2.us-east-1--dp--http--tencent.cos.sa-saopaulo
aws.ec2.us-east-1--dp--http--upcloud.cos.us-1
aws.ec2.us-east-1--dp--httpb-100mb--alibaba.oss.ap-northeast-1
aws.ec2.us-east-1--dp--httpb-100mb--alibaba.oss.ap-northeast-2
aws.ec2.us-east-1--dp--httpb-100mb--alibaba.oss.ap-southeast-1
aws.ec2.us-east-1--dp--httpb-100mb--alibaba.oss.ap-southeast-3
aws.ec2.us-east-1--dp--httpb-100mb--alibaba.oss.ap-southeast-5
aws.ec2.us-east-1--dp--httpb-100mb--alibaba.oss.ap-southeast-6
aws.ec2.us-east-1--dp--httpb-100mb--alibaba.oss.ap-southeast-7
aws.ec2.us-east-1--dp--httpb-100mb--alibaba.oss.eu-central-1
aws.ec2.us-east-1--dp--httpb-100mb--alibaba.oss.eu-west-1
aws.ec2.us-east-1--dp--httpb-100mb--alibaba.oss.me-central-1
aws.ec2.us-east-1--dp--httpb-100mb--alibaba.oss.me-east-1
aws.ec2.us-east-1--dp--httpb-100mb--alibaba.oss.na-south-1
aws.ec2.us-east-1--dp--httpb-100mb--alibaba.oss.us-east-1
aws.ec2.us-east-1--dp--httpb-100mb--alibaba.oss.us-west-1
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.australiacentral
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.australiaeast
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.australiasoutheast
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.brazilsouth
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.canadacentral
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.canadaeast
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.centralindia
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.centralus
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.eastasia
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.eastus
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.eastus2
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.francecentral
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.germanywestcentral
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.israelcentral
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.italynorth
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.japaneast
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.japanwest
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.koreacentral
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.koreasouth
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.mexicocentral
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.newzealandnorth
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.northcentralus
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.northeurope
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.norwayeast
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.polandcentral
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.qatarcentral
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.southafricanorth
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.southcentralus
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.southeastasia
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.southindia
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.spaincentral
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.swedencentral
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.switzerlandnorth
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.uaenorth
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.uksouth
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.ukwest
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.westcentralus
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.westeurope
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.westindia
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.westus
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.westus2
aws.ec2.us-east-1--dp--httpb-100mb--azure.storage.westus3
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.africa-south1
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.asia
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.asia-east1
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.asia-east2
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.asia-northeast1
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.asia-northeast2
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.asia-northeast3
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.asia-south1
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.asia-south2
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.asia-southeast1
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.asia-southeast2
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.australia-southeast1
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.australia-southeast2
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.eu
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.europe-central2
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.europe-north1
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.europe-southwest1
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.europe-west1
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.europe-west10
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.europe-west12
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.europe-west2
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.europe-west3
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.europe-west4
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.europe-west6
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.europe-west8
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.europe-west9
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.me-central1
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.me-west1
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.northamerica-northeast1
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.northamerica-northeast2
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.northamerica-south1
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.southamerica-east1
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.southamerica-west1
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.us
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.us-central1
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.us-east1
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.us-east4
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.us-east5
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.us-south1
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.us-west1
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.us-west2
aws.ec2.us-east-1--dp--httpb-100mb--gcp.gcs.us-west3
aws.ec2.us-east-1--dp--httpb-100mb--ibm.cos.ap-geo
aws.ec2.us-east-1--dp--httpb-100mb--ibm.cos.au-syd
aws.ec2.us-east-1--dp--httpb-100mb--ibm.cos.br-sao
aws.ec2.us-east-1--dp--httpb-100mb--ibm.cos.ca-tor
aws.ec2.us-east-1--dp--httpb-100mb--ibm.cos.eu-de
aws.ec2.us-east-1--dp--httpb-100mb--ibm.cos.eu-es
aws.ec2.us-east-1--dp--httpb-100mb--ibm.cos.eu-gb
aws.ec2.us-east-1--dp--httpb-100mb--ibm.cos.eu-geo
aws.ec2.us-east-1--dp--httpb-100mb--ibm.cos.jp-osa
aws.ec2.us-east-1--dp--httpb-100mb--ibm.cos.jp-tok
aws.ec2.us-east-1--dp--httpb-100mb--ibm.cos.us-east
aws.ec2.us-east-1--dp--httpb-100mb--ibm.cos.us-geo
aws.ec2.us-east-1--dp--httpb-100mb--ibm.cos.us-south
aws.ec2.us-east-1--dp--httpb-100mb--ionos.cos.de
aws.ec2.us-east-1--dp--httpb-100mb--ionos.cos.eu-central-2
aws.ec2.us-east-1--dp--httpb-100mb--ionos.cos.eu-central-3
aws.ec2.us-east-1--dp--httpb-100mb--ionos.cos.eu-south-2
aws.ec2.us-east-1--dp--httpb-100mb--ionos.cos.us-central-1
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.ap-south
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.au-mel
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.br-gru
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.es-mad
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.eu-central
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.fr-par
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.gb-lon
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.id-cgk
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.in-maa
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.it-mil
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.jp-osa
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.nl-ams
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.se-sto
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.sg-sin
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.us-east
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.us-iad
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.us-lax
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.us-mia
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.us-ord
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.us-sea
aws.ec2.us-east-1--dp--httpb-100mb--linode.storage.us-southeast
aws.ec2.us-east-1--dp--httpb-100mb--scaleway.cos.fr-par
aws.ec2.us-east-1--dp--httpb-100mb--scaleway.cos.nl-ams
aws.ec2.us-east-1--dp--httpb-100mb--scaleway.cos.pl-waw
aws.ec2.us-east-1--dp--httpb-100mb--tencent.cos.ap-bangkok
aws.ec2.us-east-1--dp--httpb-100mb--tencent.cos.ap-jakarta
aws.ec2.us-east-1--dp--httpb-100mb--tencent.cos.ap-seoul
aws.ec2.us-east-1--dp--httpb-100mb--tencent.cos.ap-singapore
aws.ec2.us-east-1--dp--httpb-100mb--tencent.cos.ap-tokyo
aws.ec2.us-east-1--dp--httpb-100mb--tencent.cos.eu-frankfurt
aws.ec2.us-east-1--dp--httpb-100mb--tencent.cos.na-ashburn
aws.ec2.us-east-1--dp--httpb-100mb--tencent.cos.na-siliconvalley
aws.ec2.us-east-1--dp--httpb-100mb--tencent.cos.sa-saopaulo
aws.ec2.us-east-1--dp--httpb-100mb--upcloud.cos.us-1
aws.ec2.us-east-1--dp--https--alibaba.oss.ap-northeast-1
aws.ec2.us-east-1--dp--https--alibaba.oss.ap-northeast-2
aws.ec2.us-east-1--dp--https--alibaba.oss.ap-southeast-1
aws.ec2.us-east-1--dp--https--alibaba.oss.ap-southeast-3
aws.ec2.us-east-1--dp--https--alibaba.oss.ap-southeast-5
aws.ec2.us-east-1--dp--https--alibaba.oss.ap-southeast-6
aws.ec2.us-east-1--dp--https--alibaba.oss.ap-southeast-7
aws.ec2.us-east-1--dp--https--alibaba.oss.eu-central-1
aws.ec2.us-east-1--dp--https--alibaba.oss.eu-west-1
aws.ec2.us-east-1--dp--https--alibaba.oss.me-central-1
aws.ec2.us-east-1--dp--https--alibaba.oss.me-east-1
aws.ec2.us-east-1--dp--https--alibaba.oss.na-south-1
aws.ec2.us-east-1--dp--https--alibaba.oss.us-east-1
aws.ec2.us-east-1--dp--https--alibaba.oss.us-west-1
aws.ec2.us-east-1--dp--https--azure.storage.australiacentral
aws.ec2.us-east-1--dp--https--azure.storage.australiaeast
aws.ec2.us-east-1--dp--https--azure.storage.australiasoutheast
aws.ec2.us-east-1--dp--https--azure.storage.brazilsouth
aws.ec2.us-east-1--dp--https--azure.storage.canadacentral
aws.ec2.us-east-1--dp--https--azure.storage.canadaeast
aws.ec2.us-east-1--dp--https--azure.storage.centralindia
aws.ec2.us-east-1--dp--https--azure.storage.centralus
aws.ec2.us-east-1--dp--https--azure.storage.eastasia
aws.ec2.us-east-1--dp--https--azure.storage.eastus
aws.ec2.us-east-1--dp--https--azure.storage.eastus2
aws.ec2.us-east-1--dp--https--azure.storage.francecentral
aws.ec2.us-east-1--dp--https--azure.storage.germanywestcentral
aws.ec2.us-east-1--dp--https--azure.storage.israelcentral
aws.ec2.us-east-1--dp--https--azure.storage.italynorth
aws.ec2.us-east-1--dp--https--azure.storage.japaneast
aws.ec2.us-east-1--dp--https--azure.storage.japanwest
aws.ec2.us-east-1--dp--https--azure.storage.koreacentral
aws.ec2.us-east-1--dp--https--azure.storage.koreasouth
aws.ec2.us-east-1--dp--https--azure.storage.mexicocentral
aws.ec2.us-east-1--dp--https--azure.storage.newzealandnorth
aws.ec2.us-east-1--dp--https--azure.storage.northcentralus
aws.ec2.us-east-1--dp--https--azure.storage.northeurope
aws.ec2.us-east-1--dp--https--azure.storage.norwayeast
aws.ec2.us-east-1--dp--https--azure.storage.polandcentral
aws.ec2.us-east-1--dp--https--azure.storage.qatarcentral
aws.ec2.us-east-1--dp--https--azure.storage.southafricanorth
aws.ec2.us-east-1--dp--https--azure.storage.southcentralus
aws.ec2.us-east-1--dp--https--azure.storage.southeastasia
aws.ec2.us-east-1--dp--https--azure.storage.southindia
aws.ec2.us-east-1--dp--https--azure.storage.spaincentral
aws.ec2.us-east-1--dp--https--azure.storage.swedencentral
aws.ec2.us-east-1--dp--https--azure.storage.switzerlandnorth
aws.ec2.us-east-1--dp--https--azure.storage.uaenorth
aws.ec2.us-east-1--dp--https--azure.storage.uksouth
aws.ec2.us-east-1--dp--https--azure.storage.ukwest
aws.ec2.us-east-1--dp--https--azure.storage.westcentralus
aws.ec2.us-east-1--dp--https--azure.storage.westeurope
aws.ec2.us-east-1--dp--https--azure.storage.westindia
aws.ec2.us-east-1--dp--https--azure.storage.westus
aws.ec2.us-east-1--dp--https--azure.storage.westus2
aws.ec2.us-east-1--dp--https--azure.storage.westus3
aws.ec2.us-east-1--dp--https--cloudflare.r2.eu
aws.ec2.us-east-1--dp--https--cloudflare.r2.wnam
aws.ec2.us-east-1--dp--https--digitalocean.spaces.ams3
aws.ec2.us-east-1--dp--https--digitalocean.spaces.blr1
aws.ec2.us-east-1--dp--https--digitalocean.spaces.fra1
aws.ec2.us-east-1--dp--https--digitalocean.spaces.lon1
aws.ec2.us-east-1--dp--https--digitalocean.spaces.nyc3
aws.ec2.us-east-1--dp--https--digitalocean.spaces.sfo2
aws.ec2.us-east-1--dp--https--digitalocean.spaces.sfo3
aws.ec2.us-east-1--dp--https--digitalocean.spaces.sgp1
aws.ec2.us-east-1--dp--https--digitalocean.spaces.syd1
aws.ec2.us-east-1--dp--https--digitalocean.spaces.tor1
aws.ec2.us-east-1--dp--https--gcp.gcs.africa-south1
aws.ec2.us-east-1--dp--https--gcp.gcs.asia
aws.ec2.us-east-1--dp--https--gcp.gcs.asia-east1
aws.ec2.us-east-1--dp--https--gcp.gcs.asia-east2
aws.ec2.us-east-1--dp--https--gcp.gcs.asia-northeast1
aws.ec2.us-east-1--dp--https--gcp.gcs.asia-northeast2
aws.ec2.us-east-1--dp--https--gcp.gcs.asia-northeast3
aws.ec2.us-east-1--dp--https--gcp.gcs.asia-south1
aws.ec2.us-east-1--dp--https--gcp.gcs.asia-south2
aws.ec2.us-east-1--dp--https--gcp.gcs.asia-southeast1
aws.ec2.us-east-1--dp--https--gcp.gcs.asia-southeast2
aws.ec2.us-east-1--dp--https--gcp.gcs.australia-southeast1
aws.ec2.us-east-1--dp--https--gcp.gcs.australia-southeast2
aws.ec2.us-east-1--dp--https--gcp.gcs.eu
aws.ec2.us-east-1--dp--https--gcp.gcs.europe-central2
aws.ec2.us-east-1--dp--https--gcp.gcs.europe-north1
aws.ec2.us-east-1--dp--https--gcp.gcs.europe-southwest1
aws.ec2.us-east-1--dp--https--gcp.gcs.europe-west1
aws.ec2.us-east-1--dp--https--gcp.gcs.europe-west10
aws.ec2.us-east-1--dp--https--gcp.gcs.europe-west12
aws.ec2.us-east-1--dp--https--gcp.gcs.europe-west2
aws.ec2.us-east-1--dp--https--gcp.gcs.europe-west3
aws.ec2.us-east-1--dp--https--gcp.gcs.europe-west4
aws.ec2.us-east-1--dp--https--gcp.gcs.europe-west6
aws.ec2.us-east-1--dp--https--gcp.gcs.europe-west8
aws.ec2.us-east-1--dp--https--gcp.gcs.europe-west9
aws.ec2.us-east-1--dp--https--gcp.gcs.me-central1
aws.ec2.us-east-1--dp--https--gcp.gcs.me-west1
aws.ec2.us-east-1--dp--https--gcp.gcs.northamerica-northeast1
aws.ec2.us-east-1--dp--https--gcp.gcs.northamerica-northeast2
aws.ec2.us-east-1--dp--https--gcp.gcs.northamerica-south1
aws.ec2.us-east-1--dp--https--gcp.gcs.southamerica-east1
aws.ec2.us-east-1--dp--https--gcp.gcs.southamerica-west1
aws.ec2.us-east-1--dp--https--gcp.gcs.us
aws.ec2.us-east-1--dp--https--gcp.gcs.us-central1
aws.ec2.us-east-1--dp--https--gcp.gcs.us-east1
aws.ec2.us-east-1--dp--https--gcp.gcs.us-east4
aws.ec2.us-east-1--dp--https--gcp.gcs.us-east5
aws.ec2.us-east-1--dp--https--gcp.gcs.us-south1
aws.ec2.us-east-1--dp--https--gcp.gcs.us-west1
aws.ec2.us-east-1--dp--https--gcp.gcs.us-west2
aws.ec2.us-east-1--dp--https--gcp.gcs.us-west3
aws.ec2.us-east-1--dp--https--hetzner.cos.fsn1
aws.ec2.us-east-1--dp--https--hetzner.cos.hel1
aws.ec2.us-east-1--dp--https--hetzner.cos.nbg1
aws.ec2.us-east-1--dp--https--ibm.cos.ap-geo
aws.ec2.us-east-1--dp--https--ibm.cos.au-syd
aws.ec2.us-east-1--dp--https--ibm.cos.br-sao
aws.ec2.us-east-1--dp--https--ibm.cos.ca-tor
aws.ec2.us-east-1--dp--https--ibm.cos.eu-de
aws.ec2.us-east-1--dp--https--ibm.cos.eu-es
aws.ec2.us-east-1--dp--https--ibm.cos.eu-gb
aws.ec2.us-east-1--dp--https--ibm.cos.eu-geo
aws.ec2.us-east-1--dp--https--ibm.cos.jp-osa
aws.ec2.us-east-1--dp--https--ibm.cos.jp-tok
aws.ec2.us-east-1--dp--https--ibm.cos.us-east
aws.ec2.us-east-1--dp--https--ibm.cos.us-geo
aws.ec2.us-east-1--dp--https--ibm.cos.us-south
aws.ec2.us-east-1--dp--https--ionos.cos.de
aws.ec2.us-east-1--dp--https--ionos.cos.eu-central-2
aws.ec2.us-east-1--dp--https--ionos.cos.eu-central-3
aws.ec2.us-east-1--dp--https--ionos.cos.eu-south-2
aws.ec2.us-east-1--dp--https--ionos.cos.us-central-1
aws.ec2.us-east-1--dp--https--linode.storage.ap-south
aws.ec2.us-east-1--dp--https--linode.storage.au-mel
aws.ec2.us-east-1--dp--https--linode.storage.br-gru
aws.ec2.us-east-1--dp--https--linode.storage.es-mad
aws.ec2.us-east-1--dp--https--linode.storage.eu-central
aws.ec2.us-east-1--dp--https--linode.storage.fr-par
aws.ec2.us-east-1--dp--https--linode.storage.gb-lon
aws.ec2.us-east-1--dp--https--linode.storage.id-cgk
aws.ec2.us-east-1--dp--https--linode.storage.in-maa
aws.ec2.us-east-1--dp--https--linode.storage.it-mil
aws.ec2.us-east-1--dp--https--linode.storage.jp-osa
aws.ec2.us-east-1--dp--https--linode.storage.nl-ams
aws.ec2.us-east-1--dp--https--linode.storage.se-sto
aws.ec2.us-east-1--dp--https--linode.storage.sg-sin
aws.ec2.us-east-1--dp--https--linode.storage.us-east
aws.ec2.us-east-1--dp--https--linode.storage.us-iad
aws.ec2.us-east-1--dp--https--linode.storage.us-lax
aws.ec2.us-east-1--dp--https--linode.storage.us-mia
aws.ec2.us-east-1--dp--https--linode.storage.us-ord
aws.ec2.us-east-1--dp--https--linode.storage.us-sea
aws.ec2.us-east-1--dp--https--linode.storage.us-southeast
aws.ec2.us-east-1--dp--https--ovhcloud.cos.us-east-va
aws.ec2.us-east-1--dp--https--ovhcloud.cos.us-west-or
aws.ec2.us-east-1--dp--https--scaleway.cos.fr-par
aws.ec2.us-east-1--dp--https--scaleway.cos.nl-ams
aws.ec2.us-east-1--dp--https--scaleway.cos.pl-waw
aws.ec2.us-east-1--dp--https--tencent.cos.ap-bangkok
aws.ec2.us-east-1--dp--https--tencent.cos.ap-jakarta
aws.ec2.us-east-1--dp--https--tencent.cos.ap-seoul
aws.ec2.us-east-1--dp--https--tencent.cos.ap-singapore
aws.ec2.us-east-1--dp--https--tencent.cos.ap-tokyo
aws.ec2.us-east-1--dp--https--tencent.cos.eu-frankfurt
aws.ec2.us-east-1--dp--https--tencent.cos.na-ashburn
aws.ec2.us-east-1--dp--https--tencent.cos.na-siliconvalley
aws.ec2.us-east-1--dp--https--tencent.cos.sa-saopaulo
aws.ec2.us-east-1--dp--https--upcloud.cos.us-1
aws.ec2.us-east-1--dp--https--vultr.cos.sjc
aws.ec2.us-east-1--dp--httpsb-100mb--cloudflare.r2.eu
aws.ec2.us-east-1--dp--httpsb-100mb--cloudflare.r2.wnam
aws.ec2.us-east-1--dp--httpsb-100mb--digitalocean.spaces.ams3
aws.ec2.us-east-1--dp--httpsb-100mb--digitalocean.spaces.blr1
aws.ec2.us-east-1--dp--httpsb-100mb--digitalocean.spaces.fra1
aws.ec2.us-east-1--dp--httpsb-100mb--digitalocean.spaces.lon1
aws.ec2.us-east-1--dp--httpsb-100mb--digitalocean.spaces.nyc3
aws.ec2.us-east-1--dp--httpsb-100mb--digitalocean.spaces.sfo2
aws.ec2.us-east-1--dp--httpsb-100mb--digitalocean.spaces.sfo3
aws.ec2.us-east-1--dp--httpsb-100mb--digitalocean.spaces.sgp1
aws.ec2.us-east-1--dp--httpsb-100mb--digitalocean.spaces.syd1
aws.ec2.us-east-1--dp--httpsb-100mb--digitalocean.spaces.tor1
aws.ec2.us-east-1--dp--httpsb-100mb--hetzner.cos.fsn1
aws.ec2.us-east-1--dp--httpsb-100mb--hetzner.cos.hel1
aws.ec2.us-east-1--dp--httpsb-100mb--hetzner.cos.nbg1
aws.ec2.us-east-1--dp--httpsb-100mb--ovhcloud.cos.us-east-va
aws.ec2.us-east-1--dp--httpsb-100mb--ovhcloud.cos.us-west-or
aws.ec2.us-east-1--dp--httpsb-100mb--vultr.cos.sjc
aws.ec2.us-east-1--dp--tcping4--alibaba.oss.ap-northeast-1
aws.ec2.us-east-1--dp--tcping4--alibaba.oss.ap-northeast-2
aws.ec2.us-east-1--dp--tcping4--alibaba.oss.ap-southeast-1
aws.ec2.us-east-1--dp--tcping4--alibaba.oss.ap-southeast-3
aws.ec2.us-east-1--dp--tcping4--alibaba.oss.ap-southeast-5
aws.ec2.us-east-1--dp--tcping4--alibaba.oss.ap-southeast-6
aws.ec2.us-east-1--dp--tcping4--alibaba.oss.ap-southeast-7
aws.ec2.us-east-1--dp--tcping4--alibaba.oss.eu-central-1
aws.ec2.us-east-1--dp--tcping4--alibaba.oss.eu-west-1
aws.ec2.us-east-1--dp--tcping4--alibaba.oss.me-central-1
aws.ec2.us-east-1--dp--tcping4--alibaba.oss.me-east-1
aws.ec2.us-east-1--dp--tcping4--alibaba.oss.na-south-1
aws.ec2.us-east-1--dp--tcping4--alibaba.oss.us-east-1
aws.ec2.us-east-1--dp--tcping4--alibaba.oss.us-west-1
aws.ec2.us-east-1--dp--tcping4--apac.central-asia
aws.ec2.us-east-1--dp--tcping4--apac.east-asia
aws.ec2.us-east-1--dp--tcping4--apac.oceania
aws.ec2.us-east-1--dp--tcping4--apac.south-asia
aws.ec2.us-east-1--dp--tcping4--apac.southeast-asia
aws.ec2.us-east-1--dp--tcping4--azure.storage.australiacentral
aws.ec2.us-east-1--dp--tcping4--azure.storage.australiaeast
aws.ec2.us-east-1--dp--tcping4--azure.storage.australiasoutheast
aws.ec2.us-east-1--dp--tcping4--azure.storage.brazilsouth
aws.ec2.us-east-1--dp--tcping4--azure.storage.canadacentral
aws.ec2.us-east-1--dp--tcping4--azure.storage.canadaeast
aws.ec2.us-east-1--dp--tcping4--azure.storage.centralindia
aws.ec2.us-east-1--dp--tcping4--azure.storage.centralus
aws.ec2.us-east-1--dp--tcping4--azure.storage.eastasia
aws.ec2.us-east-1--dp--tcping4--azure.storage.eastus
aws.ec2.us-east-1--dp--tcping4--azure.storage.eastus2
aws.ec2.us-east-1--dp--tcping4--azure.storage.francecentral
aws.ec2.us-east-1--dp--tcping4--azure.storage.germanywestcentral
aws.ec2.us-east-1--dp--tcping4--azure.storage.israelcentral
aws.ec2.us-east-1--dp--tcping4--azure.storage.italynorth
aws.ec2.us-east-1--dp--tcping4--azure.storage.japaneast
aws.ec2.us-east-1--dp--tcping4--azure.storage.japanwest
aws.ec2.us-east-1--dp--tcping4--azure.storage.koreacentral
aws.ec2.us-east-1--dp--tcping4--azure.storage.koreasouth
aws.ec2.us-east-1--dp--tcping4--azure.storage.mexicocentral
aws.ec2.us-east-1--dp--tcping4--azure.storage.newzealandnorth
aws.ec2.us-east-1--dp--tcping4--azure.storage.northcentralus
aws.ec2.us-east-1--dp--tcping4--azure.storage.northeurope
aws.ec2.us-east-1--dp--tcping4--azure.storage.norwayeast
aws.ec2.us-east-1--dp--tcping4--azure.storage.polandcentral
aws.ec2.us-east-1--dp--tcping4--azure.storage.qatarcentral
aws.ec2.us-east-1--dp--tcping4--azure.storage.southafricanorth
aws.ec2.us-east-1--dp--tcping4--azure.storage.southcentralus
aws.ec2.us-east-1--dp--tcping4--azure.storage.southeastasia
aws.ec2.us-east-1--dp--tcping4--azure.storage.southindia
aws.ec2.us-east-1--dp--tcping4--azure.storage.spaincentral
aws.ec2.us-east-1--dp--tcping4--azure.storage.swedencentral
aws.ec2.us-east-1--dp--tcping4--azure.storage.switzerlandnorth
aws.ec2.us-east-1--dp--tcping4--azure.storage.uaenorth
aws.ec2.us-east-1--dp--tcping4--azure.storage.uksouth
aws.ec2.us-east-1--dp--tcping4--azure.storage.ukwest
aws.ec2.us-east-1--dp--tcping4--azure.storage.westcentralus
aws.ec2.us-east-1--dp--tcping4--azure.storage.westeurope
aws.ec2.us-east-1--dp--tcping4--azure.storage.westindia
aws.ec2.us-east-1--dp--tcping4--azure.storage.westus
aws.ec2.us-east-1--dp--tcping4--azure.storage.westus2
aws.ec2.us-east-1--dp--tcping4--azure.storage.westus3
aws.ec2.us-east-1--dp--tcping4--cloudflare.r2.eu
aws.ec2.us-east-1--dp--tcping4--cloudflare.r2.wnam
aws.ec2.us-east-1--dp--tcping4--digitalocean.spaces.ams3
aws.ec2.us-east-1--dp--tcping4--digitalocean.spaces.blr1
aws.ec2.us-east-1--dp--tcping4--digitalocean.spaces.fra1
aws.ec2.us-east-1--dp--tcping4--digitalocean.spaces.lon1
aws.ec2.us-east-1--dp--tcping4--digitalocean.spaces.nyc3
aws.ec2.us-east-1--dp--tcping4--digitalocean.spaces.sfo2
aws.ec2.us-east-1--dp--tcping4--digitalocean.spaces.sfo3
aws.ec2.us-east-1--dp--tcping4--digitalocean.spaces.sgp1
aws.ec2.us-east-1--dp--tcping4--digitalocean.spaces.syd1
aws.ec2.us-east-1--dp--tcping4--digitalocean.spaces.tor1
aws.ec2.us-east-1--dp--tcping4--eu.eu-central
aws.ec2.us-east-1--dp--tcping4--eu.eu-east
aws.ec2.us-east-1--dp--tcping4--eu.eu-north
aws.ec2.us-east-1--dp--tcping4--eu.eu-south
aws.ec2.us-east-1--dp--tcping4--eu.eu-west
aws.ec2.us-east-1--dp--tcping4--hetzner.cos.fsn1
aws.ec2.us-east-1--dp--tcping4--hetzner.cos.hel1
aws.ec2.us-east-1--dp--tcping4--hetzner.cos.nbg1
aws.ec2.us-east-1--dp--tcping4--ibm.cos.ap-geo
aws.ec2.us-east-1--dp--tcping4--ibm.cos.au-syd
aws.ec2.us-east-1--dp--tcping4--ibm.cos.br-sao
aws.ec2.us-east-1--dp--tcping4--ibm.cos.ca-tor
aws.ec2.us-east-1--dp--tcping4--ibm.cos.eu-de
aws.ec2.us-east-1--dp--tcping4--ibm.cos.eu-es
aws.ec2.us-east-1--dp--tcping4--ibm.cos.eu-gb
aws.ec2.us-east-1--dp--tcping4--ibm.cos.eu-geo
aws.ec2.us-east-1--dp--tcping4--ibm.cos.jp-osa
aws.ec2.us-east-1--dp--tcping4--ibm.cos.jp-tok
aws.ec2.us-east-1--dp--tcping4--ibm.cos.us-east
aws.ec2.us-east-1--dp--tcping4--ibm.cos.us-geo
aws.ec2.us-east-1--dp--tcping4--ibm.cos.us-south
aws.ec2.us-east-1--dp--tcping4--ionos.cos.de
aws.ec2.us-east-1--dp--tcping4--ionos.cos.eu-central-2
aws.ec2.us-east-1--dp--tcping4--ionos.cos.eu-central-3
aws.ec2.us-east-1--dp--tcping4--ionos.cos.eu-south-2
aws.ec2.us-east-1--dp--tcping4--ionos.cos.us-central-1
aws.ec2.us-east-1--dp--tcping4--linode.storage.ap-south
aws.ec2.us-east-1--dp--tcping4--linode.storage.au-mel
aws.ec2.us-east-1--dp--tcping4--linode.storage.br-gru
aws.ec2.us-east-1--dp--tcping4--linode.storage.es-mad
aws.ec2.us-east-1--dp--tcping4--linode.storage.eu-central
aws.ec2.us-east-1--dp--tcping4--linode.storage.fr-par
aws.ec2.us-east-1--dp--tcping4--linode.storage.gb-lon
aws.ec2.us-east-1--dp--tcping4--linode.storage.id-cgk
aws.ec2.us-east-1--dp--tcping4--linode.storage.in-maa
aws.ec2.us-east-1--dp--tcping4--linode.storage.it-mil
aws.ec2.us-east-1--dp--tcping4--linode.storage.jp-osa
aws.ec2.us-east-1--dp--tcping4--linode.storage.nl-ams
aws.ec2.us-east-1--dp--tcping4--linode.storage.se-sto
aws.ec2.us-east-1--dp--tcping4--linode.storage.sg-sin
aws.ec2.us-east-1--dp--tcping4--linode.storage.us-east
aws.ec2.us-east-1--dp--tcping4--linode.storage.us-iad
aws.ec2.us-east-1--dp--tcping4--linode.storage.us-lax
aws.ec2.us-east-1--dp--tcping4--linode.storage.us-mia
aws.ec2.us-east-1--dp--tcping4--linode.storage.us-ord
aws.ec2.us-east-1--dp--tcping4--linode.storage.us-sea
aws.ec2.us-east-1--dp--tcping4--linode.storage.us-southeast
aws.ec2.us-east-1--dp--tcping4--mea.middle-east
aws.ec2.us-east-1--dp--tcping4--mea.north-africa
aws.ec2.us-east-1--dp--tcping4--mea.sub-saharan-africa
aws.ec2.us-east-1--dp--tcping4--north-america.us-midwest
aws.ec2.us-east-1--dp--tcping4--north-america.us-mountain
aws.ec2.us-east-1--dp--tcping4--north-america.us-northeast
aws.ec2.us-east-1--dp--tcping4--north-america.us-pnw
aws.ec2.us-east-1--dp--tcping4--north-america.us-southeast
aws.ec2.us-east-1--dp--tcping4--north-america.us-southwest
aws.ec2.us-east-1--dp--tcping4--oci.oss.af-johannesburg-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.ap-chuncheon-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.ap-hyderabad-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.ap-melbourne-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.ap-mumbai-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.ap-osaka-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.ap-seoul-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.ap-singapore-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.ap-singapore-2
aws.ec2.us-east-1--dp--tcping4--oci.oss.ap-sydney-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.ap-tokyo-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.ca-montreal-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.ca-toronto-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.eu-amsterdam-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.eu-frankfurt-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.eu-madrid-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.eu-marseille-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.eu-milan-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.eu-paris-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.eu-stockholm-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.eu-zurich-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.il-jerusalem-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.me-abudhabi-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.me-dubai-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.me-jeddah-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.me-riyadh-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.mx-monterrey-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.mx-queretaro-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.sa-bogota-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.sa-santiago-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.sa-saopaulo-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.sa-valparaiso-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.sa-vinhedo-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.uk-cardiff-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.uk-london-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.us-ashburn-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.us-chicago-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.us-phoenix-1
aws.ec2.us-east-1--dp--tcping4--oci.oss.us-sanjose-1
aws.ec2.us-east-1--dp--tcping4--ovhcloud.cos.us-east-va
aws.ec2.us-east-1--dp--tcping4--ovhcloud.cos.us-west-or
aws.ec2.us-east-1--dp--tcping4--scaleway.cos.fr-par
aws.ec2.us-east-1--dp--tcping4--scaleway.cos.nl-ams
aws.ec2.us-east-1--dp--tcping4--scaleway.cos.pl-waw
aws.ec2.us-east-1--dp--tcping4--tencent.cos.ap-bangkok
aws.ec2.us-east-1--dp--tcping4--tencent.cos.ap-jakarta
aws.ec2.us-east-1--dp--tcping4--tencent.cos.ap-seoul
aws.ec2.us-east-1--dp--tcping4--tencent.cos.ap-singapore
aws.ec2.us-east-1--dp--tcping4--tencent.cos.ap-tokyo
aws.ec2.us-east-1--dp--tcping4--tencent.cos.eu-frankfurt
aws.ec2.us-east-1--dp--tcping4--tencent.cos.na-ashburn
aws.ec2.us-east-1--dp--tcping4--tencent.cos.na-siliconvalley
aws.ec2.us-east-1--dp--tcping4--tencent.cos.sa-saopaulo
aws.ec2.us-east-1--dp--tcping4--upcloud.cos.us-1
aws.ec2.us-east-1--dp--tcping4--vultr.cos.sjc
aws.ec2.us-east-1--dp--tcping6--apac.central-asia
aws.ec2.us-east-1--dp--tcping6--apac.east-asia
aws.ec2.us-east-1--dp--tcping6--apac.oceania
aws.ec2.us-east-1--dp--tcping6--apac.south-asia
aws.ec2.us-east-1--dp--tcping6--apac.southeast-asia
aws.ec2.us-east-1--dp--tcping6--cloudflare.r2.eu
aws.ec2.us-east-1--dp--tcping6--cloudflare.r2.wnam
aws.ec2.us-east-1--dp--tcping6--eu.eu-central
aws.ec2.us-east-1--dp--tcping6--eu.eu-east
aws.ec2.us-east-1--dp--tcping6--eu.eu-north
aws.ec2.us-east-1--dp--tcping6--eu.eu-south
aws.ec2.us-east-1--dp--tcping6--eu.eu-west
aws.ec2.us-east-1--dp--tcping6--hetzner.cos.fsn1
aws.ec2.us-east-1--dp--tcping6--hetzner.cos.hel1
aws.ec2.us-east-1--dp--tcping6--hetzner.cos.nbg1
aws.ec2.us-east-1--dp--tcping6--linode.storage.ap-south
aws.ec2.us-east-1--dp--tcping6--linode.storage.au-mel
aws.ec2.us-east-1--dp--tcping6--linode.storage.br-gru
aws.ec2.us-east-1--dp--tcping6--linode.storage.es-mad
aws.ec2.us-east-1--dp--tcping6--linode.storage.eu-central
aws.ec2.us-east-1--dp--tcping6--linode.storage.fr-par
aws.ec2.us-east-1--dp--tcping6--linode.storage.gb-lon
aws.ec2.us-east-1--dp--tcping6--linode.storage.id-cgk
aws.ec2.us-east-1--dp--tcping6--linode.storage.in-maa
aws.ec2.us-east-1--dp--tcping6--linode.storage.it-mil
aws.ec2.us-east-1--dp--tcping6--linode.storage.jp-osa
aws.ec2.us-east-1--dp--tcping6--linode.storage.nl-ams
aws.ec2.us-east-1--dp--tcping6--linode.storage.se-sto
aws.ec2.us-east-1--dp--tcping6--linode.storage.sg-sin
aws.ec2.us-east-1--dp--tcping6--linode.storage.us-east
aws.ec2.us-east-1--dp--tcping6--linode.storage.us-iad
aws.ec2.us-east-1--dp--tcping6--linode.storage.us-lax
aws.ec2.us-east-1--dp--tcping6--linode.storage.us-mia
aws.ec2.us-east-1--dp--tcping6--linode.storage.us-ord
aws.ec2.us-east-1--dp--tcping6--linode.storage.us-sea
aws.ec2.us-east-1--dp--tcping6--linode.storage.us-southeast
aws.ec2.us-east-1--dp--tcping6--mea.middle-east
aws.ec2.us-east-1--dp--tcping6--mea.north-africa
aws.ec2.us-east-1--dp--tcping6--mea.sub-saharan-africa
aws.ec2.us-east-1--dp--tcping6--north-america.us-midwest
aws.ec2.us-east-1--dp--tcping6--north-america.us-mountain
aws.ec2.us-east-1--dp--tcping6--north-america.us-northeast
aws.ec2.us-east-1--dp--tcping6--north-america.us-pnw
aws.ec2.us-east-1--dp--tcping6--north-america.us-southeast
aws.ec2.us-east-1--dp--tcping6--north-america.us-southwest
aws.ec2.us-east-1--dp--tcping6--scaleway.cos.fr-par
aws.ec2.us-east-1--dp--tcping6--scaleway.cos.nl-ams
aws.ec2.us-east-1--dp--tcping6--scaleway.cos.pl-waw
aws.ec2.us-east-1--dp--tcping6--vultr.cos.sjc
gcp.us-central1--dp--gping4--aws.ca-central-1
gcp.us-central1--dp--gping4--aws.us-east-1
gcp.us-central1--dp--gping4--aws.us-east-2
gcp.us-central1--dp--gping4--aws.us-west-1
gcp.us-central1--dp--gping4--aws.us-west-2

Last Mile Measurements (471 IDs)

Tests from cloud providers to geographic endpoints (countries, continents, US states) and tests from geographic probe networks (RIPE Atlas, Globalping) to cloud services. Includes tests from regions like EU, APAC, MEA, Americas, etc.

apac--dp--adns--akamai.dns
apac--dp--adns--alibaba.dns
apac--dp--adns--aws.route53
apac--dp--adns--azure.dns
apac--dp--adns--bunny.dns
apac--dp--adns--cloudflare.dns
apac--dp--adns--digitalocean.dns
apac--dp--adns--dnsmadeeasy.dns
apac--dp--adns--easydns.dns
apac--dp--adns--gcp.dns
apac--dp--adns--ns1.dns
apac--dp--adns--rage4.dns
apac--dp--adns--ultradns.dns
apac--dp--aping4--akamai.cdn
apac--dp--aping4--alibaba.cdn
apac--dp--aping4--aws.cloudfront
apac--dp--aping4--bunny.cdn
apac--dp--aping4--cachefly.cdn
apac--dp--aping4--cloudflare.cdn
apac--dp--aping4--digitalocean.cdn
apac--dp--aping4--fastly.cdn
apac--dp--aping4--gcp.cdn
apac--dp--aping4--scaleway.cdn
apac--dp--aping4--tencent.cdn
apac--dp--gping4--akamai.cdn
apac--dp--gping4--alibaba.cdn
apac--dp--gping4--aws.cloudfront
apac--dp--gping4--bunny.cdn
apac--dp--gping4--cachefly.cdn
apac--dp--gping4--cdnetworks.cdn
apac--dp--gping4--cloudflare.cdn
apac--dp--gping4--digitalocean.cdn
apac--dp--gping4--fastly.cdn
apac--dp--gping4--gcp.cdn
apac--dp--gping4--scaleway.cdn
apac--dp--gping4--tencent.cdn
aws.ec2.us-east-1--dp--tcping4--ad
aws.ec2.us-east-1--dp--tcping4--ae
aws.ec2.us-east-1--dp--tcping4--af
aws.ec2.us-east-1--dp--tcping4--ag
aws.ec2.us-east-1--dp--tcping4--ai
aws.ec2.us-east-1--dp--tcping4--al
aws.ec2.us-east-1--dp--tcping4--am
aws.ec2.us-east-1--dp--tcping4--ao
aws.ec2.us-east-1--dp--tcping4--apac
aws.ec2.us-east-1--dp--tcping4--ar
aws.ec2.us-east-1--dp--tcping4--at
aws.ec2.us-east-1--dp--tcping4--au
aws.ec2.us-east-1--dp--tcping4--aw
aws.ec2.us-east-1--dp--tcping4--az
aws.ec2.us-east-1--dp--tcping4--ba
aws.ec2.us-east-1--dp--tcping4--bb
aws.ec2.us-east-1--dp--tcping4--bd
aws.ec2.us-east-1--dp--tcping4--be
aws.ec2.us-east-1--dp--tcping4--bf
aws.ec2.us-east-1--dp--tcping4--bg
aws.ec2.us-east-1--dp--tcping4--bh
aws.ec2.us-east-1--dp--tcping4--bi
aws.ec2.us-east-1--dp--tcping4--bj
aws.ec2.us-east-1--dp--tcping4--bm
aws.ec2.us-east-1--dp--tcping4--bn
aws.ec2.us-east-1--dp--tcping4--bo
aws.ec2.us-east-1--dp--tcping4--bq
aws.ec2.us-east-1--dp--tcping4--br
aws.ec2.us-east-1--dp--tcping4--bs
aws.ec2.us-east-1--dp--tcping4--bt
aws.ec2.us-east-1--dp--tcping4--bw
aws.ec2.us-east-1--dp--tcping4--by
aws.ec2.us-east-1--dp--tcping4--bz
aws.ec2.us-east-1--dp--tcping4--ca
aws.ec2.us-east-1--dp--tcping4--cd
aws.ec2.us-east-1--dp--tcping4--central-america
aws.ec2.us-east-1--dp--tcping4--cg
aws.ec2.us-east-1--dp--tcping4--ch
aws.ec2.us-east-1--dp--tcping4--ci
aws.ec2.us-east-1--dp--tcping4--cl
aws.ec2.us-east-1--dp--tcping4--co
aws.ec2.us-east-1--dp--tcping4--cr
aws.ec2.us-east-1--dp--tcping4--cw
aws.ec2.us-east-1--dp--tcping4--cy
aws.ec2.us-east-1--dp--tcping4--cz
aws.ec2.us-east-1--dp--tcping4--de
aws.ec2.us-east-1--dp--tcping4--dj
aws.ec2.us-east-1--dp--tcping4--dk
aws.ec2.us-east-1--dp--tcping4--do
aws.ec2.us-east-1--dp--tcping4--dz
aws.ec2.us-east-1--dp--tcping4--ec
aws.ec2.us-east-1--dp--tcping4--ee
aws.ec2.us-east-1--dp--tcping4--eg
aws.ec2.us-east-1--dp--tcping4--es
aws.ec2.us-east-1--dp--tcping4--et
aws.ec2.us-east-1--dp--tcping4--eu
aws.ec2.us-east-1--dp--tcping4--fi
aws.ec2.us-east-1--dp--tcping4--fj
aws.ec2.us-east-1--dp--tcping4--fo
aws.ec2.us-east-1--dp--tcping4--fr
aws.ec2.us-east-1--dp--tcping4--ga
aws.ec2.us-east-1--dp--tcping4--gb
aws.ec2.us-east-1--dp--tcping4--gd
aws.ec2.us-east-1--dp--tcping4--ge
aws.ec2.us-east-1--dp--tcping4--gf
aws.ec2.us-east-1--dp--tcping4--gh
aws.ec2.us-east-1--dp--tcping4--gi
aws.ec2.us-east-1--dp--tcping4--gl
aws.ec2.us-east-1--dp--tcping4--gm
aws.ec2.us-east-1--dp--tcping4--gn
aws.ec2.us-east-1--dp--tcping4--gr
aws.ec2.us-east-1--dp--tcping4--gt
aws.ec2.us-east-1--dp--tcping4--gu
aws.ec2.us-east-1--dp--tcping4--gy
aws.ec2.us-east-1--dp--tcping4--hk
aws.ec2.us-east-1--dp--tcping4--hn
aws.ec2.us-east-1--dp--tcping4--hr
aws.ec2.us-east-1--dp--tcping4--hu
aws.ec2.us-east-1--dp--tcping4--id
aws.ec2.us-east-1--dp--tcping4--ie
aws.ec2.us-east-1--dp--tcping4--il
aws.ec2.us-east-1--dp--tcping4--im
aws.ec2.us-east-1--dp--tcping4--in
aws.ec2.us-east-1--dp--tcping4--iq
aws.ec2.us-east-1--dp--tcping4--ir
aws.ec2.us-east-1--dp--tcping4--is
aws.ec2.us-east-1--dp--tcping4--it
aws.ec2.us-east-1--dp--tcping4--je
aws.ec2.us-east-1--dp--tcping4--jm
aws.ec2.us-east-1--dp--tcping4--jo
aws.ec2.us-east-1--dp--tcping4--jp
aws.ec2.us-east-1--dp--tcping4--ke
aws.ec2.us-east-1--dp--tcping4--kg
aws.ec2.us-east-1--dp--tcping4--kh
aws.ec2.us-east-1--dp--tcping4--ki
aws.ec2.us-east-1--dp--tcping4--kn
aws.ec2.us-east-1--dp--tcping4--kw
aws.ec2.us-east-1--dp--tcping4--ky
aws.ec2.us-east-1--dp--tcping4--kz
aws.ec2.us-east-1--dp--tcping4--la
aws.ec2.us-east-1--dp--tcping4--lb
aws.ec2.us-east-1--dp--tcping4--li
aws.ec2.us-east-1--dp--tcping4--lk
aws.ec2.us-east-1--dp--tcping4--lr
aws.ec2.us-east-1--dp--tcping4--lt
aws.ec2.us-east-1--dp--tcping4--lu
aws.ec2.us-east-1--dp--tcping4--lv
aws.ec2.us-east-1--dp--tcping4--ly
aws.ec2.us-east-1--dp--tcping4--ma
aws.ec2.us-east-1--dp--tcping4--mc
aws.ec2.us-east-1--dp--tcping4--md
aws.ec2.us-east-1--dp--tcping4--me
aws.ec2.us-east-1--dp--tcping4--mea
aws.ec2.us-east-1--dp--tcping4--mg
aws.ec2.us-east-1--dp--tcping4--mh
aws.ec2.us-east-1--dp--tcping4--mk
aws.ec2.us-east-1--dp--tcping4--ml
aws.ec2.us-east-1--dp--tcping4--mm
aws.ec2.us-east-1--dp--tcping4--mn
aws.ec2.us-east-1--dp--tcping4--mo
aws.ec2.us-east-1--dp--tcping4--mq
aws.ec2.us-east-1--dp--tcping4--mt
aws.ec2.us-east-1--dp--tcping4--mu
aws.ec2.us-east-1--dp--tcping4--mv
aws.ec2.us-east-1--dp--tcping4--mw
aws.ec2.us-east-1--dp--tcping4--mx
aws.ec2.us-east-1--dp--tcping4--my
aws.ec2.us-east-1--dp--tcping4--mz
aws.ec2.us-east-1--dp--tcping4--na
aws.ec2.us-east-1--dp--tcping4--nc
aws.ec2.us-east-1--dp--tcping4--ne
aws.ec2.us-east-1--dp--tcping4--ng
aws.ec2.us-east-1--dp--tcping4--nl
aws.ec2.us-east-1--dp--tcping4--no
aws.ec2.us-east-1--dp--tcping4--north-america
aws.ec2.us-east-1--dp--tcping4--np
aws.ec2.us-east-1--dp--tcping4--nz
aws.ec2.us-east-1--dp--tcping4--om
aws.ec2.us-east-1--dp--tcping4--pa
aws.ec2.us-east-1--dp--tcping4--pe
aws.ec2.us-east-1--dp--tcping4--pg
aws.ec2.us-east-1--dp--tcping4--ph
aws.ec2.us-east-1--dp--tcping4--pk
aws.ec2.us-east-1--dp--tcping4--pl
aws.ec2.us-east-1--dp--tcping4--pr
aws.ec2.us-east-1--dp--tcping4--ps
aws.ec2.us-east-1--dp--tcping4--pt
aws.ec2.us-east-1--dp--tcping4--pw
aws.ec2.us-east-1--dp--tcping4--py
aws.ec2.us-east-1--dp--tcping4--qa
aws.ec2.us-east-1--dp--tcping4--ro
aws.ec2.us-east-1--dp--tcping4--rs
aws.ec2.us-east-1--dp--tcping4--ru
aws.ec2.us-east-1--dp--tcping4--rw
aws.ec2.us-east-1--dp--tcping4--sa
aws.ec2.us-east-1--dp--tcping4--sb
aws.ec2.us-east-1--dp--tcping4--sc
aws.ec2.us-east-1--dp--tcping4--sd
aws.ec2.us-east-1--dp--tcping4--se
aws.ec2.us-east-1--dp--tcping4--sg
aws.ec2.us-east-1--dp--tcping4--si
aws.ec2.us-east-1--dp--tcping4--sk
aws.ec2.us-east-1--dp--tcping4--sl
aws.ec2.us-east-1--dp--tcping4--sn
aws.ec2.us-east-1--dp--tcping4--so
aws.ec2.us-east-1--dp--tcping4--south-america
aws.ec2.us-east-1--dp--tcping4--sr
aws.ec2.us-east-1--dp--tcping4--ss
aws.ec2.us-east-1--dp--tcping4--sv
aws.ec2.us-east-1--dp--tcping4--sx
aws.ec2.us-east-1--dp--tcping4--sz
aws.ec2.us-east-1--dp--tcping4--tc
aws.ec2.us-east-1--dp--tcping4--tg
aws.ec2.us-east-1--dp--tcping4--th
aws.ec2.us-east-1--dp--tcping4--tj
aws.ec2.us-east-1--dp--tcping4--tl
aws.ec2.us-east-1--dp--tcping4--tn
aws.ec2.us-east-1--dp--tcping4--tr
aws.ec2.us-east-1--dp--tcping4--tt
aws.ec2.us-east-1--dp--tcping4--tw
aws.ec2.us-east-1--dp--tcping4--tz
aws.ec2.us-east-1--dp--tcping4--ua
aws.ec2.us-east-1--dp--tcping4--ug
aws.ec2.us-east-1--dp--tcping4--us.ak
aws.ec2.us-east-1--dp--tcping4--us.al
aws.ec2.us-east-1--dp--tcping4--us.ar
aws.ec2.us-east-1--dp--tcping4--us.az
aws.ec2.us-east-1--dp--tcping4--us.ca
aws.ec2.us-east-1--dp--tcping4--us.co
aws.ec2.us-east-1--dp--tcping4--us.ct
aws.ec2.us-east-1--dp--tcping4--us.de
aws.ec2.us-east-1--dp--tcping4--us.fl
aws.ec2.us-east-1--dp--tcping4--us.ga
aws.ec2.us-east-1--dp--tcping4--us.hi
aws.ec2.us-east-1--dp--tcping4--us.ia
aws.ec2.us-east-1--dp--tcping4--us.id
aws.ec2.us-east-1--dp--tcping4--us.il
aws.ec2.us-east-1--dp--tcping4--us.in
aws.ec2.us-east-1--dp--tcping4--us.ks
aws.ec2.us-east-1--dp--tcping4--us.ky
aws.ec2.us-east-1--dp--tcping4--us.la
aws.ec2.us-east-1--dp--tcping4--us.ma
aws.ec2.us-east-1--dp--tcping4--us.md
aws.ec2.us-east-1--dp--tcping4--us.me
aws.ec2.us-east-1--dp--tcping4--us.mi
aws.ec2.us-east-1--dp--tcping4--us.mn
aws.ec2.us-east-1--dp--tcping4--us.mo
aws.ec2.us-east-1--dp--tcping4--us.ms
aws.ec2.us-east-1--dp--tcping4--us.mt
aws.ec2.us-east-1--dp--tcping4--us.nc
aws.ec2.us-east-1--dp--tcping4--us.nd
aws.ec2.us-east-1--dp--tcping4--us.ne
aws.ec2.us-east-1--dp--tcping4--us.nh
aws.ec2.us-east-1--dp--tcping4--us.nj
aws.ec2.us-east-1--dp--tcping4--us.nm
aws.ec2.us-east-1--dp--tcping4--us.nv
aws.ec2.us-east-1--dp--tcping4--us.ny
aws.ec2.us-east-1--dp--tcping4--us.oh
aws.ec2.us-east-1--dp--tcping4--us.ok
aws.ec2.us-east-1--dp--tcping4--us.or
aws.ec2.us-east-1--dp--tcping4--us.pa
aws.ec2.us-east-1--dp--tcping4--us.ri
aws.ec2.us-east-1--dp--tcping4--us.sc
aws.ec2.us-east-1--dp--tcping4--us.sd
aws.ec2.us-east-1--dp--tcping4--us.tn
aws.ec2.us-east-1--dp--tcping4--us.tx
aws.ec2.us-east-1--dp--tcping4--us.ut
aws.ec2.us-east-1--dp--tcping4--us.va
aws.ec2.us-east-1--dp--tcping4--us.vt
aws.ec2.us-east-1--dp--tcping4--us.wa
aws.ec2.us-east-1--dp--tcping4--us.wi
aws.ec2.us-east-1--dp--tcping4--us.wv
aws.ec2.us-east-1--dp--tcping4--us.wy
aws.ec2.us-east-1--dp--tcping4--uy
aws.ec2.us-east-1--dp--tcping4--uz
aws.ec2.us-east-1--dp--tcping4--ve
aws.ec2.us-east-1--dp--tcping4--vg
aws.ec2.us-east-1--dp--tcping4--vi
aws.ec2.us-east-1--dp--tcping4--vn
aws.ec2.us-east-1--dp--tcping4--ws
aws.ec2.us-east-1--dp--tcping4--xk
aws.ec2.us-east-1--dp--tcping4--za
aws.ec2.us-east-1--dp--tcping4--zm
aws.ec2.us-east-1--dp--tcping4--zw
aws.ec2.us-east-1--dp--tcping6--apac
aws.ec2.us-east-1--dp--tcping6--central-america
aws.ec2.us-east-1--dp--tcping6--eu
aws.ec2.us-east-1--dp--tcping6--mea
aws.ec2.us-east-1--dp--tcping6--north-america
aws.ec2.us-east-1--dp--tcping6--south-america
central-america--dp--adns--akamai.dns
central-america--dp--adns--alibaba.dns
central-america--dp--adns--aws.route53
central-america--dp--adns--azure.dns
central-america--dp--adns--bunny.dns
central-america--dp--adns--cloudflare.dns
central-america--dp--adns--digitalocean.dns
central-america--dp--adns--dnsmadeeasy.dns
central-america--dp--adns--easydns.dns
central-america--dp--adns--gcp.dns
central-america--dp--adns--ns1.dns
central-america--dp--adns--rage4.dns
central-america--dp--adns--ultradns.dns
central-america--dp--aping4--akamai.cdn
central-america--dp--aping4--alibaba.cdn
central-america--dp--aping4--aws.cloudfront
central-america--dp--aping4--bunny.cdn
central-america--dp--aping4--cachefly.cdn
central-america--dp--aping4--cdnetworks.cdn
central-america--dp--aping4--cloudflare.cdn
central-america--dp--aping4--digitalocean.cdn
central-america--dp--aping4--fastly.cdn
central-america--dp--aping4--gcp.cdn
central-america--dp--aping4--scaleway.cdn
central-america--dp--aping4--tencent.cdn
central-america--dp--gping4--akamai.cdn
central-america--dp--gping4--alibaba.cdn
central-america--dp--gping4--aws.cloudfront
central-america--dp--gping4--bunny.cdn
central-america--dp--gping4--cachefly.cdn
central-america--dp--gping4--cdnetworks.cdn
central-america--dp--gping4--cloudflare.cdn
central-america--dp--gping4--digitalocean.cdn
central-america--dp--gping4--fastly.cdn
central-america--dp--gping4--gcp.cdn
central-america--dp--gping4--scaleway.cdn
central-america--dp--gping4--tencent.cdn
eu--dp--adns--akamai.dns
eu--dp--adns--alibaba.dns
eu--dp--adns--aws.route53
eu--dp--adns--azure.dns
eu--dp--adns--bunny.dns
eu--dp--adns--cloudflare.dns
eu--dp--adns--digitalocean.dns
eu--dp--adns--dnsmadeeasy.dns
eu--dp--adns--easydns.dns
eu--dp--adns--gcp.dns
eu--dp--adns--ns1.dns
eu--dp--adns--rage4.dns
eu--dp--adns--ultradns.dns
eu--dp--aping4--akamai.cdn
eu--dp--aping4--alibaba.cdn
eu--dp--aping4--aws.cloudfront
eu--dp--aping4--bunny.cdn
eu--dp--aping4--cachefly.cdn
eu--dp--aping4--cdnetworks.cdn
eu--dp--aping4--cloudflare.cdn
eu--dp--aping4--digitalocean.cdn
eu--dp--aping4--fastly.cdn
eu--dp--aping4--gcp.cdn
eu--dp--aping4--scaleway.cdn
eu--dp--aping4--tencent.cdn
eu--dp--gping4--akamai.cdn
eu--dp--gping4--alibaba.cdn
eu--dp--gping4--aws.cloudfront
eu--dp--gping4--bunny.cdn
eu--dp--gping4--cachefly.cdn
eu--dp--gping4--cdnetworks.cdn
eu--dp--gping4--cloudflare.cdn
eu--dp--gping4--digitalocean.cdn
eu--dp--gping4--fastly.cdn
eu--dp--gping4--gcp.cdn
eu--dp--gping4--scaleway.cdn
eu--dp--gping4--tencent.cdn
mea--dp--adns--akamai.dns
mea--dp--adns--alibaba.dns
mea--dp--adns--aws.route53
mea--dp--adns--azure.dns
mea--dp--adns--bunny.dns
mea--dp--adns--cloudflare.dns
mea--dp--adns--digitalocean.dns
mea--dp--adns--dnsmadeeasy.dns
mea--dp--adns--easydns.dns
mea--dp--adns--gcp.dns
mea--dp--adns--ns1.dns
mea--dp--adns--rage4.dns
mea--dp--adns--ultradns.dns
mea--dp--aping4--akamai.cdn
mea--dp--aping4--alibaba.cdn
mea--dp--aping4--aws.cloudfront
mea--dp--aping4--bunny.cdn
mea--dp--aping4--cachefly.cdn
mea--dp--aping4--cdnetworks.cdn
mea--dp--aping4--cloudflare.cdn
mea--dp--aping4--digitalocean.cdn
mea--dp--aping4--fastly.cdn
mea--dp--aping4--gcp.cdn
mea--dp--aping4--scaleway.cdn
mea--dp--aping4--tencent.cdn
mea--dp--gping4--akamai.cdn
mea--dp--gping4--alibaba.cdn
mea--dp--gping4--aws.cloudfront
mea--dp--gping4--bunny.cdn
mea--dp--gping4--cachefly.cdn
mea--dp--gping4--cdnetworks.cdn
mea--dp--gping4--cloudflare.cdn
mea--dp--gping4--digitalocean.cdn
mea--dp--gping4--fastly.cdn
mea--dp--gping4--gcp.cdn
mea--dp--gping4--scaleway.cdn
mea--dp--gping4--tencent.cdn
north-america--dp--adns--akamai.dns
north-america--dp--adns--alibaba.dns
north-america--dp--adns--aws.route53
north-america--dp--adns--azure.dns
north-america--dp--adns--bunny.dns
north-america--dp--adns--cloudflare.dns
north-america--dp--adns--digitalocean.dns
north-america--dp--adns--dnsmadeeasy.dns
north-america--dp--adns--easydns.dns
north-america--dp--adns--gcp.dns
north-america--dp--adns--ns1.dns
north-america--dp--adns--rage4.dns
north-america--dp--adns--ultradns.dns
north-america--dp--aping4--akamai.cdn
north-america--dp--aping4--alibaba.cdn
north-america--dp--aping4--aws.cloudfront
north-america--dp--aping4--bunny.cdn
north-america--dp--aping4--cachefly.cdn
north-america--dp--aping4--cdnetworks.cdn
north-america--dp--aping4--cloudflare.cdn
north-america--dp--aping4--digitalocean.cdn
north-america--dp--aping4--fastly.cdn
north-america--dp--aping4--gcp.cdn
north-america--dp--aping4--scaleway.cdn
north-america--dp--aping4--tencent.cdn
north-america--dp--gping4--akamai.cdn
north-america--dp--gping4--alibaba.cdn
north-america--dp--gping4--aws.cloudfront
north-america--dp--gping4--bunny.cdn
north-america--dp--gping4--cachefly.cdn
north-america--dp--gping4--cdnetworks.cdn
north-america--dp--gping4--cloudflare.cdn
north-america--dp--gping4--digitalocean.cdn
north-america--dp--gping4--fastly.cdn
north-america--dp--gping4--gcp.cdn
north-america--dp--gping4--scaleway.cdn
north-america--dp--gping4--tencent.cdn
south-america--dp--adns--akamai.dns
south-america--dp--adns--alibaba.dns
south-america--dp--adns--aws.route53
south-america--dp--adns--azure.dns
south-america--dp--adns--bunny.dns
south-america--dp--adns--cloudflare.dns
south-america--dp--adns--digitalocean.dns
south-america--dp--adns--dnsmadeeasy.dns
south-america--dp--adns--easydns.dns
south-america--dp--adns--gcp.dns
south-america--dp--adns--ns1.dns
south-america--dp--adns--rage4.dns
south-america--dp--adns--ultradns.dns
south-america--dp--aping4--akamai.cdn
south-america--dp--aping4--alibaba.cdn
south-america--dp--aping4--aws.cloudfront
south-america--dp--aping4--bunny.cdn
south-america--dp--aping4--cachefly.cdn
south-america--dp--aping4--cdnetworks.cdn
south-america--dp--aping4--cloudflare.cdn
south-america--dp--aping4--digitalocean.cdn
south-america--dp--aping4--fastly.cdn
south-america--dp--aping4--gcp.cdn
south-america--dp--aping4--scaleway.cdn
south-america--dp--aping4--tencent.cdn
south-america--dp--gping4--akamai.cdn
south-america--dp--gping4--alibaba.cdn
south-america--dp--gping4--aws.cloudfront
south-america--dp--gping4--bunny.cdn
south-america--dp--gping4--cachefly.cdn
south-america--dp--gping4--cdnetworks.cdn
south-america--dp--gping4--cloudflare.cdn
south-america--dp--gping4--digitalocean.cdn
south-america--dp--gping4--fastly.cdn
south-america--dp--gping4--gcp.cdn
south-america--dp--gping4--scaleway.cdn
south-america--dp--gping4--tencent.cdn

Cloud Looking Glass

Cloud Looking Glass Methodology Documentation

Table of Contents

Overview

About This Dataset

Architecture

Account Naming Convention

Test Scheduling Methodology

Universal Tests

Distributed Tests

Data Flow Architecture

Event Validation Process

Automated Detection

Manual Verification

Infrastructure Components

Control Servers

Test Agents

External Test Probes

Measurement Precision

HTTP Measurements Before the Sampling Fix

Google Cloud Storage Regional Endpoints

Amazon S3 Copy Size

Retried API Calls

Amazon DynamoDB Reads

Amazon DynamoDB Table Waits

Firestore Database Creation

Google Cloud Storage Copies

Block and File Storage Timing

Function Tests Aligned Across Clouds

Message Delivery Tests Aligned Across Clouds

Compute Instance Launch and Delete

Same-Zone Network Targets

DNS Zone and Record Waits

CDN Distribution Steps

gpt-oss-120b on the Global Endpoint

AI Prompt Timeout on Google Cloud

Stalled AI Prompts on Google Cloud

Dataset

Sponsorship

About Sponsorship

Schema

Schema Diagram

Tables

tests Table

test_commands Table

test_targets Table

test_outages Table

test_status_* Rollup Tables

Service Types

Primary Services

Supporting Services

Test Categories

Control Plane Tests

Data Plane Tests

Networking Tests

4.3.1 Zonal Measurements

4.3.2 Regional Measurements

4.3.3 Cross-Region Measurements

4.3.4 Edge Measurements

4.3.5 Cross-Cloud Measurements

4.3.6 Last Mile Measurements

Data Characteristics

Update Frequency

Data Volume

Data Retention

Availability vs Performance

Availability Metrics

Calculating Availability

Performance Metrics

Measurement Methodology

Measurement Columns

Performance Analysis Examples

Service Events

Isolated Events

Identifying Isolated Events in the Schema

Large Service Events (LSEs)

Identifying LSEs in the Schema

LSE Impact Assessment

Differentiating Event Types - Key Schema Indicators

Practical Query for Event Classification