iSpot logo

Is iSpot Down?

SaaSLive status, outages, and incident history

No. iSpot is up right now.

Every monitored iSpot system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · 60s while moving

Know the moment iSpot breaks

iSpot is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official iSpot status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

iSpot Component Status

The main iSpot systems on this page. All 23 are operational right now.

23operational
DaaS Data Availability » CIULD
Operational
DaaS Data Availability » IULD
Operational
DaaS Data Availability » Telecast Ratings
Operational

20 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Dashboard/Site Availability » Creative Assessment, Dashboard/Site Availability » DR1VE, Dashboard/Site Availability » iSpot Analytics, Dashboard/Site Availability » Platf0rm, Dashboard/Site Availability » Website, Key KPIs » Airings, Key KPIs » Attention, Key KPIs » Final Spend, Key KPIs » Frequency, Key KPIs » Initial Spend, Key KPIs » Lift, Key KPIs » Linear Conversions, and 8 more.

See all of them free

Component statuses may change independently during partial outages.

Recent iSpot Outages & Incidents

Incident history from the official iSpot status page, including resolution updates.

Processing Delay 9/11-9/13Resolved Sep 14, 2026 · 94h 22mResolved

Resolved: iSpot Data Processing Delay The recent data processing delays have been fully resolved. Both the data backlog and the associated metadata repopulation are complete, and reporting is now current across dashboards and API. No data was lost at any point — the issue caused a temporary processing delay, not data loss. Impacted and now resolved: Event dates: September 11–13 Metrics: OTT Impressions, OTT Conversions, and Linear Conversions Impacted metadata is now resolved and functional as well All of the above are fully repopulated and current in dashboards and API. What you need to do: Nothing for dashboard users — figures have updated automatically. If you pulled data via API or export during the affected window (Sept 11–13), we'd recommend re-pulling those dates to capture the final figures. What we've done to prevent recurrence: Pipeline modernization: A complete rewrite of the affected pipeline was already underway and is targeted for completion within the next 60 days, providing a more scalable and resilient foundation. Additional capacity: Increased capacity and throughput on the affected component to improve stability while the replacement is completed. Active oversight: Our on-call team is monitoring the pipeline around the clock, including weekends, while these safeguards remain in place. Enhanced monitoring & alerting: Added hourly monitoring of data delivery, volume, and quality, with alerts calibrated for expected daily and seasonal patterns to catch issues sooner. We appreciate your patience, and please reach out with any questions. --- [2026-09-17T10:01:21.417-07:00] (identified) Update: Processing Delay 9/11–9/13 (OTT Impressions & Conversions, Linear Conversions) Overall Status: Resolved (Minor Reporting Detail Pending) Data Backlog Resolved All delayed measurement data for September 11–13 has been reprocessed and loaded. Zero data was lost. OTT Impressions & Conversions: Reprocessing complete; data loaded. Linear Conversions: Reprocessing complete; data loaded. Linear Impressions / OTT & Linear Lift: Unaffected. Current Focus: Metadata Repopulation Core numbers are fully verified, but metadata fields for September 11 (and limited records for September 12) are partially incomplete. What is accurate: Top-line impression and conversion totals are 100% complete and accurate. What is impacted: Granular reports filtered by campaign, creative, publisher, or placement ID may show missing details for 9/11–9/12. Next Steps: We are working on a fix to repopulate the missing metadata and will provide a correction timeline shortly. --- [2026-09-16T13:56:18.616-07:00] (identified) Status update on the delayed measurement data for September 11–13. No data was lost.     - OTT Impressions & Conversions: Reprocessing nearly complete; final load is taking longer than anticipated. Estimated sometime tomorrow (9/17), with the goal of completion by morning.   - Linear Conversions: Reprocessing nearly complete; final load is taking longer than anticipated. Estimated sometime tomorrow (9/17), with the goal of completion by morning.   - Linear Impressions / OTT & Linear Lift: No impact   We expect these dates to be fully restored in the dashboard and API sometime tomorrow, with the goal of morning, and will confirm once complete. --- [2026-09-15T09:48:30.390-07:00] (identified) Update: Processing Delay 9/11–9/13 (OTT Impressions & Conversions, Linear Conversions)   Status update on the delayed measurement data for September 11–13. No data was lost.   - OTT Impressions & Conversions: Reprocessing nearly complete; final load begins this afternoon/evening   - Linear Conversions: Reprocessing nearly complete; final load begins this afternoon/evening   - Linear Impressions / OTT & Linear Lift: No impact   We expect these dates to be fully restored in the dashboard and API by tomorrow morning, and will confirm once --- [2026-09-14T14:26:04.304-07:00] (identified) We identified a processing delay affecting pixel-based measurement data for event dates September 11-13. Not data was lost - the events were captured, and reprocessing is in progress to restore the affected impression and conversion data. Current Status: OTT Impressions & Conversions: Delayed for Sept 11-13; reprocessing in progress Linear Conversions: Delayed for Sept 11-13; reprocessing in progress Linear Impressions: No impact OTT & Linear Lift: No Impact We expect these dates to be fully repopulated in the dashboard and API within the next 48 hours and will confirm status as we progress.

iSpot Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a iSpot incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 5 days with incidentsSep 25

Live iSpot Outage Reports

Problems reported by engineers using iSpot. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No iSpot problems reported yet.

Something wrong with iSpot on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About iSpot

Is iSpot down? iSpot reports live availability for 26 components at status.ispot.tv, among them Airings, iSpot Analytics and Media Measurement. Track iSpot outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

Over the past 30 days, PulsAPI has measured iSpot uptime at 100.00%. Response times, incident history, and SLA tracking for iSpot are available on the PulsAPI dashboard.

iSpot Status FAQ

Is iSpot down right now?

The verdict at the top of this page comes from the latest poll of the official iSpot status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if iSpot is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until iSpot recovers.

How do I check iSpot uptime history?

PulsAPI tracks iSpot uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever iSpot changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect iSpot outages?

PulsAPI reads the official iSpot status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual iSpot components?

Yes. PulsAPI monitors 23 individual iSpot components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when iSpot goes down?

Yes. Create a free account and subscribe to iSpot: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with iSpot to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot iSpot problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor iSpot?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so iSpot plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track iSpot with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services