Back to public feed
Transparency Surface

Public vendor accountability

This surface turns report-outcome telemetry into a public transparency layer. It shows which integrations are active, how often submissions complete, and where friction still exists, without pretending that a submitted report automatically equals a takedown.

Vendor Accountability

Public reporting throughput by provider

Rolling 30-day submission telemetry across live integrations. Success rate excludes skipped and in-progress records so cooldowns and queued jobs do not distort provider performance.

Live Integrations
Vendors Active In 30d
Submitted In 30d
Blocked Or Failed
Provider
30d Success
30d Cases
Last Seen
Methodology

Success rate is calculated from submitted, blocked, and error outcomes only. Skipped cooldowns and processing states are excluded so the percentage reflects real provider handling rather than queue state.

Outcome meanings

Submitted means the platform completed a report attempt. Blocked means the vendor stopped the flow or demanded an unhandled condition. Error covers transport or integration failures.

Scope

This page shows provider-facing reporting telemetry, not downstream takedown proof. Domain case pages remain the source for registrar status changes and confirmed takedown timelines.