Vercel – Blob deliveries failing in some situations

by

Dec 13, 11:32 UTC
Resolved – This incident has been resolved, all blob URLs are working as usual.

Dec 13, 11:04 UTC
Monitoring – The issue affecting the delivery of blobs with double slashes (//) in their URLs has been resolved. Blobs are now accessible as expected.

Please note that due to caching, some requests for these blobs may still be redirected for up to two hours. We are working to purge the cache to ensure immediate availability.

Thank you for your patience and understanding.

Dec 13, 10:15 UTC
Identified – We are aware of an issue affecting the delivery of blobs that contain double slashes (//) in their URLs. These blobs may not be accessible at the moment due to an unexpected change in our URL handling.

Our team is actively working on a fix and will provide updates as soon as possible. We apologize for the inconvenience and appreciate your patience.

DigitalOcean – Spaces CDN

by

Dec 13, 11:01 UTC
Resolved – Our Engineering team has confirmed that the issues with Spaces CDN functionality has been fully resolved. Users should now be able to use CDN functionality normally.

If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Dec 13, 10:55 UTC
Monitoring – Our Engineering team has implemented a fix to resolve the CDN functionality issue and is currently monitoring the situation.

We will continue to monitor this at our end and will share an update once the issue is resolved completely.

Dec 13, 09:55 UTC
Investigating – Our Engineering team is investigating an issue affecting Spaces CDN functionality globally. During this time, users may experience issues when enabling Spaces CDN and with existing CDN services.

We apologize for the inconvenience and will share an update once we have more information.

Supabase – Maintenance required on Supavisor in ap-northeast-2 (Seoul) region.

by

Dec 13, 11:00 UTC
Completed – The scheduled maintenance has been completed.

Dec 13, 10:00 UTC
In progress – Scheduled maintenance is currently in progress. We will provide updates as necessary.

Dec 12, 09:42 UTC
Scheduled – We will be performing maintenance on Supavisor in ap-northeast-2 (Seoul) region on 2024-12-13 at 10:00UTC.

Connections to Supavisor in the effected region may be temporarily disconnected during this period as we perform this required maintenance.

Atlassian Analytics – INCOMPATIBLE VIEW SCHEMA CHANGE errors being encountered when attempting to query the jira_issue table

by

Dec 13, 09:30 UTC
Resolved – The issue has now been resolved

Dec 13, 05:27 UTC
Identified – The issue has been identified and a fix is being implemented.

Dec 13, 05:06 UTC
Update – We are continuing to monitor for any further issues.

Dec 13, 04:46 UTC
Monitoring – A fix has been implemented and we are monitoring the results.

Dec 13, 04:02 UTC
Identified – The issue has been identified and a fix is being implemented.

Dec 13, 03:14 UTC
Investigating – We are investigating reports of intermittent errors for some Atlassian Analytics Cloud customers. We will provide more details once we identify the root cause.

DigitalOcean – Managed Database Operations

by

Dec 13, 04:05 UTC
Resolved – Our Engineering team has confirmed the full resolution of the issue impacting Managed Database Operations, and all systems are now operating normally. Users may safely resume operations, including upgrades, resizes, forking, and ad-hoc maintenance patches.

If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Dec 13, 03:13 UTC
Monitoring – Our Engineering team has implemented a fix for the issue impacting Managed Database Operations. The team is monitoring the situation, and we will share an update once this is fully resolved.

Dec 12, 22:03 UTC
Update – Our Engineering team is continuing to work on investigating the root cause of the issue affecting Managed Database Operations. At this time, we are seeing improvement and some new cluster creations are completing successfully.

To avoid potential downtime, we continue to ask users to refrain from performing operations that trigger node rotations, such as upgrades, resizes, forking, and ad-hoc maintenance patches.

We apologize for any inconvenience caused and appreciate your patience. We will post further updates as soon we have more information.

Dec 12, 19:35 UTC
Update – During our investigation, we identified that operations triggering node rotation, such as upgrades, resizes, forking and ad-hoc maintenance patches, may cause issues connecting to the cluster.

To prevent potential downtime, we recommend avoiding these operations until the issue is fully resolved.

We apologize for the inconvenience and appreciate your patience as we work to address the situation.

Dec 12, 18:34 UTC
Investigating – Our Engineering team is investigating an issue with the Managed Database clusters which is causing forks, restores and new creates to fail. The Mongo clusters are unaffected and should be operating normally.

Our team is currently assessing the root cause and working to resolve the issue as quickly as possible.

We apologize for any inconvenience this may cause and will share an update as soon as we have more information.

DigitalOcean – DNS Resolution in NYC1

by

Dec 13, 01:24 UTC
Resolved – Our Engineering team has confirmed that the issues with Authoritative DNS resolution in NYC1 has been fully resolved. DNS queries should now be resolving normally.

If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Dec 13, 01:10 UTC
Monitoring – Our Engineering team has implemented a fix to resolve the issues with Authoritative DNS Resolution in NYC1 and is currently monitoring the situation.

We will continue to monitor this at our end and will share an update once the issue is resolved completely.

Dec 12, 23:20 UTC
Investigating – Our Engineering team is investigating an issue with intermittent failures and increased latency in DNS resolution in NYC1.

During this time, a subset of users may experience issues with DNS resolution, or see errors returned when querying DNS records which are hosted on the DigitalOcean authoritative DNS infrastructure.

We apologize for the inconvenience and will share an update once we have more information.

Discord – Server Availability

by

Dec 12, 16:50 PST
Resolved – This incident has been resolved.

Dec 12, 16:41 PST
Identified – The issue has been identified and a fix is being implemented.

Dec 12, 16:22 PST
Investigating – We’re investigating issues with some servers becoming unavailable.

Zapier – Outage on OpenAI services

by

Dec 12, 06:27 PST
Resolved – The OpenAI team has officially resolved this incident so all related integrations are functioning again.

Dec 11, 20:26 PST
Monitoring – OpenAI services have largely recovered, and we are closely monitoring the situation to ensure the fix has fully resolved the issue.

Our team is assessing the timeframe and duration of the incident. Once confirmed, we will replay any errored Zap runs impacted by this outage.

Dec 11, 16:48 PST
Identified – Due to an outage in OpenAI services, customers may experience issues with OpenAI steps in their Zaps and AI features such as Chatbots and AI prompts.