Questions

It starts with a guess from your device's time zone, which needs no permission and sends nothing anywhere. If you share your location, your position is matched against country borders inside your browser, and that replaces the guess. You can always choose a country yourself from the button at the top of every page, and that choice wins: if your location later says you have crossed a border, the site asks before switching, because emergency numbers changing on their own would be worse than a one-tap question.

Each country's numbers carry a label saying how far they can be trusted. About fifty countries, including every EU member state, India, Nepal, the United States, Bangladesh, Pakistan and Sri Lanka, were checked against a government or official page, which is linked beside the numbers with the date it was checked. The rest come from Wikipedia's list of emergency telephone numbers, a well-maintained compiled list that is still not an official source, and are labelled 'confirm locally'. Where no numbers are known at all, the site says so rather than guessing.

Because the public data differs. Every country gets earthquakes from the USGS, multi-hazard alerts from GDACS, satellite detections from NASA, nearby hospitals from OpenStreetMap and a news search. Nepal also gets the government's incident record with verified casualty figures, district tables and a road advisory. India gets official warnings from the National Disaster Management Authority's SACHET feed, and the United States gets active alerts from the National Weather Service. The site says which of these it is showing for your country instead of making every country look the same.

Because they are counting different things. The figures on this site count individual incident reports filed to BIPAD, the Government of Nepal's disaster portal. That log undercounts mass-casualty disasters severely: across one entire monsoon it recorded 196 deaths, never more than seven in a day, while international press reported roughly 1,300 dead from a single flood. No feed this site can reach publishes the authoritative national toll. Treat these numbers as a floor and a guide to which districts are being hit, never as a national total. Press coverage is shown alongside them for that reason. Outside Nepal, no source available to the site counts casualties, so no death figures are shown at all.

Because no public feed publishes live road status for Nepal, and inventing one would be dangerous. BIPAD has fields for road and bridge damage and across 400 recent incidents every single one read zero. This site could infer closures from hazard proximity and it would look convincing, but a wrong safe route during a flood can send someone onto a washed-out road. Instead the Roads page names highways with a landslide or flood reported nearby, says clearly that it is not a closure list, and links to Traffic Police on 103, who have the real answer.

No. It aggregates public feeds: the USGS, GDACS run by the European Commission, NASA, the Government of Nepal's BIPAD portal, India's NDMA SACHET and the US National Weather Service. It is not operated by any of them and is not an official warning service. In an emergency, instructions from local authorities take precedence over anything shown here.

No. There is no account system and no user database, so there is nothing to breach. The distance between you and a hazard is calculated inside your own browser, against a list the server already sent, so the server is never told where you are. The one exception is the nearby-hospitals search: that needs a position, so your location is rounded to about one kilometre before it is sent and nothing is stored at either end.

The live view refreshes about every three minutes while it is open, and again whenever you return to it. Behind that, each source is polled on its own schedule: incident records every few minutes, press coverage every twenty minutes, road information every few hours. If a source fails, the page keeps the last good data and says so rather than showing a blank or a stale figure without warning.

That no source published a number, which is different from a source publishing zero. A blank death toll shown as 0 would be a lie told by formatting, so the two are always kept apart. Not reported means unknown; 0 means someone checked and there were none.

It is free on both. On Android you can install the app file directly from the install page. On iPhone, open the site in Safari, tap Share, then Add to Home Screen: that gives you the same app with offline support and alerts on iOS 16.4 and later. There is no paid tier and no App Store listing, because Apple charges 99 US dollars a year for the developer programme that TestFlight and the App Store both require.

Because in Nepal's incident record it kills more people than any other hazard. It is not dramatic and it rarely makes the news, but during the monsoon it is the leading recorded cause of death in that data, mostly at night in the Terai. The guidance page includes it for the same reason, and lists it first wherever snakebites are being reported.

The underlying data belongs to its publishers and each carries its own terms: BIPAD, SACHET, the National Weather Service, the USGS, GDACS and NASA are all public sources, emergency numbers marked as compiled come from Wikipedia under CC BY-SA 4.0, country borders come from Natural Earth, and OpenStreetMap data is available under the Open Database Licence. Please credit them rather than this site. For the code or for working together, get in touch.