Rtt · Phoenix Framework

ams Amsterdam, Netherlands

	RTT	Loss
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	6ms	0.0%
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	8ms	0.0%
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	12ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	17ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	18ms	0.0%
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	22ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	24ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	36ms	0.0%
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	77ms	0.0%
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	83ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	95ms	0.0%
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	96ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	112ms	0.0%
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	118ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	135ms	0.0%
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	143ms	0.0%
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	150ms	0.0%
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	151ms	0.0%
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	194ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	243ms	0.0%
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	244ms	0.0%
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	244ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	250ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	254ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	259ms	0.0%
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	271ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	282ms	0.0%

arn Stockholm, Sweden

	RTT	Loss
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	3ms	0.0%
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	19ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	24ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	29ms	0.0%
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	29ms	0.0%
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	30ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	36ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	51ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	101ms	0.0%
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	104ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	112ms	0.0%
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	114ms	0.0%
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	128ms	0.0%
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	138ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	152ms	0.0%
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	158ms	0.0%
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	163ms	0.0%
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	174ms	0.0%
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	230ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	255ms	0.0%
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	267ms	0.0%
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	282ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	284ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	287ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	289ms	0.0%
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	315ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	368ms	0.0%

atl Atlanta, Georgia (US)

	RTT	Loss
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	15ms	0.0%
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	25ms	0.0%
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	29ms	0.0%
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	55ms	0.0%
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	68ms	0.0%
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	91ms	0.0%
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	99ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	102ms	0.0%
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	108ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	113ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	114ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	117ms	0.0%
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	125ms	0.0%
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	126ms	0.0%
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	149ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	172ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	179ms	0.0%
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	194ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	197ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	202ms	0.0%
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	206ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	211ms	0.0%
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	220ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	241ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	245ms	0.0%
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	258ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	287ms	0.0%

bog Bogotá, Colombia

	RTT	Loss	Actions
aws-s3-af-south-1 unreachable-aws-s3-af-south-1		100.0%
aws-s3-ap-east-1 unreachable-aws-s3-ap-east-1		100.0%
aws-s3-ap-northeast-1 unreachable-aws-s3-ap-northeast-1		100.0%
aws-s3-ap-northeast-2 unreachable-aws-s3-ap-northeast-2		100.0%
aws-s3-ap-northeast-3 unreachable-aws-s3-ap-northeast-3		100.0%
aws-s3-ap-south-1 unreachable-aws-s3-ap-south-1		100.0%
aws-s3-ap-south-2 unreachable-aws-s3-ap-south-2		100.0%
aws-s3-ap-southeast-1 unreachable-aws-s3-ap-southeast-1		100.0%
aws-s3-ap-southeast-2 unreachable-aws-s3-ap-southeast-2		100.0%
aws-s3-ap-southeast-3 unreachable-aws-s3-ap-southeast-3		100.0%
aws-s3-ap-southeast-4 unreachable-aws-s3-ap-southeast-4		100.0%
aws-s3-ca-central-1 unreachable-aws-s3-ca-central-1		100.0%
aws-s3-eu-central-1 unreachable-aws-s3-eu-central-1		100.0%
aws-s3-eu-central-2 unreachable-aws-s3-eu-central-2		100.0%
aws-s3-eu-north-1 unreachable-aws-s3-eu-north-1		100.0%
aws-s3-eu-south-1 unreachable-aws-s3-eu-south-1		100.0%
aws-s3-eu-south-2 unreachable-aws-s3-eu-south-2		100.0%
aws-s3-eu-west-1 unreachable-aws-s3-eu-west-1		100.0%
aws-s3-eu-west-2 unreachable-aws-s3-eu-west-2		100.0%
aws-s3-eu-west-3 unreachable-aws-s3-eu-west-3		100.0%
aws-s3-me-central-1 unreachable-aws-s3-me-central-1		100.0%
aws-s3-me-south-1 unreachable-aws-s3-me-south-1		100.0%
aws-s3-sa-east-1 unreachable-aws-s3-sa-east-1		100.0%
aws-s3-us-east-1 unreachable-aws-s3-us-east-1		100.0%
aws-s3-us-east-2 unreachable-aws-s3-us-east-2		100.0%
aws-s3-us-west-1 unreachable-aws-s3-us-west-1		100.0%
aws-s3-us-west-2 unreachable-aws-s3-us-west-2		100.0%

bom Mumbai, India

	RTT	Loss
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	1ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	18ms	0.0%
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	79ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	93ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	108ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	125ms	0.0%
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	128ms	0.0%
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	128ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	133ms	0.0%
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	134ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	139ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	140ms	0.0%
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	146ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	147ms	0.0%
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	152ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	160ms	0.0%
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	167ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	184ms	0.0%
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	206ms	0.0%
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	226ms	0.0%
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	228ms	0.0%
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	237ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	241ms	0.0%
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	269ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	284ms	0.0%
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	327ms	0.0%
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	339ms	0.0%

bos Boston, Massachusetts (US)

	RTT	Loss	Actions
aws-s3-af-south-1 unreachable-aws-s3-af-south-1		100.0%
aws-s3-ap-east-1 unreachable-aws-s3-ap-east-1		100.0%
aws-s3-ap-northeast-1 unreachable-aws-s3-ap-northeast-1		100.0%
aws-s3-ap-northeast-2 unreachable-aws-s3-ap-northeast-2		100.0%
aws-s3-ap-northeast-3 unreachable-aws-s3-ap-northeast-3		100.0%
aws-s3-ap-south-1 unreachable-aws-s3-ap-south-1		100.0%
aws-s3-ap-south-2 unreachable-aws-s3-ap-south-2		100.0%
aws-s3-ap-southeast-1 unreachable-aws-s3-ap-southeast-1		100.0%
aws-s3-ap-southeast-2 unreachable-aws-s3-ap-southeast-2		100.0%
aws-s3-ap-southeast-3 unreachable-aws-s3-ap-southeast-3		100.0%
aws-s3-ap-southeast-4 unreachable-aws-s3-ap-southeast-4		100.0%
aws-s3-ca-central-1 unreachable-aws-s3-ca-central-1		100.0%
aws-s3-eu-central-1 unreachable-aws-s3-eu-central-1		100.0%
aws-s3-eu-central-2 unreachable-aws-s3-eu-central-2		100.0%
aws-s3-eu-north-1 unreachable-aws-s3-eu-north-1		100.0%
aws-s3-eu-south-1 unreachable-aws-s3-eu-south-1		100.0%
aws-s3-eu-south-2 unreachable-aws-s3-eu-south-2		100.0%
aws-s3-eu-west-1 unreachable-aws-s3-eu-west-1		100.0%
aws-s3-eu-west-2 unreachable-aws-s3-eu-west-2		100.0%
aws-s3-eu-west-3 unreachable-aws-s3-eu-west-3		100.0%
aws-s3-me-central-1 unreachable-aws-s3-me-central-1		100.0%
aws-s3-me-south-1 unreachable-aws-s3-me-south-1		100.0%
aws-s3-sa-east-1 unreachable-aws-s3-sa-east-1		100.0%
aws-s3-us-east-1 unreachable-aws-s3-us-east-1		100.0%
aws-s3-us-east-2 unreachable-aws-s3-us-east-2		100.0%
aws-s3-us-west-1 unreachable-aws-s3-us-west-1		100.0%
aws-s3-us-west-2 unreachable-aws-s3-us-west-2		100.0%

