Japan's Disaster Emergency Message Dial 171 and web171: a guide for English speakers
After a large earthquake in Japan, calls into the affected area jam as everyone tries to reach family at once. NTT, Japan's main phone company, then opens two message boards keyed to a phone number: a voice board, the Disaster Emergency Message Dial (171), and a text board on the web, web171. They let people leave and check "we're OK" messages without the call having to connect to the other person.
When it's available
The service opens when a disaster such as an earthquake makes it hard to get calls through. NTT announces the start and how it will operate on TV, radio and its website. Outside a disaster it is closed, except on practice days (below).
Recording a message
- Dial 171 and follow the prompts.
- Press 1 to record (or 3 to record with a PIN).
- Enter the phone number, including the area code. If you're in the disaster area, use your own home number; otherwise use the number of the person in the area you're trying to reach.
- Speak for up to 30 seconds after the beep.
Playing back
- Dial 171 and press 2 (or 4 with a PIN).
- Enter the same phone number with the area code.
- Messages play newest first. Press 8 to repeat one and 9 to skip to the next.
The details that matter
| What NTT East says | |
|---|---|
| Which numbers | Messages can be recorded only for fixed, mobile, PHS and IP phone numbers in the disaster area (generally designated by prefecture) |
| Phones you can use | Fixed lines, public phones, NTT's special public phones at evacuation centers; also mobile phones, but check with your carrier. Not rotary phones |
| Length and number | Up to 30 seconds per message; 1 to 20 messages per number (announced when the service opens) |
| How long kept | Until the service period ends, then deleted |
| Cost | No charge for calls through NTT East/West phone service; free from the special public phones at evacuation centers. Other carriers set their own call charges |
| Privacy | A PIN limits recording and playback to the people who know it |
| Language | Japanese only. NTT East says it has no plan to add English prompts |
Practice days
| When | Hours |
|---|---|
| The 1st and 15th of every month | 00:00 to 24:00 |
| First three days of the new year | Jan 1 00:00 to Jan 3 24:00 |
| Disaster preparedness and volunteer week | Jan 15 9:00 to Jan 21 17:00 |
| Disaster preparedness week | Aug 30 9:00 to Sep 5 17:00 |
Because the prompts are in Japanese, a practice run is the only way to know the rhythm before you need it.
web171: text, and reachable from overseas
web171 is a text message board on the internet. Messages are found using a phone number as the key, and can be checked from anywhere, including overseas, which makes it the better option for family abroad. Up to 10 email addresses can be registered to be notified automatically when a new message is posted.
A family plan in five lines
- The number everyone will use (a home landline in Japan, or one family member's mobile).
- What to say in 30 seconds: who, where you are, whether anyone is hurt, where you're going next.
- Where to meet if home is unusable.
- A relative outside the area who can relay news.
- A card in your wallet or go-bag with the steps above, in English.
Everyday
On the 1st or 15th of any month, try 171 and web171 with family in Japan, and agree whose number you'll use.
When it counts
When calls to the disaster area won't go through, you can still leave and hear 'we're safe' messages.
Sources and when we checked them
- NTT East, How to Record Messages, Disaster Emergency Message Dial (171) (checked 2026-10-31)
- NTT East, How to Play Back Messages (checked 2026-10-31)
- NTT East, Outline and Service System, Disaster Emergency Message Dial (171) (checked 2026-10-31)
- NTT East, Practice Guide, Disaster Emergency Message Dial (171) (checked 2026-10-31)
- NTT East, FAQ, Disaster Emergency Message Dial (171) (checked 2026-10-31)
- NTT, Web171 Disaster Message Board (checked 2026-10-31)
Spotted a mistake? Tell us through the contact form ("Report a mistake"). We check it, fix it, and log the change in Updates.