- Test - lists.nanog.org

Craigslist technical contact - IP Ranges blocked
by Erik Zhu 18 Feb '19

18 Feb '19

Hello All, Does anyone know the best way to get connect to Craiglist technical support regarding the blocked IP ranges. We are an ISP in Canada, and since early this year we noticed that most of our IP blocks are blocked on some of the Craigslist's servers. One easy example is finding any items on Craigslist, hit reply, and gives an error "Sorry, something went wrong", the web analyzer indicates status code 403 forbidden. I understand that if individual subscriber IP could be automatically blocked due to certain reasons by Craigslist, but I don't know why our entire IP blocks could be blocked, even some IP ranges are never assigned to any active services. Did anyone have the encountered the same issue before, how can we get it resolved? Thanks, Erik

2 1

Re: A Zero Spam Mail System [Feedback Request]
by hank＠interall.co.il 18 Feb '19

18 Feb '19

On 18/02/2019 04:03, Viruthagiri Thirumavalavan wrote: If that is the case you should have a startup worth at least $10M with numerous VC banging down your door. If not, you need to ask yourself the question "why not?". -Hank > Hello Everyone, > > My name is Viruthagiri Thirumavalavan. I'm the guy who proposed SMTP > over TLS on Port 26 last month. I'm also the guy who attacked (???) > John Levine. > > Today I have something to show you. Long story short.... I solved > the email spam problem. Well... Actually I solved it long time back. > I'm just ready to disclose it today. Again... > > @Everyone > > Here is what you all should know. > > It's my 5 years of research. So it's worth more than 50 words. I > started my work back in 2013 and I used to call my work "XMail" at > that time. It's now called "Dombox" > > My prototype codebase has around 200,000 lines of code. [To be > exact: 466,965 ++ 254,169 --] > > Sequoia Capital is one of the well known venture firm in the world. > They have invested in over 250 companies since 1972, including > Apple, Google, Oracle, PayPal, Stripe, YouTube, Instagram, Yahoo! > and WhatsApp. Bill Coughran is a senior investor in Sequoia Capital. > According to his linkedin profile, he started as a Programmer in the > late 60s and held many engineering related positions over the years. > Worked in Bell Laboratories for 20 years. Worked as SVP of > Engineering in Google for 8.5 years. To quote his words "I have some > level of expertise about the current email systems, which is why I > was did some investigating". So this man is one of the toughest > person to impress. But he is one of the nicest investor I have met. > When I asked him whether he can take a look, he didn't insult me > with words like "You think you are the inventor of FUSSP?" He just > told me "Sure, I'd be happy to." He went through my entire paper and > then sent me this mail. He later turned me down because it's hard > for a startup to distribute a new solution. Maybe he is right. Or > maybe I'll overcome that too. [Today's discussion is about whether I > solved the spam problem. Not about how I'm gonna distribute the > solution] > > Yesterday I published my work on a medium blog post and linked my > white paper. An engineer read my white paper and sent me this mail. > These guys see value in my white paper because they completed my > ~300 pages white paper. ---------------------------------- > > Materials: > > System Overview - > https://medium.com/@Viruthagiri/dombox-the-zero-spam-mail-system-2b08ff7432… > > White Paper - https://www.dombox.org/dombox.pdf > > Flowcharts - https://www.dombox.org/flowcharts.pdf > > Prototype - https://www.youtube.com/watch?v=VK2eSfCurx4 [This is the > video I uploaded before posting to DMARC list. So the interface is > little outdated] > > -- > Best Regards, > > Viruthagiri Thirumavalavan > Dombox, Inc.

1 0

TATA/AS6453 BGP communities
by Tim Warnock 18 Feb '19

18 Feb '19

Hey, Anyone have a list of BGP communities for TATA/AS6453? Mainly chasing geo tags. Their peeringdb contacts are non-responsive. Thanks Tim.

2 2

Amazon contact off-list
by Ben Cannon 17 Feb '19

17 Feb '19

Can someone from Amazon (preferably SF Bay area) contact me off-list please? -Ben. -Ben Cannon CEO 6x7 Networks & 6x7 Telecom, LLC ben(a)6by7.net <mailto:ben@6by7.net>

1 0

OT/venting: RIPE legal - please stop this madness!
by Markus 16 Feb '19

16 Feb '19