cdg Paris, France

	RTT	Loss
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	1ms	0.0%
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	9ms	0.0%
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	9ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	10ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	16ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	17ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	20ms	0.0%
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	29ms	0.0%
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	81ms	0.0%
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	84ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	85ms	0.0%
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	100ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	116ms	0.0%
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	127ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	132ms	0.0%
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	147ms	0.0%
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	151ms	0.0%
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	151ms	0.0%
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	159ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	168ms	0.0%
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	191ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	198ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	211ms	0.0%
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	218ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	242ms	0.0%
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	285ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	294ms	0.0%

den Denver, Colorado (US)

	RTT	Loss	Actions
aws-s3-af-south-1 unreachable-aws-s3-af-south-1		100.0%
aws-s3-ap-east-1 unreachable-aws-s3-ap-east-1		100.0%
aws-s3-ap-northeast-1 unreachable-aws-s3-ap-northeast-1		100.0%
aws-s3-ap-northeast-2 unreachable-aws-s3-ap-northeast-2		100.0%
aws-s3-ap-northeast-3 unreachable-aws-s3-ap-northeast-3		100.0%
aws-s3-ap-south-1 unreachable-aws-s3-ap-south-1		100.0%
aws-s3-ap-south-2 unreachable-aws-s3-ap-south-2		100.0%
aws-s3-ap-southeast-1 unreachable-aws-s3-ap-southeast-1		100.0%
aws-s3-ap-southeast-2 unreachable-aws-s3-ap-southeast-2		100.0%
aws-s3-ap-southeast-3 unreachable-aws-s3-ap-southeast-3		100.0%
aws-s3-ap-southeast-4 unreachable-aws-s3-ap-southeast-4		100.0%
aws-s3-ca-central-1 unreachable-aws-s3-ca-central-1		100.0%
aws-s3-eu-central-1 unreachable-aws-s3-eu-central-1		100.0%
aws-s3-eu-central-2 unreachable-aws-s3-eu-central-2		100.0%
aws-s3-eu-north-1 unreachable-aws-s3-eu-north-1		100.0%
aws-s3-eu-south-1 unreachable-aws-s3-eu-south-1		100.0%
aws-s3-eu-south-2 unreachable-aws-s3-eu-south-2		100.0%
aws-s3-eu-west-1 unreachable-aws-s3-eu-west-1		100.0%
aws-s3-eu-west-2 unreachable-aws-s3-eu-west-2		100.0%
aws-s3-eu-west-3 unreachable-aws-s3-eu-west-3		100.0%
aws-s3-me-central-1 unreachable-aws-s3-me-central-1		100.0%
aws-s3-me-south-1 unreachable-aws-s3-me-south-1		100.0%
aws-s3-sa-east-1 unreachable-aws-s3-sa-east-1		100.0%
aws-s3-us-east-1 unreachable-aws-s3-us-east-1		100.0%
aws-s3-us-east-2 unreachable-aws-s3-us-east-2		100.0%
aws-s3-us-west-1 unreachable-aws-s3-us-west-1		100.0%
aws-s3-us-west-2 unreachable-aws-s3-us-west-2		100.0%

dfw Dallas, Texas (US)

	RTT	Loss
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	24ms	0.0%
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	32ms	0.0%
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	41ms	0.0%
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	45ms	0.0%
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	62ms	0.0%
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	102ms	0.0%
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	111ms	0.0%
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	117ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	123ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	124ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	124ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	138ms	0.0%
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	139ms	0.0%
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	143ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	156ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	186ms	0.0%
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	187ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	188ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	203ms	0.0%
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	204ms	0.0%
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	215ms	0.0%
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	218ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	220ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	224ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	247ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	267ms	0.0%
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	273ms	0.0%

ewr Secaucus, NJ (US)

	RTT	Loss
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	10ms	0.0%
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	23ms	0.0%
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	67ms	0.0%
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	70ms	0.0%
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	73ms	0.0%
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	75ms	0.0%
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	82ms	0.0%
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	84ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	88ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	89ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	91ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	95ms	0.0%
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	103ms	0.0%
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	115ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	154ms	0.0%
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	174ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	176ms	0.0%
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	189ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	200ms	0.0%
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	205ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	217ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	218ms	0.0%
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	232ms	0.0%
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	235ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	253ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	264ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	307ms	0.0%

eze Ezeiza, Argentina

	RTT	Loss	Actions
