Cloud Looking Glass Methodology Documentation

Version: 1.0

Date: August 2025

Dataset: cloudlookingglass

1. Overview
2. Architecture
3. Dataset
1. 3.1 Access
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. Query Examples
1. 10.1 Recent Test Failures
2. 10.2 Service Performance Analysis
3. 10.3 Large Service Event Detection
4. 10.4 Historical Trend Analysis
5. 10.5 Provider Comparison
11. Data Retention
12. Appendix A: Status ID Reference
1. 12.1 Control Plane Status IDs
2. 12.2 Data Plane Status IDs
3. 12.3 Networking Status IDs
  1. 12.3.1 Zonal Measurements
  2. 12.3.2 Regional Measurements
  3. 12.3.3 Cross-Region Measurements
  4. 12.3.4 Cross-Cloud Measurements
  5. 12.3.5 Edge Measurements
  6. 12.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 5 minutes (288 times per day)
Multi-Cloud Coverage: AWS (primary), GCP, Azure, and 20+ other providers
Global Reach: 25+ regions, 100+ availability zones
Triple Redundancy: Three independent test accounts (designated as 'com', 'net', and 'org' 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 three independent test accounts per cloud provider, labeled as 'com', 'net', and 'org' (account 1, 2, and 3) 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 5-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 5 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 5-minute interval.

Data Flow Architecture

Test Initiation
- Cron-based schedulers trigger tests every 5 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 (288 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
- BigQuery replication for long-term analytics
Event Detection
- Triple-redundant validation across all test accounts (com/net/org)
- 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
Conduct both universal and distributed assigned measurements
Capture multi-level timing measurements
Push results to both BigQuery and 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.
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.
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.

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.

Dataset

Cloud Looking Glass uses Google BigQuery as its data lake for storing and analyzing cloud service monitoring data. The dataset contains billions of test results from continuous monitoring across 26+ cloud providers.

Access

Dataset Access: Access to the BigQuery dataset is granted to project sponsors.

Sponsorship: Support the project on GoFundMe
Access Request: Email info@cloudlooking.glass for details
Dataset ID: cloudlookingglass.cloudlookingglass
Project ID: cloudlookingglass

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: BigQuery storage and query processing costs
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

Query Examples:


-- Example: Query from any GCP project
SELECT * FROM `cloudlookingglass.tests` 
WHERE timestamp > TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 1 HOUR)
LIMIT 10;

Schema

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

Schema Diagram


┌─────────────────────────────────────────────────────────────────────────┐
│                           BIGQUERY DATASET SCHEMA                        │
└─────────────────────────────────────────────────────────────────────────┘

                    PRIMARY TABLES (Available in BigQuery)
                    
┌──────────────────────┐  ┌──────────────────────┐  ┌──────────────────────┐
│      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_org                          │
│ 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    - 5 minute intervals, 1 week retention
• test_status_1m    - 10 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 BigQuery dataset.

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): 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-nova-lite-20250626-1')
operation (STRING): Specific operation that failed (e.g., 'attach-volume-st1', 'converse-fact-nova-lite')
test_ids (ARRAY): 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): Structured identifiers for affected services (see Status ID Format section)
tlds (ARRAY): Top-level domains affected ('com', 'net', 'org') 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 available in both PostgreSQL and BigQuery databases, providing pre-computed aggregations for efficient time-series analysis.

Available Tables:

test_status - Real-time ingest table (24-hour window, 5-minute intervals)
test_status_1w - 5-minute aggregates with 1-week retention
test_status_1m - 10-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_org, 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): 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', 'org', 'merged')
expires (TIMESTAMP): When current measurement window expires
measurements (ARRAY): Historical measurements (288 values = 24 hours)
measurements_current (ARRAY): Current window measurements
status (STRING): Current status indicator
stdev (ARRAY): 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

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 Claude 3 Haiku
- Status ID: aws.bedrock.us-east-1--dp--converse-fact-claude-3-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

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.

