haivision/srt

Secure, Reliable, Transport

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 53 minutes ago
Added to GitGenius on September 19th, 2026
Created on April 6th, 2017
Open Issues & Pull Requests: 365 (+0)
GitHub issues: Enabled
Number of forks: 942
Total Stargazers: 3,603 (+0)
Total Subscribers: 143 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 26.7 hours
Mean response time: 68.2 days
90th percentile: 213.3 days
Tracked items: 156

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 39% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "Type: Question" is answered fastest, typically in about 2 hours, while "[API]" waits about 4 weeks. Only 41% of issues opened in the past year have been closed. Three people close 78% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 80
New in 7 days: 0
Closed in 7 days: 10
Avg open age: 554 days
Stale 30+ days: 68
Stale 90+ days: 67

Recent activity

Opened in 7 days: 0
Closed in 7 days: 10
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Type: Bug (75)
  • [core] (69)
  • Type: Maintenance (42)
  • Type: Question (31)
  • Type: Enhancement (23)
  • [API] (23)
  • [build] (12)
  • Required: User help (7)

Detailed Description

SRT is a transport protocol for ultra low-latency live video and audio streaming over unreliable networks.

SRT addresses the challenge of delivering high-quality video streams across congested or noisy networks where packet loss and jitter are common. The protocol maintains constant end-to-end latency by dynamically adapting to real-time network conditions between endpoints. It employs AES encryption to protect media payloads and uses Automatic Repeat reQuest as its primary error recovery mechanism, where receivers alert senders to retransmit missing packets. The tool also supports Forward Error Correction and Connection Bonding for additional stream protection and failover capabilities, reducing the need for buffering on the receiver side.

SRT suits organizations building live streaming workflows where sub-second latency and reliability are critical, particularly for contribution and distribution endpoints in video production. The protocol is appropriate for scenarios involving severe packet loss or bandwidth fluctuations where traditional transport methods fail. It works as an open-source implementation with an Internet Draft specification and an established community of users.

The project maintains active development with regular engagement in its community channels and ongoing refinement of its core protocol implementation and supporting tools.