aws-s3-af-south-1 unreachable-aws-s3-af-south-1		100.0%
aws-s3-ap-east-1 unreachable-aws-s3-ap-east-1		100.0%
aws-s3-ap-northeast-1 unreachable-aws-s3-ap-northeast-1		100.0%
aws-s3-ap-northeast-2 unreachable-aws-s3-ap-northeast-2		100.0%
aws-s3-ap-northeast-3 unreachable-aws-s3-ap-northeast-3		100.0%
aws-s3-ap-south-1 unreachable-aws-s3-ap-south-1		100.0%
aws-s3-ap-south-2 unreachable-aws-s3-ap-south-2		100.0%
aws-s3-ap-southeast-1 unreachable-aws-s3-ap-southeast-1		100.0%
aws-s3-ap-southeast-2 unreachable-aws-s3-ap-southeast-2		100.0%
aws-s3-ap-southeast-3 unreachable-aws-s3-ap-southeast-3		100.0%
aws-s3-ap-southeast-4 unreachable-aws-s3-ap-southeast-4		100.0%
aws-s3-ca-central-1 unreachable-aws-s3-ca-central-1		100.0%
aws-s3-eu-central-1 unreachable-aws-s3-eu-central-1		100.0%
aws-s3-eu-central-2 unreachable-aws-s3-eu-central-2		100.0%
aws-s3-eu-north-1 unreachable-aws-s3-eu-north-1		100.0%
aws-s3-eu-south-1 unreachable-aws-s3-eu-south-1		100.0%
aws-s3-eu-south-2 unreachable-aws-s3-eu-south-2		100.0%
aws-s3-eu-west-1 unreachable-aws-s3-eu-west-1		100.0%
aws-s3-eu-west-2 unreachable-aws-s3-eu-west-2		100.0%
aws-s3-eu-west-3 unreachable-aws-s3-eu-west-3		100.0%
aws-s3-me-central-1 unreachable-aws-s3-me-central-1		100.0%
aws-s3-me-south-1 unreachable-aws-s3-me-south-1		100.0%
aws-s3-sa-east-1 unreachable-aws-s3-sa-east-1		100.0%
aws-s3-us-east-1 unreachable-aws-s3-us-east-1		100.0%
aws-s3-us-east-2 unreachable-aws-s3-us-east-2		100.0%
aws-s3-us-west-1 unreachable-aws-s3-us-west-1		100.0%
aws-s3-us-west-2 unreachable-aws-s3-us-west-2		100.0%

fra Frankfurt, Germany

	RTT	Loss
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	4ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	8ms	0.0%
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	10ms	0.0%
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	14ms	0.0%
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	20ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	21ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	26ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	33ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	84ms	0.0%
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	84ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	96ms	0.0%
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	97ms	0.0%
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	106ms	0.0%
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	120ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	135ms	0.0%
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	153ms	0.0%
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	155ms	0.0%
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	163ms	0.0%
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	172ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	188ms	0.0%
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	194ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	198ms	0.0%
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	235ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	251ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	268ms	0.0%
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	279ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	296ms	0.0%

gdl Guadalajara, Mexico

	RTT	Loss	Actions
aws-s3-af-south-1 unreachable-aws-s3-af-south-1		100.0%
aws-s3-ap-east-1 unreachable-aws-s3-ap-east-1		100.0%
aws-s3-ap-northeast-1 unreachable-aws-s3-ap-northeast-1		100.0%
aws-s3-ap-northeast-2 unreachable-aws-s3-ap-northeast-2		100.0%
aws-s3-ap-northeast-3 unreachable-aws-s3-ap-northeast-3		100.0%
aws-s3-ap-south-1 unreachable-aws-s3-ap-south-1		100.0%
aws-s3-ap-south-2 unreachable-aws-s3-ap-south-2		100.0%
aws-s3-ap-southeast-1 unreachable-aws-s3-ap-southeast-1		100.0%
aws-s3-ap-southeast-2 unreachable-aws-s3-ap-southeast-2		100.0%
aws-s3-ap-southeast-3 unreachable-aws-s3-ap-southeast-3		100.0%
aws-s3-ap-southeast-4 unreachable-aws-s3-ap-southeast-4		100.0%
aws-s3-ca-central-1 unreachable-aws-s3-ca-central-1		100.0%
aws-s3-eu-central-1 unreachable-aws-s3-eu-central-1		100.0%
aws-s3-eu-central-2 unreachable-aws-s3-eu-central-2		100.0%
aws-s3-eu-north-1 unreachable-aws-s3-eu-north-1		100.0%
aws-s3-eu-south-1 unreachable-aws-s3-eu-south-1		100.0%
aws-s3-eu-south-2 unreachable-aws-s3-eu-south-2		100.0%
aws-s3-eu-west-1 unreachable-aws-s3-eu-west-1		100.0%
aws-s3-eu-west-2 unreachable-aws-s3-eu-west-2		100.0%
aws-s3-eu-west-3 unreachable-aws-s3-eu-west-3		100.0%
aws-s3-me-central-1 unreachable-aws-s3-me-central-1		100.0%
aws-s3-me-south-1 unreachable-aws-s3-me-south-1		100.0%
aws-s3-sa-east-1 unreachable-aws-s3-sa-east-1		100.0%
aws-s3-us-east-1 unreachable-aws-s3-us-east-1		100.0%
aws-s3-us-east-2 unreachable-aws-s3-us-east-2		100.0%
aws-s3-us-west-1 unreachable-aws-s3-us-west-1		100.0%
aws-s3-us-west-2 unreachable-aws-s3-us-west-2		100.0%

gig Rio de Janeiro, Brazil

	RTT	Loss	Actions
aws-s3-af-south-1 unreachable-aws-s3-af-south-1		100.0%
aws-s3-ap-east-1 unreachable-aws-s3-ap-east-1		100.0%
aws-s3-ap-northeast-1 unreachable-aws-s3-ap-northeast-1		100.0%
aws-s3-ap-northeast-2 unreachable-aws-s3-ap-northeast-2		100.0%
aws-s3-ap-northeast-3 unreachable-aws-s3-ap-northeast-3		100.0%
aws-s3-ap-south-1 unreachable-aws-s3-ap-south-1		100.0%
aws-s3-ap-south-2 unreachable-aws-s3-ap-south-2		100.0%
aws-s3-ap-southeast-1 unreachable-aws-s3-ap-southeast-1		100.0%
aws-s3-ap-southeast-2 unreachable-aws-s3-ap-southeast-2		100.0%
aws-s3-ap-southeast-3 unreachable-aws-s3-ap-southeast-3		100.0%
aws-s3-ap-southeast-4 unreachable-aws-s3-ap-southeast-4		100.0%
aws-s3-ca-central-1 unreachable-aws-s3-ca-central-1		100.0%
aws-s3-eu-central-1 unreachable-aws-s3-eu-central-1		100.0%
aws-s3-eu-central-2 unreachable-aws-s3-eu-central-2		100.0%
aws-s3-eu-north-1 unreachable-aws-s3-eu-north-1		100.0%
aws-s3-eu-south-1 unreachable-aws-s3-eu-south-1		100.0%
aws-s3-eu-south-2 unreachable-aws-s3-eu-south-2		100.0%
aws-s3-eu-west-1 unreachable-aws-s3-eu-west-1		100.0%
aws-s3-eu-west-2 unreachable-aws-s3-eu-west-2		100.0%
aws-s3-eu-west-3 unreachable-aws-s3-eu-west-3		100.0%
aws-s3-me-central-1 unreachable-aws-s3-me-central-1		100.0%
aws-s3-me-south-1 unreachable-aws-s3-me-south-1		100.0%
aws-s3-sa-east-1 unreachable-aws-s3-sa-east-1		100.0%
aws-s3-us-east-1 unreachable-aws-s3-us-east-1		100.0%
aws-s3-us-east-2 unreachable-aws-s3-us-east-2		100.0%
aws-s3-us-west-1 unreachable-aws-s3-us-west-1		100.0%
aws-s3-us-west-2 unreachable-aws-s3-us-west-2		100.0%

