Is Temporal Down Right Now? Check if there is a current outage ongoing.

Temporal is currently Operational

Last checked 2025-06-14T13:29:48.150Z from Temporal's official status page

Historical record of incidents for Temporal

Jun 12, 2025

Report: "External metrics outage"

Last update 2025-06-12T18:29:51.712Z

investigating2025-06-12T18:29:51.708Z

Users ingesting metrics via Temporal Cloud's metrics endpoint will see no data

Report: "Investigating issue for namespaces in GCP regions"

Last update 2025-06-12T18:22:40.409Z

investigating2025-06-12T18:22:40.406Z

We are currently investigating this issue.

Jun 11, 2025

Report: "Some customers in AWS regions may experience delays in visibility task processing"

Last update 2025-06-11T20:28:27.899Z

investigating2025-06-11T20:28:27.896Z

We are currently investigating this issue. Workflow execution is unaffected.

Jun 2, 2025

Report: "Audit log delivery delayed"

Last update 2025-06-02T16:42:52.276Z

resolved2025-06-02T16:42:52.261Z

This incident has been resolved.

identified2025-06-02T15:27:42.845Z

The delivery of audit logs for cloud events stopped publishing at 2025-05-30T17:54:00Z. The problem has been identified and a fix is actively being deployed. Once deployed, all events will be backfilled.

Report: "Audit log delivery delayed"

Last update 2025-06-02T11:42:00.000Z

Resolved2025-06-02T11:42:00.000Z

This incident has been resolved.

Identified2025-06-02T10:27:00.000Z

May 29, 2025

Report: "Some customers in ap-south-2 (AWS) may experience elevated API latencies"

Last update 2025-05-29T18:01:59.231Z

resolved2025-05-29T18:01:59.214Z

This incident has been resolved.

identified2025-05-29T17:39:02.691Z

A network issue has been identified by the cloud provider that is actively being investigated.

Report: "Some customers in ap-south-2 (AWS) may experience elevated API latencies"

Last update 2025-05-29T13:01:00.000Z

Resolved2025-05-29T13:01:00.000Z

This incident has been resolved.

Identified2025-05-29T12:39:00.000Z

A network issue has been identified by the cloud provider that is actively being investigated.

May 17, 2025

Report: "New Customer Onboarding Issue"

Last update 2025-05-17T01:05:16.521Z

resolved2025-05-17T01:05:16.495Z

The issue is fixed. New customers should be able to onboard without a problem.

identified2025-05-16T21:58:24.955Z

New customers may experience temporary delays signing up for Temporal Cloud.

May 15, 2025

Report: "Services running hot in US-E-1"

Last update 2025-05-15T16:12:25.490Z

resolved2025-05-15T16:12:25.474Z

Note that the system had no errors; this was due to pure demand spike. Performance has returned to nominal levels, we will watch carefully as always.

investigating2025-05-15T16:04:39.638Z

We have added capacity, performance has improved, and we are continuing to monitor.

investigating2025-05-15T15:47:01.825Z

Some customers may experience higher-than-usual latencies

May 9, 2025

Report: "New customer onboarding issue"

Last update 2025-05-09T00:29:36.475Z

resolved2025-05-09T00:29:36.458Z

This incident has been resolved.

identified2025-05-08T23:15:35.245Z

The issue has been identified and a fix is being implemented.

investigating2025-05-08T22:29:19.114Z

The new customer onboarding has some issue.

Apr 23, 2025

Report: "Some customers in us-east-1 (AWS) may experience elevated API latencies"

Last update 2025-04-23T19:05:12.695Z

resolved2025-04-23T01:08:29.000Z

This incident has been resolved.

investigating2025-04-23T01:07:10.366Z

We have resolved the original source of this problem, and are working to isolate the workflows involved, and will be contacting any affected customers with more specific information.

investigating2025-04-23T00:35:36.141Z

In addition, we currently believe a small number of workflows may be stuck. Research is ongoing.

investigating2025-04-23T00:01:38.270Z

We are currently investigating this issue.

Apr 14, 2025

Report: "Customers are experiencing issues logging into Temporal Cloud UI"

Last update 2025-04-14T22:56:06.352Z

resolved2025-04-14T22:56:06.336Z

This incident has been resolved.

monitoring2025-04-14T22:51:33.378Z

A fix has been implemented and we are monitoring the results.

identified2025-04-14T22:32:22.730Z

This is due to our downstream provider Auth0: https://status.auth0.com/incidents We are working closely with them to get updates and mitigate this issue

