Trace Route – request timed out

Hello,

I'm not familiar with CMD, Ping and Tracert.

This is only the case for certain websites. I can access the website, but I always get error_time_out from Chrome.
I need to brush chrome 2-3 times to get there.

With the Tracert I get this result below. Can someone tell me what these results mean?

Code:

  
  
  
  1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace completely.

Thanks for any help

Approach to timed events in a frame-like library – a matter of life (cycle) and death

I am working on an auxiliary library that should send data to a server at a certain interval, eg. 1 minute.

The idea is that the user of this library does not have to deal with inserting the event handlers, disposing, etc. Regardless of which app it uses, the help library should look after the app data, search for files, and post a server once a minute.

The library should send telemetry data to the server. A developer in the code states when to send some of the data – but I do not want to send it in this instance. Instead, I want to stack the requests and send them in an interval. Therefore, the data is first stored locally and sent to the server later.

I was thinking about using System.Timers.Timer for the job, but …
If the parent app quits or crashes, the timer is still there, triggering it On_Elapsed Event.

How would you implement this kind of functionality? Maybe something other than a timer?

The goals:

  • Null / minimal configuration for the developer using this framework
  • Send data stacked from time to time and not as soon as data is displayed
  • The application should specify an instance of a telemetry client class. However, more than one instance or more than one instance may be specified. I do not want dozens of timers running in the background.