gru Sao Paulo, Brazil

	RTT	Loss
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	3ms	0.0%
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	114ms	0.0%
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	130ms	0.0%
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	136ms	0.0%
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	180ms	0.0%
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	187ms	0.0%
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	189ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	190ms	0.0%
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	192ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	201ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	207ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	210ms	0.0%
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	220ms	0.0%
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	243ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	266ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	282ms	0.0%
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	287ms	0.0%
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	300ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	313ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	333ms	0.0%
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	345ms	0.0%
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	348ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	358ms	0.0%
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	371ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	373ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	373ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	379ms	0.0%

hkg Hong Kong, Hong Kong

	RTT	Loss	Actions
aws-s3-af-south-1 unreachable-aws-s3-af-south-1		100.0%
aws-s3-ap-east-1 unreachable-aws-s3-ap-east-1		100.0%
aws-s3-ap-northeast-1 unreachable-aws-s3-ap-northeast-1		100.0%
aws-s3-ap-northeast-2 unreachable-aws-s3-ap-northeast-2		100.0%
aws-s3-ap-northeast-3 unreachable-aws-s3-ap-northeast-3		100.0%
aws-s3-ap-south-1 unreachable-aws-s3-ap-south-1		100.0%
aws-s3-ap-south-2 unreachable-aws-s3-ap-south-2		100.0%
aws-s3-ap-southeast-1 unreachable-aws-s3-ap-southeast-1		100.0%
aws-s3-ap-southeast-2 unreachable-aws-s3-ap-southeast-2		100.0%
aws-s3-ap-southeast-3 unreachable-aws-s3-ap-southeast-3		100.0%
aws-s3-ap-southeast-4 unreachable-aws-s3-ap-southeast-4		100.0%
aws-s3-ca-central-1 unreachable-aws-s3-ca-central-1		100.0%
aws-s3-eu-central-1 unreachable-aws-s3-eu-central-1		100.0%
aws-s3-eu-central-2 unreachable-aws-s3-eu-central-2		100.0%
aws-s3-eu-north-1 unreachable-aws-s3-eu-north-1		100.0%
aws-s3-eu-south-1 unreachable-aws-s3-eu-south-1		100.0%
aws-s3-eu-south-2 unreachable-aws-s3-eu-south-2		100.0%
aws-s3-eu-west-1 unreachable-aws-s3-eu-west-1		100.0%
aws-s3-eu-west-2 unreachable-aws-s3-eu-west-2		100.0%
aws-s3-eu-west-3 unreachable-aws-s3-eu-west-3		100.0%
aws-s3-me-central-1 unreachable-aws-s3-me-central-1		100.0%
aws-s3-me-south-1 unreachable-aws-s3-me-south-1		100.0%
aws-s3-sa-east-1 unreachable-aws-s3-sa-east-1		100.0%
aws-s3-us-east-1 unreachable-aws-s3-us-east-1		100.0%
aws-s3-us-east-2 unreachable-aws-s3-us-east-2		100.0%
aws-s3-us-west-1 unreachable-aws-s3-us-west-1		100.0%
aws-s3-us-west-2 unreachable-aws-s3-us-west-2		100.0%

iad Ashburn, Virginia (US)

	RTT	Loss
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	2ms	0.0%
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	10ms	0.0%
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	15ms	0.0%
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	62ms	0.0%
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	75ms	0.0%
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	84ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	85ms	0.0%
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	92ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	98ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	100ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	100ms	0.0%
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	112ms	0.0%
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	117ms	0.0%
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	146ms	0.0%
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	173ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	183ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	199ms	0.0%
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	200ms	0.0%
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	202ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	219ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	219ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	224ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	231ms	0.0%
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	232ms	0.0%
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	246ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	256ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	256ms	0.0%

jnb Johannesburg, South Africa

	RTT	Loss
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	27ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	117ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	124ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	165ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	168ms	0.0%
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	168ms	0.0%
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	174ms	0.0%
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	175ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	176ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	185ms	0.0%
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	212ms	0.0%
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	274ms	0.0%
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	285ms	0.0%
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	296ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	301ms	0.0%
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	307ms	0.0%
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	338ms	0.0%
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	343ms	0.0%
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	348ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	351ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	357ms	0.0%
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	382ms	0.0%
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	407ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	415ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	442ms	0.0%
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	476ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	488ms	0.0%

lax Los Angeles, California (US)

	RTT	Loss
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	10ms	0.0%
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	27ms	0.0%
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	59ms	0.0%
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	61ms	0.0%
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	73ms	0.0%
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	123ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	130ms	0.0%
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	131ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	135ms	0.0%
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	135ms	0.0%
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	142ms	0.0%
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	147ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	149ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	151ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	151ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	152ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	164ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	167ms	0.0%
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	171ms	0.0%
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	175ms	0.0%
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	190ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	195ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	210ms	0.0%
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	248ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	250ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	253ms	0.0%
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	299ms	0.0%