investigating2025-04-14T22:15:17.744Z

We are currently investigating this issue.

Apr 9, 2025

Report: "Some customers in us-east-1 (AWS) may experience elevated API latencies"

Last update 2025-04-09T19:17:06.763Z

resolved2025-04-09T19:17:06.748Z

This incident has been resolved.

identified2025-04-09T16:36:11.072Z

Some customers in us-east-1 (AWS) may experience elevated API latencies.

Apr 8, 2025

Report: "Customers in AWS eu-west-1 may experience elevated latencies and error rates"

Last update 2025-04-08T14:30:23.554Z

postmortem2025-04-08T13:46:06.229Z

On April 4th, 2025, Temporal Cloud in AWS eu-west-1 experienced a service outage from 1647 UTC to 1717 UTC. During this 30 minute window all customers of this region saw high API latencies and a peak gRPC error rate of 87%. The root cause was a latent internal TLS configuration change that had previous rolled out to the cell, with the trigger being an unrelated History service restart during a WAL rollout. As each History service restarted more and more of the overall service pool was unable to connect to the WAL and cell performance and availability deteriorated. The issue was mitigated by reverting the latent configuration change. After which we identified the sequence of events which lead to the configuration change laying dormant instead of being immediately applied and have instituted process improvements to prevent it from happening in the future.

resolved2025-04-04T17:20:03.184Z

This incident has been resolved.

investigating2025-04-04T16:59:37.339Z

Some customers in AWS eu-west-1 may experience elevated API latencies

Report: "Some customers in AWS ap-south-1 may experience elevated latencies and error rates"

Last update 2025-04-08T14:27:15.425Z

resolved2025-03-27T14:03:57.714Z

This incident has been resolved.

monitoring2025-03-27T13:49:58.265Z

The fix has been rolled out and we are seeing recoveries to latencies/errors

identified2025-03-27T13:19:48.311Z

The hotfix is currently being rolled out to the impacted cluster

identified2025-03-27T13:08:58.641Z

The issue has been identified and a fix is being implemented.

investigating2025-03-27T13:08:43.448Z

We are continuing to investigate this issue.

investigating2025-03-27T12:55:49.708Z

We are currently investigating this issue

Report: "Some customers may experience errors when attempting to log in to cloud.temporal.io"

Last update 2025-04-08T14:24:27.895Z

resolved2025-04-01T20:51:55.549Z

This incident has been resolved.

investigating2025-04-01T20:39:55.249Z

Some users may experience errors when attempting to log in to cloud.temporal.io

Report: "Some customers in AWS us-west-2 may experience elevated visibility persistence latencies"

Last update 2025-04-08T14:23:59.681Z

resolved2025-04-02T02:25:41.862Z

This incident has been resolved.

investigating2025-04-02T01:52:29.548Z

We are continuing to investigate this issue.

investigating2025-04-02T01:50:02.809Z

Some customers in aws us-west-2 may experience elevated visibility persistence latencies.

Report: "Some customers in AWS us-west-2 may experience elevated visibility persistence latencies"

Last update 2025-04-08T14:23:45.767Z

resolved2025-04-03T02:01:15.275Z

This incident has been resolved.

monitoring2025-04-03T01:47:20.229Z

Latencies have returned to normal and we are monitoring the system.

investigating2025-04-03T01:33:46.851Z

Some customers in aws us-west-2 may experience elevated visibility persistence latencies.

Mar 29, 2025

Report: "Audit Log Delivery Delay"

Last update 2025-03-29T00:08:10.941Z

resolved2025-03-28T21:00:00.000Z

The delivery of audit logs for any Cloud events that occurred between 3/26/2025 15:30 UTC and 3/27/2025 17:30 UTC was delayed. These audit logs have since been delivered to their destinations as of 3/28/2025 21:00 UTC

Mar 27, 2025

Report: "User Permission Updates Delay"

Last update 2025-03-27T16:28:05.581Z

resolved2025-03-26T18:30:00.000Z

Any permission changs related to user creation/deletion/update were accepted by the system, but were not processed until 19:15 UTC

Mar 22, 2025

Report: "Some customers in AWS us-west-2 may experience elevated latencies"

Last update 2025-03-22T05:01:11.604Z

resolved2025-03-22T05:01:11.584Z

This incident has been resolved.

monitoring2025-03-22T04:34:19.268Z

A fix has been implemented and we are monitoring the results.

identified2025-03-22T04:18:45.939Z

