-
Notifications
You must be signed in to change notification settings - Fork 5
Troubleshooting
Common issues and their solutions.
Install uv first:
# macOS/Linux
curl -LsSf https://astral.sh/uv/install.sh | sh
# Or via pip
pip install uvMonocle needs Rust installed:
# Install Rust if needed
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
# Then install monocle
cargo install monocleMake sure ~/.cargo/bin is in your PATH.
bgp-radar needs Go installed:
# Install Go (or use install-deps)
uv run bgp-explorer install-deps
# Or manually
go install github.com/hervehildenbrand/bgp-radar/cmd/bgp-radar@latestMake sure ~/go/bin is in your PATH.
BGPStream requires the C library first:
# macOS
brew install bgpstream
# Then Python binding
uv sync --extra bgpstreamOn Linux, you may need to build libBGPStream from source. See bgpstream.caida.org.
Set your API key:
# Option 1: Environment variable
export ANTHROPIC_API_KEY=your_key_here
# Option 2: .env file
echo "ANTHROPIC_API_KEY=your_key_here" > .env
# Option 3: CLI argument
uv run bgp-explorer --api-key your_key_here chatVerify your key at console.anthropic.com:
- Check the key is not expired
- Ensure you have credits/quota available
- Confirm you're using the correct key (not a test key)
RIPE Stat is occasionally slow or unavailable:
- Wait a few seconds and retry
- Check stat.ripe.net status
- The cache (5-minute TTL) reduces repeated failures
Globalping has rate limits:
- Wait between measurements
- Register for higher quotas at globalping.io
- Try with fewer probes or different locations
Some locations have limited probe availability:
> Ping 8.8.8.8 from Antarctica
No probes available in the specified location.
Would you like to try from a different location?
Try broader regions or different countries.
Refresh the data:
uv run bgp-explorer --refresh-peeringdb chatThis downloads the latest CAIDA dump.
Start monitoring first:
> /monitor start
Or check if bgp-radar is installed:
bgp-radar --helpThe bgp-radar binary wasn't found. Either:
-
Run
install-depsto install it:uv run bgp-explorer install-deps
-
Or specify the path:
uv run bgp-explorer --bgp-radar-path /path/to/bgp-radar chat
This is normal if nothing unusual is happening. To test:
- Check status:
/monitor status - Wait for natural events (can take minutes to hours)
- Try monitoring more collectors:
--collectors rrc00,rrc01,rrc10
The ASN might not exist or might have no announcements:
> What prefixes does AS999999 announce?
AS999999 is not announcing any prefixes, or the ASN does not exist.
Try searching by company name instead:
> Search for ASNs from Google
The prefix might not be announced globally:
- Check if it's a private prefix (RFC 1918, etc.)
- The prefix might be filtered by some networks
- Try a covering prefix if checking a more-specific
If a specific tool fails, Claude will note it and continue:
Error getting IXP presence: Connection timeout
Continuing investigation with available data...
This is normal graceful degradation.
-
High thinking budget: Lower it with
/thinking 4000 - Network latency: RIPE Stat and other APIs add latency
- Complex queries: Multi-step investigations take longer
- Clear conversation history:
/clear - Restart the session
- Use shorter conversations for simple lookups
Long outputs are summarized. For full data:
- Ask for specific items: "Show me the first 20 prefixes"
- Export to JSON:
/export output.json - Use
--output jsonfor full data
Ensure your terminal supports UTF-8 and ANSI colors:
# Check terminal settings
echo $TERM
echo $LANGTry a different terminal emulator if issues persist.
If you can't resolve an issue:
- Check for open issues: github.com/hervehildenbrand/bgp-explorer/issues
- Open a new issue with:
- Python version (
python --version) - OS and version
- Error message or behavior
- Steps to reproduce
- Python version (
- Installation - Verify installation steps
- Configuration - Check configuration options
- Contributing - Help improve BGP Explorer