Is Dynatrace AWS - Cluster 12 in APAC Southeast Sydney down?
Current Dynatrace AWS - Cluster 12 in APAC Southeast Sydney status is UP

We checked the official Dynatrace AWS - Cluster 12 in APAC Southeast Sydney Status Page 5 min. 0 sec. ago. Learn more
Having a problem? Help Allie Gator keep this page accurate!

Report an Issue

Stay informed of future downtime with dashboards and notifications

Recent Dynatrace AWS - Cluster 12 in APAC Southeast Sydney Outages and Issues

Follow the recent outages and downtime for Dynatrace AWS - Cluster 12 in APAC Southeast Sydney in the table below.

Start Time

Type

Length

Message

Details

March 14, 2024 03:10 UTC

WARN

ongoing

Potential Impact of Log Monitoring in LMv2

See more
Start Time

March 14, 2024 03:10 UTC

Type WARN
Affected Components

US East - Virginia - AWS - Cluster 1 in US East Virginia

US West - Oregon - AWS - Cluster 2 in US West Oregon

US East - Virginia - AWS - Cluster 3 in US East Virginia

EU West - Ireland - AWS - Cluster 4 in EU West Ireland

EU Central - Frankfurt - AWS - Cluster 79 in EU Central Frankfurt

AP South - Mumbai - AWS - Cluster 85 in AP South Mumbai

CA Central - Canada - AWS - Cluster 86 in CA Central Canada

AP Northeast - Tokyo - AWS - Cluster 87 in AP Northeast Tokyo

CA Central - Canada - AWS - Cluster 88 in CA Central Canada

East US - Virginia - Azure - Cluster 0 in US East Virginia

EU West - Ireland - AWS - Cluster 9 in EU West Ireland

US East - Virginia - AWS - Cluster 10 in US East Virginia

US East - Virginia - AWS - Cluster 11 in US East Virginia

AP Southeast - Sydney - AWS - Cluster 12 in APAC Southeast Sydney

EU West - Ireland - AWS - Cluster 13 in EU West Ireland

US East - Virginia - AWS - Cluster 14 in US East Virginia

US East - Virginia - AWS - Cluster 15 in US East Virginia

US West - Oregon - AWS - Cluster 16 in US West Oregon

US East - Virginia - AWS - Cluster 17 in US East Virginia

US West - Oregon - AWS - Cluster 18 in US West Oregon

US East - Virginia - AWS - Cluster 71 in US East Virginia

US East - Virginia - AWS - Cluster 72 in US East Virginia

US East - Virginia - AWS - Cluster 73 in US East Virginia

SA East - São Paulo - AWS - Cluster 74 in SA East São Paulo

US East - Virginia - AWS - Cluster 75 in US East Virginia

EU West - London - AWS - Cluster 77 in EU West London

AP Southeast - Singapore - AWS - Cluster 78 in APAC Southeast Singapore

AP Southeast - Sydney - AWS - Cluster 80 in APAC Southeast Sydney

US East - Virginia - AWS - Cluster 81 in US East Virginia

East US - Virginia - AWS - Cluster 82 in US East Virginia

US West - Oregon - AWS - Cluster 83 in US West Oregon

East US - Virginia - AWS - Cluster 84 in US East Virginia

East US - Virginia - Azure - Cluster 1 in US East Virginia

East US - Virginia - Azure - Cluster 2 in US East Virginia

West Europe - Netherlands - Azure - Cluster 3 in West Europe Netherlands

US West 3 - Arizona - Azure - Cluster 4 in US West 3 Arizona

CA Central - Canada - Azure - Cluster 5 in Canada Central

Switzerland North - Zurich - Azure - Cluster 7 in Switzerland North

East US - Virginia - Azure - Cluster 8 in US East Virginia

US East - Virginia - Azure - Cluster 9 in US East Virginia

US East4 - Virginia - GCP - Cluster 1 in US East4 Virginia

US East4 - Virginia - GCP - Cluster 3 in US East4 Virginia

US East4 - Virginia - GCP - Cluster 4 in US East4 Virginia

US East - Virginia - Dynatrace for Government

EU West - London - AWS - Cluster 76 in EU West London

UAE North - Azure - Cluster 6 in UAE North

AP Southeast - Sydney - AWS - Cluster 5 in APAC Southeast Sydney

US East - Virginia - AWS - Cluster 6 in US East Virginia

EU West - Ireland - AWS - Cluster 7 in EU West Ireland

US East - Virginia - AWS - Cluster 8 in US East Virginia

EUROPE West3 - Frankfurt - GCP - Cluster 2 in EUROPE West3 Frankfurt

Message

Potential Impact of Log Monitoring in LMv2

Details

We are actively working on the fix for Managed customers. The fix is expected to be released within the next 24 hours.

March 14, 2024 02:30 UTC

WARN

40 minutes

Potential Impact of Log Monitoring in LMv2

See more
Start Time

March 14, 2024 02:30 UTC

Type WARN
Affected Components

US East - Virginia - AWS - Cluster 1 in US East Virginia

US West - Oregon - AWS - Cluster 2 in US West Oregon