The issue has been identified and a fix is being implemented.

Mar 12, 2025

Report: "Some customers in the AWS us-west-2 region might notice a delay in the visibility API"

Last update 2025-03-12T12:40:44.795Z

resolved2025-03-12T12:40:44.770Z

This incident has been resolved.

monitoring2025-03-12T11:55:11.271Z

We are seeing Visibility API latency improvements and anticipate an accelerating full recovery.

identified2025-03-12T11:35:48.418Z

The issue has been identified and we are working to scale the cluster further.

investigating2025-03-12T10:36:38.173Z

We are currently investigating this issue.

Report: "Some customers in the AWS us-west-2 region might notice a delay in the visibility API"

Last update 2025-03-12T05:25:38.846Z

resolved2025-03-12T05:25:38.831Z

Visibility API latencies are fully recovered and the visibility task backlog has been drained.

monitoring2025-03-12T05:00:04.629Z

After a slight wobble Visibility API latencies are mostly recovered and we are working to process the backlog of visibility tasks ASAP. We will continue to monitor this until the backlog is fully drained.

investigating2025-03-12T04:24:25.229Z

We are currently investigating a regression back towards degraded visibility API performance. We will update again when we know more.

monitoring2025-03-12T04:07:21.586Z

Visibility API latency has improved and we are now working through the backlog of visibility tasks.

identified2025-03-12T03:10:11.784Z

We are waiting on the fix to fully rollout and anticipate that we will begin to see recovery soon.

identified2025-03-12T01:57:51.200Z

The issue has been identified and a fix is being implemented.

investigating2025-03-12T01:45:14.000Z

The issue is only with the visibility API and is not affecting workflows in anyway. We are investigating the issue.

Mar 11, 2025

Report: "Some customer of us-east-2 may see degraded Create/Delete/Update Namespace performance"

Last update 2025-03-11T15:23:45.544Z

resolved2025-03-10T23:48:30.000Z

This incident has been resolved.

monitoring2025-03-10T23:47:32.991Z

The original incident was incorrectly reported as affecting us-east-1 when in fact it was only affecting us-east-2. We apologize for misreporting the incident, but it has been resolved.

monitoring2025-03-10T23:45:17.431Z

We are continuing to monitor for any further issues.

monitoring2025-03-10T23:44:41.838Z

We are continuing to monitor for any further issues.

monitoring2025-03-10T23:40:30.587Z

A fix has been implemented and we are monitoring the results.

identified2025-03-10T23:16:52.293Z

The issue has been identified and a fix is being implemented.

investigating2025-03-10T22:43:31.468Z

We are currently investigating this issue.

Mar 5, 2025

Report: "Higher latencies and error rate observed for some customers in us-east-1"

Last update 2025-03-05T10:02:05.833Z

resolved2025-03-05T10:02:05.812Z

This incident has been resolved.

monitoring2025-03-05T09:47:18.029Z

A fix has been implemented and we are monitoring the result.

investigating2025-03-05T09:27:23.552Z

We are continuing to investigate this issue.

investigating2025-03-05T08:05:38.000Z

We are currently investigating the issue.

Feb 26, 2025

Report: "Some customers in AWS us-west-2 may experience elevated latencies"

Last update 2025-02-26T02:59:16.690Z

resolved2025-02-26T02:59:16.673Z

This incident has been resolved.

monitoring2025-02-26T02:58:23.914Z

A fix has been implemented and we are monitoring the result.

investigating2025-02-26T00:31:32.070Z

Some customers in AWS us-west-2 may experience elevated latencies related to visibility task processing. The core system is not impacted.

Feb 21, 2025

Report: "Customers in GCP us-east4 experience unavailability of service"

Last update 2025-02-21T22:50:01.926Z

resolved2025-02-21T22:50:01.905Z

This incident has been resolved.

monitoring2025-02-21T22:43:26.435Z

A fix has been implemented and we are monitoring the results.

identified2025-02-21T22:10:02.022Z

The issue has been identified and a fix is being implemented.

investigating2025-02-21T21:50:51.000Z

Customers in GCP us-east4 experience unavailability of service

Report: "Customers in GCP us-west1 experience unavailability of service"

Last update 2025-02-21T11:37:25.774Z

resolved2025-02-21T11:34:21.949Z

This incident has been resolved.

monitoring2025-02-21T11:18:48.000Z

A fix has been implemented and we are monitoring the results.

identified2025-02-21T11:15:39.000Z

We are continuing to work on a fix for this issue.

