Hello

If you would like to report a bug, send feedback, or offer help, please see the contact page.

Thank you to all supporters of the project!

Since 2015 ping.pe had seen tremendous growth. To support the project and to keep up with the load I re-wrote its code multiple times. It has been a fun challenge!

Questions and Answers

Q: How to help?

A: If you can donate a VM, please see the contact page.

Q: Why won't you add more VPS/Cloud endpoints, there are so many providers out there!

A: The purpose of ping.pe is to provide a diagnostic tool for network connectivity issues on IP transit level, where more does not equal better. The best way to diagnose route propagation and packet loss is to have endpoints single homed with major Tier 1 and Tier 2 providers.

Most VPS/Cloud providers are T3 multihomed networks (they have peering with multiple carriers), which reduces the diagnostic value they could potentially provide.

Q: I represent a T1/T2 provider and can donate a VM

A: If you can provide a VM with a single-homed connection to a T1/T2 IP transit provider, that would be helpful.

The required specs are:

Single-homed connection to a T1/T2 IP transit provider
2 GB RAM
2 Core CPU
15 GB Disk
OS: Rocky/Alma v9
Network: 10 Mbit uplink
IP: Static public IP is preferred, but NAT is OK, in which case I will only need 3 ports forwarded.

If this is something you can offer, please contact me: pingpebox@gmail.com

Cheers!