- Detected by Pingoru
- Mar 19, 2026, 09:34 AM UTC
- Resolved
- Mar 19, 2026, 05:54 PM UTC
- Duration
- 8h 19m
Affected: TAP Programmatic UI (Yield-Op)TAP Programmatic UI (Yield-Op)TAP Programmatic UI (Yield-Op)
Timeline · 2 updates
-
investigating Mar 19, 2026, 09:34 AM UTC
We are currently investigating performance issues affecting the TAP Programmatic user interface. Users may experience latency, error messages, or unexpected behavior while navigating the Programmatic tab to manage deals or packages. Our engineering teams are working to identify the root cause and restore full stability to the platform as quickly as possible. Please note that this issue is limited to the user interface; ad delivery and bidding processes remain unaffected. More information to come.
-
resolved Mar 19, 2026, 05:54 PM UTC
A fix has been applied. TAP Programmatic interface is once again operating under normal parameters. This incident is considered resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 09:06 AM UTC
- Resolved
- Mar 19, 2026, 09:06 AM UTC
- Duration
- 39s
Affected: Manadge (TAP Programmatic Analytics Dashboard)Manadge (TAP Programmatic Analytics Dashboard)Manadge (TAP Programmatic Analytics Dashboard)
Timeline · 2 updates
-
identified Mar 19, 2026, 09:06 AM UTC
We are investigating an issue whereby some publishers are seeing reduced auction counts in their Manadge (TAP Programmatic Dashboard) dashboards. We have identified and are working on a solution which will fix the issue for data going forward. More information to come.
-
resolved Mar 19, 2026, 09:06 AM UTC
This incident is now resolved. We have rolled out a fix which addresses the issue going forward. Please note that clients may see reduced auction counts for 12-18 March ET (inclusive) for any auctions where there were no bids.
Read the full incident report →
- Detected by Pingoru
- Mar 17, 2026, 08:45 PM UTC
- Resolved
- Mar 18, 2026, 12:10 AM UTC
- Duration
- 3h 25m
Affected: Omny Studio Management PortalOmny Studio Management PortalOmny Studio Management Portal
Timeline · 3 updates
-
investigating Mar 17, 2026, 08:45 PM UTC
We are investigating an issue causing delays in Omny analytics to display for some organizations. The issue is known to affect data from 2026-03-17 07:00 UTC onwards. This incident does not affect Podcast Metrics data. More information to come.
-
identified Mar 17, 2026, 10:12 PM UTC
A fix was applied to the data processing mechanisms. Data is currently starting to populate and catch up in the UI. More information to come.
-
resolved Mar 18, 2026, 12:10 AM UTC
Processing has caught up and data is now up to date in the UI. Data mechanisms are operating normally. This incident is considered resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 26, 2026, 01:58 PM UTC
- Resolved
- Feb 27, 2026, 04:30 PM UTC
- Duration
- 1d 2h
Affected: Manadge (TAP Programmatic Analytics Dashboard)Manadge (TAP Programmatic Analytics Dashboard)Manadge (TAP Programmatic Analytics Dashboard)
Timeline · 3 updates
-
investigating Feb 26, 2026, 01:58 PM UTC
We are currently investigating an issue impacting all deals created after February 11th, where the deal name is all in lowercase. More information to come
-
identified Feb 26, 2026, 05:06 PM UTC
We have identified the issue and are actively working on a permanent solution The deals that were created since Feb11th have been fixed. However, any new deals created will still be in lowercase and the fix is planned for early next week. More information to come.
-
resolved Feb 27, 2026, 04:30 PM UTC
This incident is now resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 23, 2026, 08:28 AM UTC
- Resolved
- Feb 24, 2026, 10:13 PM UTC
- Duration
- 1d 13h
Affected: Manadge (TAP Programmatic Analytics Dashboard)Manadge (TAP Programmatic Analytics Dashboard)Manadge (TAP Programmatic Analytics Dashboard)
Timeline · 2 updates
-
investigating Feb 23, 2026, 08:28 AM UTC
We are currently investigating an issue impacting the All Deals Troubleshooter (Beta). The number of Bid requests displayed is incorrect. In the meantime, for a proper troubleshooting, we recommend using My Dashboard- Deals Troubleshooting and Bids Dashboards. More information to come.
-
resolved Feb 24, 2026, 10:13 PM UTC
A fix has been applied. The correct values for Bid Requests are now being displayed in the All Deals Troubleshooter (BETA). This feature remains in the BETA phase of development. Should you encounter any bugs, we appreciate your collaboration in reporting them to our Support team. This incident is considered resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 08:06 AM UTC
- Resolved
- Feb 24, 2026, 10:30 PM UTC
- Duration
- 4d 14h
Affected: Live Streaming Delivery - West
Timeline · 3 updates
-
investigating Feb 20, 2026, 08:06 AM UTC
We are currently investigating a networking issue in our Vancouver datacenter and evaluating the potential impact.
-
monitoring Feb 20, 2026, 10:11 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 24, 2026, 10:30 PM UTC
This incident is considered resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 18, 2026, 04:13 PM UTC
- Resolved
- Feb 19, 2026, 09:00 AM UTC
- Duration
- 16h 47m
Affected: TAP UITAP UITAP API
Timeline · 3 updates
-
investigating Feb 18, 2026, 04:13 PM UTC
We are currently investigating an issue impacting station tags updating or creation process. A new station tag can be created, but stations cannot be added to the tag. More information to come.
-
monitoring Feb 18, 2026, 09:21 PM UTC
A fix has been deployed. Users should now be able to add stations to station tags normally. We will monitor the situation closely.
-
resolved Feb 19, 2026, 09:00 AM UTC
This incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Feb 11, 2026, 02:27 PM UTC
- Resolved
- Feb 13, 2026, 05:41 PM UTC
- Duration
- 2d 3h
Affected: Omny Studio Management PortalOmny Studio Management PortalOmny Studio Management PortalOmny Studio Management APIOmny Studio Management APIOmny Studio Management API
Timeline · 3 updates
-
investigating Feb 11, 2026, 02:27 PM UTC
We are investigating an issue impacting Omny Studio API and UI services. Some of our users can experience slowness and intermittent errors while navigating through the API/UI. More information to come.
-
monitoring Feb 11, 2026, 03:39 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 13, 2026, 05:41 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 05, 2026, 12:10 PM UTC
- Resolved
- Feb 05, 2026, 08:10 PM UTC
- Duration
- 8h
Affected: Programmatic Ad DeliveryProgrammatic Ad DeliveryProgrammatic Ad DeliveryTAP Programmatic UI (Yield-Op)TAP Programmatic UI (Yield-Op)TAP Programmatic UI (Yield-Op)
Timeline · 2 updates
-
identified Feb 05, 2026, 12:10 PM UTC
We have identify an issue impacting deals created with The Trade Desk. The synchronization will fail if the seller name, email and notes are empty. The team is already working on a fix that we expect to be released to production later today. More information to come.
-
resolved Feb 05, 2026, 08:10 PM UTC
Remediation measures have been put in place. Deal synchronization is back to working as expected with TTD. This incident is considered resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 03, 2026, 08:53 PM UTC
- Resolved
- Feb 03, 2026, 10:17 PM UTC
- Duration
- 1h 24m
Affected: Triton ConsoleTriton ConsoleTriton Console
Timeline · 2 updates
-
investigating Feb 03, 2026, 08:53 PM UTC
We have identified an issue making Stream Access Control no longer available in the Console UI despite users having appropriate permission levels. Our team is actively working on a hot fix. More information to come.
-
resolved Feb 03, 2026, 10:17 PM UTC
A fix has been applied. Stream Access Control should not be back to being accessible as normal. This incident is considered resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 02, 2026, 07:33 PM UTC
- Resolved
- Feb 03, 2026, 01:45 PM UTC
- Duration
- 18h 11m
Affected: TAP UITAP UITAP UITAP APITAP APITAP API
Timeline · 3 updates
-
investigating Feb 02, 2026, 07:33 PM UTC
Wee are investigating an issue preventing location targeting to be added or modified in a flight in TAP. Users are seeing errors when attempting to add or modify location-based targeting in TAP flights. More information to come.
-
monitoring Feb 02, 2026, 08:43 PM UTC
Mitigation measures have been applied. Functionality is back to normal in TAP UI. We will monitor the situation closely.
-
resolved Feb 03, 2026, 01:45 PM UTC
This incident is considered resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 02, 2026, 02:43 PM UTC
- Resolved
- Feb 02, 2026, 03:44 PM UTC
- Duration
- 1h
Affected: Live Streaming Delivery - EastLive Streaming Delivery - West
Timeline · 2 updates
-
investigating Feb 02, 2026, 02:43 PM UTC
We are currently experiencing an active network connectivity issue originating from an network provider. This issue is resulting in intermittent connectivity for stations operating on our streaming infrastructure from South America. Affected stations may experience intermittent connection instability, including brief service disruptions or degraded streaming performance. Due to our redundancy mechanisms, the listeners that were connected before the problem will remain connected and new connections will be redirected to another data center. More information to come
-
resolved Feb 02, 2026, 03:44 PM UTC
Our ISP partner has applied mitigation measures. Connectivity to our São Paulo location has been restored to normal operating parameters. This incident is considered resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 30, 2026, 03:44 PM UTC
- Resolved
- Feb 03, 2026, 12:13 PM UTC
- Duration
- 3d 20h
Affected: TAP UITAP ExploreTAP UITAP UITAP ExploreTAP Explore
Timeline · 4 updates
-
investigating Jan 30, 2026, 03:44 PM UTC
We are aware of an issue affecting the accuracy of data displayed in TAP Explore and TAP UI for flights that were created on January 30th. Users may notice that metrics and report outputs for these specific flights do not reflect the correct information. Our teams are actively investigating the root cause and working to resolve the data inconsistency as soon as possible. More information to come.
-
investigating Jan 30, 2026, 04:37 PM UTC
We are continuing to investigate the issue and found that it is also impacting pacing, which could result in certain flights delivering slightly more or less than expected. More information to come.
-
monitoring Feb 02, 2026, 07:26 AM UTC
A fix has been implemented on Friday around 4PM UTC. We are monitoring the results.
-
resolved Feb 03, 2026, 12:13 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 19, 2026, 02:52 PM UTC
- Resolved
- Jan 20, 2026, 06:02 PM UTC
- Duration
- 1d 3h
Affected: Podcast Metrics UIPodcast Metrics UIPodcast Metrics UIData Collection Services (LT / LC)Data Collection Services (LT / LC)Data Collection Services (LT / LC)
Timeline · 3 updates
-
identified Jan 19, 2026, 02:52 PM UTC
We are currently experiencing a data processing delay for podcasts being measured through Log Collection. The result of this processing delay will have the podcasts show as "N/A - Not Associated to a Program" in Podcast Metrics. We are working on mitigation measures. More information to come.
-
monitoring Jan 20, 2026, 03:58 PM UTC
Data processing for log collected podcasts has caught up to normal operating parameters. Users should now see much less occurrences of "N/A - Not Associated to a Program" in Podcast Metrics. We will continue to monitor the situation closely.
-
resolved Jan 20, 2026, 06:02 PM UTC
This incident is considered resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 15, 2026, 02:29 PM UTC
- Resolved
- Jan 15, 2026, 04:55 PM UTC
- Duration
- 2h 26m
Affected: Programmatic Ad DeliveryProgrammatic Ad DeliveryProgrammatic Ad Delivery
Timeline · 2 updates
-
investigating Jan 15, 2026, 02:29 PM UTC
We've gotten reports of deals with Bidswitch created since December that are not running as intended. Our teams are investigating the situation.
-
resolved Jan 15, 2026, 04:55 PM UTC
Only deals configured via BidSwitch with the “Ignore bidder seat” setting enabled in TAP UI were affected. We have disabled this setting, and delivery has resumed. This incident is now resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 13, 2026, 09:32 PM UTC
- Resolved
- Jan 15, 2026, 02:27 PM UTC
- Duration
- 1d 16h
Affected: TAP UITAP ExploreTAP UITAP UITAP ExploreTAP ExploreTAP Programmatic UI (Yield-Op)TAP Programmatic UI (Yield-Op)TAP Programmatic UI (Yield-Op)Podcast Metrics UIPodcast Metrics UIPodcast Metrics UIStreaming Metrics UIWebcast Metrics UIStreaming Metrics UIStreaming Metrics UIWebcast Metrics UIWebcast Metrics UIRoyalty Reporting Metrics UIRoyalty Reporting Metrics UI
Timeline · 3 updates
-
investigating Jan 13, 2026, 09:32 PM UTC
We are currently investigating issues with errors accessing or loading content in TAP, Metrics and Settings UI. More information to come.
-
monitoring Jan 13, 2026, 09:58 PM UTC
A fix has been applied. TAP UI, Metrics UI and Settings UI should now be loading content properly. We will be monitoring the situation closely.
-
resolved Jan 15, 2026, 02:27 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 06, 2026, 05:21 PM UTC
- Resolved
- Jan 06, 2026, 07:01 PM UTC
- Duration
- 1h 39m
Affected: TAP UITAP UITAP UI
Timeline · 2 updates
-
identified Jan 06, 2026, 05:21 PM UTC
We have identified the cause of a bug that is causing TAP UI to refuse valid tracking pixels. Users will encounter an error when attempting to add a tracking pixel to a creative. A hot fix is currently being worked on and should be deployed soon. More information to come.
-
resolved Jan 06, 2026, 07:01 PM UTC
A fix has been deployed. TAP should be back to properly validating tracking pixels. This incident is considered resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 31, 2025, 08:31 PM UTC
- Resolved
- Jan 01, 2026, 02:38 AM UTC
- Duration
- 6h 7m
Affected: Live Streaming Delivery - East
Timeline · 3 updates
-
investigating Dec 31, 2025, 08:31 PM UTC
We are currently investigating a network connectivity problem in our Montreal data centre. Listener and client impact should be minimal. Our team is working to restore network connectivity as soon as possible. More information to come.
-
identified Dec 31, 2025, 11:21 PM UTC
The problem has been found to be a faulty network switch. We are replacing the equipment. Impact on listeners should be minimal. More information to come.
-
resolved Jan 01, 2026, 02:38 AM UTC
The replacement equipment has been installed, configured and is online. This incident is considered resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 23, 2025, 08:36 AM UTC
- Resolved
- Feb 03, 2026, 03:29 PM UTC
- Duration
- 42d 6h
Affected: Live Streaming Delivery - South East & PacificLive Streaming Delivery - SouthSAM Broadcaster Cloud
Timeline · 4 updates
-
investigating Dec 23, 2025, 08:36 AM UTC
We are currently experiencing network connectivity issues originating from one of our network providers. This issue is resulting in intermittent connectivity for stations operating on our Los Angeles and Singapore streaming infrastructure. Affected stations may experience intermittent connection instability, including brief service disruptions or degraded streaming performance. More information to come.
-
identified Dec 23, 2025, 03:33 PM UTC
The issue has been identified to be a a cut in our provider's trans-pacific oceanic fibre line. Our service provider is planing for the repairs of the line. At the moment we do not have an ETA for the repairs but the provider is hinting at end of January. In the meantime, we are taking steps to mitigate the issue by moving traffic to other routes. Clients having listeners in Asia (Singapore) with services hosted in North America (such as SAM Broadcaster) will experience momentary service drops as we attempt to move traffic to other locations and routes. More information to come.
-
identified Jan 05, 2026, 06:29 PM UTC
Our third-party carrier has advised that the cable repair is scheduled to commence on January 23rd, 2026. It is expected to be completed by 1 February 2026. More information to come.
-
resolved Feb 03, 2026, 03:29 PM UTC
Our provider has completed repairs on their trans-pacific oceanic fibre line. This incident is considered resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 19, 2025, 03:08 PM UTC
- Resolved
- Jan 07, 2026, 03:03 PM UTC
- Duration
- 18d 23h
Affected: Podcast Metrics UIPodcast Metrics UIPodcast Metrics UI
Timeline · 4 updates
-
investigating Dec 19, 2025, 03:08 PM UTC
We are investigating an issue preventing users from creating, modifying and sharing new lineups in Podcast Metrics Lineups. Existing lineups, manual reporting in Explore as well as Saved Queries are unaffected. Only the functions in "Management" are affected. More information to come.
-
identified Dec 23, 2025, 03:31 PM UTC
The issue is still being investigated by our development team. Due to the holiday code freeze, a fix is expected to be applied early January. More information to come.
-
monitoring Jan 07, 2026, 12:07 PM UTC
A fix has been deployed and we are monitoring the results.
-
resolved Jan 07, 2026, 03:03 PM UTC
This incident is considered resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 18, 2025, 08:43 AM UTC
- Resolved
- Dec 19, 2025, 12:36 PM UTC
- Duration
- 1d 3h
Affected: Programmatic Ad DeliveryProgrammatic Ad DeliveryProgrammatic Ad Delivery
Timeline · 3 updates
-
investigating Dec 18, 2025, 08:43 AM UTC
We are currently investigating an issue impacting deals synchronization with DV360. More information to come.
-
monitoring Dec 18, 2025, 10:17 AM UTC
A fix has been implemented and we are monitoring the results. Only newly created deals with DV360 and Xandr were impacted. More information to come.
-
resolved Dec 19, 2025, 12:36 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 15, 2025, 04:24 PM UTC
- Resolved
- Dec 17, 2025, 07:47 AM UTC
- Duration
- 1d 15h
Affected: Manadge (TAP Programmatic Analytics Dashboard)Manadge (TAP Programmatic Analytics Dashboard)Manadge (TAP Programmatic Analytics Dashboard)
Timeline · 3 updates
-
investigating Dec 15, 2025, 04:24 PM UTC
We are investigating an issue where dashboard data is not loading in Manadge. More information to come.
-
monitoring Dec 15, 2025, 04:31 PM UTC
Services were restarted and data is once again available. We will be monitoring the situation closely.
-
resolved Dec 17, 2025, 07:47 AM UTC
This incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Dec 06, 2025, 01:19 PM UTC
- Resolved
- Dec 06, 2025, 04:57 PM UTC
- Duration
- 3h 37m
Affected: Live Streaming Delivery
Timeline · 4 updates
-
investigating Dec 06, 2025, 01:19 PM UTC
We are investigating an issue with our streaming servers in Europe which is preventing streams to be delivered to listeners. Our team is working to redistribute streaming to other locations and unaffected Media Gateway instances. More information to come.
-
investigating Dec 06, 2025, 01:51 PM UTC
The issue was affecting only new connections to the Media Gateways. In order to apply corrective measure to the affected MGs, we need to move all traffic from them to healthy servers. This will cause a disconnection to existing listeners, who should reconnect quickly to new healthy instance. More information to come.
-
monitoring Dec 06, 2025, 03:18 PM UTC
Our team has applied mitigation measures and service is back to normal. The issue seems to have been cause by an unexpected situation in the MediaGateway when handling TimeShift mounts. We are looking into ways of handling such situations so they don't cause a cascading effect in the future. More information to come.
-
resolved Dec 06, 2025, 04:57 PM UTC
After several hours of monitoring, we confirm the issue has been fully resolved and all services are operating normally. Our preliminary analysis indicates the problem was caused by a combination of factors related to Timeshift technology, including a software bug, a race condition, and a configuration issue. These factors led certain servers to stop accepting new connections while maintaining existing listener sessions. Immediate corrective actions were implemented, and additional follow-up measures are scheduled for early next week to prevent recurrence. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Dec 03, 2025, 01:49 PM UTC
- Resolved
- Dec 10, 2025, 07:02 PM UTC
- Duration
- 7d 5h
Affected: Royalty Reporting Metrics UIRoyalty Reporting Metrics UIRoyalty Reporting Metrics UI
Timeline · 4 updates
-
investigating Dec 03, 2025, 01:49 PM UTC
Good morning. We are currently investigating an issue affecting the Royalty reports. Performance results are not appearing from November 19th onward. We will provide an update as soon as we have more information.
-
identified Dec 04, 2025, 07:33 PM UTC
The issue has been identified. Our team is working to restore the missing data. More information to come.
-
monitoring Dec 08, 2025, 09:23 PM UTC
A fix has been applied, Data has been restored. Royalty Reporting data should be available under normal data delays. We will monitor the situation closely.
-
resolved Dec 10, 2025, 07:02 PM UTC
This incident is considered resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 24, 2025, 02:01 PM UTC
- Resolved
- Nov 25, 2025, 02:12 PM UTC
- Duration
- 1d
Affected: TAP Reporting - Inventory Availability ForecastingTAP Reporting - Inventory Availability ForecastingTAP Reporting - Inventory Availability Forecasting
Timeline · 3 updates
-
identified Nov 24, 2025, 02:01 PM UTC
Avails/Forecasting UI are currently not reflecting flights created or updated since Friday Nov 21. A fix is in progress, and updates will resume once processing is restored. The team is focus on solving the problem, we will keep you posted on progress.
-
monitoring Nov 25, 2025, 08:55 AM UTC
The fix has been implemented and we are monitoring the results.
-
resolved Nov 25, 2025, 02:12 PM UTC
This incident is now resolved.
Read the full incident report →