Challenge the net:
3d Traceroute
 
Get your
free beta
  
Freeware: 2.4.39.2 Release date: 2008-03-24
PRO: 2.4.39.2 Release date: 2008-03-24
Freeware Beta 2.3.33.56 Release date: 2008-01-06
PRO Beta 2.3.34.58 Release date: 2008-03-07
 
3d Traceroute FREE
3d Traceroute PRO
  Buy
be up to date
Fun Stuff
Links
  Outlook Spam Protection
  /0   56

"Day and Night" might be the admins most loved toy.

DaN does a simple task: collect all the traces. If the traces use the same route, it results in one column. If the route changes, a new column is added. So Day And Night is "route path in relation to time".

For the ease of use, the changes are colored:

next trace needs one more hop
212.74.74.169
pos1-1-kyle.NYC.router.COLT.NET
107 ms 351 ms 100 ms 806		  
  212.74.74.169
pos1-1-kyle.NYC.router.COLT.NET
110 ms 220 ms 110 ms 1

next trace needs one hop less
  212.74.65.53
pos1-0-scooby.FFM.router.COLT.NET
20 ms 111 ms 10 ms 2
212.74.65.53
pos1-0-scooby.FFM.router.COLT.NET
20 ms 351 ms 10 ms 201		  

no pattern detectable, but a change
212.74.88.18
pos-5-0-cr4.MUC.router.COLT.NET
21 ms 231 ms 10 ms 806		 212.74.88.13
pos-3-0-cr4.STR.router.COLT.NET
30 ms 231 ms 30 ms 1
212.121.154.89
cr1.fra.de.colt.net
19 ms 120 ms 10 ms 806		 212.74.88.9
pos-2-0-cr3.STR.router.COLT.NET
20 ms 120 ms 20 ms 1

 

