Every day at the same time, my internet dies for 1 minute. How do I investigate?
I&#x27;m actually surprised by all of the comments.  The community jumped right into solving OP&#x27;s problem and has largely ignored the OP&#x27;s original question of &quot;how could I begin investigating this?&quot;  Another variation of this question could be &quot;how do I troubleshoot complex network issues?&quot;<p>After 20 years of network&#x2F;system&#x2F;software engineering across a wide variety of network sizes and levels of complexity, I teach people the following method to troubleshoot complex network issues:<p>1.  Write down the symptoms that you&#x27;re seeing.  How do you <i>know</i> something is wrong?  What do you see happening?<p>2.  Draw a diagram that includes all of the components and nodes involved.  (this is hard)<p>3.  Develop some hypotheses that could be worth testing. (this is hard and highly variable based on knowledge&#x2F;experience)<p>4.  Establish a &quot;test plan&quot; that allows you to prove&#x2F;disprove the hypotheses while making <i>minimal</i> changes to the system.  Start from one source device and work your way out to the farthest component you identified in your diagram.  Start at the lowest OSI layer and work your way up.<p>5.  Methodically test components, step by step, along the diagram.<p>6.  As you test, record your results.  Add new hypothesis to the list as you gather more information but don&#x27;t start testing them right away!  You can develop a new test plan after you finish the first one that proves&#x2F;disproves your new hypotheses.<p>7.  Repeat all steps, adding new information, until you find a solution.<p>I know this seems like a lot of steps when you&#x27;re just troubleshooting a WiFi issue at home--it may be overkill.  However, this framework applies to that scenario or when you&#x27;re diagnosing any complex network issue.  You&#x27;ll learn more about the systems, protocols, and devices that truly make up the Internet than you could ever imagine.  Through repetition and experience, these steps will get easier and some of them can happen quickly and in your head.<p>To help you get started, here&#x27;s some info for steps 1, 2, and 3:<p>1.  From your post: &quot;3:40pm every day my wifi loses internet access. My devices remain connected to the network, but all traffic dies. Almost exactly 1 minute later everything is resumed&quot;<p>2.  Start your diagram off as an &quot;equipment string diagram&quot;.  This will include all physical devices between you and the Internet.  Along the way, you may need to modify the equipment string diagram to include &quot;virtual&quot; devices, network segments, various protocols&#x2F;servers, etc.  Your diagram should include at least the following items:<p><pre><code>  - Your laptop&#x2F;desktop.  If it&#x27;s happening to all devices, then pick one.  Identify your IP and MAC addresses
  - The WiFi access point that device is connected to.  Identify the IP and MAC addresses
  - Any switches, firewalls, modems, etc that connect from your WiFi access point to your Internet Service Provider (ISP) and their IP and MAC addresses.
  - The &quot;next hop&quot; from your modem into the ISP&#x27;s network.  You can use a cloud to represent the ISP&#x27;s network that you don&#x27;t know&#x2F;understand, but always identify the IP address of the device that your modem first reaches.  If you can find the MAC address (or other OSI Layer 2 address) as well, even better.
</code></pre>
That&#x27;s the equipment string between you and &quot;The Internet&quot;.  For now, you can ignore the complexity inside the ISP&#x27;s network and beyond.  You might have to add more of that later, but start small.<p>We know there are other components involved in making the Internet work that introduce complexity and can cause issues along the way.  Let&#x27;s list them on your diagram and identify what servers are used and where they might be located.<p><pre><code>  - DHCP (local to your network and also between your modem and ISP)
  - DNS (could be local to your network and often is a third party service either run by your ISP or not)
  - Encryption (VPNs, SSL certificates, network device clock settings, etc)
  - IP routing (what devices do IP routing?  Hint: all devices that operate at Layer 3, using IP, do IP routing--including your workstations)
</code></pre>
3.  Some hypotheses (some were identified in the comments):<p><pre><code>  - Is there a device in the equipment string that is rebooting every day?
  - Is DNS intermittently failing?
  - Is DHCP releasing&#x2F;renewing your IP address assignment?  This could be from your device -&gt; local DHCP server OR your modem -&gt; ISP DHCP server
  - Is there an upstream connectivity issue with your ISP?
  - Is your WiFi access point losing connectivity?</code></pre>