lhr London, United Kingdom

	RTT	Loss
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	2ms	0.0%
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	9ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	10ms	0.0%
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	14ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	16ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	27ms	0.0%
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	30ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	35ms	0.0%
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	75ms	0.0%
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	87ms	0.0%
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	92ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	93ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	118ms	0.0%
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	122ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	141ms	0.0%
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	146ms	0.0%
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	147ms	0.0%
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	149ms	0.0%
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	184ms	0.0%
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	235ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	240ms	0.0%
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	243ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	254ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	261ms	0.0%
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	274ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	285ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	293ms	0.0%

mad Madrid, Spain

	RTT	Loss	Actions
aws-s3-af-south-1 unreachable-aws-s3-af-south-1		100.0%
aws-s3-ap-east-1 unreachable-aws-s3-ap-east-1		100.0%
aws-s3-ap-northeast-1 unreachable-aws-s3-ap-northeast-1		100.0%
aws-s3-ap-northeast-2 unreachable-aws-s3-ap-northeast-2		100.0%
aws-s3-ap-northeast-3 unreachable-aws-s3-ap-northeast-3		100.0%
aws-s3-ap-south-1 unreachable-aws-s3-ap-south-1		100.0%
aws-s3-ap-south-2 unreachable-aws-s3-ap-south-2		100.0%
aws-s3-ap-southeast-1 unreachable-aws-s3-ap-southeast-1		100.0%
aws-s3-ap-southeast-2 unreachable-aws-s3-ap-southeast-2		100.0%
aws-s3-ap-southeast-3 unreachable-aws-s3-ap-southeast-3		100.0%
aws-s3-ap-southeast-4 unreachable-aws-s3-ap-southeast-4		100.0%
aws-s3-ca-central-1 unreachable-aws-s3-ca-central-1		100.0%
aws-s3-eu-central-1 unreachable-aws-s3-eu-central-1		100.0%
aws-s3-eu-central-2 unreachable-aws-s3-eu-central-2		100.0%
aws-s3-eu-north-1 unreachable-aws-s3-eu-north-1		100.0%
aws-s3-eu-south-1 unreachable-aws-s3-eu-south-1		100.0%
aws-s3-eu-south-2 unreachable-aws-s3-eu-south-2		100.0%
aws-s3-eu-west-1 unreachable-aws-s3-eu-west-1		100.0%
aws-s3-eu-west-2 unreachable-aws-s3-eu-west-2		100.0%
aws-s3-eu-west-3 unreachable-aws-s3-eu-west-3		100.0%
aws-s3-me-central-1 unreachable-aws-s3-me-central-1		100.0%
aws-s3-me-south-1 unreachable-aws-s3-me-south-1		100.0%
aws-s3-sa-east-1 unreachable-aws-s3-sa-east-1		100.0%
aws-s3-us-east-1 unreachable-aws-s3-us-east-1		100.0%
aws-s3-us-east-2 unreachable-aws-s3-us-east-2		100.0%
aws-s3-us-west-1 unreachable-aws-s3-us-west-1		100.0%
aws-s3-us-west-2 unreachable-aws-s3-us-west-2		100.0%

mia Miami, Florida (US)

	RTT	Loss
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	26ms	0.0%
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	39ms	0.0%
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	39ms	0.0%
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	68ms	0.0%
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	86ms	0.0%
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	103ms	0.0%
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	105ms	0.0%
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	110ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	119ms	0.0%
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	121ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	130ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	153ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	166ms	0.0%
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	173ms	0.0%
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	176ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	182ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	187ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	198ms	0.0%
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	200ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	211ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	222ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	222ms	0.0%
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	226ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	237ms	0.0%
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	248ms	0.0%
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	254ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	294ms	0.0%

nrt Tokyo, Japan

	RTT	Loss
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	3ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	9ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	33ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	51ms	0.0%
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	66ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	80ms	0.0%
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	102ms	0.0%
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	106ms	0.0%
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	119ms	0.0%
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	124ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	125ms	0.0%
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	169ms	0.0%
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	183ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	216ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	219ms	0.0%
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	231ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	234ms	0.0%
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	241ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	256ms	0.0%
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	257ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	257ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	261ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	264ms	0.0%
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	279ms	0.0%
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	289ms	0.0%
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	295ms	0.0%
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	381ms	0.0%

ord Chicago, Illinois (US)

	RTT	Loss
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	11ms	0.0%
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	20ms	0.0%
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	25ms	0.0%
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	51ms	0.0%
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	58ms	0.0%
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	88ms	0.0%
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	90ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	101ms	0.0%
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	106ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	114ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	117ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	130ms	0.0%
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	131ms	0.0%
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	132ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	155ms	0.0%
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	159ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	188ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	190ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	197ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	207ms	0.0%
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	216ms	0.0%
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	225ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	237ms	0.0%
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	238ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	244ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	255ms	0.0%
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	264ms	0.0%

otp Bucharest, Romania

	RTT	Loss	Actions
aws-s3-af-south-1 unreachable-aws-s3-af-south-1		100.0%
aws-s3-ap-east-1 unreachable-aws-s3-ap-east-1		100.0%
aws-s3-ap-northeast-1 unreachable-aws-s3-ap-northeast-1		100.0%
aws-s3-ap-northeast-2 unreachable-aws-s3-ap-northeast-2		100.0%
aws-s3-ap-northeast-3 unreachable-aws-s3-ap-northeast-3		100.0%
aws-s3-ap-south-1 unreachable-aws-s3-ap-south-1		100.0%
aws-s3-ap-south-2 unreachable-aws-s3-ap-south-2		100.0%
aws-s3-ap-southeast-1 unreachable-aws-s3-ap-southeast-1		100.0%
aws-s3-ap-southeast-2 unreachable-aws-s3-ap-southeast-2		100.0%
aws-s3-ap-southeast-3 unreachable-aws-s3-ap-southeast-3		100.0%
aws-s3-ap-southeast-4 unreachable-aws-s3-ap-southeast-4		100.0%
aws-s3-ca-central-1 unreachable-aws-s3-ca-central-1		100.0%
aws-s3-eu-central-1 unreachable-aws-s3-eu-central-1		100.0%
aws-s3-eu-central-2 unreachable-aws-s3-eu-central-2		100.0%
aws-s3-eu-north-1 unreachable-aws-s3-eu-north-1		100.0%
aws-s3-eu-south-1 unreachable-aws-s3-eu-south-1		100.0%
aws-s3-eu-south-2 unreachable-aws-s3-eu-south-2		100.0%
aws-s3-eu-west-1 unreachable-aws-s3-eu-west-1		100.0%
aws-s3-eu-west-2 unreachable-aws-s3-eu-west-2		100.0%
aws-s3-eu-west-3 unreachable-aws-s3-eu-west-3		100.0%
aws-s3-me-central-1 unreachable-aws-s3-me-central-1		100.0%
aws-s3-me-south-1 unreachable-aws-s3-me-south-1		100.0%
aws-s3-sa-east-1 unreachable-aws-s3-sa-east-1		100.0%
aws-s3-us-east-1 unreachable-aws-s3-us-east-1		100.0%
aws-s3-us-east-2 unreachable-aws-s3-us-east-2		100.0%
aws-s3-us-west-1 unreachable-aws-s3-us-west-1		100.0%
aws-s3-us-west-2 unreachable-aws-s3-us-west-2		100.0%

