Dolby.io Outage History

Dolby.io is up right now

Dolby.io had 24 outages in the last 2 years totaling 337h 20m of downtime — averaging 1 incident per month.

There were 24 Dolby.io outages since June 2, 2024 totaling 337h 20m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.dolby.io

Major May 17, 2026

Streaming in the phx-1 region is impacted

Detected by Pingoru
May 17, 2026, 07:52 AM UTC
Resolved
May 17, 2026, 08:44 AM UTC
Duration
52m
Affected: US Western Region (PHX-1), United States
Timeline · 3 updates
  1. investigating May 17, 2026, 07:52 AM UTC

    Due to Cloud Provider initiated maintenance, streaming in the phx-1 region is impacted. We are working to resolve this with the cloud provider and will provide further updates as soon as we have more information.

  2. monitoring May 17, 2026, 08:11 AM UTC

    The cloud provider maintenance is complete, the functionality is restored and we are monitoring.

  3. resolved May 17, 2026, 08:44 AM UTC

    Cloud provider maintenance in PHX-1 has been completed, and streaming functionality has been restored. This incident is now resolved.

Read the full incident report →

Minor March 4, 2026

Currently observing issues creating transcoders in IAD (Ashburn) cluster

Detected by Pingoru
Mar 04, 2026, 05:01 PM UTC
Resolved
Mar 05, 2026, 08:01 AM UTC
Duration
15h
Affected: US Eastern Region (IAD-1), United States
Timeline · 3 updates
  1. investigating Mar 04, 2026, 05:01 PM UTC

    We are currently investigating this issue.

  2. monitoring Mar 05, 2026, 07:07 AM UTC

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

  3. resolved Mar 05, 2026, 08:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 5, 2026

Degraded services for LON and FRA Cluster Reagion

Detected by Pingoru
Feb 05, 2026, 05:03 PM UTC
Resolved
Feb 05, 2026, 11:15 PM UTC
Duration
6h 11m
Affected: London (LON-1), United KingdomFrankfurt (FRA-1), Germany
Timeline · 4 updates
  1. investigating Feb 05, 2026, 05:03 PM UTC

    We are currently investigating this issue.

  2. monitoring Feb 05, 2026, 06:00 PM UTC

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

  3. monitoring Feb 05, 2026, 06:01 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Feb 05, 2026, 11:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 28, 2026

Instability with WHIP publishing through the Singapore region

Detected by Pingoru
Jan 28, 2026, 01:12 PM UTC
Resolved
Jan 28, 2026, 01:56 PM UTC
Duration
44m
Affected: Singapore (SGP-1)
Timeline · 3 updates
  1. investigating Jan 28, 2026, 01:12 PM UTC

    We are currently experiencing instability with WHIP publishing through the Singapore region. To ensure consistent performance, we recommend using alternative WHIP publishing regions at this time. Our team is actively investigating and will provide updates as they become available.

  2. monitoring Jan 28, 2026, 01:37 PM UTC

    Due to ongoing network issues in the Singapore region, WHIP streams are currently experiencing instability.

  3. resolved Jan 28, 2026, 01:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 26, 2025

Degraded service in lon-1

Detected by Pingoru
Nov 26, 2025, 12:08 PM UTC
Resolved
Nov 26, 2025, 11:12 PM UTC
Duration
11h 4m
Affected: London (LON-1), United Kingdom
Timeline · 3 updates
  1. investigating Nov 26, 2025, 12:08 PM UTC

    We are currently investigating this issue.

  2. monitoring Nov 26, 2025, 07:24 PM UTC

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

  3. resolved Nov 26, 2025, 11:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 31, 2025

Degraded services on FRA-1 from 06:40 to 06:50UTC

Detected by Pingoru
Oct 31, 2025, 11:24 AM UTC
Resolved
Oct 31, 2025, 02:01 PM UTC
Duration
2h 36m
Affected: Frankfurt (FRA-1), Germany
Timeline · 2 updates
  1. monitoring Oct 31, 2025, 11:24 AM UTC

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

  2. resolved Oct 31, 2025, 02:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 15, 2025

