Comments on: Internet speed decay -- We need a script!
REBOL Technologies

Comments on: Internet speed decay -- We need a script!

Carl Sassenrath, CTO
REBOL Technologies
11-Feb-2010 20:25 GMT

Article #0460
Main page || Index || Prior Article [0459] || Next Article [0461] || 10 Comments || Send feedback

Each month I've seen the Internet get slower and slower. The problem is not our local computers or even our internal networks. It's happening on the Internet side of our gateway/NATs... but could be just specific routes or destination servers. It's difficult to tell.

I've finally decided that I need to run a few network monitoring scripts on our servers. I think they can be quite simple, simply connecting to various other web servers (in the world of REBOL) and storing/averaging time differences. The script can be written in REBOL in less than a page. Perhaps when it connects to other servers, it could grab their timing info and store it as well.

For example, on the time-net.r script could run via cron and read via HTTP the time-data.r file from,, and various other servers. It then updates its own time-data.r file. (That way, by looking at the result for one server, I can see other server summaries as well.)

I'm hoping that someone in the REBOL community has already written such a script, so I don't have to write it myself. As you know, my todo list is overflowing.

I'm sure there are many other webmasters and IT people who might use such a script as well.

So, post a comment if you have such a script! We all thank you.



11-Feb-2010 13:10:43
I'd be willing to participate if you get one.
Allen K
12-Feb-2010 14:20:37
Hi Carl,

Here are couple of sites that monitor the health of the internet.

Carl Sassenrath
12-Feb-2010 18:02:15
Paul: ok, will let you know.

Allen: I use those... but, I need something more specific to the systems/servers we run.

13-Feb-2010 11:55:23
Carl, errr.... isn't this a low priority compared to say, R3?
Carl Sassenrath
13-Feb-2010 18:30:29
Maarten, precisely. That's why I'm asking you to write it. I figure you especially have one in your back pocket.

It's much needed here, because we're losing up to 50% of our packets in many of our connections. We've got to determine the source so we can get it fixed.

14-Feb-2010 12:50:21
Look here under measurement tools:

These are used by research network to track down problems (I have used iperf). As their network are state of the art, they have quite some subtle ones.


16-Feb-2010 3:08:31
delay: func [
   {computes the response time of web-servers = delay of the internet}
   host "IP-Address or host-url"
   /local p rc t
] [
  p: open join tcp:// host
  insert p "GET / HTTP/1.0^M^/^M^/" ; HTTP GET Request
  rc: copy p 
  close p
  t: now/time/precise - now/zone ; current GMT
  t - to time! fifth parse find/tail rc "Date:" none

example: delay ""

16-Feb-2010 11:30:17
Carl, for first diagnostics of packet loss, MTR is very helpful. WinMTR ( is a version for win32.
17-Feb-2010 13:43:42
I've used Charles with good results. Not sure how it compares to other tools mentioned here, though.
Carl Sassenrath
22-Mar-2010 21:41:58
Thanks for the suggestions.

Just a quick update... I've not had time to try any of the above tools but have done a few traceroutes during the problem periods... and found recently that the backbone routers were routing the packets more than 20 hops... and doing some pretty crazy routes. This looks like a much deeper problem than I had imagined.

Post a Comment:

You can post a comment here. Keep it on-topic.


Blog id:



 Note: HTML tags allowed for: b i u li ol ul font p br pre tt blockquote

This is a technical blog related to the above topic. We reserve the right to remove comments that are off-topic, irrelevant links, advertisements, spams, personal attacks, politics, religion, etc.

Updated 22-Feb-2024   -   Copyright Carl Sassenrath   -   WWW.REBOL.COM   -   Edit   -   Blogger Source Code