Validated BigQuery Queries

These queries have been tested and confirmed to return results from the BigQuery dataset.

IMPORTANT NOTE about test_targets.type field:

CRUD tests (e.g., crud-instance-linux, crud-bucket): Use type = 'target'
Network tests (e.g., tcping4, ping6, dns): Use type = 'source' and type = 'dest'
When joining with test_targets, check which test type you're querying to use the correct filter
For queries covering all test types, use type IN ('source', 'target', 'dest')

1. Find Recent Test Failures


-- Get recent failures for a specific test type
-- Returns actual failures from the last 7 days
SELECT 
  t.test_id,
  t.name,
  t.timestamp,
  t.status
FROM `cloudlookingglass.tests` t
WHERE t.name = 'crud-instance-linux'
  AND t.status != 'success'
  AND t.timestamp > TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 7 DAY)
ORDER BY t.timestamp DESC
LIMIT 10;

-- Example result:
-- test_id: 'd46409fa-6f0e-4426-8544-2969e04c3fd2'
-- name: 'crud-instance-linux'
-- timestamp: 2025-08-18 04:51:41
-- status: 'mixed'

2. Correlate Outage to Raw Test Data


-- Given a documented outage, find all related test details
-- Real example: EBS volume attachment failure from August 15, 2025
WITH outage_tests AS (
  SELECT test_id
  FROM `cloudlookingglass.test_outages`,
  UNNEST(test_ids) AS test_id
  WHERE outage_id = 'aws-cp-crud-volume-st1-20250815-1'
)
SELECT 
  t.test_id,
  t.name,
  tc.sequence,
  tc.name AS command_name,
  tc.status AS command_status,
  tc.measurement_mean,
  tc.unit
FROM outage_tests ot
JOIN `cloudlookingglass.tests` t ON ot.test_id = t.test_id
JOIN `cloudlookingglass.test_commands` tc ON t.test_id = tc.test_id
ORDER BY tc.sequence
LIMIT 10;

-- Actual results show the CRUD sequence where attach-volume-st1 failed:
-- sequence 1: create-volume-st1 (success)
-- sequence 2: attach-volume-st1 (failed) <- The failure documented in outage
-- sequence 3: detach-volume-st1 (success)

3. Analyze Service Performance Trends


-- Calculate success rates by service and region
-- IMPORTANT: CRUD tests use type='target' not 'source' in test_targets
SELECT 
  DATE(t.timestamp) AS test_date,
  REGEXP_EXTRACT(t.name, r'crud-(.+)') AS service,
  tt.cloud_region,
  COUNT(*) AS total_tests,
  COUNTIF(t.status = 'success') AS successful_tests,
  ROUND(COUNTIF(t.status = 'success') * 100.0 / COUNT(*), 2) AS success_rate
FROM `cloudlookingglass.tests` t
JOIN `cloudlookingglass.test_targets` tt 
  ON t.test_id = tt.test_id AND tt.type = 'target'  -- CRUD tests use 'target'
WHERE t.name LIKE 'crud-%'
  AND t.timestamp > TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 3 DAY)
  AND tt.cloud = 'aws'
GROUP BY test_date, service, cloud_region
HAVING total_tests >= 50  -- Realistic threshold
ORDER BY test_date DESC, success_rate ASC
LIMIT 10;

-- Actual results:
-- service: 'inference-claude-3-haiku', region: 'us-east-1', success_rate: 99.62%
-- service: 'bucket', region: 'us-east-1', success_rate: 100.0%
-- Most services run ~780-3000+ tests/day depending on variants

4. Cross-Region Network Latency Analysis


-- Analyze TCP connectivity latency between AWS regions
-- Shows actual network latency measurements from the last 24 hours
SELECT 
  source.cloud_region AS source_region,
  dest.cloud_region AS dest_region,
  t.name AS test_type,
  COUNT(*) AS measurements,
  ROUND(AVG(tc.measurement_mean), 2) AS avg_latency_ms,
  ROUND(MIN(tc.measurement_mean), 2) AS min_latency_ms,
  ROUND(MAX(tc.measurement_mean), 2) AS max_latency_ms