A sample:
7 212.74.88.37
pos-6-0-cr4.BER.router.COLT.NET
11 ms 261 ms 0 ms 806		 212.74.88.37
pos-6-0-cr4.BER.router.COLT.NET
11 ms 261 ms 11 ms 1		 212.74.88.37
pos-6-0-cr4.BER.router.COLT.NET
10 ms 261 ms 10 ms 2		 212.74.88.37
pos-6-0-cr4.BER.router.COLT.NET
11 ms 261 ms 0 ms 201		 212.74.88.37
pos-6-0-cr4.BER.router.COLT.NET
5 ms 261 ms 0 ms 2
8 212.74.88.29
pos-7-0-cr3.MUC.router.COLT.NET
20 ms 120 ms 10 ms 806		 212.74.88.29
pos-7-0-cr3.MUC.router.COLT.NET
20 ms 120 ms 20 ms 1		 212.74.88.29
pos-7-0-cr3.MUC.router.COLT.NET
15 ms 120 ms 10 ms 2		 212.74.88.29
pos-7-0-cr3.MUC.router.COLT.NET
20 ms 120 ms 10 ms 201		 212.74.88.29
pos-7-0-cr3.MUC.router.COLT.NET
20 ms 120 ms 10 ms 2
9 212.74.88.18
pos-5-0-cr4.MUC.router.COLT.NET
21 ms 231 ms 10 ms 806		 212.74.88.13
pos-3-0-cr4.STR.router.COLT.NET
30 ms 231 ms 30 ms 1		 212.74.88.13
pos-3-0-cr4.STR.router.COLT.NET
20 ms 231 ms 20 ms 2		 212.74.88.13
pos-3-0-cr4.STR.router.COLT.NET
22 ms 231 ms 10 ms 201		 212.74.88.18
pos-5-0-cr4.MUC.router.COLT.NET
30 ms 231 ms 10 ms 2
10 212.121.154.89
cr1.fra.de.colt.net
19 ms 120 ms 10 ms 806		 212.74.88.9
pos-2-0-cr3.STR.router.COLT.NET
20 ms 120 ms 20 ms 1		 212.74.88.9
pos-2-0-cr3.STR.router.COLT.NET
15 ms 120 ms 10 ms 2		 212.74.88.9
pos-2-0-cr3.STR.router.COLT.NET
21 ms 131 ms 10 ms 201		 212.74.88.93
pos-11-0-cr1.FRA.router.COLT.NET
20 ms 131 ms 10 ms 2
11 212.121.154.2
cr2.fra.de.colt.net
22 ms 190 ms 10 ms 806		 212.74.88.5
pos-4-0-cr4.FRA.router.COLT.NET
20 ms 190 ms 20 ms 1		 212.74.88.5
pos-4-0-cr4.FRA.router.COLT.NET
15 ms 190 ms 10 ms 2		 212.74.88.5
pos-4-0-cr4.FRA.router.COLT.NET
22 ms 190 ms 10 ms 201		 212.74.88.81
pos-9-0-cr2.FRA.router.COLT.NET
15 ms 190 ms 10 ms 2
12 212.74.65.53
pos1-0-scooby.FFM.router.COLT.NET
21 ms 111 ms 10 ms 806		 212.74.65.61
pos1-3-mystery-machine.FRA.router.COLT.NET
20 ms 111 ms 20 ms 1		 212.74.88.85
pos-10-0-cr2.FRA.router.COLT.NET
20 ms 111 ms 10 ms 2		 212.74.88.85
pos-10-0-cr2.FRA.router.COLT.NET
20 ms 111 ms 10 ms 201		 212.74.65.53
pos1-0-scooby.FFM.router.COLT.NET
20 ms 111 ms 10 ms 2
13 212.74.74.169
pos1-1-kyle.NYC.router.COLT.NET
107 ms 351 ms 100 ms 806		 212.74.65.49
pos2-0-scooby.FFM.router.COLT.NET
20 ms 351 ms 20 ms 1		 212.74.65.53
pos1-0-scooby.FFM.router.COLT.NET
20 ms 351 ms 10 ms 2		 212.74.65.53
pos1-0-scooby.FFM.router.COLT.NET
20 ms 351 ms 10 ms 201		 212.74.74.169
pos1-1-kyle.NYC.router.COLT.NET
105 ms 351 ms 10 ms 2
14 212.74.74.161
pos1-3-kenny.NYC.router.COLT.NET
107 ms 220 ms 100 ms 806		 212.74.74.169
pos1-1-kyle.NYC.router.COLT.NET
110 ms 220 ms 110 ms 1		 212.74.74.169
pos1-1-kyle.NYC.router.COLT.NET
106 ms 220 ms 100 ms 2		 212.74.74.169
pos1-1-kyle.NYC.router.COLT.NET
109 ms 221 ms 100 ms 201		 212.74.74.161
pos1-3-kenny.NYC.router.COLT.NET
105 ms 221 ms 100 ms 2
15 63.214.53.253
gige5-1-310.ipcolo2.NewYork1.Level3.net
108 ms 301 ms 100 ms 806		 212.74.74.161
pos1-3-kenny.NYC.router.COLT.NET
101 ms 301 ms 80 ms 1		 212.74.74.161
pos1-3-kenny.NYC.router.COLT.NET
110 ms 301 ms 80 ms 2		 212.74.74.161
pos1-3-kenny.NYC.router.COLT.NET
109 ms 301 ms 80 ms 201		 63.214.53.253
gige5-1-310.ipcolo2.NewYork1.Level3.net
100 ms 301 ms 80 ms 2
16 64.159.17.162
ae0-56.mp2.NewYork1.Level3.net
109 ms 291 ms 100 ms 806		 63.214.53.253
gige5-1-310.ipcolo2.NewYork1.Level3.net
110 ms 291 ms 110 ms 1		 63.214.53.253
gige5-1-310.ipcolo2.NewYork1.Level3.net
110 ms 291 ms 100 ms 2		 63.214.53.253
gige5-1-310.ipcolo2.NewYork1.Level3.net
110 ms 291 ms 100 ms 201		 64.159.17.162
ae0-56.mp2.NewYork1.Level3.net
100 ms 291 ms 100 ms 2
17 209.247.9.121
so-3-0-0.mp1.Seattle1.Level3.net
178 ms 371 ms 170 ms 806		 64.159.17.162
ae0-56.mp2.NewYork1.Level3.net
110 ms 371 ms 110 ms 1		 64.159.17.162
ae0-56.mp2.NewYork1.Level3.net
110 ms 371 ms 100 ms 2		 64.159.17.162
ae0-56.mp2.NewYork1.Level3.net
111 ms 371 ms 100 ms 201		 209.247.10.137
so-1-0-0.mp1.Seattle1.Level3.net
210 ms 371 ms 100 ms 2
18 64.159.16.3
gige9-0.hsipaccess1.Seattle1.Level3.net
178 ms 361 ms 170 ms 806		 209.247.9.121
so-3-0-0.mp1.Seattle1.Level3.net
170 ms 361 ms 170 ms 1		 209.247.10.137
so-1-0-0.mp1.Seattle1.Level3.net
245 ms 361 ms 170 ms 2		 209.247.9.121
so-3-0-0.mp1.Seattle1.Level3.net
179 ms 361 ms 170 ms 201		 64.159.16.3
gige9-0.hsipaccess1.Seattle1.Level3.net
200 ms 361 ms 170 ms 2
19 209.245.183.18
unknown.Level3.net
185 ms 570 ms 170 ms 806		 64.159.16.3
gige9-0.hsipaccess1.Seattle1.Level3.net
181 ms 570 ms 181 ms 1		 64.159.16.3
gige9-0.hsipaccess1.Seattle1.Level3.net
200 ms 570 ms 170 ms 2		 64.159.16.3
gige9-0.hsipaccess1.Seattle1.Level3.net
177 ms 570 ms 170 ms 201		 209.245.183.18
unknown.Level3.net
200 ms 570 ms 170 ms 2
20 216.122.94.9
nat-94-9.nameserve.net
197 ms 371 ms 170 ms 806		 209.245.183.18
unknown.Level3.net
190 ms 371 ms 10 ms 1		 209.245.183.18
unknown.Level3.net
205 ms 371 ms 10 ms 2		 209.245.183.18
unknown.Level3.net
188 ms 371 ms 10 ms 201		 216.122.94.9
nat-94-9.nameserve.net
210 ms 371 ms 10 ms 2
21 216.122.9.119
host04.hostweb.de
187 ms 361 ms 170 ms 806		 216.122.94.9
nat-94-9.nameserve.net
180 ms 361 ms 180 ms 1		 216.122.94.9
nat-94-9.nameserve.net
210 ms 361 ms 180 ms 2		 216.122.94.9
nat-94-9.nameserve.net
197 ms 361 ms 170 ms 201		 216.122.9.119
host04.hostweb.de
210 ms 361 ms 170 ms 2
22 216.122.9.119
host04.hostweb.de
190 ms 211 ms 190 ms 1		 216.122.9.119
host04.hostweb.de
210 ms 211 ms 180 ms 2		 216.122.9.119
host04.hostweb.de
189 ms 291 ms 170 ms 201

(Notice: this is a condensed trace, time entries are missing.)

How to create it?

First setup 3d Traceroute for a 'long periode' trace. Don't forget to check 'autolog traces' and set the 'new trace' time to a reasonable value (60 seconds?).

After one or more days you will have a huge playback-file that can be analyzed.

You can stop the trace now. Even finishing 3D Traceroute is no problem (reload the trace via Playback (F8)).

Switch to "as list", click the 'day and night' button.

Thats it.


Day and Night Trace options

Traces can be saved and loaded. They are considerable smaller than Playback-logs and load much faster.

The grid allows drag and drop of columns to exchange positions.

  
Impressum
quittengelb