Hi list! The following is off-topic/venting. It's about RIPE and my company in Germany. If you don't care about this even remotely, don't read on and don't flame me. I'm just so pissed and I have no other connection to the ISP (and related) community than the NANOG mailing list and I know there are some other European ISPs on this list. Here goes: My company has been a RIPE LIR for 17 years now. This week was the first time ever that I became, was and still am really, really pissed at RIPE. There's some madness going on in RIPEs legal department. It appears they recently hired some retard who now wants to prove he/she is a smartass. Harsh words, but I have no other explanation for what's going on right now! Here's the story: Sunday, 10th February, 17:08 CET: I sent away the online application for an additional LIR account. Automatic E-Mail confirmation received. Monday, 11th February, 15:07 CET: I didn't receive a human reply yet, and since the business day was nearing its end, I mailed them about the status, and asked whether I could come by their Amsterdam office the next day to sign the required documents - in order to speed up the whole process. Monday, 11th February, 15:57 CET: Reply from RIPE. Let me just copy and paste: "I regret to inform you that we do not offer the possibility to sign your contracts in our office and regrettably there is no option to speed up the application procedure." - Ok, no biggie. But then: Quote start. "We can see that this is an additional LIR account for Lightup Network Solutions GmbH & Co. KG. We are currently reviewing applications with a legal entity type 'GmbH & Co. KG' together with our legal department and they have stated the following: "GmbH & Co. KG" is a sub-form of a "KG" (partnership). It normally consists of a general partner and one or more limited partners, which can be legal or natural persons. According to "Due Diligence for the Quality of the RIPE NCC Registration Data" the signing party of an agreement can either be a legal or a natural person. A "KG" is not considered a legal person and cant be the signing party in our agreements. The agreement can be signed though by one of the legal or natural persons that are partners (general or limited). We therefore cannot register Lightup Network Solutions GmbH & Co. KG. As you already have an LIR account with us, we will have to update your existing account, de.lightupnet, before we can register this second account for Lightup Network Solutions GmbH & Co. KG. I created a new ticket for your company update and my colleagues will contact you shortly for the update." Quote end. That didn't sound so good. I've had a company with the legal form GmbH & Co. KG (it's a German company) for about 15 years now and my initial gut feeling was "That's just plain bullsh*t!". Tuesday, 12th February, 12:30: I receive another E-Mail. New ticket, as they promised. Quote start. "It has come to our attention, that the legal name of your LIR account has been registered incorrectly. It was advised by our Legal Department that the legal form of your company as "GmbH & Co. KG" is a form of a general partnership that does not have a legal personality. If there is a document proving opposite, please send it to us. According to our procedure, we can only sign an agreement with a legal person that has a legal personality or a natural person. Therefore, we will have to correct your legal name to <Markus Stalder trading as "Lightup Network Solutions GmbH & Co. KG">, instead of <Lightup Network Solutions GmbH & Co. KG>." Quote end. They also asked that I upload a photo/scan of my passport, which I did. I just thought: Ok, let them have their way. If they want to change my LIRs description, who really cares. All I want is to create a 2nd LIR and speed this whole thing up. But, since they want to be SO LEGALLY CORRECT, I replied and mentioned the following. Let me copy and paste. Quote start. "I just uploaded my passport. However, following your logic, you need to change all of the following German legal forms in your database to "Individual-name trading as ...": - OHG - KG - GmbH & Co. OHG - GmbH & Co. KG I understand that you would have to do that with a GbR, as a GbR cannot get registered in the commercial register of companies and you need to specify the names of the individuals. But I think with the above 4 legal forms you are making as mistake here. Although it is correct that a GmbH & Co. KG does not have a legal personality that differs from its general partners (Persoenlich haftende Gesellschafterin) or limited partners (Kommanditist), a GmbH & Co. KG is still a legal entity as its able to sue in front of court, or get sued in front of court. A GmbH & Co. KG can also purchase rights and enter into liabilities, can purchase property and other in rem rights related to estates. (Source: <https://www.frankfurt-main.ihk.de/existenzgruendung/rechtsfragen/idem/kg/>) That being said, since Lightup Network Solutions GmbH & Co. KG was founded, I have never ever signed a contract where the contractual partner was "Markus Stalder trading as Lightup Network Solutions GmbH & Co. KG" but the contractual partner was always Lightup Network Solutions GmbH & Co. KG. That includes application forms towards government entities as well as contracts with larger corporations. Actually, my gut feeling based on my own experience with my GmbH & Co. KG in the last decades tells me that you are making a mistake here. And, if you want to be really accurate: You must be aware that the Kommanditist (limited partner) is not allowed to represent the company. That is something only the Komplementaerin (general partner) can do. The general partner of Lightup Network Solutions GmbH & Co. KG is AirAccess GmbH. I'm attaching both company extracts for your convenience. So, correct would be: AirAccess GmbH trading as Lightup Network Solutions GmbH & Co. KG" Quote end. Wednesday, 13th February, 18:02: Reply from RIPE: Quote start: "Many thanks for the clarification and the provided documents. Please be informed that our Due Diligence for the Quality of the RIPE NCC Registration Data <https://www.ripe.net/publications/docs/ripe-700> has been implemented in 2018. As the application process for our members was not so strict before, it was possible to register an LIR account under the partnership name. Currently, we are working on correcting these details in the Database. At this moment we are reviewing German applications with a legal entity type 'GmbH & Co. KG' together with our legal department. Thus the information you provided is very helpful. On the review the documents you submitted, we indeed can see that "AirAccess GmbH" is a general partner with a special right to represent the company. The names of both LIR accounts (de.lightupnet, de.lightupnet1) will be corrected tomorrow. It will be confirmed to you once the account are updated." Quote end. ... another day passes ... Thursday, 14th February, 16:11: Now for the E-Mail from RIPE that blew my mind, in a negative sense. Quote start: "Many thanks for your patience. We have reviewed your case internally and agreed that there is no need to sign a new agreement for LIR account <de.lightupnet>, as it was signed by the director of the company. It has also come to our attention that, the company AirAccess GmbH (reg. No HRB 56386) already has LIR account <de.airaccess>. Therefore LIR <de.airaccess> should be linked as an additional account to <de.lightupnet>, and <de.lightupnet1>. Please be informed that the following will be applied to all additional LIR accounts: - The /22 IPv4 allocation you will receive is subject to the RIPE NCC Transfer Policy and can therefore only be transferred 24 months after the allocation date. - Members with multiple LIR accounts are entitled to just one vote at RIPE NCC General Meetings. The oldest LIR account will receive the vote. - If you wish to transfer internet resources between your LIR accounts, you need to pay the full annual service fee for all LIR accounts. - If you wish to close LIR account, you need to pay the full annual service fee for all LIR accounts. At this moment could you please inform us what name you prefer for LIR accounts <de.lightupnet>, <de.lightupnet1>: "AirAccess GmbH" or "AirAccess GmbH trading us Lightup Network Solutions GmbH & Co. KG"? Once it is clarified, we will proceed with updating the legal details of your accounts and process the application for <de.lightupnet1>." Quote end. Spontaneous thought: HOLY F*CK, ARE THEY SERIOUS ?! ?! ?! They want to change the name of my company - Lightup Network Solutions GmbH & Co. KG - to a completely different company: AirAccess GmbH !!! Totally unrelated to each other, different business, different everything. The only thing these two companies have in common is that they're both mine. RIPE MUST BE NUTS! Here my reply: Quote start. "Hi <name of RIPE NCC support person>, thanks for your mail. Ok, now you are really taking it over the top. 1) You want to link AirAccess GmbH as an additional account to de.lightupnet. And you want to do this for a company which is a legal entity by itself. I do not allow you to do this. AirAccess GmbH is a legal entity by itself and I do not want that you change anything about its current LIR status, name or anything else. 2) You are offering that I can choose the name for de.lightupnet and de.lightupnet1 to be "AirAccess GmbH", a company which is an entity by itself and is merely the Komplementaerin (general partner) for Lightup Network Solutions GmbH & GmbH Co. KG. I'm shocked by that idea. That is just completely wrong. Of course I do NOT want de.lightupnet and de.lightupnet1 to be named "AirAccess GmbH" because it would be an factual error. And I don't want RIPE to make wrong statements about our company/companies towards the public. It would be like offering to present nl.ripe as KPN. Or Nike as Adidas. As it appears right now your legal department is doing a mistake when it comes to understanding how GmbH + Co. KGs work. Could you also please let me know the E-Mail address or telephone number where I can file a complaint about this whole procedure? Thank you." Quote end. This is where it stands right now. It's Friday, 15th February. The work week is over. I'm sitting here, waiting for RIPE since Monday to send me the LIR agreement for the 2nd LIR, so that I can sign it, pay it, and be done with it. My rhetorical questions are: 1) Are they fucking serious ... I can't remember the last time I was this angry at anyone. 2) It's RIPE. A large, established organisation that's been around forever. WHY THE F*CK does it take them always 1 day to process something, to reply to something? They have TONS of employees, they have TONS of LIRs that pay them TONS of money, why is everything moving so slowly with them ?! ?! ?! It's 2019, not 1995 FOR F*CKS SAKE !!! Get your act together and adapt to the times, modernize yourself and BE FASTER. UARRRGHHHL. 3) Why in heavens name do they EXACTLY have to start with this whole f*cked-up process when I ACTUALLY need something from them (a 2nd LIR account)? Why in this very moment? Yeah, because my company popped up on their screen because I applied for a 2nd LIR account, makes sense. But, could they not simply process the damn LIR application at the same time to speed this whole thing up, and later change this sh*t. No, of course, it would be not efficient for them to do that, but it's NOT MY FAULT they didn't ask to update this data/fix this company sh*t earlier. But now THEY MAKE IT MY PROBLEM. Because I'm losing precious time. F*CK! 4) If you look at the LIR list for Germany here - <https://www.ripe.net/membership/indices/DE.html> - and search for "GmbH & Co. KG" in the document, you will see many companies that are still "unchanged": Company name GmbH & Co. KG, but you will also see some that were already "updated" according to RIPE logic: "Firstname Lastname trading as "Company GmbH & Co. KG" - the "funny" thing is that this is just wrong as I explained earlier. They have to re-do all these changes. By looking at this list it appears I'm the first where they offer to change it to "Another-company-name GmbH trading as Company GmbH & Co. KG" JUST BECAUSE I told them that with GmbH & Co. KGs the Kommanditist (legal partner) is not allowed to represent the company. So, being the first, and looking at that list for comparison tells me they have no idea what they are doing! Have a good day everyone and down with unnecessary, over-the-top bureaucracy! It's 2019 FOR F*CKS SAKE!!! Regards Markus

