- ris-users - mailman.ripe.net

RIS Quarterly Planning Q2 2022
by Paul de Weerd 31 Mar '22

31 Mar '22

Dear colleagues, We've prepared our quarterly plans for RIS and they can be found at: https://www.ripe.net/support/documentation/quarterly-planning/ris We hope that by providing these plans, we can better inform the community of the ongoing work we're doing on RIS and get feedback on it. If you have any input on these plans or suggestions for future work, please reach out to us. Kind regards, Paul de Weerd RIPE NCC

1 0

Today RIS session in SpatialChat - RIPE 83
by Michela Galante 25 Nov '21

25 Nov '21

Dear RIS users, It has been a long time since we have sent you some news related to RIS (the RIPE NCC Routing Information Service) through this mailing list. As you might know the RIPE 83 meeting is happening this week. The event has a virtual format and registration is free: https://ripe83.ripe.net/attend/register/ The registration will allow you to participate through Meetecho, the RIPE 83 conference platform, and SpatialChat, the virtual coffee break area. Hereby we would like to invite you to participate to the RIS Jam session that will happen today in SpatialChat between 17.00 and 18.30 (UTC+1): during this session, we, the team operating the RIS service, will be available to listen to your feedback and to answer any questions that you might have. Date: Thursday, 25 November Time: 17:00-18:30 (UTC+1) Where: SpatialChat – RIS JAM Hope to see many of you in SpatialChat! Best regards, Michela Galante on behalf of the RIPE RIS Team

1 0

Data inconsistency affecting RIS dumps and RIPEstat APIs and widgets
by Oleg Muravskiy 10 Dec '19

10 Dec '19

Dear RIS users, We have discovered a data inconsistency affecting RIS dumps and data available through RIPEstat APIs and widgets. The BGP updates that took place on 1 November between 10:00–11:47 and 14:00–15:33 were not accounted for when generating RIS dump files and most of the datasets of RIPEstat. This resulted in an incorrect representation of the BGP state data for routes that have not been updated since then. RIS update files and RIS Looking Glass are not affected. We are working on a fix and will re-generate correct RIS dump files and RIPEstat datasets. We are sorry for any inconveniences this may have caused. Oleg Muravskiy RIPE NCC

1 1

Does bgpdump show select route?
by Qiao Xiang 22 May '19

22 May '19

Dear all, How are you doing? I am new to the bgpdump tool. I use it to transfer a .bz2 RIB data file on Route Views to ASCII file as suggested in the following page: http://www.routeviews.org/routeviews/index.php/archive/ In the resulting ASCII file, all entries are marked as TABLE_DUMPV2 type. However, I am wondering, if entries of selected routes are marked in the file? If so, what is the marker? Thank you very much. Best Qiao Xiang -- Qiao Xiang Postdoctoral Fellow, Department of Computer Science, Yale University

2 1

New RIS Remote Route Collectors at InterLAN Bucharest, Equinix Singapore
by Colin Petrie 04 Jul '18

04 Jul '18

Dear colleagues, The RIPE NCC is pleased to announce two new Remote Route Collectors (RRCs) for the Routing Information Service (RIS). RRC22 is now online at InterLAN in Bucharest. We would like to thank InterLAN for their help and support. RRC23 is now online at Equinix Singapore in Singapore. We would like to thank Equinix for their help and support. The data from these new collectors is already available via RIPEstat, and the raw data is available in the archives. Peering with RIS ---------------- If you would like to peer with us, please fill in the form at: http://www.ris.ripe.net/cgi-bin/peerreg.cgi For more information about peering with RIS, please see: https://www.ripe.net/analyse/internet-measurements/routing-information-serv… About RIS ------------- RIS aims to collect and store Border Gateway Protocol (BGP) routing information and make it publicly available for the Internet community. The RIPEstat tools that provide access to this data can help network operators troubleshoot routing problems by providing eBGP data collected over time without being limited to a single BGP view. RIS deploys RRCs at major Internet exchanges, where they peer with other networks. At this time, RIS has more than 750 peers at 22 different Internet exchanges. For more information, please see: https://ripe.net/ris/ If you have any further questions, please contact <ris at ripe.net> Kind Regards, Colin Petrie RIPE NCC

1 0

High amount of v6 prefixes at CATNIX and SFINX
by Johanna Ullrich 23 Apr '18

23 Apr '18

Hello! Relying on RIS data, I am currently investigating BGP announcement for IPv6 for my research. For some reason, CATNIX and SFINX members appear to announce a lot more prefixes than the others. While I found typically less than 50 /32 prefixes for the other Internet exchanges, I see almost 900 /32 for SFINX and even 9000 /32 for CATNIX. I wonder whether there is a specific reason, e.g., with respect to aggregation or policies. I am really looking forward to your reply. Thank you a lot for help! Regards, Johanna Dr. Johanna Ullrich Senior Researcher http://www.sba-research.org/ Identifizierung gemäß § 14 UGB Firmenname: SBA Research gGmbH Firmensitz: Favoritenstraße 16, 1040 Wien Firmenbuchnummer: 345659y Firmenbuchgericht: Handelsgericht Wien DVR-Nummer: 4012257

1 0