identified2025-02-21T11:10:40.000Z

The issue has been identified and a fix is being implemented.

investigating2025-02-21T10:34:51.000Z

Customers in GCP us-west1 experience unavailability of service

Report: "Some customers in AWS us-east-1 may experience elevated API latencies"

Last update 2025-02-21T07:16:09.267Z

resolved2025-02-21T07:16:09.240Z

This incident has been resolved.

monitoring2025-02-21T02:49:01.900Z

A fix has been implemented and we are monitoring the results.

identified2025-02-21T01:18:24.303Z

We are continuing to work on a fix for this issue.

identified2025-02-21T00:52:50.503Z

The issue has been identified and a fix is being implemented.

investigating2025-02-20T22:20:22.000Z

Some customers in AWS us-east-1 may experience elevated API latencies.

Feb 5, 2025

Report: "temporal.io website temporarily unavailable"

Last update 2025-02-05T04:32:52.420Z

resolved2025-02-05T04:07:27.657Z

This is resolved.

monitoring2025-02-05T04:01:54.879Z

Issue is resolved, will monitor a bit.

investigating2025-02-05T03:56:18.000Z

http://temporal.io website is temporarily unavailable. Note: https://cloud.temporal.io/ is NOT impacted. Temporal Cloud service is NOT impacted.

Jan 19, 2025

Report: "Temporal Workflow Web UI not accessible for a subset of namespaces in AWS us-east-1"

Last update 2025-01-19T18:42:43.840Z

resolved2025-01-19T18:42:43.820Z

Web UI functionality has been fully restored.

monitoring2025-01-19T18:35:21.802Z

We have remedied the issue and are monitoring to make sure web traffic remains healthy

investigating2025-01-19T18:22:19.986Z

We are continuing to investigate this issue.

investigating2025-01-19T18:22:06.463Z

We are currently investigating the issue

Jan 11, 2025

Report: "Some customers in AWS us-east-1 may experience elevated API latencies"

Last update 2025-01-11T00:18:52.352Z

resolved2025-01-11T00:18:52.336Z

This incident has been resolved.

monitoring2025-01-10T23:04:25.404Z

A fix has been implemented and we are monitoring the results.

identified2025-01-10T21:23:28.198Z

The issue has been identified and a fix is being implemented.

Jan 8, 2025

Report: "Namespace creation failed for some customers"

Last update 2025-01-08T20:09:08.070Z

resolved2025-01-08T20:09:08.051Z

This incident has been resolved.

monitoring2025-01-08T18:48:48.290Z

A fix has been implemented and we are monitoring the system.

identified2025-01-08T18:42:03.343Z

We are continuing to work on a fix for this issue.

identified2025-01-08T18:41:26.985Z

A recent release of our control plane led to namespace creation failure for some of our customers. We have identified the issue and are rolling out a fix.

Jan 4, 2025

Report: "Increased latency and reduced availability for some customers in the AWS ap-south-1 (Asia Pacific (Mumbai))"

Last update 2025-01-04T06:59:44.639Z

resolved2025-01-04T06:59:44.625Z

This incident has been resolved.

monitoring2025-01-04T06:33:26.108Z

A fix has been implemented and we are monitoring the results.

identified2025-01-04T06:25:34.238Z

The issue has been identified and a fix is being implemented.

investigating2025-01-04T06:08:21.171Z

We are continuing to investigate this issue.

investigating2025-01-04T06:03:35.856Z

We are currently investigating this issue.

Dec 28, 2024

Report: "Degraded response for some namespaces in ap-south-1 (Asia Pacific (Mumbai))"

Last update 2024-12-28T06:39:19.347Z

resolved2024-12-28T06:39:19.335Z

This incident has been resolved.

identified2024-12-28T06:38:32.438Z

We believe that the service has fully recovered and are closing this incident

identified2024-12-28T06:28:38.116Z

Customers should be seeing significant recovery (not yet complete)

identified2024-12-28T05:53:19.544Z

We are continuing to work on a fix for this issue.

identified2024-12-28T05:52:56.664Z

We believe we have identified the cause of this incident and are taking remedial steps

Dec 17, 2024

Report: "Updates of namespace configuration via web UI are failing"

Last update 2024-12-17T20:02:10.873Z

resolved2024-12-17T17:54:17.367Z

This incident has been resolved.

monitoring2024-12-17T14:09:50.979Z

A fix has been implemented and we are monitoring the results.

identified2024-12-17T13:45:34.714Z

