From matthew at ripe.net Tue Mar 9 20:05:17 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 9 Mar 2004 20:05:17 +0100 Subject: ANNOUNCEMENT: The RIS Project's Second Remote Route Collector in North America Deployed at the NYIIX (RRC11) Message-ID: <004a01c40609$76135fb0$300200c1@rockstar> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Apologies for duplicate mails] Dear All, The RIPE NCC is pleased to announce that the RIS Project's second Remote Route Collector in North America, RRC11, is now ready to peer with members at the New York International Internet Exchange (NYIIX). The collector is our first outside of the RIPE region to accept IPv6 peering sessions. RRC11, operational since February 2004, is located at TELEHOUSE's NYIIX 25 Broadway facility and is the twelfth collector to be deployed by the RIS. The RRC has an interface on the shared NYIIX fabric, running both IPv4 and IPv6, and collects routing information from all exchange members willing to peer with us. Many thanks to Alexander Koch and Tiscali for helping us out with transit. Our details: - ------------ - - Peering addresses: 198.32.160.99 (IPv4); 2001:504:1:0:0:A501:2654:1 (IPv6) - - Autonomous system: 12654 - - Policy: http://www.ripe.net/ris/rrc11.html - - Peering requests: * Email: rispeering at ripe.net * Web form at URL: http://www.ris.ripe.net/cgi-bin/peerreg.cgi The RIS is also present at MAE-West in San Jose and we are currently looking for more peers there. - - Peering information: http://www.ripe.net/ris/rrc08.html The Routing Information Service (RIS), which started as a modest RIPE NCC project in 1999, has gradually grown to over 300 IPv4 and IPv6 peers at now twelve data collection points in Europe, Japan and North America. Our mission is to collect BGP routing information over a function of time and make it available to the Internet community. In essence, this means devising tools that can help ISPs debug problems over time without being limited to a BGP view, and providing RIS raw data regarding the Internet's historical development. RIS Info: http://www.ripe.net/ris/ RIS Tools: http://www.ripe.net/ris/query.html Please send your comments to ris at ripe.net. Best regards, The RIS Team --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/ -----BEGIN PGP SIGNATURE----- Version: PGP 7.0.4 iQA/AwUBQE4VOMHkFbJe+GdoEQI2XACeMfEqCG4JioK3rlaQh7yZP4BEYiEAn2JI nygyTIa7qxAPQ7/UalgNLPK1 =nKut -----END PGP SIGNATURE----- From arife at ripe.net Fri Mar 12 15:16:26 2004 From: arife at ripe.net (Arife Vural) Date: Fri, 12 Mar 2004 15:16:26 +0100 Subject: ANNOUNCEMENT: New tool (RIB-stat) is available from RIS. Message-ID: <20040312141626.GM9335@ripe.net> Dear All, In collaboration with the Technical University of Munich, we are pleased to make available a new experimental tool, RIB-stat v. 1.0, on the RIS web site. This tool allows you to reconstruct the RIB table at any arbitrary point in time. It does so by taking the RIB dump closest to the desired time, then apply all BGP updates collected by the RIS up to the desired time retroactively. A possible application for this tool is to understand routing problems, with this tool one can reconstruct the RIB shortly before and after a routing problem started. By comparing the RIB's, one can find out which BGP update(s) triggered the problem. This tool is a prototype written in Perl. Depending on the number of BGP feeds, BGP activity and RRC, it can take 30 minutes to apply 8 hours of BGP updates to a RIB. We expect that it can be speeded up considerably by rewriting it in a compiled language. Before doing so, we would like to have some feedback on whether you consider a tool like this useful and expect to use it in daily operations. The code can be downloaded from http://www.ris.ripe.net/source/RIB-stat-1.0.tar.gz The file RIB-stat.pl contains the actual code, the file README an example on how to use it. Please send your feedback and comments to ris at ripe.net. Kind regards, RIS Team From arife at ripe.net Mon Mar 22 17:34:10 2004 From: arife at ripe.net (Arife Vural) Date: Mon, 22 Mar 2004 17:34:10 +0100 Subject: NOTIFICATION: Session resets on RRC03 on Tuesday, 23/03/04 between 09:00am and 12:00pm CET. Message-ID: <20040322163410.GC6204@ripe.net> Dear RIS-users, As part of the migration at AMS-IX infrastructure, there will be a few session resets on RRC03 at 23rd of March, 2004 CET between 09:00am and 12:00pm. You will notice those session resets on the size of rawdata files. Rawdata files will be bigger than usual. If you do any processing on RRC03 rawdata files, it would take longer. Or if you do some analysis by using RRC03 rawdata, it would be good to keep in mind those session resets. Kind regards, Arife From matthew at ripe.net Tue Mar 23 18:51:32 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 23 Mar 2004 18:51:32 +0100 Subject: ANNOUNCEMENT: RIPE NCC's RRC03 Ready to Peer with GN-IX Members Message-ID: <003601c410ff$7a49fa70$300200c1@rockstar> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Apologies for duplicate mails] Dear All, The RIPE NCC is pleased to announce that the Routing Information Service's (RIS) Remote Route Collector, RRC03, is now ready to peer with members at the Groningen Internet Exchange (GN-IX). RRC03 is located at the NIKHEF in Amsterdam. It is the fourth RRC to come online and has been operational since February 2001. RRC03 has an interface on the shared AMS-IX, NL-IX and GN-IX media and collects routing information from all exchange members willing to peer with the RIPE NCC's RIS project. Our details: - - Peering addresses: GN-IX: 193.111.172.29 NL-IX: 194.153.154.45 AMS-IX: 195.69.144.69, 2001:7f8:1::a501:2654:1 - - Autonomous system: 12654 - - Peering Policy: http://www.ripe.net/ris/rrc03.html Please send us your peering request by replying to this mail or using the web form at URL: http://www.ris.ripe.net/cgi-bin/peerreg.cgi +++ The Routing Information Service (RIS), which started as a modest RIPE NCC project in 1999, has gradually grown to over 300 peers at twelve data collection points in Europe, Japan and North America. Our mission is to collect BGP routing information over a function of time and make it available to the Internet community. In essence, this means creating tools that can help ISPs debug problems over time without being limited to a BGP view, and providing "raw data" regarding the historical development of the Internet. RIS Tools: http://www.ripe.net/ris/query.html +++ Please send your comments to ris at ripe.net. For more information about the RIS, see URL: http://www.ripe.net/ris/ Kind regards, The RIS Team --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/ -----BEGIN PGP SIGNATURE----- Version: PGP 7.0.4 iQA/AwUBQGB5GMHkFbJe+GdoEQIHHACfbTLtTQGib2kEe2rX4OoRPeveP9MAoKaD xFJFZuaO7oggwy0Hh3X7qH7w =GlYH -----END PGP SIGNATURE----- From matthew at ripe.net Fri Mar 26 14:15:57 2004 From: matthew at ripe.net (Matthew Williams) Date: Fri, 26 Mar 2004 14:15:57 +0100 Subject: LAST REMINDER: Two More Days Until the Deadline for Inter-Domain Routing Workshop (IDRWS) Contributions Message-ID: <003701c41334$79da8e10$300200c1@rockstar> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Apologies for duplicate mails] Dear All, The Inter-Domain Routing Workshop will take place at the RIPE NCC in Amsterdam during the weekend before RIPE 48 (May 1-2, 2004). This RIPE meeting will also be held in Amsterdam. The goal of the workshop is to bring together a focused group of operators, vendors, and researchers to discuss important mid- and long-term operational problems, as well as new academic ideas, in an OPEN forum. The wide scope for topics was intended on our part. Please remember to submit the abstract of your contribution for the workshop by March 28, 2004. See URL for more information: http://www.tm.uka.de/idrws/ Please feel free to drop us a line at idrws at ripe.net. Kind regards, Matthew Williams --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/ -----BEGIN PGP SIGNATURE----- Version: PGP 7.0.4 iQA/AwUBQGQtCcHkFbJe+GdoEQIrmgCfbqka6sFozswIISSklDoh4RFqZvMAoJ8Z Yc/ECI+aav7m1rxW3DdliYyc =lfTS -----END PGP SIGNATURE----- From matthew at ripe.net Fri Mar 26 14:58:24 2004 From: matthew at ripe.net (Matthew Williams) Date: Fri, 26 Mar 2004 14:58:24 +0100 Subject: NOTIFICATION: RRC02 at SFINX Currently Offline Message-ID: <003d01c4133a$67c23bf0$300200c1@rockstar> [Apologies for duplicate emails] Dear All, RIS Notification: ----------------- RRC02 is currently offline due to hardware problems. We are working hard together with SFINX to bring it back online again. There will be a time gap in RIS data collected by RRC02 due to the downtime. Other RIS services are not affected. We will keep you posted on our progress. -------------------------------------- Apologies for the inconvenience. Best regards, The RIS team --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/ From risops at ripe.net Mon Mar 29 03:37:56 2004 From: risops at ripe.net (Generic RIS account) Date: Mon, 29 Mar 2004 01:37:56 GMT Subject: RIS Statistics Report Message-ID: <200403290137.i2T1bu8h011598@halfweg.ripe.net> RIS Statistics Report (20040323-20040329) This report was generated at Mon Mar 29 00:15:01 UTC 2004. It analyses the BGP Routing Tables which are collected by RIS Remote Collectors at different locations around the world. Check http://www.ris.ripe.net/weekly-report/ for more info. o Prefix Distribution RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 APNIC 24751 24697 23858 0 24148 17496 23942 9595 20287 9903 23430 23140 ARIN 58047 57991 55756 0 57789 19167 56505 15499 43355 15645 55605 54873 LACNIC 5501 5501 5474 0 5490 3811 5493 2286 4351 1579 5474 5402 RIPE NCC 39352 23011 22448 0 36305 18719 20660 12477 21577 9907 22625 21669 OLD 31895 30934 28755 0 31087 16161 29068 10064 22381 8795 28451 28129 IANA 284 278 272 0 278 173 266 135 189 98 209 196 RFC1918 6 1 0 0 3 1 0 0 1 0 2 0 OTHER 0 0 0 0 0 0 0 0 0 0 0 0 TOTAL 159836 142413 136563 0 155100 75528 135934 50056 112141 45927 135796 133409 AS number distributions wrt RIR and single-homed/multi-homed. o ASes per RIR region RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 ARIN 9818 9807 9701 0 9779 4941 9275 4113 7982 4134 9682 9632 APNIC 1987 1987 1957 0 1983 1698 1926 1000 1834 1170 1954 1940 RIPE NCC 5312 5301 5294 0 5306 4821 4716 3520 4695 3103 5279 5257 LACNIC 47 47 44 0 46 39 44 33 41 20 44 44 IANA 1 1 1 0 1 1 1 1 1 1 1 1 Private 18 10 6 0 12 6 8 3 10 4 4 3 Others 0 0 0 0 0 0 0 0 0 0 0 0 Total 17183 17153 17003 0 17127 11506 15970 8670 14563 8432 16964 16877 o Number of single-homed ASes. RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 ARIN 2964 3214 4176 0 3225 2325 4412 1695 3638 2493 4424 6659 APNIC 580 621 749 0 673 834 747 355 670 554 768 1311 RIPE NCC 1414 1732 1890 0 1568 2341 1921 1532 1907 1677 2263 3680 LACNIC 24 24 24 0 24 22 24 18 22 13 24 34 IANA 1 1 1 0 1 1 1 1 1 1 1 1 Private 14 7 4 0 8 4 6 1 7 4 1 3 Others 0 0 0 0 0 0 0 0 0 0 0 0 Total 4997 5599 6844 0 5499 5527 7111 3602 6245 4742 7481 11688 o Number of multi-homed ASes. RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 ARIN 6854 6593 5525 0 6554 2616 4863 2418 4344 1641 5258 2973 APNIC 1407 1366 1208 0 1310 864 1179 645 1164 616 1186 629 RIPE NCC 3898 3569 3404 0 3738 2480 2795 1988 2788 1426 3016 1577 LACNIC 23 23 20 0 22 17 20 15 19 7 20 10 IANA 0 0 0 0 0 0 0 0 0 0 0 0 Private 4 3 2 0 4 2 2 2 3 0 3 0 Others 0 0 0 0 0 0 0 0 0 0 0 0 Total 12186 11554 10159 0 11628 5979 8859 5068 8318 3690 9483 5189 IANA : AS52947 o List of martians appearing throughout the week. Prefix Origin AS 10.0.0.0/8 3320 172.30.84.48/29 8968 172.30.84.56/29 8968 192.168.191.128/25 5417 o List of hot-spots during the week. Prefix Origin AS Number of updates 209.182.81.0/24 19071 422739 69.19.219.0/24 19864 276121 194.126.42.0/24 25122 131095 82.108.0.0/14 4589 124792 216.159.230.0/24 30455 103627 207.191.56.0/24 4519 90950 207.191.47.0/24 4519 90950 139.91.40.0/24 8522 88778 139.91.252.0/24 8522 88777 202.149.240.0/20 4761 62054 Total number of RIS BGP peering sessions: 368 From matthew at ripe.net Wed Mar 31 15:43:01 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 31 Mar 2004 15:43:01 +0200 Subject: NOTIFICATION: Hardware Problems on RRC02 at SFINX (cont.) Message-ID: <005d01c41726$15edab30$300200c1@rockstar> [Apologies for duplicate emails] Dear All, RIS Notification: ----------------- We have some bad news. It seems that the current RRC02 might need to have its hardware replaced. This particular box is sadly out of warranty, which means, in the worst case, that we will have to go through the motions of ordering a new one. We will keep you posted on developments. -------------------------------------- Apologies for the inconvenience. Best regards, The RIS team > -----Original Message----- > From: ris-users-admin at ripe.net > [mailto:ris-users-admin at ripe.net] On Behalf Of Matthew Williams > Sent: 26 March 2004 14:58 > To: ris-users at ripe.net > Subject: NOTIFICATION: RRC02 at SFINX Currently Offline > > > [Apologies for duplicate emails] > > Dear All, > > RIS Notification: > ----------------- > > RRC02 is currently offline due to hardware problems. We are > working hard together with SFINX to bring it back online again. > > There will be a time gap in RIS data collected by RRC02 due > to the downtime. Other RIS services are not affected. > > We will keep you posted on our progress. > > -------------------------------------- > > Apologies for the inconvenience. > > Best regards, > > The RIS team > > --- > > Matthew Williams (MW243-RIPE) > > Customer Liaison Engineer > > RIPE NCC - http://www.ripe.net/np/ >