RIS Servers Problem
by Shahin Gharghi 21 Jun '17

21 Jun '17

Dear Colleagues, I'm using RIS RAW data for my BGPMon software. I saw a lot of IPv6 Bogons from some RIS servers like server 15. The problem was those prefixes orginated from our AS and in soem cases from our customers AS that don't have IPv6 peer at all. Yesterday I noticed it is not a IPv6 bogon. It's the hex version of our IPv4 prefix. Check this example out: 4f7f::/19 Time: 2017-06-21 00:16:17 79.127.0.0/19 Time: 2017-06-21 00:16:17 have you noticed this problem? -- Shahin Gharghi

2 1

New RIS Remote Route Collector at NAPAfrica Johannesburg (RRC19)
by Colin Petrie 30 Jun '16

30 Jun '16

Dear colleagues, The RIPE NCC is pleased to announce a new Remote Route Collector (RRC) for the Routing Information Service (RIS). This is our first collector in Africa. RRC19 is now online at NAPAfrica JB in Johannesburg. We would like to thank Teraco and Workonline Communications for their help and support. The data from this new collector is already available via RIPEstat. The raw data will be available in the archives in the near future. Peering with RIS ---------------- If you would like to peer with us, please fill in the form at: http://www.ris.ripe.net/cgi-bin/peerreg.cgi For more information about peering with RIS, please see: https://www.ripe.net/analyse/internet-measurements/routing-information-serv… About RIS ------------- RIS aims to collect and store Border Gateway Protocol (BGP) routing information and make it publicly available for the Internet community. The RIPEstat tools that provide access to this data can help network operators troubleshoot routing problems by providing eBGP data collected over time without being limited to a single BGP view. RIS deploys RRCs at major Internet exchanges, where they peer with other networks. At this time, RIS has more than 650 peers at 21 different Internet exchanges. For more information, please see: https://ripe.net/ris/ If you have any further questions, please contact <ris at ripe.net> Regards, Colin Petrie Systems Engineer RIPE NCC

1 0

Want to more traffic/sale on your site
by K.RANA 11 Dec '15

11 Dec '15

Hi, My name is K.RANA, and I was doing some research on some of your competitors' websites when I came across your www.ripe.net site. I ran an analysis on your site using one of our software and found simple coding & optimization issues that are harming your search rankings pretty bad. Would you be interested in an analysis report and keywords suggestion list with Google 1st page projection? I want is the opportunity to discuss how I could help improve the profitability and search traffic to your site. Let us know your expectations from your website; we can help you to realize it. What time good for you to discuss? Please provide me your contact no and Skype id. Kind Regards, K.RANA - india

1 0

Issues with ASPATH from rib
by Pavel Odintsov 29 Nov '15

29 Nov '15

Hello! I'm trying to build mapping from IP to AS number with bgpdump-1.4.99.15 and my custom toolkit. So I downloaded dump http://archive.routeviews.org/bgpdata/2015.11/RIBS/rib.20151128.0600.bz2 and trying to parse it with bgpdump. For about 90% of full BGP table I'm getting correct values for ASPATH. For example for my ASN 198068 I got: TIME: 11/28/15 06:00:03 TYPE: TABLE_DUMP_V2/IPV4_UNICAST PREFIX: 46.36.223.0/24 SEQUENCE: 55029 FROM: 147.28.7.2 AS3130 ORIGINATED: 11/11/15 18:25:25 ORIGIN: IGP ASPATH: 3130 2914 9002 198068 NEXT_HOP: 147.28.7.2 MULTI_EXIT_DISC: 2 COMMUNITY: 2914:410 2914:1201 2914:2202 2914:3200 3130:380 But some prefixes I'm getting very strange ASPATH with ASN enclosed in curly quotes. For example you could look at: TIME: 11/28/15 06:00:01 TYPE: TABLE_DUMP_V2/IPV4_UNICAST PREFIX: 5.39.176.0/21 SEQUENCE: 5583 FROM: 147.28.7.1 AS3130 ORIGINATED: 11/13/15 08:02:15 ORIGIN: IGP ASPATH: 3130 2914 3356 8530 {198753} NEXT_HOP: 147.28.7.1 AGGREGATOR: AS8530 91.143.64.24 COMMUNITY: 2914:420 2914:1007 2914:2000 2914:3000 3130:380 How I should interpret this record "3130 2914 3356 8530 {198753}"? Who are origin for this prefix 8530 or 198753? After some time of digging to this data I got more strange example: TIME: 11/28/15 06:00:06 TYPE: TABLE_DUMP_V2/IPV4_UNICAST PREFIX: 69.43.64.0/18 SEQUENCE: 108538 FROM: 195.208.112.161 AS3277 ORIGINATED: 11/27/15 13:37:08 ORIGIN: IGP ASPATH: 3277 3267 174 32432 {6939,46887} NEXT_HOP: 195.208.112.161 AGGREGATOR: AS32432 38.88.209.254 COMMUNITY: 3277:3267 3277:65321 3277:65323 3277:65331 So I really haven't any ideas about this ASPATH: 3277 3267 174 32432 {6939,46887}. Could you clarify both cases (with single and multiple AS numbers) with curly quotes? -- Sincerely yours, Pavel Odintsov

2 1