Teradek Core Outage History

Teradek Core is up right now

Pingoru has recorded 23 incidents for Teradek Core: 1 in the last 12 months and 0 in the last 90 days.

Source: status.corecloud.tv

23incidents recorded
1last 12 months
0last 90 days
2 hourstypical duration

Incidents, newest first

Minor April 22, 2026 Degraded Availability of Cloud Streaming Servers 2h 4m Core Application Servers, Cloud Streaming Servers

Started Apr 22, 2026, 11:31 AM UTC· resolved Apr 22, 2026, 01:35 PM UTC

  1. monitoring Apr 22, 2026, 11:31 AM UTC

    Dear Customers, We'd like to inform you that we are currently experiencing an issue affecting cloud-hosted streaming servers due to an ongoing incident on the provider's side. During this time, certain operations involving streaming servers may not function as expected. You may encounter errors, delays, or inconsistent behavior when starting, stopping, or managing streaming sessions. Our platform interface remains operational; however, the underlying infrastructure supporting streaming workloads is currently impacted. The provider's engineering team is actively investigating the issue. We are monitoring the situation closely and will share updates as more information becomes available. Thank you for your patience.

  2. monitoring Apr 22, 2026, 11:37 AM UTC

    We are continuing to monitor for any further issues.

  3. monitoring Apr 22, 2026, 11:39 AM UTC

    We’d like to share an update regarding the recent cloud service disruption. Our cloud provider has implemented a fix for the issue affecting the infrastructure, and services are now recovering. They are currently monitoring the system to ensure full stability. We will continue to keep an eye on the situation and will provide a final update once everything is fully resolved. Thank you for your patience and understanding.

  4. resolved Apr 22, 2026, 01:35 PM UTC

    Dear Customers, We would like to inform you that the recent cloud service incident has been fully resolved. Our cloud provider has confirmed that the issue affecting the infrastructure, including API operations and the Cloud Control Panel, has been fixed. All services are now operating normally. If you continue to experience any issues, please let us know and we’ll be happy to assist. Thank you for your patience throughout this process.

Read the full incident report →

Minor May 22, 2025 Degraded Performance for Droplet-Based Services Across Multiple Regions 4h 49m Cloud Streaming Servers

Started May 22, 2025, 03:37 PM UTC· resolved May 22, 2025, 08:26 PM UTC

  1. investigating May 22, 2025, 03:37 PM UTC

    One of our cloud infrastructure providers is currently experiencing issues that are impacting the creation of cloud servers in some regions. As a result, you may encounter elevated failure rates when launching new cloud servers or redeploying existing cloud servers. Our Engineering team is actively monitoring the situation to ensure a swift resolution. We apologize for the inconvenience and will provide further updates as soon as new information becomes available.

  2. monitoring May 22, 2025, 06:51 PM UTC

    The issue causing failed server creation has been identified and resolved. You may now be able to launch new cloud servers or start/redeploy existing ones. We’re actively monitoring the situation and will update once it’s fully resolved.

  3. resolved May 22, 2025, 08:26 PM UTC

    A recent issue affecting cloud server creation and redeployment in certain regions has now been fully resolved. At this time, all related services are functioning as expected. We’ll continue observing system performance to maintain stability going forward. Thank you for your understanding throughout this situation. If you notice anything unusual or need further support, feel free to submit a ticket through your account—we’re here to help.

Read the full incident report →

Major January 24, 2025 Core Service 2d 4h Core Application Servers, Registration and Authentication, Cloud Streaming Servers

Started Jan 24, 2025, 07:17 AM UTC· resolved Jan 26, 2025, 11:22 AM UTC

  1. investigating Jan 24, 2025, 07:17 AM UTC

    We are currently experiencing unexpected issues with our service. Our engineering team is actively investigating the problem and working diligently to resolve it as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience and understanding during this time.

  2. identified Jan 24, 2025, 07:41 AM UTC

    We’re currently experiencing an issue with DNS, which is temporarily affecting access to corecloud.tv. Services are expected to be restored within the next few hours.

  3. identified Jan 24, 2025, 11:21 AM UTC

    We're still experiencing a DNS outage from an external provider, temporarily affecting access to corecloud.tv and teradek.com. While services are expected to be restored, propagation may take some time globally, potentially causing temporary disruptions.

  4. identified Jan 24, 2025, 02:35 PM UTC

    We’re still experiencing a DNS outage from an external provider. Access to corecloud.tv has been restored, but Сloud server and device connections remain affected. Services are on track to be fully restored, but global propagation might take some time and could lead to temporary interruptions. We apologize for any inconvenience this may cause and sincerely value your patience and support during this time.

  5. monitoring Jan 24, 2025, 07:28 PM UTC

    At Teradek Live Production, we pride ourselves on creating hardware and software that help you produce high-quality video content for your live events. However, sometimes issues arise. When they do, we work quickly and efficiently to resolve them while implementing measures to prevent similar occurrences in the future. *What was the problem? A domain name change outside of Teradek Core was erroneously sent to the top-level domain providers. *Has it been fixed? Yes, this issue was corrected on Thursday night. However, it temporarily impacted DNS and authentication services in Core, particularly on our cloud servers. Please note that DNS changes can take 24–48 hours to fully propagate. All services should be restored once this propagation process is complete. *Will I be affected? If you have an event scheduled before the DNS propagation is complete (within the next 24–48 hours), you may experience issues. We have a workaround in place: >> If you have an event scheduled, please reach out to [email protected]. Our team is ready to assist. >> Locally, if you are unable to connect your Prism to Core, please use the DNS entry 1.1.1.1, which should resolve the issue.

  6. resolved Jan 26, 2025, 11:22 AM UTC

    We’re happy to report that the DNS outage from our external provider has been fully resolved. Access to corecloud.tv and all cloud server and device connections has been fully restored. DNS propagation has completed globally, and all services are now operating normally. We regret any inconvenience caused by this incident and appreciate your patience and support throughout the process. What’s next? All systems are back online, and no further impact is expected. If you continue to encounter any issues, please don’t hesitate to reach out to us at [email protected]. Our team is always here to help.

Read the full incident report →

Minor January 3, 2025 Issues with transcoding servers in Core 3d 1h Cloud Streaming Servers

Started Jan 03, 2025, 02:45 PM UTC· resolved Jan 06, 2025, 03:53 PM UTC

  1. investigating Jan 03, 2025, 02:45 PM UTC

    We are currently experiencing issues with transcoding servers. Our team is actively working on resolving this, and the issue is expected to be fixed by January 6th. Thank you for your patience.

  2. resolved Jan 06, 2025, 03:53 PM UTC

    The issue with the transcoding server has been resolved.

Read the full incident report →