phx Phoenix, Arizona (US)

	RTT	Loss	Actions
aws-s3-af-south-1 unreachable-aws-s3-af-south-1		100.0%
aws-s3-ap-east-1 unreachable-aws-s3-ap-east-1		100.0%
aws-s3-ap-northeast-1 unreachable-aws-s3-ap-northeast-1		100.0%
aws-s3-ap-northeast-2 unreachable-aws-s3-ap-northeast-2		100.0%
aws-s3-ap-northeast-3 unreachable-aws-s3-ap-northeast-3		100.0%
aws-s3-ap-south-1 unreachable-aws-s3-ap-south-1		100.0%
aws-s3-ap-south-2 unreachable-aws-s3-ap-south-2		100.0%
aws-s3-ap-southeast-1 unreachable-aws-s3-ap-southeast-1		100.0%
aws-s3-ap-southeast-2 unreachable-aws-s3-ap-southeast-2		100.0%
aws-s3-ap-southeast-3 unreachable-aws-s3-ap-southeast-3		100.0%
aws-s3-ap-southeast-4 unreachable-aws-s3-ap-southeast-4		100.0%
aws-s3-ca-central-1 unreachable-aws-s3-ca-central-1		100.0%
aws-s3-eu-central-1 unreachable-aws-s3-eu-central-1		100.0%
aws-s3-eu-central-2 unreachable-aws-s3-eu-central-2		100.0%
aws-s3-eu-north-1 unreachable-aws-s3-eu-north-1		100.0%
aws-s3-eu-south-1 unreachable-aws-s3-eu-south-1		100.0%
aws-s3-eu-south-2 unreachable-aws-s3-eu-south-2		100.0%
aws-s3-eu-west-1 unreachable-aws-s3-eu-west-1		100.0%
aws-s3-eu-west-2 unreachable-aws-s3-eu-west-2		100.0%
aws-s3-eu-west-3 unreachable-aws-s3-eu-west-3		100.0%
aws-s3-me-central-1 unreachable-aws-s3-me-central-1		100.0%
aws-s3-me-south-1 unreachable-aws-s3-me-south-1		100.0%
aws-s3-sa-east-1 unreachable-aws-s3-sa-east-1		100.0%
aws-s3-us-east-1 unreachable-aws-s3-us-east-1		100.0%
aws-s3-us-east-2 unreachable-aws-s3-us-east-2		100.0%
aws-s3-us-west-1 unreachable-aws-s3-us-west-1		100.0%
aws-s3-us-west-2 unreachable-aws-s3-us-west-2		100.0%

qro Querétaro, Mexico

	RTT	Loss	Actions
aws-s3-af-south-1 unreachable-aws-s3-af-south-1		100.0%
aws-s3-ap-east-1 unreachable-aws-s3-ap-east-1		100.0%
aws-s3-ap-northeast-1 unreachable-aws-s3-ap-northeast-1		100.0%
aws-s3-ap-northeast-2 unreachable-aws-s3-ap-northeast-2		100.0%
aws-s3-ap-northeast-3 unreachable-aws-s3-ap-northeast-3		100.0%
aws-s3-ap-south-1 unreachable-aws-s3-ap-south-1		100.0%
aws-s3-ap-south-2 unreachable-aws-s3-ap-south-2		100.0%
aws-s3-ap-southeast-1 unreachable-aws-s3-ap-southeast-1		100.0%
aws-s3-ap-southeast-2 unreachable-aws-s3-ap-southeast-2		100.0%
aws-s3-ap-southeast-3 unreachable-aws-s3-ap-southeast-3		100.0%
aws-s3-ap-southeast-4 unreachable-aws-s3-ap-southeast-4		100.0%
aws-s3-ca-central-1 unreachable-aws-s3-ca-central-1		100.0%
aws-s3-eu-central-1 unreachable-aws-s3-eu-central-1		100.0%
aws-s3-eu-central-2 unreachable-aws-s3-eu-central-2		100.0%
aws-s3-eu-north-1 unreachable-aws-s3-eu-north-1		100.0%
aws-s3-eu-south-1 unreachable-aws-s3-eu-south-1		100.0%
aws-s3-eu-south-2 unreachable-aws-s3-eu-south-2		100.0%
aws-s3-eu-west-1 unreachable-aws-s3-eu-west-1		100.0%
aws-s3-eu-west-2 unreachable-aws-s3-eu-west-2		100.0%
aws-s3-eu-west-3 unreachable-aws-s3-eu-west-3		100.0%
aws-s3-me-central-1 unreachable-aws-s3-me-central-1		100.0%
aws-s3-me-south-1 unreachable-aws-s3-me-south-1		100.0%
aws-s3-sa-east-1 unreachable-aws-s3-sa-east-1		100.0%
aws-s3-us-east-1 unreachable-aws-s3-us-east-1		100.0%
aws-s3-us-east-2 unreachable-aws-s3-us-east-2		100.0%
aws-s3-us-west-1 unreachable-aws-s3-us-west-1		100.0%
aws-s3-us-west-2 unreachable-aws-s3-us-west-2		100.0%

scl Santiago, Chile

	RTT	Loss	Actions