US East - Virginia - AWS - Cluster 3 in US East Virginia

EU West - Ireland - AWS - Cluster 4 in EU West Ireland

EU Central - Frankfurt - AWS - Cluster 46 in EU Central Frankfurt

EU West - London - AWS - Cluster 47 in EU West London

US East - Virginia - AWS - Cluster 57 in US East Virginia

EU West - Ireland - AWS - Cluster 58 in EU West Ireland

US West - Oregon - AWS - Cluster 59 in US West Oregon

EU Central - Frankfurt - AWS - Cluster 79 in EU Central Frankfurt

AP South - Mumbai - AWS - Cluster 85 in AP South Mumbai

CA Central - Canada - AWS - Cluster 86 in CA Central Canada

AP Northeast - Tokyo - AWS - Cluster 87 in AP Northeast Tokyo

CA Central - Canada - AWS - Cluster 88 in CA Central Canada

East US - Virginia - Azure - Cluster 0 in US East Virginia

Retain-AWS-asia-pacific - Dynatrace Product

Retain-Azure-americas - Dynatrace Product

US East - Virginia - AWS - Cluster 63 in US East Virginia

US East - Virginia - AWS - Cluster 64 in US East Virginia

EU West - Ireland - AWS - Cluster 65 in EU West Ireland

UAE North - Azure - Cluster 6 in UAE North

AP Southeast - Sydney - AWS - Cluster 5 in APAC Southeast Sydney

US East - Virginia - AWS - Cluster 6 in US East Virginia

EU West - Ireland - AWS - Cluster 7 in EU West Ireland

US East - Virginia - AWS - Cluster 8 in US East Virginia

EU West - Ireland - AWS - Cluster 9 in EU West Ireland

US East - Virginia - AWS - Cluster 10 in US East Virginia

US East - Virginia - AWS - Cluster 11 in US East Virginia

AP Southeast - Sydney - AWS - Cluster 12 in APAC Southeast Sydney

EU West - Ireland - AWS - Cluster 13 in EU West Ireland

US East - Virginia - AWS - Cluster 14 in US East Virginia

US East - Virginia - AWS - Cluster 15 in US East Virginia

US West - Oregon - AWS - Cluster 16 in US West Oregon

US East - Virginia - AWS - Cluster 17 in US East Virginia

US West - Oregon - AWS - Cluster 18 in US West Oregon

EU West - Ireland - AWS - Cluster 19 in EU West Ireland

EU West - Ireland - AWS - Cluster 20 in EU West Ireland

US East - Virginia - AWS - Cluster 21 in US East Virginia

US East - Virginia - AWS - Cluster 22 in US East Virginia

EU West - Ireland - AWS - Cluster 23 in EU West Ireland

US East - Virginia - AWS - Cluster 25 in US East Virginia

US East - Virginia - AWS - Cluster 26 in US East Virginia

US East - Virginia - AWS - Cluster 28 in US East Virginia

EU West - Ireland - AWS - Cluster 29 in EU West Ireland

US East - Virginia - AWS - Cluster 31 in US East Virginia

US East - Virginia - AWS - Cluster 32 in US East Virginia

EU West - Ireland - AWS - Cluster 33 in EU West Ireland

EU West - Ireland - AWS - Cluster 34 in EU West Ireland

US East - Virginia - AWS - Cluster 35 in US East Virginia

US East - Virginia - AWS - Cluster 36 in US East Virginia

US West - Oregon - AWS - Cluster 37 in US West Oregon

EU West - Ireland - AWS - Cluster 38 in EU West Ireland

US East - Virginia - AWS - Cluster 39 in US East Virginia

AP Southeast - Sydney - AWS - Cluster 40 in APAC Southeast Sydney

EU West - Ireland - AWS - Cluster 41 in EU West Ireland

US East - Virginia - AWS - Cluster 42 in US East Virginia

EU West - Ireland - AWS - Cluster 43 in EU West Ireland

US East - Virginia - AWS - Cluster 44 in US East Virginia

US East - Virginia - AWS - Cluster 45 in US East Virginia

US East - Virginia - AWS - Cluster 48 in US East Virginia

EU Central - Frankfurt - AWS - Cluster 49 in EU Central Frankfurt

US East - Virginia - AWS - Cluster 50 in US East Virginia

US East - Virginia - AWS - Cluster 51 in US East Virginia

AP Southeast - Sydney - AWS - Cluster 52 in APAC Southeast Sydney

US East - Virginia - AWS - Cluster 53 in US East Virginia

US East - Virginia - AWS - Cluster 56 in US East Virginia

US East - Virginia - AWS - Cluster 60 in US East Virginia

US East - Virginia - AWS - Cluster 61 in US East Virginia

US East - Virginia - AWS - Cluster 62 in US East Virginia

CA Central - Canada - AWS - Cluster 66 in CA Central Canada

US East - Virginia - AWS - Cluster 67 in US East Virginia

US East - Virginia - AWS - Cluster 68 in US East Virginia

CA Central - Canada - AWS - Cluster 69 in CA Central Canada