FROM `cloudlookingglass.tests` t
JOIN `cloudlookingglass.test_commands` tc ON t.test_id = tc.test_id
JOIN `cloudlookingglass.test_targets` source 
  ON t.test_id = source.test_id AND source.type = 'source'
JOIN `cloudlookingglass.test_targets` dest 
  ON t.test_id = dest.test_id AND dest.type = 'dest'
WHERE t.name IN ('tcping4', 'tcping6')
  AND tc.metric = 'rtt'
  AND source.cloud = 'aws'
  AND dest.cloud = 'aws'
  AND source.cloud_region != dest.cloud_region
  AND t.timestamp > TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 24 HOUR)
GROUP BY source_region, dest_region, test_type
HAVING measurements > 10
ORDER BY avg_latency_ms DESC
LIMIT 10;

-- Actual results show cross-region latencies:
-- us-east-1 to cn-northwest-1: ~265ms (transcontinental)
-- us-east-1 to ap-southeast-7: ~245ms (transpacific)
-- us-east-1 to cn-north-1: ~244ms (transcontinental)

5. Identify Performance Outliers


-- Find EC2 instance creation operations with abnormally high latency
-- Uses percentile analysis to identify outliers
WITH latency_stats AS (
  SELECT 
    tc.name AS command_name,
    tt.cloud_region,
    APPROX_QUANTILES(tc.measurement_mean, 100)[OFFSET(50)] AS p50_latency,
    APPROX_QUANTILES(tc.measurement_mean, 100)[OFFSET(95)] AS p95_latency,
    APPROX_QUANTILES(tc.measurement_mean, 100)[OFFSET(99)] AS p99_latency
  FROM `cloudlookingglass.tests` t
  JOIN `cloudlookingglass.test_commands` tc ON t.test_id = tc.test_id
  JOIN `cloudlookingglass.test_targets` tt ON t.test_id = tt.test_id
  WHERE tc.metric = 'latency'
    AND tc.unit = 'ms'
    AND tc.name = 'create-instance-linux'
    AND t.timestamp > TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 7 DAY)
    AND tt.type = 'target'  -- CRUD tests use 'target'
  GROUP BY tc.name, tt.cloud_region
)
SELECT 
  t.test_id,
  tc.name AS command_name,
  t.timestamp,
  tt.cloud_region,
  ROUND(tc.measurement_mean / 1000, 1) AS latency_seconds,
  ROUND(ls.p50_latency / 1000, 1) AS p50_seconds,
  ROUND(ls.p95_latency / 1000, 1) AS p95_seconds
FROM `cloudlookingglass.tests` t
JOIN `cloudlookingglass.test_commands` tc ON t.test_id = tc.test_id
JOIN `cloudlookingglass.test_targets` tt ON t.test_id = tt.test_id
JOIN latency_stats ls 
  ON tc.name = ls.command_name 
  AND tt.cloud_region = ls.cloud_region
WHERE tc.metric = 'latency'
  AND tc.name = 'create-instance-linux'
  AND tc.measurement_mean > ls.p95_latency
  AND t.timestamp > TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 1 DAY)
  AND tt.type = 'target'  -- CRUD tests use 'target'
ORDER BY tc.measurement_mean DESC
LIMIT 10;

-- Typical EC2 instance creation latencies:
-- p50: ~15-16 seconds
-- p95: ~18-20 seconds
-- Outliers: >24 seconds

6. Test Volume by Cloud Provider


-- Count tests by cloud provider in the last 24 hours
-- Note: Different test types use different 'type' values in test_targets
SELECT 
  tt.cloud,
  COUNT(DISTINCT t.test_id) AS test_count,
  COUNT(DISTINCT t.name) AS unique_test_types
