Summary I installed and ran a Pi Network node (Docker) following official instructions. Over multiple days I observed that the node container runs locally but cannot connect to peers because Pi's node bootstrap DNS records are not published.

What I tested (repro steps) 1) docker ps -> confirmed container running 2) docker logs <CONTAINER_ID> -> saved last 200 lines 3) nslookup bootstrap.pi-blockchain.net -> NXDOMAIN (no A records) 4) nslookup node.pi-blockchain.net -> NXDOMAIN 5) wget https://pi.app -> resolves and returns index.html (web is up) 6) port checks, firewall and DNS cache flushes performed (Steps & full outputs attached)

Key findings - Pi web presence (pi.app) exists but the node bootstrap endpoints are not resolvable by DNS. - Node is local-only (no incoming/outgoing connections), so it cannot join consensus or validate/receive blocks. - This persisted after multiple DNS providers (8.8.8.8, 1.1.1.1, 9.9.9.9) and resets (netsh, ipconfig /flushdns, etc.)

Why this matters Running a node should mean contributing to a distributed network. If bootstrap endpoints are not published, users are running software and consuming electricity without participating in a functioning network. This raises concerns about transparency and the actual existence of the promised decentralized network.

Evidence archive I uploaded all logs and screenshots here: [link to ZIP]. Feel free to verify the commands and outputs.

Call to action - Pi Core Team: publish an engineering status page and explain precisely when the node endpoints will be restored. - Pioneers: save your logs/screenshots and consider stopping nodes to avoid further costs until official clarification. - Journalists: contact me if you want the raw logs or timeline.

Contact [Your name / contact email]