US East - Virginia - AWS - Cluster 70 in US East Virginia

US East - Virginia - AWS - Cluster 71 in US East Virginia

US East - Virginia - AWS - Cluster 72 in US East Virginia

US East - Virginia - AWS - Cluster 73 in US East Virginia

SA East - São Paulo - AWS - Cluster 74 in SA East São Paulo

US East - Virginia - AWS - Cluster 75 in US East Virginia

EU West - London - AWS - Cluster 76 in EU West London

EU West - London - AWS - Cluster 77 in EU West London

AP Southeast - Singapore - AWS - Cluster 78 in APAC Southeast Singapore

AP Southeast - Sydney - AWS - Cluster 80 in APAC Southeast Sydney

US East - Virginia - AWS - Cluster 81 in US East Virginia

East US - Virginia - AWS - Cluster 82 in US East Virginia

US West - Oregon - AWS - Cluster 83 in US West Oregon

East US - Virginia - AWS - Cluster 84 in US East Virginia

East US - Virginia - Azure - Cluster 1 in US East Virginia

East US - Virginia - Azure - Cluster 2 in US East Virginia

West Europe - Netherlands - Azure - Cluster 3 in West Europe Netherlands

US West 3 - Arizona - Azure - Cluster 4 in US West 3 Arizona

CA Central - Canada - Azure - Cluster 5 in Canada Central

Switzerland North - Zurich - Azure - Cluster 7 in Switzerland North

East US - Virginia - Azure - Cluster 8 in US East Virginia

US East - Virginia - Azure - Cluster 9 in US East Virginia

US East4 - Virginia - GCP - Cluster 1 in US East4 Virginia

US East4 - Virginia - GCP - Cluster 3 in US East4 Virginia

US East4 - Virginia - GCP - Cluster 4 in US East4 Virginia

US East - Virginia - Dynatrace for Government

Retain-AWS-americas - Dynatrace Product

Retain-AWS-europe - Dynatrace Product

Retain-Azure-europe - Dynatrace Product

Retain-Azure-asia-pacific - Dynatrace Product

Retain-GCP-americas - Dynatrace Product

Retain-GCP-europe - Dynatrace Product

Retain-GCP-asia-pacific - Dynatrace Product

US West - Oregon - AWS - Cluster 24 in US West Oregon

AP Southeast - Sydney - AWS - Cluster 27 in APAC Southeast Sydney

EU West - Ireland - AWS - Cluster 30 in EU West Ireland

EUROPE West3 - Frankfurt - GCP - Cluster 2 in EUROPE West3 Frankfurt

US East - Virginia - AWS - Cluster 54 in US East Virginia

Message

Potential Impact of Log Monitoring in LMv2

Details

We are actively working on the fix for Managed customers. The fix is expected to be released within the next 24 hours.

March 13, 2024 13:50 UTC

WARN

about 13 hours

Potential Impact of Log Monitoring in LMv2

See more
Start Time

March 13, 2024 13:50 UTC

Type WARN
Affected Components

US East - Virginia - AWS - Cluster 1 in US East Virginia

US West - Oregon - AWS - Cluster 2 in US West Oregon

US East - Virginia - AWS - Cluster 3 in US East Virginia

EU West - Ireland - AWS - Cluster 4 in EU West Ireland

AP Southeast - Sydney - AWS - Cluster 5 in APAC Southeast Sydney

US East - Virginia - AWS - Cluster 6 in US East Virginia

EU West - Ireland - AWS - Cluster 7 in EU West Ireland

US East - Virginia - AWS - Cluster 8 in US East Virginia

EU West - Ireland - AWS - Cluster 9 in EU West Ireland

US East - Virginia - AWS - Cluster 10 in US East Virginia

US East - Virginia - AWS - Cluster 11 in US East Virginia

AP Southeast - Sydney - AWS - Cluster 12 in APAC Southeast Sydney

EU West - Ireland - AWS - Cluster 13 in EU West Ireland

US East - Virginia - AWS - Cluster 14 in US East Virginia

US East - Virginia - AWS - Cluster 15 in US East Virginia

US West - Oregon - AWS - Cluster 16 in US West Oregon

US East - Virginia - AWS - Cluster 17 in US East Virginia

US West - Oregon - AWS - Cluster 18 in US West Oregon

EU West - Ireland - AWS - Cluster 19 in EU West Ireland

EU West - Ireland - AWS - Cluster 20 in EU West Ireland

US East - Virginia - AWS - Cluster 21 in US East Virginia

US East - Virginia - AWS - Cluster 22 in US East Virginia

EU West - Ireland - AWS - Cluster 23 in EU West Ireland

US East - Virginia - AWS - Cluster 25 in US East Virginia

US East - Virginia - AWS - Cluster 26 in US East Virginia

US East - Virginia - AWS - Cluster 28 in US East Virginia

US East - Virginia - AWS - Cluster 31 in US East Virginia

US East - Virginia - AWS - Cluster 32 in US East Virginia

EU West - Ireland - AWS - Cluster 33 in EU West Ireland

EU West - Ireland - AWS - Cluster 34 in EU West Ireland

