We can't test every router, ISP and operating system out there. You can. One email from Ilyes fixed the IPv6 test for everyone hitting the same bug - two days after he spotted the clue. (Psst - there's a bug loose on this page. Catch it three times.) The Hall of Fame Founding Bug Hunter How one email became a fix Oct 7 The clue Ilyes notices the IPv6 test passes on Android but fails on Windows - and that the two write the address differently. Ilyes notices the IPv6 test passes on Android but fails on Windows - and that the two write the address differently. Oct 9 The fix We confirm "::" and ":0:" were being treated as different addresses, dropping valid candidates. Fix ships. We confirm "::" and ":0:" were being treated as different addresses, dropping valid candidates. Fix ships. Oct 9 The retest Ilyes runs the test again on the same Windows PC. Correct result. Ilyes runs the test again on the same Windows PC. Correct result. Now The card First name in the Hall of Fame, and a test that works for everyone who hit the same bug. First name in the Hall of Fame, and a test that works for everyone who hit the same bug. You see what we can't We test on a handful of setups. Your router, ISP and operating system may be a combination we have never seen.

Half a sentence is enough "Fails on Windows, passes on Android" was all it took last time. You don't need to know why it's broken. A real person reads it No ticket bots. If your report leads to a fix, you are the first to know - and your name can go up here. What did you find? Even "this looks weird" is useful. The draft already asks the right questions - just fill in what you know. Preview your card Your email draft Subject: [NAT Checker] Bug report What did you do? What did you expect to happen? What happened instead? (a screenshot helps a lot) Your browser and local time are pre-filled so we can reproduce it - delete them if you like. Cards go up when a report leads to a change - and only with your OK, under the name you pick.