FROM `cloudlookingglass.tests` t
JOIN `cloudlookingglass.test_targets` tt 
  ON t.test_id = tt.test_id 
WHERE t.timestamp > TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 24 HOUR)
  AND tt.cloud IS NOT NULL
  AND tt.type IN ('source', 'target')  -- Include both types
GROUP BY tt.cloud
ORDER BY test_count DESC
LIMIT 10;

-- Actual results:
-- aws: ~1.2M tests, 38 unique test types
-- gcp: ~4K tests, 1 test type

7. Command Success Rate Analysis


-- Analyze which specific commands fail most frequently
SELECT 
  tc.name AS command_name,
  COUNT(*) AS total_executions,
  COUNTIF(tc.status = 'success') AS successful,
  COUNTIF(tc.status = 'failed') AS failed,
  ROUND(COUNTIF(tc.status = 'failed') * 100.0 / COUNT(*), 2) AS failure_rate
FROM `cloudlookingglass.test_commands` tc
JOIN `cloudlookingglass.tests` t ON tc.test_id = t.test_id
WHERE t.timestamp > TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 3 DAY)
  AND tc.name IS NOT NULL
GROUP BY tc.name
HAVING total_executions > 100
ORDER BY failure_rate DESC
LIMIT 20;

8. Geographic Distribution of Tests


-- Show test distribution by geographic region
SELECT 
  geo_regions[SAFE_OFFSET(0)] AS geo_region,
  COUNT(DISTINCT test_id) AS test_count,
  COUNT(DISTINCT hostname) AS unique_hosts
FROM `cloudlookingglass.test_targets`
WHERE type IN ('source', 'target')  -- Include both types
  AND ARRAY_LENGTH(geo_regions) > 0
GROUP BY geo_region
ORDER BY test_count DESC
LIMIT 10;

-- Actual results:
-- north-america: ~216M tests, 22 unique hosts
-- eu: ~4.7M tests, 22 unique hosts
-- mea: ~4.4M tests, 22 unique hosts
-- apac: ~4.4M tests, 22 unique hosts
-- central-america: ~4.4M tests, 22 unique hosts

9. Recent Documented Outages


-- List recent documented outages with details
SELECT 
  outage_id,
  operation,
  partial,
  ARRAY_LENGTH(test_ids) AS affected_tests,
  SUBSTR(notes, 1, 200) AS notes_preview
FROM `cloudlookingglass.test_outages`
WHERE outage_id LIKE 'aws-%2025%'
ORDER BY outage_id DESC
LIMIT 10;

10. Test Resource Utilization


-- Monitor CPU and RAM usage during tests
SELECT 
  name,
  AVG(util_cpu) AS avg_cpu_percent,
  MAX(util_cpu) AS max_cpu_percent,
  AVG(util_ram) AS avg_ram_percent,
  MAX(util_ram) AS max_ram_percent,
  COUNT(*) AS test_count
FROM `cloudlookingglass.tests`
WHERE timestamp > TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 24 HOUR)
  AND util_cpu IS NOT NULL
GROUP BY name
HAVING test_count > 50
ORDER BY avg_cpu_percent DESC
LIMIT 10;

Data Characteristics

Update Frequency

Tests run every 5 minutes (288 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: Indefinite retention in BigQuery
No automatic data expiration or deletion
Historical data available from project inception

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, events_org 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

All control plane and data plane tests leverage official provider CLIs (AWS CLI, gcloud, az, etc.), ensuring consistency with real-world usage patterns while extracting granular timing information that enables meaningful cross-provider comparisons.

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 triple-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 three test accounts (.com, .net, or .org) experiences failures

-- Find isolated events affecting single accounts
SELECT 
    status_id,
    interval_start,
    events_com,
    events_net,
    events_org,
    events_merged,
    CASE 
        WHEN (events_com > 0 AND events_net = 0 AND events_org = 0) THEN 'Isolated to .com'
        WHEN (events_net > 0 AND events_com = 0 AND events_org = 0) THEN 'Isolated to .net'
        WHEN (events_org > 0 AND events_com = 0 AND events_net = 0) THEN 'Isolated to .org'
        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 + events_org) > 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 three 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, events_org: 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_org,
    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 OR events_org > 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_org,
        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_org > 0 AS INT64) as affected_accounts,
        -- Calculate merge ratio
        SAFE_DIVIDE(events_merged, GREATEST(events_com, events_net, events_org)) 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 OR events_org > 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