US East - Virginia - AWS - Cluster 35 in US East Virginia

US East - Virginia - AWS - Cluster 36 in US East Virginia

US West - Oregon - AWS - Cluster 37 in US West Oregon

EU West - Ireland - AWS - Cluster 38 in EU West Ireland

US East - Virginia - AWS - Cluster 39 in US East Virginia

AP Southeast - Sydney - AWS - Cluster 40 in APAC Southeast Sydney

EU West - Ireland - AWS - Cluster 41 in EU West Ireland

US East - Virginia - AWS - Cluster 42 in US East Virginia

EU West - Ireland - AWS - Cluster 43 in EU West Ireland

US East - Virginia - AWS - Cluster 44 in US East Virginia

US East - Virginia - AWS - Cluster 45 in US East Virginia

EU Central - Frankfurt - AWS - Cluster 46 in EU Central Frankfurt

EU West - London - AWS - Cluster 47 in EU West London

US East - Virginia - AWS - Cluster 48 in US East Virginia

EU Central - Frankfurt - AWS - Cluster 49 in EU Central Frankfurt

US East - Virginia - AWS - Cluster 50 in US East Virginia

US East - Virginia - AWS - Cluster 51 in US East Virginia

AP Southeast - Sydney - AWS - Cluster 52 in APAC Southeast Sydney

US East - Virginia - AWS - Cluster 53 in US East Virginia

US East - Virginia - AWS - Cluster 56 in US East Virginia

US East - Virginia - AWS - Cluster 57 in US East Virginia

EU West - Ireland - AWS - Cluster 58 in EU West Ireland

US West - Oregon - AWS - Cluster 59 in US West Oregon

US East - Virginia - AWS - Cluster 61 in US East Virginia

US East - Virginia - AWS - Cluster 62 in US East Virginia

US East - Virginia - AWS - Cluster 63 in US East Virginia

US East - Virginia - AWS - Cluster 64 in US East Virginia

EU West - Ireland - AWS - Cluster 65 in EU West Ireland

CA Central - Canada - AWS - Cluster 66 in CA Central Canada

CA Central - Canada - AWS - Cluster 69 in CA Central Canada

US East - Virginia - AWS - Cluster 70 in US East Virginia

US East - Virginia - AWS - Cluster 71 in US East Virginia

US East - Virginia - AWS - Cluster 72 in US East Virginia

US East - Virginia - AWS - Cluster 73 in US East Virginia

SA East - São Paulo - AWS - Cluster 74 in SA East São Paulo

US East - Virginia - AWS - Cluster 75 in US East Virginia

EU West - London - AWS - Cluster 76 in EU West London

EU West - London - AWS - Cluster 77 in EU West London

EU Central - Frankfurt - AWS - Cluster 79 in EU Central Frankfurt

East US - Virginia - AWS - Cluster 82 in US East Virginia

US West - Oregon - AWS - Cluster 83 in US West Oregon

East US - Virginia - AWS - Cluster 84 in US East Virginia

AP South - Mumbai - AWS - Cluster 85 in AP South Mumbai

CA Central - Canada - AWS - Cluster 86 in CA Central Canada

AP Northeast - Tokyo - AWS - Cluster 87 in AP Northeast Tokyo

CA Central - Canada - AWS - Cluster 88 in CA Central Canada

East US - Virginia - Azure - Cluster 0 in US East Virginia

East US - Virginia - Azure - Cluster 1 in US East Virginia

East US - Virginia - Azure - Cluster 2 in US East Virginia

US West 3 - Arizona - Azure - Cluster 4 in US West 3 Arizona

CA Central - Canada - Azure - Cluster 5 in Canada Central

UAE North - Azure - Cluster 6 in UAE North

East US - Virginia - Azure - Cluster 8 in US East Virginia

US East - Virginia - Azure - Cluster 9 in US East Virginia

US East4 - Virginia - GCP - Cluster 1 in US East4 Virginia

US East4 - Virginia - GCP - Cluster 3 in US East4 Virginia

US East4 - Virginia - GCP - Cluster 4 in US East4 Virginia

US East - Virginia - Dynatrace for Government

Retain-AWS-americas - Dynatrace Product

Retain-AWS-europe - Dynatrace Product

Retain-AWS-asia-pacific - Dynatrace Product

Retain-Azure-americas - Dynatrace Product

Retain-Azure-europe - Dynatrace Product

Retain-Azure-asia-pacific - Dynatrace Product

Retain-GCP-americas - Dynatrace Product

Retain-GCP-europe - Dynatrace Product

Retain-GCP-asia-pacific - Dynatrace Product

US East - Virginia - AWS - Cluster 67 in US East Virginia

US East - Virginia - AWS - Cluster 68 in US East Virginia

AP Southeast - Singapore - AWS - Cluster 78 in APAC Southeast Singapore

AP Southeast - Sydney - AWS - Cluster 80 in APAC Southeast Sydney

US East - Virginia - AWS - Cluster 81 in US East Virginia

West Europe - Netherlands - Azure - Cluster 3 in West Europe Netherlands

US East - Virginia - AWS - Cluster 60 in US East Virginia