We are continuing to work on a fix for this issue.

identified2024-12-17T13:12:09.303Z

The issue has been identified and a fix is being implemented.

investigating2024-12-17T13:06:54.227Z

Updates via tcld or API are working with no issue. Only web UI is affected.

investigating2024-12-17T13:02:05.855Z

We are currently investigating this issue.

Dec 15, 2024

Report: "Temporal service degradation in aws us-east-1 region for some customers"

Last update 2024-12-15T03:44:12.040Z

resolved2024-12-15T03:00:00.000Z

Some Temporal cloud customers in the AWS us-east-1 region experienced elevated latency and reduced availability

Dec 9, 2024

Report: "Some customers in AWS us-east-2 may experience elevated API latencies"

Last update 2024-12-09T17:16:57.750Z

resolved2024-12-09T17:16:57.734Z

This incident has been resolved.

monitoring2024-12-09T16:58:20.861Z

A fix has been implemented and we are monitoring the issue.

investigating2024-12-09T16:50:52.331Z

Some customers in AWS us-east-2 may experience elevated API latencies

Dec 4, 2024

Report: "Small number of customers in AWS ap-southeast-1 may experience an elevated rate of API errors"

Last update 2024-12-04T23:31:11.437Z

resolved2024-12-04T23:31:11.425Z

This incident has been resolved.

identified2024-12-04T23:08:23.124Z

Please note that this is exclusively impacting requests from the Temporal Cloud UI.

investigating2024-12-04T23:03:10.596Z

Small number of customers in AWS ap-southeast-1 may experience an elevated rate of API errors

Oct 4, 2024

Report: "Namespace creation failed for some customers"

Last update 2024-10-04T21:48:58.461Z

resolved2024-10-04T21:00:00.000Z

A recent release of our control plane led to namespace creation failure for some of our customers. We have since rolled back the release which mitigated the issue.

Sep 30, 2024

Report: "Storage billing for namespaces on GCP has been temporarily disabled."

Last update 2024-09-30T21:45:56.738Z

resolved2024-09-30T21:45:56.725Z

This incident has been resolved.

identified2024-09-27T14:44:00.907Z

The issue has been identified and a fix is being implemented.

investigating2024-09-26T18:36:39.711Z

Storage billing for namespaces on GCP has been temporarily disabled. We are working on a fix. In the meantime, storage costs might be inaccurate. Please know that there will be no charge for GCP namespace storage until this is resolved.

Sep 27, 2024

Report: "Some customers in AWS ap-south-1 may experience elevated API latencies"

Last update 2024-09-27T19:00:44.468Z

resolved2024-09-27T19:00:44.451Z

This incident has been resolved.

identified2024-09-27T18:54:38.160Z

The issue has been identified and a fix is being implemented.

investigating2024-09-27T18:52:48.988Z

Some customers in AWS ap-south-1 may experience elevated API latencies.

Report: "Some customers might experience an inability to configure some aspects of their namespace."

Last update 2024-09-27T02:57:54.346Z

resolved2024-09-27T02:30:16.000Z

This incident has been resolved.

identified2024-09-27T02:29:35.166Z

We are in the process of deploying a fix for this issue.

identified2024-09-27T00:31:43.669Z

We are continuing to work on a fix for this issue.

identified2024-09-27T00:15:36.000Z

Some customers might experience an inability to configure some aspects of their namespace. The issue has been identified and a fix is being implemented.

Sep 25, 2024

Report: "Permission updates to newly created namespaces are delayed."

Last update 2024-09-25T19:09:37.086Z

resolved2024-09-25T19:09:37.070Z

This incident has been resolved.

identified2024-09-25T18:54:00.795Z

The issue has been identified and a fix is being deployed.

investigating2024-09-25T18:53:12.000Z

Namespace permission updates are delayed.

Sep 11, 2024

Report: "Customers in us-east-1 may experience elevated rate of API errors"

Last update 2024-09-11T21:02:23.377Z

resolved2024-09-11T21:02:23.365Z

This incident has been resolved.

identified2024-09-11T19:34:18.772Z

We are continuing to work on a fix for this issue.

identified2024-09-11T18:59:20.129Z

The issue has been identified and we are working on the fix

investigating2024-09-11T18:53:07.339Z

Customers in us-east-1 may experience elevated rate of API errors since 17:30 UTC

Report: "Customers in us-east-1 may experience elevated API latencies"

Last update 2024-09-11T17:43:08.249Z

resolved2024-09-11T17:43:08.233Z

