The short answer
Use a dated timeline and keep MizuCue in the foreground while the problem happens. Note the local time and timezone, connection type, what stopped, and whether another device saw the same issue. MizuCue records this iPhone's connection state and whether the Wi-Fi router and selected internet destinations responded. These observations cannot prove which provider or service caused the drop.
Write down the conditions
Start with the details that disappear after a connection recovers. Use the actual clock time and timezone for the first symptom and recovery, and name the connection that was active, such as Wi-Fi or Cellular. Write what stopped working: one website, one app, calls, video, or the whole connection.
- Record the start time, recovery time, and any repeated drop times.
- Note the active connection type and whether you moved between Wi-Fi and Cellular.
- If another device is available, check it during the same window. A second device can help distinguish one service from a broader observed issue, but it is not proof of the cause.
Keep a foreground record
Open MizuCue and look at Status while you troubleshoot. Status summarizes what this iPhone can currently observe, including the phone, the Wi-Fi router when it is directly visible, and selected internet checks.
- Leave MizuCue open in the foreground while you wait for the next interruption. Live History begins forming after the first measured checks.
- When the problem appears, note what stopped and the time shown on the iPhone. Keep the session running through recovery when you can.
- Do not expect recording to continue after switching to another app or sending MizuCue to the background. iOS may suspend the app, so a later gap can be unmeasured.
Read the measured window
Open History after the session and inspect the same time range. Look for response times, interruptions, connection changes, and which layer needed attention. A gray or unmeasured period means MizuCue did not record a check during that time. It is a coverage gap, not a recorded outage.
Compare the MizuCue timeline with your notes and any second-device observation. One selected destination failing while other checks respond can point to a narrower observed problem. Several checks changing together can show a broader observed interruption. Neither pattern establishes that a provider, router, device, DNS service, or website is at fault.
Live Status and the latest hour of History are free. An annual subscription unlocks longer retained History and report export when you need to preserve more context.