osrg/gobgp

BGP implemented in the Go Programming Language

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 2 hours ago
Added to GitGenius on September 16th, 2026
Created on September 14th, 2014
Open Issues & Pull Requests: 229 (+0)
GitHub issues: Enabled
Number of forks: 826
Total Stargazers: 4,110 (+0)
Total Subscribers: 109 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.1 days
Mean response time: 81.7 days
90th percentile: 169.7 days
Tracked items: 131

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Roughly one issue in five opened in the past year never receives a reply. 99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 56% of issues opened in the past year have been closed. Three people close 74% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 69
New in 7 days: 9
Closed in 7 days: 4
Avg open age: 578 days
Stale 30+ days: 55
Stale 90+ days: 54

Recent activity

Opened in 7 days: 7
Closed in 7 days: 3
Comments in 7 days: 1
Events in 7 days: 8

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.

Detailed Description

GoBGP is a Border Gateway Protocol implementation written in Go.

GoBGP solves the problem of needing a programmable, embeddable BGP stack for modern network infrastructure. Rather than relying on monolithic routing daemons, it provides BGP as a library and standalone daemon that can be integrated into applications or deployed as a network service. The implementation handles BGP protocol mechanics including route advertisement, path selection, and peer management while exposing programmatic interfaces for dynamic control and monitoring.

The tool suits organizations building software-defined networking solutions, network automation platforms, or custom routing applications where standard BGP daemons lack the flexibility or integration points needed. It works well in containerized and cloud-native environments where Go's deployment characteristics align with infrastructure tooling. Teams should adopt it when they need to embed BGP functionality directly into applications, require fine-grained control over routing behavior through APIs, or want to avoid the operational overhead of managing separate BGP processes.

The project maintains steady development activity with regular commits addressing bug fixes and feature enhancements. Pull requests receive consistent review and integration. The codebase shows active maintenance through ongoing updates to handle protocol edge cases and operational scenarios. Issue tracking demonstrates engagement with user-reported problems and feature requests, with responses and resolutions occurring throughout the development cycle.