US West - Oregon - AWS - Cluster 24 in US West Oregon

AP Southeast - Sydney - AWS - Cluster 27 in APAC Southeast Sydney

EU West - Ireland - AWS - Cluster 30 in EU West Ireland

EUROPE West3 - Frankfurt - GCP - Cluster 2 in EUROPE West3 Frankfurt

EU West - Ireland - AWS - Cluster 29 in EU West Ireland

US East - Virginia - AWS - Cluster 54 in US East Virginia

Switzerland North - Zurich - Azure - Cluster 7 in Switzerland North

Message

Potential Impact of Log Monitoring in LMv2

Details

A fix has been released to all SaaS tenants. A workaround for Manager clusters is available and a fix will be released for Managed customers shortly.

March 11, 2024 13:00 UTC

WARN

2 days

Potential Impact of Log Monitoring in LMv2

See more
Start Time

March 11, 2024 13:00 UTC

Type WARN
Affected Components

West Europe - Netherlands - Azure - Cluster 3 in West Europe Netherlands

US East - Virginia - AWS - Cluster 60 in US East Virginia

US East - Virginia - AWS - Cluster 70 in US East Virginia

CA Central - Canada - AWS - Cluster 86 in CA Central Canada

CA Central - Canada - AWS - Cluster 69 in CA Central Canada

US East - Virginia - AWS - Cluster 71 in US East Virginia

US East - Virginia - AWS - Cluster 72 in US East Virginia

US East - Virginia - AWS - Cluster 53 in US East Virginia

US East - Virginia - AWS - Cluster 56 in US East Virginia

US East - Virginia - AWS - Cluster 6 in US East Virginia

EU West - Ireland - AWS - Cluster 7 in EU West Ireland

US East - Virginia - AWS - Cluster 8 in US East Virginia

EU West - Ireland - AWS - Cluster 9 in EU West Ireland

EU West - Ireland - AWS - Cluster 13 in EU West Ireland

US East - Virginia - AWS - Cluster 14 in US East Virginia

US East - Virginia - AWS - Cluster 15 in US East Virginia

US West - Oregon - AWS - Cluster 16 in US West Oregon

US East - Virginia - AWS - Cluster 17 in US East Virginia

US West - Oregon - AWS - Cluster 18 in US West Oregon

EU West - Ireland - AWS - Cluster 19 in EU West Ireland

EU West - Ireland - AWS - Cluster 20 in EU West Ireland

US East - Virginia - AWS - Cluster 21 in US East Virginia

US East - Virginia - AWS - Cluster 26 in US East Virginia

AP Southeast - Sydney - AWS - Cluster 27 in APAC Southeast Sydney

US East - Virginia - AWS - Cluster 28 in US East Virginia

EU West - Ireland - AWS - Cluster 30 in EU West Ireland

US East - Virginia - AWS - Cluster 31 in US East Virginia

US East - Virginia - AWS - Cluster 32 in US East Virginia

EU West - Ireland - AWS - Cluster 34 in EU West Ireland

US East - Virginia - AWS - Cluster 35 in US East Virginia

US East - Virginia - AWS - Cluster 36 in US East Virginia

US West - Oregon - AWS - Cluster 37 in US West Oregon

EU West - Ireland - AWS - Cluster 38 in EU West Ireland

US East - Virginia - AWS - Cluster 39 in US East Virginia

AP Southeast - Sydney - AWS - Cluster 40 in APAC Southeast Sydney

EU West - Ireland - AWS - Cluster 41 in EU West Ireland

US East - Virginia - AWS - Cluster 42 in US East Virginia

EU West - Ireland - AWS - Cluster 43 in EU West Ireland

US East - Virginia - AWS - Cluster 44 in US East Virginia

US East - Virginia - AWS - Cluster 45 in US East Virginia

EU Central - Frankfurt - AWS - Cluster 46 in EU Central Frankfurt

EU West - London - AWS - Cluster 47 in EU West London

US East - Virginia - AWS - Cluster 48 in US East Virginia

EU Central - Frankfurt - AWS - Cluster 49 in EU Central Frankfurt

US East - Virginia - AWS - Cluster 51 in US East Virginia

AP Southeast - Sydney - AWS - Cluster 52 in APAC Southeast Sydney

US East - Virginia - AWS - Cluster 57 in US East Virginia

US West - Oregon - AWS - Cluster 59 in US West Oregon

US East - Virginia - AWS - Cluster 62 in US East Virginia

US East - Virginia - AWS - Cluster 63 in US East Virginia

US East - Virginia - AWS - Cluster 64 in US East Virginia

EU West - Ireland - AWS - Cluster 65 in EU West Ireland

CA Central - Canada - AWS - Cluster 66 in CA Central Canada

US East - Virginia - AWS - Cluster 67 in US East Virginia

US East - Virginia - AWS - Cluster 68 in US East Virginia

US East - Virginia - AWS - Cluster 73 in US East Virginia

SA East - São Paulo - AWS - Cluster 74 in SA East São Paulo

US East - Virginia - AWS - Cluster 75 in US East Virginia

