microsoft/msquic

Cross-platform, C implementation of the IETF QUIC protocol, exposed to C, C++, C# and Rust.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 25 minutes ago
Added to GitGenius on September 14th, 2026
Created on October 26th, 2019
Open Issues & Pull Requests: 349 (+0)
GitHub issues: Enabled
Number of forks: 698
Total Stargazers: 4,777 (+0)
Total Subscribers: 119 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 17.2 hours
Mean response time: 69.7 days
90th percentile: 162.3 days
Tracked items: 601

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 3% of issues opened in the past year have never received a reply. 57% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "Area: Build" is answered fastest, typically in under an hour, while "ci-failure" waits about 5 days. 46% of tracked open issues have had no activity in three months. 61% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 250
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 689 days
Stale 30+ days: 232
Stale 90+ days: 198

Recent activity

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

Top labels

  • Area: Core (207)
  • feature request (103)
  • external (94)
  • Area: Testing (77)
  • Triaged (72)
  • ci-failure (66)
  • bvt (51)
  • Area: API (45)

Detailed Description

MsQuic is a cross-platform C implementation of the IETF QUIC protocol that exposes language bindings for C++, C#, and Rust.

QUIC addresses limitations of traditional TLS-over-TCP by encrypting all packets, enabling parallel streams of reliable and unreliable data, allowing application data exchange in the first round trip, improving congestion control and loss recovery, surviving client IP or port changes, and supporting stateless load balancing. MsQuic implements this protocol as a general-purpose library optimized for both client and server use cases, with particular emphasis on maximal throughput and minimal latency through asynchronous IO, receive-side scaling support, UDP send and receive coalescing, and kernel stack bypass via XDP.

Developers should choose MsQuic if they need a production-grade QUIC implementation with strong performance characteristics across multiple platforms. The library suits projects requiring high-throughput network communication, low-latency connections, or scenarios where clients may change network connectivity. The project provides comprehensive documentation covering platform support, building, testing, API usage, deployment, and diagnostics, along with sample applications for quick evaluation.

The project maintains active engagement with users through discussion forums and Discord channels. Development includes attention to performance measurement through a dedicated dashboard. The codebase receives contributions guided by documented contribution guidelines and maintains a curated list of issues suitable for new contributors.