Degradation in FRA-1 Region

Detected by Pingoru
Oct 15, 2025, 01:01 PM UTC
Resolved
Oct 15, 2025, 07:15 PM UTC
Duration
6h 13m
Affected: Frankfurt (FRA-1), Germany
Timeline · 2 updates
  1. investigating Oct 15, 2025, 01:01 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 15, 2025, 07:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 27, 2025

Outages With The Public Internet Across Bangalore

Detected by Pingoru
Sep 27, 2025, 02:16 PM UTC
Resolved
Sep 27, 2025, 08:17 PM UTC
Duration
6h 1m
Affected: Bangalore (BLA-1), India
Timeline · 2 updates
  1. monitoring Sep 27, 2025, 02:16 PM UTC

    We have observed outages with the public internet across Bangalore, including issues affecting our cloud provider in the region, between 2025-09-27T11:10:00Z and 2025-09-27T12:35:00Z. We are actively monitoring the situation, as this may impact users of our streaming services attempting to publish or subscribe to Bangalore. We recommend directing your traffic to other regions until we see stabilization of the public network in Bangalore.

  2. resolved Sep 27, 2025, 08:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 19, 2025

Issue with Transcoder Startup on PHX-1 and IAD-1 – No Impact on Active Transcoders

Detected by Pingoru
Aug 19, 2025, 04:15 AM UTC
Resolved
Aug 19, 2025, 07:26 AM UTC
Duration
3h 11m
Affected: US Eastern Region (IAD-1), United StatesUS Western Region (PHX-1), United States
Timeline · 3 updates
  1. investigating Aug 19, 2025, 04:15 AM UTC

    We're currently investigating an issue affecting transcoder startup in the PHX and IAD-1 regions. Please note that NO disruption expected for transcoders that are currently running. Our team is actively working to identify the root cause.

  2. monitoring Aug 19, 2025, 05:41 AM UTC

    Cloud provider platform slowdown causing degraded startup and status notification performance on Transcoders in IAD-1 and PHX-1. We’re actively monitoring the services.

  3. resolved Aug 19, 2025, 07:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 30, 2025

API failures

Detected by Pingoru
Jul 30, 2025, 07:00 PM UTC
Resolved
Jul 30, 2025, 07:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 30, 2025, 10:19 PM UTC

    Some API calls result in 503 errors between 19:15 - 19:55. This impacted the Dolby Millicast core services.

Read the full incident report →

Minor December 6, 2024

Degraded Service on SGP(singapore) datacenter

Detected by Pingoru
Dec 06, 2024, 03:43 AM UTC
Resolved
Dec 06, 2024, 04:21 AM UTC
Duration
38m
Affected: Singapore (SGP-1)
Timeline · 3 updates
  1. investigating Dec 06, 2024, 03:43 AM UTC

    We are currently investigating this issue.

  2. monitoring Dec 06, 2024, 04:09 AM UTC

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

  3. resolved Dec 06, 2024, 04:21 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 5, 2024

Degraded service in SGP (Singapore) datacenter

Detected by Pingoru
Dec 05, 2024, 05:59 PM UTC
Resolved
Dec 05, 2024, 08:48 PM UTC
Duration
2h 48m
Affected: Singapore (SGP-1)
Timeline · 2 updates
  1. investigating Dec 05, 2024, 05:59 PM UTC

    We are seeing degraded service due to network impairment in our SGP region. We recommend using alternative regions when possible.

  2. resolved Dec 05, 2024, 08:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 23, 2024

Degraded service in BLR (Bangalore) datacenter

Detected by Pingoru
Sep 23, 2024, 11:45 PM UTC
Resolved
Sep 24, 2024, 02:38 AM UTC
Duration
2h 52m
Affected: Bangalore (BLA-1), India
Timeline · 3 updates
  1. investigating Sep 23, 2024, 11:45 PM UTC

    We are seeing degraded service due to network impairment in our BLR region. We recommend using alternative regions.

  2. monitoring Sep 24, 2024, 02:17 AM UTC

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

  3. resolved Sep 24, 2024, 02:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 4, 2024