EU West - London - AWS - Cluster 77 in EU West London

AP Southeast - Singapore - AWS - Cluster 78 in APAC Southeast Singapore

US East - Virginia - AWS - Cluster 81 in US East Virginia

East US - Virginia - AWS - Cluster 82 in US East Virginia

US West - Oregon - AWS - Cluster 83 in US West Oregon

East US - Virginia - AWS - Cluster 84 in US East Virginia

AP South - Mumbai - AWS - Cluster 85 in AP South Mumbai

AP Northeast - Tokyo - AWS - Cluster 87 in AP Northeast Tokyo

CA Central - Canada - AWS - Cluster 88 in CA Central Canada

East US - Virginia - Azure - Cluster 0 in US East Virginia

East US - Virginia - Azure - Cluster 1 in US East Virginia

East US - Virginia - Azure - Cluster 2 in US East Virginia

US West 3 - Arizona - Azure - Cluster 4 in US West 3 Arizona

CA Central - Canada - Azure - Cluster 5 in Canada Central

UAE North - Azure - Cluster 6 in UAE North

Switzerland North - Zurich - Azure - Cluster 7 in Switzerland North

East US - Virginia - Azure - Cluster 8 in US East Virginia

US East - Virginia - Azure - Cluster 9 in US East Virginia

US East4 - Virginia - GCP - Cluster 1 in US East4 Virginia

EUROPE West3 - Frankfurt - GCP - Cluster 2 in EUROPE West3 Frankfurt

US East4 - Virginia - GCP - Cluster 3 in US East4 Virginia

US East4 - Virginia - GCP - Cluster 4 in US East4 Virginia

US East - Virginia - Dynatrace for Government

Retain-AWS-americas - Dynatrace Product

Retain-AWS-europe - Dynatrace Product

Retain-AWS-asia-pacific - Dynatrace Product

Retain-Azure-americas - Dynatrace Product

Retain-Azure-europe - Dynatrace Product

Retain-Azure-asia-pacific - Dynatrace Product

Retain-GCP-americas - Dynatrace Product

Retain-GCP-europe - Dynatrace Product

Retain-GCP-asia-pacific - Dynatrace Product

Dynatrace Managed - Dynatrace ecosystem services

US East - Virginia - AWS - Cluster 11 in US East Virginia

AP Southeast - Sydney - AWS - Cluster 12 in APAC Southeast Sydney

EU West - Ireland - AWS - Cluster 29 in EU West Ireland

US East - Virginia - AWS - Cluster 10 in US East Virginia

US East - Virginia - AWS - Cluster 22 in US East Virginia

EU West - Ireland - AWS - Cluster 23 in EU West Ireland

US West - Oregon - AWS - Cluster 24 in US West Oregon

US East - Virginia - AWS - Cluster 25 in US East Virginia

EU West - Ireland - AWS - Cluster 33 in EU West Ireland

US East - Virginia - AWS - Cluster 50 in US East Virginia

US East - Virginia - AWS - Cluster 54 in US East Virginia

US East - Virginia - AWS - Cluster 61 in US East Virginia

EU West - London - AWS - Cluster 76 in EU West London

EU Central - Frankfurt - AWS - Cluster 79 in EU Central Frankfurt

AP Southeast - Sydney - AWS - Cluster 80 in APAC Southeast Sydney

EU West - Ireland - AWS - Cluster 58 in EU West Ireland

US East - Virginia - AWS - Cluster 1 in US East Virginia

US West - Oregon - AWS - Cluster 2 in US West Oregon

US East - Virginia - AWS - Cluster 3 in US East Virginia

EU West - Ireland - AWS - Cluster 4 in EU West Ireland

AP Southeast - Sydney - AWS - Cluster 5 in APAC Southeast Sydney

Message

Potential Impact of Log Monitoring in LMv2

Details

This impacts Managed customers on version 1.286 and utilizing LMv2, as well as SaaS tenants utilizing LMv2. In the event a blank log is ingested the entire batch of log lines could potentially be rejected.

June 13, 2023 15:45 UTC

WARN

about 7 hours

In-Product Messaging application is currently unavailable

See more
Start Time

June 13, 2023 15:45 UTC

Type WARN
Affected Components

US West - Oregon - AWS - Cluster 2 in US West Oregon

US East - Virginia - AWS - Cluster 45 in US East Virginia

US East - Virginia - AWS - Cluster 6 in US East Virginia

US East - Virginia - AWS - Cluster 11 in US East Virginia

APAC Southeast - Sydney - AWS - Cluster 12 in APAC Southeast Sydney

EU West - Ireland - AWS - Cluster 13 in EU West Ireland

EU Central - Frankfurt - AWS - Cluster 49 in EU Central Frankfurt

US East - Virginia - AWS - Cluster 57 in US East Virginia

EU West - Ireland - AWS - Cluster 58 in EU West Ireland

US West - Oregon - AWS - Cluster 59 in US West Oregon

US East - Virginia - AWS - Cluster 60 in US East Virginia

CA Central - Canada - AWS - Cluster 69 in CA Central Canada