This incident has been resolved.

monitoring2024-09-11T16:10:56.406Z

A fix has been implemented and we see recovery

identified2024-09-11T15:51:48.496Z

We have identified the issue and applying the fix to mitigate it

investigating2024-09-11T15:35:05.179Z

Customers in us-east-1 may experience elevated API latencies.

Sep 10, 2024

Report: "Customers in us-east-1 may experience elevated API latencies"

Last update 2024-09-10T22:15:17.225Z

resolved2024-09-10T22:15:17.208Z

This incident has been resolved.

monitoring2024-09-10T21:23:15.008Z

The fix has been implemented, and we are seeing signs of recovery.

identified2024-09-10T20:19:18.018Z

Customers in us-east-1 may experience elevated API latencies starting 18:30 UTC

Sep 3, 2024

Report: "High error rate and latency observed in us-east-1"

Last update 2024-09-03T18:30:12.956Z

resolved2024-09-03T18:00:00.000Z

This incident has been resolved.

Aug 29, 2024

Report: "Namespace creation, updates and deletes are currently broken"

Last update 2024-08-29T10:06:19.113Z

resolved2024-08-29T10:06:19.089Z

This incident has been resolved.

monitoring2024-08-29T09:53:25.320Z

We are starting to see successful namespace operations going through

investigating2024-08-29T09:46:42.000Z

We are continuing to investigate this issue. This appears to be related to an ongoing AWS STS outage

investigating2024-08-29T09:34:34.000Z

We are continuing to investigate this issue. This appears to be related to an ongoing AWS STS outage

investigating2024-08-29T09:34:03.900Z

We are continuing to investigate this issue.

investigating2024-08-29T09:30:01.268Z

We are currently investigating this issue.

Aug 17, 2024

Report: "High latency and timeouts in us-east-1."

Last update 2024-08-17T10:54:58.331Z

resolved2024-08-17T10:53:43.995Z

This incident has been resolved.

monitoring2024-08-17T10:29:49.591Z

Our vendor has identified and resolved the issue in us-east-1.

investigating2024-08-17T09:41:24.816Z

Some customers may be experiencing high latency and occasional timeouts in us-east-1. We are investigating with our vendor.

Aug 16, 2024

Report: "High latency and timeouts in us-east-1"

Last update 2024-08-16T19:33:19.460Z

resolved2024-08-16T19:33:19.445Z

The issue has been fully resolved and all customer should be experiencing normal latency in us-east-1.

monitoring2024-08-16T19:25:03.599Z

Our vendor has identified and resolved the issue and we are seeing full recovery across us-east-1. We will continue to monitor the regions health for a while longer.

investigating2024-08-16T18:39:23.000Z

Some customers may be experiencing high latency and occasional timeouts in us-east-1. We are investigating with our vendor.

Jul 26, 2024

Report: "Customers in us-east-1 may experience elevated API latencies and error rates."

Last update 2024-07-26T07:19:58.092Z

resolved2024-07-26T07:19:58.074Z

This incident has been resolved.

monitoring2024-07-26T06:02:31.760Z

A fix has been implemented and we are monitoring the results.

identified2024-07-26T02:59:50.843Z

The issue has been identified and a fix is being implemented.

investigating2024-07-26T02:11:57.148Z

We are continuing to investigate the issue.

investigating2024-07-26T01:19:08.995Z

We are continuing to investigate the issue.

investigating2024-07-25T23:40:47.011Z

Customers in us-east-1 may experience elevated API latencies and error rates.

Jul 23, 2024

Report: "Web UI shows 500 errors"

Last update 2024-07-23T15:21:39.123Z

resolved2024-07-22T17:20:28.000Z

This incident has been resolved.

monitoring2024-07-22T17:15:05.000Z

A fix has been implemented and we are monitoring the results.

investigating2024-07-22T17:00:28.000Z

Users experience 500 errors when trying to access web UI.

Jul 18, 2024

Report: "Elevated latencies observed in us-east-1"

Last update 2024-07-18T14:28:02.770Z

resolved2024-07-18T14:28:02.756Z

This incident has been resolved.

investigating2024-07-18T14:09:11.592Z

We are currently investigating this issue.

Jul 13, 2024

Report: "Some customers in us-east-1 may experience elevated API latencies"

Last update 2024-07-13T16:17:01.397Z

resolved2024-07-13T13:09:00.000Z

Some customers in us-east-1 may experience elevated API latencies. Impacted time window: 13:09 ~ 13:17 UTC