Degraded services for BLR region

Detected by Pingoru
Sep 04, 2024, 06:46 AM UTC
Resolved
Sep 04, 2024, 07:54 AM UTC
Duration
1h 8m
Affected: Bangalore (BLA-1), India
Timeline · 3 updates
  1. investigating Sep 04, 2024, 06:46 AM UTC

    We are currently investigating this issue.

  2. monitoring Sep 04, 2024, 07:11 AM UTC

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

  3. resolved Sep 04, 2024, 07:54 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 3, 2024

WebRtc Publishing is failing

Detected by Pingoru
Sep 03, 2024, 12:31 AM UTC
Resolved
Sep 03, 2024, 03:35 AM UTC
Duration
3h 3m
Affected: US Eastern Region (IAD-1), United StatesUS Western Region (PHX-1), United StatesLondon (LON-1), United KingdomFrankfurt (FRA-1), GermanySydney (SYD-1), AustraliaSão Paulo (SAO-1), Brazil
Timeline · 7 updates
  1. investigating Sep 03, 2024, 12:31 AM UTC

    We are currently investigating this issue.

  2. investigating Sep 03, 2024, 12:35 AM UTC

    We are continuing to investigate this issue.

  3. investigating Sep 03, 2024, 12:39 AM UTC

    We are continuing to investigate this issue.

  4. investigating Sep 03, 2024, 12:43 AM UTC

    We are continuing to investigate this issue.

  5. monitoring Sep 03, 2024, 12:58 AM UTC

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

  6. monitoring Sep 03, 2024, 12:59 AM UTC

    We are continuing to monitor for any further issues.

  7. resolved Sep 03, 2024, 03:35 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 21, 2024

Degraded service in LON and AMS datacenters

Detected by Pingoru
Aug 21, 2024, 08:02 AM UTC
Resolved
Aug 21, 2024, 12:04 PM UTC
Duration
4h 1m
Affected: London (LON-1), United KingdomAmsterdam (AMS-1), Netherlands
Timeline · 4 updates
  1. investigating Aug 21, 2024, 08:02 AM UTC

    We are currently investigating this issue.

  2. investigating Aug 21, 2024, 08:26 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Aug 21, 2024, 11:06 AM UTC

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

  4. resolved Aug 21, 2024, 12:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 15, 2024

Degraded service in LON datacenter

Detected by Pingoru
Aug 15, 2024, 08:18 AM UTC
Resolved
Aug 15, 2024, 11:59 AM UTC
Duration
3h 40m
Affected: US Eastern Region (IAD-1), United StatesLondon (LON-1), United KingdomAmsterdam (AMS-1), Netherlands
Timeline · 6 updates
  1. investigating Aug 15, 2024, 08:18 AM UTC

    We are currently experiencing higher than normal response times and packetloss in the LON datacenter. We are still investigating the issue.

  2. investigating Aug 15, 2024, 08:21 AM UTC

    We are continuing to investigate this issue.

  3. investigating Aug 15, 2024, 09:07 AM UTC

    We are continuing to investigate this issue.

  4. investigating Aug 15, 2024, 09:08 AM UTC

    We are continuing to investigate this issue.

  5. monitoring Aug 15, 2024, 10:50 AM UTC

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

  6. resolved Aug 15, 2024, 11:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 1, 2024

Live Monitoring not available for SPG streams.

Detected by Pingoru
Aug 01, 2024, 04:42 PM UTC
Resolved
Aug 01, 2024, 05:52 PM UTC
Duration
1h 10m
Affected: Developer Portal
Timeline · 3 updates
  1. investigating Aug 01, 2024, 04:42 PM UTC

    The Live Monitoring tool in the dashboard is currently not available for streams being published to the SPG datacenter.

  2. identified Aug 01, 2024, 04:43 PM UTC

    A root cause has been established and a fix is being implemented.

  3. resolved Aug 01, 2024, 05:52 PM UTC

    This incident has been resolved and the Live Monitoring tool is operational for all datacenters.