SA East - São Paulo - AWS - Cluster 74 in SA East São Paulo

US East - Virginia - AWS - Cluster 75 in US East Virginia

East US - Virginia - Azure - Cluster 0 in US East Virginia

East US - Virginia - Azure - Cluster 1 in US East Virginia

East US - Virginia - Azure - Cluster 2 in US East Virginia

West Europe - Netherlands - Azure - Cluster 3 in West Europe Netherlands

US West 3 - Arizona - Azure - Cluster 4 in US West 3 Arizona

CA Central - Canada - Azure - Cluster 5 in Canada Central

US East4 - Virginia - GCP - Cluster 1 in US East4 Virginia

EUROPE West3 - Frankfurt - GCP - Cluster 2 in EUROPE West3 Frankfurt

US East4 - Virginia - GCP - Cluster 3 in US East4 Virginia

US East - Virginia - Website: dynatrace.com

CA Central - Canada - AWS - Cluster 66 in CA Central Canada

US East - Virginia - AWS - Cluster 1 in US East Virginia

US East - Virginia - AWS - Cluster 3 in US East Virginia

EU West - Ireland - AWS - Cluster 4 in EU West Ireland

APAC Southeast - Sydney - AWS - Cluster 5 in APAC Southeast Sydney

EU West - Ireland - AWS - Cluster 7 in EU West Ireland

US East - Virginia - AWS - Cluster 8 in US East Virginia

EU West - Ireland - AWS - Cluster 9 in EU West Ireland

US East - Virginia - AWS - Cluster 10 in US East Virginia

US East - Virginia - AWS - Cluster 14 in US East Virginia

US East - Virginia - AWS - Cluster 15 in US East Virginia

US West - Oregon - AWS - Cluster 16 in US West Oregon

US East - Virginia - AWS - Cluster 17 in US East Virginia

US West - Oregon - AWS - Cluster 18 in US West Oregon

EU West - Ireland - AWS - Cluster 19 in EU West Ireland

EU West - Ireland - AWS - Cluster 20 in EU West Ireland

US East - Virginia - AWS - Cluster 21 in US East Virginia

US East - Virginia - AWS - Cluster 22 in US East Virginia

EU West - Ireland - AWS - Cluster 23 in EU West Ireland

US West - Oregon - AWS - Cluster 24 in US West Oregon

US East - Virginia - AWS - Cluster 25 in US East Virginia

US East - Virginia - AWS - Cluster 26 in US East Virginia

APAC Southeast - Sydney - AWS - Cluster 27 in APAC Southeast Sydney

US East - Virginia - AWS - Cluster 28 in US East Virginia

EU West - Ireland - AWS - Cluster 29 in EU West Ireland

EU West - Ireland - AWS - Cluster 30 in EU West Ireland

US East - Virginia - AWS - Cluster 31 in US East Virginia

US East - Virginia - AWS - Cluster 32 in US East Virginia

EU West - Ireland - AWS - Cluster 33 in EU West Ireland

EU West - Ireland - AWS - Cluster 34 in EU West Ireland

US East - Virginia - AWS - Cluster 35 in US East Virginia

US East - Virginia - AWS - Cluster 36 in US East Virginia

US West - Oregon - AWS - Cluster 37 in US West Oregon

EU West - Ireland - AWS - Cluster 38 in EU West Ireland

US East - Virginia - AWS - Cluster 39 in US East Virginia

APAC Southeast - Sydney - AWS - Cluster 40 in APAC Southeast Sydney

EU West - Ireland - AWS - Cluster 41 in EU West Ireland

US East - Virginia - AWS - Cluster 42 in US East Virginia

EU West - Ireland - AWS - Cluster 43 in EU West Ireland

US East - Virginia - AWS - Cluster 44 in US East Virginia

EU Central - Frankfurt - AWS - Cluster 46 in EU Central Frankfurt

EU West - London - AWS - Cluster 47 in EU West London

US East - Virginia - AWS - Cluster 48 in US East Virginia

US East - Virginia - AWS - Cluster 50 in US East Virginia

US East - Virginia - AWS - Cluster 51 in US East Virginia

APAC Southeast - Sydney - AWS - Cluster 52 in APAC Southeast Sydney

US East - Virginia - AWS - Cluster 53 in US East Virginia

US East - Virginia - AWS - Cluster 54 in US East Virginia

US East - Virginia - AWS - Cluster 56 in US East Virginia

US East - Virginia - AWS - Cluster 61 in US East Virginia

US East - Virginia - AWS - Cluster 62 in US East Virginia

US East - Virginia - AWS - Cluster 63 in US East Virginia

US East - Virginia - AWS - Cluster 64 in US East Virginia

EU West - Ireland - AWS - Cluster 65 in EU West Ireland

US East - Virginia - AWS - Cluster 67 in US East Virginia

US East - Virginia - AWS - Cluster 68 in US East Virginia

US East - Virginia - AWS - Cluster 70 in US East Virginia

US East - Virginia - AWS - Cluster 71 in US East Virginia

US East - Virginia - AWS - Cluster 72 in US East Virginia

US East - Virginia - AWS - Cluster 73 in US East Virginia

