This page is the escalation path for p2proxy. Try the order below — most issues are resolved at step 1 or 2 without anyone needing to get paged.

1. Self-serve

Search this help centre by symptom — the Troubleshooting matrix covers the common cases. The Configuration reference covers tuning.

2. GitHub Issues — bugs and feature requests

File at github.com/BitpingApp/p2proxy/issues. Triage SLA is 2 business days.

When opening an issue, include:

• p2proxy --version output
• OS + arch (uname -a)
• Your Config.yaml with the API key redacted
• Last 100 lines of logs with log_level: debug set
• For network issues: dig grpc.bitping.com and dig boot2.bitping.com output
• For perf issues: a scrape of http://localhost:9091/metrics taken while the problem was happening

A debug-bundle one-liner:

{
  p2proxy --version
  uname -a
  sed 's/BITPING_API_KEY=.*/BITPING_API_KEY=<redacted>/' Config.yaml
  echo "--- metrics ---"
  curl -s http://localhost:9091/metrics
  echo "--- logs ---"
  journalctl -u p2proxy -n 100 --no-pager 2>/dev/null || tail -n 100 ~/.local/state/p2proxy.log 2>/dev/null
} > p2proxy-debug.txt

Attach p2proxy-debug.txt to the issue.

3. Security vulnerabilities

Do not file public GitHub issues for security bugs. Email [email protected] — see SECURITY.md for the full disclosure policy.

4. Account / billing / API-key issues

Email [email protected] for anything related to your Bitping account, billing, or rotating API keys. Include the email on the account and (if applicable) the key prefix — never the whole key.

5. Enterprise / SLA / volume pricing

Email [email protected] or use the contact form on bitping.com.