Choose acceptable routes, up to three visit dates and a party size. MachuPing checks official Machu Picchu availability and emails when a confirmed match returns. It never sells, holds or guarantees tickets.
Hi Product Hunt — I built MachuPing after seeing the same frustrating pattern: a traveller has fixed Peru dates, the official Machu Picchu calendar has no matching entry, and manually checking every route and date becomes a daily chore.
MachuPing monitors the official calendar for the acceptable routes, up to three visit dates and party size selected by the traveller. It sends an email only after a matching state is confirmed. The setup does not preselect an entry time or visitor category, so the alert hands the traveller back to the official portal to choose and verify those details. It is deliberately not a reservation: MachuPing does not sell, hold or buy tickets, and official checkout remains the source of truth.
The difficult part was not fetching a calendar. It was modelling uncertainty: a queue, timeout, incomplete response or provider error cannot honestly be called “sold out.” The monitor therefore separates confirmed unavailable, confirmed available and unknown states, suppresses duplicate alerts, and avoids promising that a slot will survive until checkout.
I would especially value feedback on the trust boundary. Is the no-resale, official-source positioning clear enough before a traveller pays for an alert?