6 6

Weekly Routing Table Report
by cscora＠apnic.net 15 Feb '19

15 Feb '19

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 16 Feb, 2019 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 737069 Prefixes after maximum aggregation (per Origin AS): 284406 Deaggregation factor: 2.59 Unique aggregates announced (without unneeded subnets): 355337 Total ASes present in the Internet Routing Table: 63249 Prefixes per ASN: 11.65 Origin-only ASes present in the Internet Routing Table: 54461 Origin ASes announcing only one prefix: 23611 Transit ASes present in the Internet Routing Table: 8788 Transit-only ASes present in the Internet Routing Table: 270 Average AS path length visible in the Internet Routing Table: 4.2 Max AS path length visible: 31 Max AS path prepend of ASN ( 16327) 25 Prefixes from unregistered ASNs in the Routing Table: 26 Number of instances of unregistered ASNs: 28 Number of 32-bit ASNs allocated by the RIRs: 25797 Number of 32-bit ASNs visible in the Routing Table: 21025 Prefixes from 32-bit ASNs in the Routing Table: 91435 Number of bogon 32-bit ASNs visible in the Routing Table: 23 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 265 Number of addresses announced to Internet: 2840868547 Equivalent to 169 /8s, 84 /16s and 54 /24s Percentage of available address space announced: 76.7 Percentage of allocated address space announced: 76.7 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.2 Total number of prefixes smaller than registry allocations: 246891 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 200469 Total APNIC prefixes after maximum aggregation: 57566 APNIC Deaggregation factor: 3.48 Prefixes being announced from the APNIC address blocks: 197448 Unique aggregates announced from the APNIC address blocks: 81948 APNIC Region origin ASes present in the Internet Routing Table: 9451 APNIC Prefixes per ASN: 20.89 APNIC Region origin ASes announcing only one prefix: 2657 APNIC Region transit ASes present in the Internet Routing Table: 1413 Average APNIC Region AS path length visible: 4.1 Max APNIC Region AS path length visible: 26 Number of APNIC region 32-bit ASNs visible in the Routing Table: 4459 Number of APNIC addresses announced to Internet: 769815906 Equivalent to 45 /8s, 226 /16s and 117 /24s APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079, 55296-56319, 58368-59391, 63488-64098, 64297-64395, 131072-139577 APNIC Address Blocks 1/8, 14/8, 27/8, 36/8, 39/8, 42/8, 43/8, 49/8, 58/8, 59/8, 60/8, 61/8, 101/8, 103/8, 106/8, 110/8, 111/8, 112/8, 113/8, 114/8, 115/8, 116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8, 123/8, 124/8, 125/8, 126/8, 133/8, 150/8, 153/8, 163/8, 171/8, 175/8, 180/8, 182/8, 183/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, 223/8, ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 217989 Total ARIN prefixes after maximum aggregation: 103510 ARIN Deaggregation factor: 2.11 Prefixes being announced from the ARIN address blocks: 217330 Unique aggregates announced from the ARIN address blocks: 104080 ARIN Region origin ASes present in the Internet Routing Table: 18359 ARIN Prefixes per ASN: 11.84 ARIN Region origin ASes announcing only one prefix: 6834 ARIN Region transit ASes present in the Internet Routing Table: 1855 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 24 Number of ARIN region 32-bit ASNs visible in the Routing Table: 2581 Number of ARIN addresses announced to Internet: 1077344416 Equivalent to 64 /8s, 54 /16s and 248 /24s ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959, 46080-47103 53248-55295, 62464-63487, 64198-64296, 393216-399260 ARIN Address Blocks 3/8, 4/8, 6/8, 7/8, 8/8, 9/8, 11/8, 12/8, 13/8, 15/8, 16/8, 17/8, 18/8, 19/8, 20/8, 21/8, 22/8, 23/8, 24/8, 26/8, 28/8, 29/8, 30/8, 32/8, 33/8, 34/8, 35/8, 38/8, 40/8, 44/8, 45/8, 47/8, 48/8, 50/8, 52/8, 53/8, 54/8, 55/8, 56/8, 57/8, 63/8, 64/8, 65/8, 66/8, 67/8, 68/8, 69/8, 70/8, 71/8, 72/8, 73/8, 74/8, 75/8, 76/8, 96/8, 97/8, 98/8, 99/8, 100/8, 104/8, 107/8, 108/8, 128/8, 129/8, 130/8, 131/8, 132/8, 134/8, 135/8, 136/8, 137/8, 138/8, 139/8, 140/8, 142/8, 143/8, 144/8, 146/8, 147/8, 148/8, 149/8, 152/8, 155/8, 156/8, 157/8, 158/8, 159/8, 160/8, 161/8, 162/8, 164/8, 165/8, 166/8, 167/8, 168/8, 169/8, 170/8, 172/8, 173/8, 174/8, 184/8, 192/8, 198/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 214/8, 215/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 202728 Total RIPE prefixes after maximum aggregation: 96543 RIPE Deaggregation factor: 2.10 Prefixes being announced from the RIPE address blocks: 198781 Unique aggregates announced from the RIPE address blocks: 117953 RIPE Region origin ASes present in the Internet Routing Table: 25827 RIPE Prefixes per ASN: 7.70 RIPE Region origin ASes announcing only one prefix: 11496 RIPE Region transit ASes present in the Internet Routing Table: 3636 Average RIPE Region AS path length visible: 4.4 Max RIPE Region AS path length visible: 28 Number of RIPE region 32-bit ASNs visible in the Routing Table: 7839 Number of RIPE addresses announced to Internet: 716829376 Equivalent to 42 /8s, 185 /16s and 242 /24s RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-45055, 47104-52223, 56320-58367 59392-61439, 61952-62463, 64396-64495 196608-210331 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/8, 62/8, 77/8, 78/8, 79/8, 80/8, 81/8, 82/8, 83/8, 84/8, 85/8, 86/8, 87/8, 88/8, 89/8, 90/8, 91/8, 92/8, 93/8, 94/8, 95/8, 109/8, 141/8, 145/8, 151/8, 176/8, 178/8, 185/8, 188/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 95234 Total LACNIC prefixes after maximum aggregation: 22511 LACNIC Deaggregation factor: 4.23 Prefixes being announced from the LACNIC address blocks: 96677 Unique aggregates announced from the LACNIC address blocks: 41867 LACNIC Region origin ASes present in the Internet Routing Table: 8074 LACNIC Prefixes per ASN: 11.97 LACNIC Region origin ASes announcing only one prefix: 2195 LACNIC Region transit ASes present in the Internet Routing Table: 1526 Average LACNIC Region AS path length visible: 5.0 Max LACNIC Region AS path length visible: 31 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 5624 Number of LACNIC addresses announced to Internet: 173195520 Equivalent to 10 /8s, 82 /16s and 193 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-270748 + ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 20622 Total AfriNIC prefixes after maximum aggregation: 4255 AfriNIC Deaggregation factor: 4.85 Prefixes being announced from the AfriNIC address blocks: 26568 Unique aggregates announced from the AfriNIC address blocks: 9252 AfriNIC Region origin ASes present in the Internet Routing Table: 1249 AfriNIC Prefixes per ASN: 21.27 AfriNIC Region origin ASes announcing only one prefix: 429 AfriNIC Region transit ASes present in the Internet Routing Table: 244 Average AfriNIC Region AS path length visible: 4.4 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 522 Number of AfriNIC addresses announced to Internet: 103345152 Equivalent to 6 /8s, 40 /16s and 236 /24s AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 102/8, 105/8, 154/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4538 4653 4192 74 ERX-CERNET-BKB China Education and Rese 7545 4648 541 540 TPG-INTERNET-AP TPG Telecom Limited, AU 7552 3085 1240 50 VIETEL-AS-AP Viettel Group, VN 45899 3014 1729 113 VNPT-AS-VN VNPT Corp, VN 4766 2808 11127 766 KIXS-AS-KR Korea Telecom, KR 9829 2751 1496 551 BSNL-NIB National Internet Backbone, IN 9808 2437 8699 26 CMNET-GD Guangdong Mobile Communication 9394 2372 4906 29 CTTNET China TieTong Telecommunications 4755 2144 422 180 TATACOMM-AS TATA Communications formerl 17974 2006 968 50 TELKOMNET-AS2-AP PT Telekomunikasi Indo Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 6327 3596 1326 92 SHAW - Shaw Communications Inc., CA 11492 3505 226 592 CABLEONE - CABLE ONE, INC., US 22773 3311 2978 172 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 16509 2545 5387 1025 AMAZON-02 - Amazon.com, Inc., US 16625 2278 1249 1724 AKAMAI-AS - Akamai Technologies, Inc., 20115 2151 2744 535 CHARTER-20115 - Charter Communications, 18566 2130 405 108 MEGAPATH5-US - MegaPath Corporation, US 30036 2098 349 239 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 209 2093 5095 585 CENTURYLINK-US-LEGACY-QWEST - CenturyLi 5650 2089 3074 1462 FRONTIER-FRTR - Frontier Communications Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 5319 1628 138 UNI2-AS, ES 39891 3778 203 20 ALJAWWALSTC-AS, SA 8551 3260 378 43 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2614 552 1904 AKAMAI-ASN1, US 12389 2226 2221 637 ROSTELECOM-AS, RU 34984 2059 339 531 TELLCOM-AS, TR 9121 1735 1692 18 TTNET, TR 13188 1604 100 46 TRIOLAN, UA 9009 1337 145 745 M247, GB 8402 1310 545 15 CORBINA-AS OJSC "Vimpelcom", RU Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 5572 3329 590 Uninet S.A. de C.V., MX 10620 2875 436 1014 Telmex Colombia S.A., CO 11830 2697 386 36 Instituto Costarricense de Electricidad 6503 1512 433 54 Axtel, S.A.B. de C.V., MX 7303 1408 937 236 Telecom Argentina S.A., AR 6147 1271 377 29 Telefonica del Peru S.A.A., PE 28573 1268 2246 186 CLARO S.A., BR 3816 1021 506 114 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11172 931 144 66 Alestra, S. de R.L. de C.V., MX 13999 916 530 245 Mega Cable, S.A. de C.V., MX Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1217 393 21 LINKdotNET-AS, EG 37611 932 107 9 Afrihost, ZA 24835 847 636 22 RAYA-AS, EG 36992 812 1538 43 ETISALAT-MISR, EG 36903 810 407 147 MT-MPLS, MA 8452 648 1731 20 TE-AS TE-AS, EG 29571 486 70 13 ORANGE-COTE-IVOIRE, CI 37492 468 470 57 ORANGE-, TN 15399 428 45 11 WANANCHI-, KE 37342 420 32 1 MOVITEL, MZ Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 5572 3329 590 Uninet S.A. de C.V., MX 12479 5319 1628 138 UNI2-AS, ES 4538 4653 4192 74 ERX-CERNET-BKB China Education and Rese 7545 4648 541 540 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3778 203 20 ALJAWWALSTC-AS, SA 6327 3596 1326 92 SHAW - Shaw Communications Inc., CA 11492 3505 226 592 CABLEONE - CABLE ONE, INC., US 22773 3311 2978 172 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 8551 3260 378 43 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 7552 3085 1240 50 VIETEL-AS-AP Viettel Group, VN Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 12479 5319 5181 UNI2-AS, ES 4538 4653 4579 ERX-CERNET-BKB China Education and Research Net 7545 4648 4108 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3778 3758 ALJAWWALSTC-AS, SA 6327 3596 3504 SHAW - Shaw Communications Inc., CA 8551 3260 3217 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 22773 3311 3139 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7552 3085 3035 VIETEL-AS-AP Viettel Group, VN 11492 3505 2913 CABLEONE - CABLE ONE, INC., US 45899 3014 2901 VNPT-AS-VN VNPT Corp, VN Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 230105 UNALLOCATED 38.110.79.0/24 23015 CMC180-TOR-AS - Cambridge Merc 266842 UNALLOCATED 45.238.156.0/22 265680 HNTELCO S.A, HN 1358592 UNALLOCATED 103.134.14.0/23 63956 COLO-AS-AP Colocation Australi 1358592 UNALLOCATED 103.134.15.0/24 63956 COLO-AS-AP Colocation Australi 65549 DOCUMENT 117.239.163.0/24 65544 UNKNOWN 224413 UNALLOCATED 131.221.136.0/22 264413 Conecta Telecom Ltda, BR 64339 UNALLOCATED 143.0.108.0/22 18747 IFX18747 - IFX Corporation, US 64355 UNALLOCATED 156.40.196.0/24 30387 NIH-NET-NCCS - National Instit 64011 UNALLOCATED 166.133.128.0/18 20057 ATT-MOBILITY-LLC-AS20057 - AT& 64011 UNALLOCATED 166.133.192.0/18 20057 ATT-MOBILITY-LLC-AS20057 - AT& Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 198.18.1.19/32 7497 CSTNET-AS-AP Computer Network Information Cente Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 27.100.7.0/24 56096 UNKNOWN 27.126.156.0/22 55827 UNKNOWN 27.126.156.0/23 55827 UNKNOWN 27.126.158.0/23 55827 UNKNOWN 41.76.136.0/22 37500 -Reserved AS-, ZZ 41.76.140.0/22 37500 -Reserved AS-, ZZ 41.78.92.0/22 14988 BTC-GATE1, BW 41.78.180.0/23 37265 -Reserved AS-, ZZ 43.255.80.0/24 36351 SOFTLAYER - SoftLayer Technologies Inc., US 43.255.82.0/24 36351 SOFTLAYER - SoftLayer Technologies Inc., US Complete listing at http://thyme.rand.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:12 /9:10 /10:36 /11:99 /12:291 /13:566 /14:1132 /15:1908 /16:13352 /17:7902 /18:13887 /19:25593 /20:39779 /21:46105 /22:91898 /23:75067 /24:416564 /25:938 /26:826 /27:878 /28:20 /29:6 /30:7 /31:0 /32:193 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 12479 4199 5319 UNI2-AS, ES 6327 3359 3596 SHAW - Shaw Communications Inc., CA 39891 2946 3778 ALJAWWALSTC-AS, SA 11492 2761 3505 CABLEONE - CABLE ONE, INC., US 8551 2716 3260 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 22773 2552 3311 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 11830 2040 2697 Instituto Costarricense de Electricidad y Telec 18566 2025 2130 MEGAPATH5-US - MegaPath Corporation, US 30036 1845 2098 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 5650 1761 2089 FRONTIER-FRTR - Frontier Communications of Amer Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1610 2:890 4:22 5:2845 6:47 7:1 8:1196 12:1868 13:313 14:1895 15:38 16:4 17:220 18:59 20:49 23:2604 24:2507 25:2 27:2547 31:2067 32:94 35:36 36:830 37:3035 38:1652 39:294 40:122 41:3132 42:723 43:2001 44:140 45:6663 46:3244 47:249 49:1342 50:1089 51:319 52:1046 54:329 55:1 56:6 57:41 58:1707 59:1061 60:495 61:2058 62:2040 63:1794 64:5078 65:2193 66:4806 67:2690 68:1173 69:3516 70:1154 71:600 72:2297 74:2757 75:421 76:544 77:1693 78:1763 79:2320 80:1612 81:1436 82:1111 83:867 84:1100 85:2143 86:552 87:1535 88:998 89:2422 90:217 91:6560 92:1233 93:2441 94:2481 95:3242 96:920 97:348 98:939 99:174 100:88 101:1163 102:407 103:20037 104:3569 105:247 106:866 107:1818 108:697 109:3684 110:1627 111:1870 112:1393 113:1413 114:1131 115:1721 116:1694 117:1916 118:2181 119:1625 120:1047 121:1032 122:2287 123:1640 124:1446 125:1960 128:1231 129:677 130:524 131:1626 132:712 133:218 134:1047 135:239 136:553 137:707 138:2030 139:840 140:572 141:814 142:797 143:1014 144:901 145:505 146:1251 147:792 148:1714 149:795 150:787 151:1006 152:1008 153:321 154:2627 155:977 156:1671 157:903 158:672 159:1921 160:1511 161:917 162:2676 163:778 164:1129 165:1567 166:439 167:1382 168:3285 169:871 170:4010 171:529 172:1093 173:2188 174:1012 175:879 176:2305 177:3994 178:2548 179:1334 180:2089 181:2436 182:2688 183:1049 184:1153 185:14732 186:3706 187:2397 188:2912 189:1949 190:8294 191:1449 192:10050 193:6556 194:5376 195:4053 196:2988 197:1744 198:5773 199:5986 200:7319 201:5111 202:10152 203:10185 204:4606 205:2991 206:3273 207:3273 208:3981 209:4230 210:3924 211:1987 212:3059 213:2895 214:1075 215:52 216:5978 217:2198 218:919 219:578 220:1850 221:996 222:991 223:1440 End of report