EU West - London - AWS - Cluster 76 in EU West London

EU West - London - AWS - Cluster 77 in EU West London

APAC Southeast - Singapore - AWS - Cluster 78 in APAC Southeast Singapore

EU Central - Frankfurt - AWS - Cluster 79 in EU Central Frankfurt

APAC Southeast - Sydney - AWS - Cluster 80 in APAC Southeast Sydney

US East - Virginia - AWS - Cluster 81 in US East Virginia

East US - Virginia - AWS - Cluster 82 in US East Virginia

US West - Oregon - AWS - Cluster 83 in US West Oregon

UAE North - Azure - Cluster 6 in UAE North

Zurich (Azure) - Azure - Cluster 7 in Switzerland North

Message

In-Product Messaging application is currently unavailable

Details

We are aware of a current issue with our in-product messaging being unavailable to customers. You may experience a loading screen within the widget that fails to fully load.

We are working to identify the root cause and will continue to update as new information becomes available. We apologize for the inconvenience.

2024-03-15 09:41:09 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-03-15 09:41:09 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-03-15 09:41:09 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-03-15 09:41:09 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-03-15 09:41:09 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

Sign Up for More Dynatrace AWS - Cluster 12 in APAC Southeast Sydney History

StatusGator has about 4 years of Dynatrace AWS - Cluster 12 in APAC Southeast Sydney status history.

No outages or status changes in the last 24 hours

Dynatrace AWS - Cluster 12 in APAC Southeast Sydney status, last 24 hours:

10:00 AM
4:00 PM
10:00 PM
4:00 AM
10:00 AM
10:00 AM
10:00 PM
10:00 AM
  • Up: 24 hours

  • Warn: 0 minutes

  • Down: 0 minutes

  • Maintenance: 0 minutes

Dynatrace AWS - Cluster 12 in APAC Southeast Sydney Outage and Status History

We've been monitoring Dynatrace AWS - Cluster 12 in APAC Southeast Sydney outages since February 19, 2020.
Here's the history of service outages we've observed from the Dynatrace AWS - Cluster 12 in APAC Southeast Sydney Status Page:

  • Up

  • Warn

  • Down

  • Maintenance

Instant enriched data from
3,570 status pages

About Our Dynatrace AWS - Cluster 12 in APAC Southeast Sydney Status Page Integration

Dynatrace AWS - Cluster 12 in APAC Southeast Sydney is a Cloud Infrastructure solution that StatusGator has been monitoring since February 2020. Over the past about 4 years, we have collected data on on more than 220 outages that affected Dynatrace AWS - Cluster 12 in APAC Southeast Sydney users. When Dynatrace AWS - Cluster 12 in APAC Southeast Sydney publishes downtime on their status page, they do so across 176 components and 63 groups using 4 different statuses: up, warn, down, and maintenance which we use to provide granular uptime metrics and notifications.

Many StatusGator users monitor Dynatrace AWS - Cluster 12 in APAC Southeast Sydney to get notified when it's down, is under maintenance, or has an outage. We've sent more than 800 notifications to our users about Dynatrace AWS - Cluster 12 in APAC Southeast Sydney incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.

If Dynatrace AWS - Cluster 12 in APAC Southeast Sydney is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.

Warn notifications are used when Dynatrace AWS - Cluster 12 in APAC Southeast Sydney is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.

Dynatrace AWS - Cluster 12 in APAC Southeast Sydney posts separate notifications for planned maintenance work. StatusGator will notify subscribers when Dynatrace AWS - Cluster 12 in APAC Southeast Sydney enters a pre-planned maintenance window, keeping you up to date.

Dynatrace AWS - Cluster 12 in APAC Southeast Sydney does not publish a feed of proactive maintenance events on their status page at this time. If they do, be sure to let us know and we'll aggregate Dynatrace AWS - Cluster 12 in APAC Southeast Sydney maintenance events into your unified calendar.

When Dynatrace AWS - Cluster 12 in APAC Southeast Sydney posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.

When Dynatrace AWS - Cluster 12 in APAC Southeast Sydney has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.

Because Dynatrace AWS - Cluster 12 in APAC Southeast Sydney has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.

Frequently Asked Questions

Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!

Dynatrace AWS - Cluster 12 in APAC Southeast Sydney Down?

Are you experiencing issues with Dynatrace AWS - Cluster 12 in APAC Southeast Sydney? Sign up to receive notifications when Dynatrace AWS - Cluster 12 in APAC Southeast Sydney publishes outages.

Dynatrace AWS - Cluster 12 in APAC Southeast Sydney Down or not working? Never be taken by surprise again.

StatusGator tells you when your cloud services have problems or their statuses change. We monitor the official status pages of more than 3,570 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more.

Looking for recent downtime and outages of Dynatrace AWS - Cluster 12 in APAC Southeast Sydney?

Sign up for StatusGator and see all historical information about Dynatrace AWS - Cluster 12 in APAC Southeast Sydney outages and performance issues. Get free, instant notifications when Dynatrace AWS - Cluster 12 in APAC Southeast Sydney goes down.