aws-s3-af-south-1 unreachable-aws-s3-af-south-1		100.0%
aws-s3-ap-east-1 unreachable-aws-s3-ap-east-1		100.0%
aws-s3-ap-northeast-1 unreachable-aws-s3-ap-northeast-1		100.0%
aws-s3-ap-northeast-2 unreachable-aws-s3-ap-northeast-2		100.0%
aws-s3-ap-northeast-3 unreachable-aws-s3-ap-northeast-3		100.0%
aws-s3-ap-south-1 unreachable-aws-s3-ap-south-1		100.0%
aws-s3-ap-south-2 unreachable-aws-s3-ap-south-2		100.0%
aws-s3-ap-southeast-1 unreachable-aws-s3-ap-southeast-1		100.0%
aws-s3-ap-southeast-2 unreachable-aws-s3-ap-southeast-2		100.0%
aws-s3-ap-southeast-3 unreachable-aws-s3-ap-southeast-3		100.0%
aws-s3-ap-southeast-4 unreachable-aws-s3-ap-southeast-4		100.0%
aws-s3-ca-central-1 unreachable-aws-s3-ca-central-1		100.0%
aws-s3-eu-central-1 unreachable-aws-s3-eu-central-1		100.0%
aws-s3-eu-central-2 unreachable-aws-s3-eu-central-2		100.0%
aws-s3-eu-north-1 unreachable-aws-s3-eu-north-1		100.0%
aws-s3-eu-south-1 unreachable-aws-s3-eu-south-1		100.0%
aws-s3-eu-south-2 unreachable-aws-s3-eu-south-2		100.0%
aws-s3-eu-west-1 unreachable-aws-s3-eu-west-1		100.0%
aws-s3-eu-west-2 unreachable-aws-s3-eu-west-2		100.0%
aws-s3-eu-west-3 unreachable-aws-s3-eu-west-3		100.0%
aws-s3-me-central-1 unreachable-aws-s3-me-central-1		100.0%
aws-s3-me-south-1 unreachable-aws-s3-me-south-1		100.0%
aws-s3-sa-east-1 unreachable-aws-s3-sa-east-1		100.0%
aws-s3-us-east-1 unreachable-aws-s3-us-east-1		100.0%
aws-s3-us-east-2 unreachable-aws-s3-us-east-2		100.0%
aws-s3-us-west-1 unreachable-aws-s3-us-west-1		100.0%
aws-s3-us-west-2 unreachable-aws-s3-us-west-2		100.0%

sea Seattle, Washington (US)

	RTT	Loss
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	7ms	0.0%
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	27ms	0.0%
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	64ms	0.0%
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	64ms	0.0%
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	84ms	0.0%
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	128ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	140ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	144ms	0.0%
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	148ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	151ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	152ms	0.0%
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	154ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	156ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	157ms	0.0%
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	158ms	0.0%
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	158ms	0.0%
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	162ms	0.0%
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	182ms	0.0%
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	203ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	215ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	217ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	222ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	235ms	0.0%
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	247ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	252ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	263ms	0.0%
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	292ms	0.0%

sin Singapore, Singapore

	RTT	Loss
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	1ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	14ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	39ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	44ms	0.0%
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	61ms	0.0%
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	69ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	71ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	75ms	0.0%
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	92ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	103ms	0.0%
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	151ms	0.0%
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	153ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	165ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	167ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	168ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	175ms	0.0%
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	179ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	195ms	0.0%
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	200ms	0.0%
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	234ms	0.0%
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	239ms	0.0%
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	242ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	248ms	0.0%
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	256ms	0.0%
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	256ms	0.0%
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	335ms	0.0%
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	335ms	0.0%

sjc San Jose, California (US)

	RTT	Loss
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	1ms	0.0%
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	20ms	0.0%
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	58ms	0.0%
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	69ms	0.0%
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	82ms	0.0%
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	107ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	120ms	0.0%
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	134ms	0.0%
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	136ms	0.0%
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	137ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	139ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	141ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	149ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	152ms	0.0%
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	154ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	155ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	156ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	162ms	0.0%
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	163ms	0.0%
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	181ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	193ms	0.0%
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	206ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	222ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	241ms	0.0%
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	253ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	258ms	0.0%
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	269ms	0.0%

syd Sydney, Australia

	RTT	Loss
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	2ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	12ms	0.0%
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	101ms	0.0%
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	130ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	131ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	142ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	145ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	172ms	0.0%
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	189ms	0.0%
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	191ms	0.0%
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	194ms	0.0%
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	205ms	0.0%
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	207ms	0.0%
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	233ms	0.0%
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	246ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	246ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	247ms	0.0%
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	260ms	0.0%
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	267ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	268ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	287ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	289ms	0.0%
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	305ms	0.0%
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	311ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	314ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	332ms	0.0%
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	414ms	0.0%

waw Warsaw, Poland

	RTT	Loss	Actions
aws-s3-af-south-1 unreachable-aws-s3-af-south-1		100.0%
aws-s3-ap-east-1 unreachable-aws-s3-ap-east-1		100.0%
aws-s3-ap-northeast-1 unreachable-aws-s3-ap-northeast-1		100.0%
aws-s3-ap-northeast-2 unreachable-aws-s3-ap-northeast-2		100.0%
aws-s3-ap-northeast-3 unreachable-aws-s3-ap-northeast-3		100.0%
aws-s3-ap-south-1 unreachable-aws-s3-ap-south-1		100.0%
aws-s3-ap-south-2 unreachable-aws-s3-ap-south-2		100.0%
aws-s3-ap-southeast-1 unreachable-aws-s3-ap-southeast-1		100.0%
aws-s3-ap-southeast-2 unreachable-aws-s3-ap-southeast-2		100.0%
aws-s3-ap-southeast-3 unreachable-aws-s3-ap-southeast-3		100.0%
aws-s3-ap-southeast-4 unreachable-aws-s3-ap-southeast-4		100.0%
aws-s3-ca-central-1 unreachable-aws-s3-ca-central-1		100.0%
aws-s3-eu-central-1 unreachable-aws-s3-eu-central-1		100.0%
aws-s3-eu-central-2 unreachable-aws-s3-eu-central-2		100.0%
aws-s3-eu-north-1 unreachable-aws-s3-eu-north-1		100.0%
aws-s3-eu-south-1 unreachable-aws-s3-eu-south-1		100.0%
aws-s3-eu-south-2 unreachable-aws-s3-eu-south-2		100.0%
aws-s3-eu-west-1 unreachable-aws-s3-eu-west-1		100.0%
aws-s3-eu-west-2 unreachable-aws-s3-eu-west-2		100.0%
aws-s3-eu-west-3 unreachable-aws-s3-eu-west-3		100.0%
aws-s3-me-central-1 unreachable-aws-s3-me-central-1		100.0%
aws-s3-me-south-1 unreachable-aws-s3-me-south-1		100.0%
aws-s3-sa-east-1 unreachable-aws-s3-sa-east-1		100.0%
aws-s3-us-east-1 unreachable-aws-s3-us-east-1		100.0%
aws-s3-us-east-2 unreachable-aws-s3-us-east-2		100.0%
aws-s3-us-west-1 unreachable-aws-s3-us-west-1		100.0%
aws-s3-us-west-2 unreachable-aws-s3-us-west-2		100.0%

