When you receive a notification that the site is unavailable, open the URL it identifies and check whether the problem is still occurring. Then give the technical contact the time, URL, and result of your check. The notification helps you start investigating, but does not explain the cause by itself.
If you read the message several hours later, the site may already have recovered. Still, record the time of the event: you will need it to investigate the cause of a recurring outage. Record the current status separately from the earlier error.
Check the URL, time, and current response
Find the site, check time, and reported result in the event. Do not confuse the time of the observed outage with the time you received the email or opened Telegram.
Open the same URL in a browser. Then check the homepage and one important page—for example, a catalog or a service booking page. If the homepage works but a section does not, say so explicitly. Saying “the whole site is down” only broadens the search without evidence.
If possible, try again using a different connection, such as a mobile network instead of office Wi-Fi. Record the conditions and result; two attempts do not establish the cause, but they show where the problem recurs. The meaning of different results is covered in the uptime monitoring guide.
Send the technical contact a concise report
A few details are enough for the first message. Here is a filled-in example for reference:
Сайт и адрес: example.ru, /catalog.
Событие reChecker: ошибка ответа 04.10 в 10:05 МСК.
Проверка владельца: в 10:12 каталог не открылся через офисную и мобильную сеть.
Другие страницы: главная открывается; форму заказа не проверяли.
Последнее известное изменение: каталог опубликован в 09:40.
Просьба: проверить текущий ответ и записи сервера; сообщить следующий шаг и время ответа.If you do not know what changed most recently, do not guess. Include the exact error text or a screenshot with personal information removed. There is no need to prepare a lengthy report while users are still experiencing the problem.
Send the details to the designated technical contact: your hosting provider or developer, depending on who maintains the site. If you need to turn the issue into a planned task, use the developer ticket template.
Assign one person to collect updates
Record who has taken the issue and when the next update is expected. If both the hosting provider and developer are involved, have one person collect their responses and keep track of which changes are already being made.
Do not blame the hosting provider based on a single event. An update that happened around the same time is also just a lead to investigate. A specialist must confirm the cause by checking the site's state, code, or server logs.
Do not change settings at random based on several suggestions in a chat. Changing addresses, deleting files, and reverting to an older version all at once can make recovery more difficult. If the technical contact suggests a temporary fix, ask what it addresses, which pages it affects, and how to check the result.
You can tell colleagues: “The catalog is not opening in our checks at 10:12 MSK. The developer has taken the issue, and we expect the next update at 10:30.” Promise customers a recovery time only after the technical contact confirms it.
Check recovery using the original URL
After you are told that the issue is fixed, open the same URL and repeat the action that exposed the problem. Check important pages on the main domain. If the problem affected a form, opening the homepage alone is not enough to close the task.
Review the next actual results in the site monitoring dashboard. A successful check confirms a response at that moment; it does not replace manually checking an order or verifying that a request was received.
Record the outcome: “At 10:42 MSK, the catalog opens on both networks, and a product can be added to the cart. We did not test order submission. The developer is still investigating the cause.” Save the ticket number and the change that was made. You can close the urgent issue after confirming recovery and leave the question of the cause as a separate task if you do not yet have an answer.