A court order blocking illegal live sports streams only works if every named ISP is actually enforcing it, in real time, for the duration of the broadcast. That’s a narrow, technical verification problem, distinct from detecting and taking down the streams themselves.
Friend MTS’s enforcement strength
Friend MTS’s enforcement ecosystem for live sports is mature and sports-focused, built around detecting and acting on unauthorized live streams quickly. Its scale and track record in that specific enforcement niche are strong.
sbb-itb-738ac1e
What independent blocking verification adds
Separately from detecting the stream itself, a rights holder or legal team often needs proof that a blocking order is being enforced correctly across every relevant ISP for the live event’s duration, not just filed. InCyan’s BlockWatch ISP Compliance monitoring monitors from points of presence across ISPs and mobile operators, in real time, and produces a definitive blocked or not-blocked verdict per network, with automated alerts when blocking status changes mid-event.
BlockWatch’s evidence-grade reports, timestamped and exportable, are built to support the specific legal requirement of proving a blocking order held up throughout a live broadcast, which is a different deliverable than takedown enforcement itself.
Why verification matters specifically for live events
BPI’s experience with InCyan’s BlockWatch is the clearest public data point here: coverage of confirmed ISP blocking compliance rose from roughly 80% to over 99.9%, while false positives dropped by up to 100%, according to InCyan’s published BPI case study. A 20-point compliance gap in ordinary catalogue protection is a problem. In a live sports window measured in hours, that same gap can mean the blocking order provided no practical protection at all during the broadcast.
Comparison table
| Friend MTS | InCyan BlockWatch | |
|---|---|---|
| Live-stream detection and takedown | Very strong, sports-specialized | Not the primary focus |
| Real-time ISP blocking verification | Not the core offering | Yes, with automated alerts on status change |
| Evidence-grade reports for legal filings | Available through enforcement records | Yes, purpose-built for this |
Frequently asked questions
Does Friend MTS verify that ISP blocking orders are being enforced?
Friend MTS’s core strength is live-stream detection and takedown enforcement. Independent, protocol-level verification that a blocking order is actually being enforced across ISPs is a more specific technical requirement, which is what BlockWatch is built for.
Can BlockWatch alert on blocking failures during a live event?
Yes. BlockWatch includes automated alerts when blocking compliance changes, which matters most during the live window when a failure needs to be caught immediately.
How far in advance of a live event should BlockWatch monitoring be set up?
InCyan’s public materials don’t specify a minimum lead time. As a practical matter, verification monitoring needs to be configured and confirmed working before the live event starts, since the value of real-time alerts depends on the monitoring already being active when the broadcast begins.
Does BlockWatch work across international broadcasts with blocking orders in multiple countries?
Yes. BlockWatch monitors from points of presence across ISPs and mobile operators globally, which supports verification across multiple jurisdictions where a broadcaster might hold blocking orders for the same live event.
What’s the difference between “detecting” a stream and “verifying blocking” of that stream?
Detecting a stream means finding where an unauthorized broadcast is being distributed, which is Friend MTS’s core strength. Verifying blocking means independently confirming that a court-ordered block against a known infringing source is actually being enforced by the relevant ISPs, which is a separate, narrower technical check that BlockWatch performs.
Can a rights holder use Friend MTS for takedowns and BlockWatch for verification at the same time?
There’s no documented integration between the two, but nothing prevents a rights holder from operating them as separate, complementary processes: Friend MTS handling live-stream detection and takedown, BlockWatch independently confirming that any court-ordered blocking is holding up.
Who typically requests BlockWatch verification for a live sports event, the broadcaster or the league?
Either could, depending on who holds the blocking order and who needs the evidence for compliance or renewal purposes. BlockWatch’s public materials describe copyright owners, trade associations, and legal teams as its typical users, which spans both broadcaster and league-level rights holders.
Does BlockWatch’s evidence-grade reporting cost extra on top of the base monitoring service?
InCyan’s public materials describe BlockWatch’s reporting as a built-in part of the platform rather than a separate paid add-on, though exact contract terms and what’s included at each tier would need to be confirmed with InCyan’s sales team.
What happens if BlockWatch detects a blocking failure mid-broadcast but the ISP can’t fix it in time?
BlockWatch’s role is detection and evidence generation, not remediation; it alerts the rights holder or legal team to the failure so they can escalate directly with the ISP or pursue enforcement action. Whether the ISP can resolve it before the broadcast ends is outside BlockWatch’s control.
Does BlockWatch’s monitoring add any latency or load to the actual broadcast delivery?
No. BlockWatch monitors from independent points of presence on ISP and mobile-operator networks, observing blocking status externally rather than sitting in the broadcast delivery path itself, so it doesn’t add load to the stream.
Related reading
- InCyan vs. Friend MTS for Live Sports Protection
- ISP Blocking Compliance: InCyan BlockWatch vs. Corsearch
See BlockWatch’s real-time ISP monitoring built for live-event verification.