1 0

Last Mile Design
by David Ratkay 15 Feb '19

15 Feb '19

I am not sure if this is a easy question to answer. But I am wondering what ISP's do for their residential and business customers for designing POP's that they usually access to get theur traffic into a given ISP and beyond. Is it usually a L1/L2 connection from the CE to the last mile POP? Or L2 even within the last mile POP. Do you just have POP's delegated to residential users and a separate POP for business users. Or is it done on a geographical basis. So for this region of City-A we manage both residential and business customers at this same POP.

23 77

Whitebox with OSPF optics
by Sami Joseph 15 Feb '19

15 Feb '19

Hey, Have you guys seen any ODM vendor that makes platforms based on Tomahawk 3 or later OSPF optics ? Thank you Sam

2 1

cgnat ams0 vrf-aware flow data export help
by Aaron Gould 14 Feb '19

14 Feb '19

Need assistance with exporting flow data for inside interface of cgnat ams0 aggregated multiservice interface I have MX960 with MS-MPC-128G doing cgnat using AMS0 (aggregated multiservice of underlying mams interfaces) using next-hop-style vrf-aware cgnat. I need the cgnat inside domain interface (ams0.551) to be configured to export flow data (jflow, sflow, ipfix, whichever version i can use) to a flow collector server, this is important so we can have flow data of *pre-nat) private ip traffic. Anyone know how ? -Aaron

1 0

adding graphs for actually unreachable RPKI INVALID prefixes to RPKI Monitor?
by nusenu 14 Feb '19

14 Feb '19

Dear NIST RPKI Monitor Team, thanks for creating and maintaining the RPKI Monitor https://rpki-monitor.antd.nist.gov/#rpki_adopters I've seen your graphs in multiple routing security presentations :) What do you think about adding graphs that show the amount of actually unreachable prefixes and IP space? (prefix where no alternative valid/unknown announcement exists) I think such graphs would help us focus on those prefixes that we should have to tackle first. This page contains examples of INVALID prefixes that would still be reachable in a route origin validating environment (see the RPKI validator screenshots): https://medium.com/@nusenu/towards-cleaning-up-rpki-invalids-d69b03ab8a8c kind regards, nusenu -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

5 8