Read the full incident report →

Minor July 11, 2024

Degraded services for SGP region

Detected by Pingoru
Jul 11, 2024, 01:26 PM UTC
Resolved
Jul 11, 2024, 02:00 PM UTC
Duration
33m
Affected: Singapore (SGP-1)
Timeline · 3 updates
  1. investigating Jul 11, 2024, 01:26 PM UTC

    We are currently observing some instabilities in the region and are investigating the issue.

  2. monitoring Jul 11, 2024, 01:40 PM UTC

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

  3. resolved Jul 11, 2024, 02:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 20, 2024

publishing failure and viewer not live failures

Detected by Pingoru
Jun 20, 2024, 12:41 AM UTC
Resolved
Jun 20, 2024, 06:08 AM UTC
Duration
5h 26m
Affected: US Eastern Region (IAD-1), United StatesUS Western Region (PHX-1), United StatesLondon (LON-1), United KingdomFrankfurt (FRA-1), GermanySingapore (SGP-1)Sydney (SYD-1), AustraliaSão Paulo (SAO-1), Brazil
Timeline · 4 updates
  1. investigating Jun 20, 2024, 01:48 AM UTC

    Publishing in the Singapore datacenter is currently unavailable. Customers will see an error message "No media servers available..." when attempting to publish to SPG. Viewing of streams in Ashburn, Frankfurt, London, Phoenix, Sao Paulo, and Sydney is currently not available. Viewers attempting to view streams in those regions will see that the stream is "not live". Streams running before this incident began are unaffected.

  2. investigating Jun 20, 2024, 01:54 AM UTC

    Viewing in all regions is now operational. Publishing to the SPG datacenter is still not available.

  3. monitoring Jun 20, 2024, 04:54 AM UTC

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

  4. resolved Jun 20, 2024, 06:08 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 18, 2024

Degraded services for LON region

Detected by Pingoru
Jun 18, 2024, 08:46 AM UTC
Resolved
Jun 18, 2024, 12:57 PM UTC
Duration
4h 10m
Affected: London (LON-1), United Kingdom
Timeline · 3 updates
  1. investigating Jun 18, 2024, 08:46 AM UTC

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

  2. monitoring Jun 18, 2024, 11:12 AM UTC

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

  3. resolved Jun 18, 2024, 12:57 PM UTC

    A fix has been implemented, and the issue has been resolved.

Read the full incident report →

Notice June 7, 2024

Degraded services for SGP - ongoing

Detected by Pingoru
Jun 07, 2024, 12:56 AM UTC
Resolved
Jun 06, 2024, 11:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 07, 2024, 12:56 AM UTC

    We are currently seeing ongoing intermittent degraded service in the Singapore datacenter. This is due to overall network instability in the region from upstream service providers. This occurrence of degraded service lasted between 22:57-23:43 UTC. see original incident for more details https://status.dolby.io/incidents/fsyj2mzzlxtz

Read the full incident report →

Minor June 4, 2024

Degraded services for SGP region - ongoing

Detected by Pingoru
Jun 04, 2024, 01:48 PM UTC
Resolved
Jun 07, 2024, 12:43 AM UTC
Duration
2d 10h
Affected: Singapore (SGP-1)
Timeline · 4 updates
  1. investigating Jun 04, 2024, 02:27 PM UTC

    We are currently seeing ongoing intermittent degraded service in the Singapore datacenter. This is due to overall network instability in the region. see original incident for more details https://status.dolby.io/incidents/fsyj2mzzlxtz

  2. monitoring Jun 05, 2024, 03:09 AM UTC

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

  3. identified Jun 07, 2024, 12:37 AM UTC

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

  4. resolved Jun 07, 2024, 12:43 AM UTC

    This incident has been resolved.

Read the full incident report →