Appendix A: Status ID Reference

I. Control Plane Status IDs (137 IDs)

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


aws.bedrock.us-east-1--cp--create-inference-claude-3-haiku
aws.bedrock.us-east-1--cp--create-inference-nova-lite
aws.bedrock.us-east-1--cp--create-inference-nova-micro
aws.bedrock.us-east-1--cp--create-inference-nova-pro
aws.bedrock.us-east-1--cp--delete-inference-claude-3-haiku
aws.bedrock.us-east-1--cp--delete-inference-nova-lite
aws.bedrock.us-east-1--cp--delete-inference-nova-micro
aws.bedrock.us-east-1--cp--delete-inference-nova-pro
aws.bedrock.us-east-1--cp--read-inference-claude-3-haiku
aws.bedrock.us-east-1--cp--read-inference-nova-lite
aws.bedrock.us-east-1--cp--read-inference-nova-micro
aws.bedrock.us-east-1--cp--read-inference-nova-pro
aws.bedrock.us-east-1--cp--update-inference-claude-3-haiku
aws.bedrock.us-east-1--cp--update-inference-nova-lite
aws.bedrock.us-east-1--cp--update-inference-nova-micro
aws.bedrock.us-east-1--cp--update-inference-nova-pro
aws.cloudfront--cp--create-distro
aws.cloudfront--cp--delete-distro
aws.cloudfront--cp--invalidate-cache
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--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

II. Data Plane Status IDs (101 IDs)

Data plane tests measure performance operations on existing cloud resources.


aws.bedrock.us-east-1--dp--converse-code-claude-3-haiku
aws.bedrock.us-east-1--dp--converse-code-nova-lite
aws.bedrock.us-east-1--dp--converse-code-nova-micro
aws.bedrock.us-east-1--dp--converse-code-nova-pro
aws.bedrock.us-east-1--dp--converse-fact-claude-3-haiku
aws.bedrock.us-east-1--dp--converse-fact-nova-lite
aws.bedrock.us-east-1--dp--converse-fact-nova-micro
aws.bedrock.us-east-1--dp--converse-fact-nova-pro
aws.bedrock.us-east-1--dp--converse-math-claude-3-haiku
aws.bedrock.us-east-1--dp--converse-math-nova-lite
aws.bedrock.us-east-1--dp--converse-math-nova-micro
aws.bedrock.us-east-1--dp--converse-math-nova-pro
aws.bedrock.us-east-1--dp--converse-reasoning-claude-3-haiku
aws.bedrock.us-east-1--dp--converse-reasoning-nova-lite
aws.bedrock.us-east-1--dp--converse-reasoning-nova-micro
aws.bedrock.us-east-1--dp--converse-reasoning-nova-pro
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

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.ngb1
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.ngb1
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.ngb1
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.ngb1
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

Dataset

Access

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

Validated BigQuery Queries

1. Find Recent Test Failures

2. Correlate Outage to Raw Test Data

3. Analyze Service Performance Trends

4. Cross-Region Network Latency Analysis

5. Identify Performance Outliers

6. Test Volume by Cloud Provider

7. Command Success Rate Analysis

8. Geographic Distribution of Tests

9. Recent Documented Outages

10. Test Resource Utilization

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

Important Notes on Event Detection

Important Notes on Status IDs

Appendix A: Status ID Reference

I. Control Plane Status IDs (137 IDs)

II. Data Plane Status IDs (101 IDs)

III. Network Status IDs (1512 IDs)

Zonal Measurements (72 IDs)