yul Montreal, Canada

	RTT	Loss	Actions
aws-s3-af-south-1 unreachable-aws-s3-af-south-1		100.0%
aws-s3-ap-east-1 unreachable-aws-s3-ap-east-1		100.0%
aws-s3-ap-northeast-1 unreachable-aws-s3-ap-northeast-1		100.0%
aws-s3-ap-northeast-2 unreachable-aws-s3-ap-northeast-2		100.0%
aws-s3-ap-northeast-3 unreachable-aws-s3-ap-northeast-3		100.0%
aws-s3-ap-south-1 unreachable-aws-s3-ap-south-1		100.0%
aws-s3-ap-south-2 unreachable-aws-s3-ap-south-2		100.0%
aws-s3-ap-southeast-1 unreachable-aws-s3-ap-southeast-1		100.0%
aws-s3-ap-southeast-2 unreachable-aws-s3-ap-southeast-2		100.0%
aws-s3-ap-southeast-3 unreachable-aws-s3-ap-southeast-3		100.0%
aws-s3-ap-southeast-4 unreachable-aws-s3-ap-southeast-4		100.0%
aws-s3-ca-central-1 unreachable-aws-s3-ca-central-1		100.0%
aws-s3-eu-central-1 unreachable-aws-s3-eu-central-1		100.0%
aws-s3-eu-central-2 unreachable-aws-s3-eu-central-2		100.0%
aws-s3-eu-north-1 unreachable-aws-s3-eu-north-1		100.0%
aws-s3-eu-south-1 unreachable-aws-s3-eu-south-1		100.0%
aws-s3-eu-south-2 unreachable-aws-s3-eu-south-2		100.0%
aws-s3-eu-west-1 unreachable-aws-s3-eu-west-1		100.0%
aws-s3-eu-west-2 unreachable-aws-s3-eu-west-2		100.0%
aws-s3-eu-west-3 unreachable-aws-s3-eu-west-3		100.0%
aws-s3-me-central-1 unreachable-aws-s3-me-central-1		100.0%
aws-s3-me-south-1 unreachable-aws-s3-me-south-1		100.0%
aws-s3-sa-east-1 unreachable-aws-s3-sa-east-1		100.0%
aws-s3-us-east-1 unreachable-aws-s3-us-east-1		100.0%
aws-s3-us-east-2 unreachable-aws-s3-us-east-2		100.0%
aws-s3-us-west-1 unreachable-aws-s3-us-west-1		100.0%
aws-s3-us-west-2 unreachable-aws-s3-us-west-2		100.0%

yyz Toronto, Canada

	RTT	Loss
aws-s3-ca-central-1 s3.ca-central-1.amazonaws.com	8ms	0.0%
aws-s3-us-east-2 s3.us-east-2.amazonaws.com	21ms	0.0%
aws-s3-us-east-1 s3.us-east-1.amazonaws.com	22ms	0.0%
aws-s3-us-west-1 s3.us-west-1.amazonaws.com	58ms	0.0%
aws-s3-us-west-2 s3.us-west-2.amazonaws.com	65ms	0.0%
aws-s3-eu-west-2 s3.eu-west-2.amazonaws.com	85ms	0.0%
aws-s3-eu-west-3 s3.eu-west-3.amazonaws.com	90ms	0.0%
aws-s3-eu-central-1 s3.eu-central-1.amazonaws.com	96ms	0.0%
aws-s3-eu-west-1 s3.eu-west-1.amazonaws.com	97ms	0.0%
aws-s3-eu-central-2 s3.eu-central-2.amazonaws.com	103ms	0.0%
aws-s3-eu-south-1 s3.eu-south-1.amazonaws.com	108ms	0.0%
aws-s3-eu-north-1 s3.eu-north-1.amazonaws.com	112ms	0.0%
aws-s3-eu-south-2 s3.eu-south-2.amazonaws.com	114ms	0.0%
aws-s3-sa-east-1 s3.sa-east-1.amazonaws.com	127ms	0.0%
aws-s3-ap-northeast-1 s3.ap-northeast-1.amazonaws.com	172ms	0.0%
aws-s3-me-south-1 s3.me-south-1.amazonaws.com	177ms	0.0%
aws-s3-ap-northeast-3 s3.ap-northeast-3.amazonaws.com	178ms	0.0%
aws-s3-ap-northeast-2 s3.ap-northeast-2.amazonaws.com	201ms	0.0%
aws-s3-ap-south-1 s3.ap-south-1.amazonaws.com	205ms	0.0%
aws-s3-me-central-1 s3.me-central-1.amazonaws.com	207ms	0.0%
aws-s3-ap-east-1 s3.ap-east-1.amazonaws.com	222ms	0.0%
aws-s3-ap-southeast-2 s3.ap-southeast-2.amazonaws.com	226ms	0.0%
aws-s3-ap-southeast-1 s3.ap-southeast-1.amazonaws.com	241ms	0.0%
aws-s3-ap-south-2 s3.ap-south-2.amazonaws.com	252ms	0.0%
aws-s3-ap-southeast-4 s3.ap-southeast-4.amazonaws.com	252ms	0.0%
aws-s3-af-south-1 s3.af-south-1.amazonaws.com	257ms	0.0%
aws-s3-ap-southeast-3 s3.ap-southeast-3.amazonaws.com	270ms	0.0%