[myastesting] Re: myAS alarm (fwd)

[Maximo Alves <]

Hey Paolo,

On Tue, Jul 08, 2003 at 07:58:52AM +0200, Paolo Moroni wrote:
>    Good morning. Last night I received the e-mail alarm I had expected.
> This is several days after the alarm situation had been artificially set
> up, so I am wondering whether the delay is - as I believe - an effect of
> the service still being developed. If not, the usefulness of the alarm
> is obviously much lower. Please let me know at your best convenience.
> Regards,
>                                                    Paolo

The delay is an effect of the service still being developed and currently
only processing data from RRC03(AMS-IX). In your particular case, the prefix
128.142.0.0/16 wasn't seen(by rrc03) during the first days of July so this 
is why the alarm message was several days delayed.   

We are now working on a new version that will in the future process data from 
all RRC's. This version also will have a much shorter response time sending
alarm messages shortly after the BGP announcements are seen on the 
Internet.

Regards,

Maximo.


> ---------- Forwarded message ----------
> Date: Tue, 8 Jul 2003 04:17:20 GMT
> From: MyAS.project@localhost
> To: Paolo.Moroni@localhost
> Cc: maximo@localhost
> Subject: myAS alarm
> 
> Dear moroni,
> Account: 513
> 
> The following announcements conflicted with your configuration and
> have triggered the alarm events below. You can find more information
> looking at www.ris.ripe.net/myas/
> 
> ORIGIN alarm:
> 
> 1 - Configured prefix: 128.142.0.0/16
> Alarm details:
>   Prefix       -    Peer        - Announcing AS - Time it first occurred  - RRC
> 128.142.0.0/16  -  193.148.15.99  -  1297  -  Tue Jul  8 02:48:25 2003  -  rrc03
> 128.142.0.0/16  -  193.148.15.97  -  1297  -  Tue Jul  8 02:48:24 2003  -  rrc03
> 
> Best regards
> myAS