February 2023 - NANOG - lists.nanog.org

Increasing problems with geolocation/IPv4 access
by Jared Mauch 06 Feb '23

06 Feb '23

I’ve been seeing an increasing problem with IP space not having the ability to be used due to the behaviors of either geolocation or worse, people blocking IP space after it’s been in-use for a period of time. Before I go back to someone at ARIN and say “your shiny unused 4.10 IP space” is non-functional and am at a place where I need to start/restart/respawn the timer, I have a few questions for people: 1) Do you see 23.138.114.0/24 in any feeds from a security provider that say it can/should be blocked? If so, I’d love to hear from you to track this down. Over the new year we had some local schools start to block this IP space. 2) many companies have geolocation feeds and services that exist and pull in data. The reputable people are easy to find, there are those that are problematic from time-to-time (I had a few customers leave Sling due to the issues with that service). 3) Have you had similar issues? How are you chasing all the issues? We’ve seen things from everything works except uploading check images to banks, to other financial service companies block the space our customers are in. If we move them to another range this solves the problem. 4) We do IPv6, these places aren’t IPv6 modern at all, so that’s no help. 5) IRR+geofeed are published of course. I’m thinking that it might be worthwhile that IP space have published placeholders when it’s well understood, eg: ARIN 4.9 space, I can predict what our next allocation would be, it would be great to have it be pre-warmed. I’ve only seen a few complaints against all our IP space over time, so I don’t think there’s anything malicious coming from the IP space to justify it, but it’s also possible they didn’t make it through. If you’re with the FKA Savvis side, can you also ping me, I’d like to see if you can reach out to our most recent complaint source to see if we can find who is publishing this. Same if you’re with Merit or the Michigan Statewide Educational Network - your teachers stopped being able to post to powerschool for their students over the new year break. They’ve fed it up to their tech people towards the ISD. Details available off-list. Any insights are welcome, and as I said, I’d like to understand where the source list is as it starts out working then gradually breaks, so someone is publishing things and they are going out further. - Jared

11 13

Typical last mile battery runtime (protecting against power cuts)
by Israel G. Lugo 06 Feb '23

06 Feb '23

Hi folks, At $day_job, I have a team of engineers who are oncall for critical services in the United Kingdom. For $reasons, the national power grid is announcing the possibility of rolling power cuts over the coming months. Right now it's "unlikely", but possible. If cuts do happen, it'll be 3+ hours, possibly several times/day. I'm looking at the cost/benefit of deploying small UPSes at people's homes, to protect their network access when oncall. Just to power the home router (+ONT if FTTP), and keep a charged laptop. I figure anything smallish should be enough for a few hours. Question is, how much battery runtime can I typically expect from ISPs' last mile infra. People will have a random mix of DSL, FTTP, DOCSIS. Another alternative is tethering with 4G. - For FTTP, I *think* (but am not sure) that the UK mostly uses PON, so guess it would be runtime of OLT and onwards - For DSL: runtime of DSLAM cabinet and onwards - For CATV: CMTS and onwards, maybe any active equipments in the HFC to the CPE? - For 4G: BSS and onwards Could anyone with last mile experience help with some ballpark figures? I.e. 15 min vs 8h or 8 days. Thank you, Israel

10 31

Looking for PoCs of rootlayer.net in Amsterdam. - AS51447 and in upstream providers
by irish.masms 06 Feb '23

06 Feb '23

Hello NANOG – longtime lurker, first time poster. I am requesting some assistance today with stopping a pervasive malware campaign being sent via email from multiple open proxies in the following IP blocks: 45.137.20.0 - 45.137.23.255 185.222.56.0 - 185.222.59.255 This IP space is assigned to rootlayer.net in Amsterdam. - AS51447 % Abuse contact for 'AS51447' is 'complain(a)rootlayer.net' All email has contained some sort of malicious code: ransomware, trojans, info sealers, and other various malware (some known and some brand new/not detected yet). The email content is spoofing various legitimate companies and banks. Since the beginning of the year when I became involved in a particular customer (elderly owner of a small business), we have been sending at least 5 complaints a day (one for each email) to complain(a)rootlayer.net, all reporting has been ignored. The most recent spoof & malware email was received at 16:33 PM PST 5 Feb 2023. Frankly, we have grown tired of filing abuse complaints into the black hole while an elderly gentleman is being targeted. I am not sure a contact at Rootlayer will be helpful at this point, but if someone has a contact it would be appreciated. More importantly, anyone have a contact at their upstream providers that may be able to beat down these criminal activities and Rootlayer? AS49981 - WorldStream B.V. AS49453 - Global Layer B.V. Any assistance would be greatly appreciated – thank you. Stay safe,

1 0

Does anyone know of a martin broadhurst?
by Dave Taht 05 Feb '23

05 Feb '23

He was apparently based in cambridge, but his site is down. Recently I stumbled across a series of articles by him that were lovingly illustrative, incredibly clearly well written, and appeared to use a C library that I don't have, covering a ton of fundamental algorithms that I would like to have in my toolkit, still, in C, because that is how I still think. I first found him whilst I was looking for a binpacking algorithm(s) and benchmarks for how well they performed on modern hardware. (I am trying to wedge 40m queues into 16 cores every 10ms) https://web.archive.org/web/20190530024749/http://www.martinbroadhurst.com/… And then I started reading the rest of his canon: Wow: https://web.archive.org/web/20190704202816/http://www.martinbroadhurst.com/… Stuff like (hit the archive per above to get these) http://www.martinbroadhurst.com/bellman-ford-algorithm-in-c.html really clean avl example: http://www.martinbroadhurst.com/avl-tree-in-c.html Anyway, given that the site is down, and he hasn´t posted anything in a year, I fear he has passed on. I did find an obituary that had about the right timing in 2021, and he had the neckbeard... Did/does anyone here know him? -- This song goes out to all the folk that thought Stadia would work: https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-69813666656… Dave Täht CEO, TekLibre, LLC

1 0

Contact for androidpolice.com
by Justin Krejci 03 Feb '23

03 Feb '23

Any contacts available that are responsible for androidpolice.com website hosting? Some of our IP space is not able to access their website. Other IP addresses of ours are working just fine. This appears to be some kind HTTP protocol layer issue but only affecting certain IP addresses. I am guessing it is some kind of web application firewall using outdated IP list data. Yes I know it is hosted at Amazon but every time I have tried to go through Amazon for support with websites they are hosting, they have 100% of the time told me they can't and/or won't help me with website hosting issues on their web platform; I have to go through their customer... which I don't have any good contact info for. I've tried reaching them on twitter, I've tried blindly emailing people listed on their website guessing their email addresses, etc. I have had zero response. Thanks! Justin

1 0

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 03 Feb '23

03 Feb '23

This is an automated weekly mailing describing the state of the Global IPv4 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 https://thyme.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. IPv4 Routing Table Report 04:00 +10GMT Sat 04 Feb, 2023 BGP Table (Global) as seen in Japan. Report Website: https://thyme.apnic.net Detailed Analysis: https://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 919404 Prefixes after maximum aggregation (per Origin AS): 347822 Deaggregation factor: 2.64 Unique aggregates announced (without unneeded subnets): 445727 Total ASes present in the Internet Routing Table: 74078 Prefixes per ASN: 12.41 Origin-only ASes present in the Internet Routing Table: 63572 Origin ASes announcing only one prefix: 26134 Transit ASes present in the Internet Routing Table: 10506 Transit-only ASes present in the Internet Routing Table: 438 Average AS path length visible in the Internet Routing Table: 4.2 Max AS path length visible: 55 Max AS path prepend of ASN (265020) 50 Prefixes from unregistered ASNs in the Routing Table: 951 Number of instances of unregistered ASNs: 961 Number of 32-bit ASNs allocated by the RIRs: 41183 Number of 32-bit ASNs visible in the Routing Table: 34103 Prefixes from 32-bit ASNs in the Routing Table: 166598 Number of bogon 32-bit ASNs visible in the Routing Table: 31 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 521 Number of addresses announced to Internet: 3062699648 Equivalent to 182 /8s, 141 /16s and 22 /24s Percentage of available address space announced: 82.7 Percentage of allocated address space announced: 82.7 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.6 Total number of prefixes smaller than registry allocations: 312179 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 240580 Total APNIC prefixes after maximum aggregation: 68793 APNIC Deaggregation factor: 3.50 Prefixes being announced from the APNIC address blocks: 235600 Unique aggregates announced from the APNIC address blocks: 97865 APNIC Region origin ASes present in the Internet Routing Table: 13261 APNIC Prefixes per ASN: 17.77 APNIC Region origin ASes announcing only one prefix: 3847 APNIC Region transit ASes present in the Internet Routing Table: 1771 Average APNIC Region AS path length visible: 4.4 Max APNIC Region AS path length visible: 26 Number of APNIC region 32-bit ASNs visible in the Routing Table: 8531 Number of APNIC addresses announced to Internet: 773543680 Equivalent to 46 /8s, 27 /16s and 87 /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-151865 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: 267075 Total ARIN prefixes after maximum aggregation: 121357 ARIN Deaggregation factor: 2.20 Prefixes being announced from the ARIN address blocks: 269014 Unique aggregates announced from the ARIN address blocks: 130096 ARIN Region origin ASes present in the Internet Routing Table: 19068 ARIN Prefixes per ASN: 14.11 ARIN Region origin ASes announcing only one prefix: 6982 ARIN Region transit ASes present in the Internet Routing Table: 1956 Average ARIN Region AS path length visible: 3.7 Max ARIN Region AS path length visible: 35 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4736 Number of ARIN addresses announced to Internet: 1286223616 Equivalent to 76 /8s, 170 /16s and 55 /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-401308 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, 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: 264437 Total RIPE prefixes after maximum aggregation: 122675 RIPE Deaggregation factor: 2.16 Prefixes being announced from the RIPE address blocks: 260933 Unique aggregates announced from the RIPE address blocks: 156189 RIPE Region origin ASes present in the Internet Routing Table: 28215 RIPE Prefixes per ASN: 9.25 RIPE Region origin ASes announcing only one prefix: 12037 RIPE Region transit ASes present in the Internet Routing Table: 3969 Average RIPE Region AS path length visible: 4.2 Max RIPE Region AS path length visible: 34 Number of RIPE region 32-bit ASNs visible in the Routing Table: 10996 Number of RIPE addresses announced to Internet: 718364800 Equivalent to 42 /8s, 209 /16s and 96 /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-213403 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: 117476 Total LACNIC prefixes after maximum aggregation: 28532 LACNIC Deaggregation factor: 4.12 Prefixes being announced from the LACNIC address blocks: 116671 Unique aggregates announced from the LACNIC address blocks: 49129 LACNIC Region origin ASes present in the Internet Routing Table: 11000 LACNIC Prefixes per ASN: 10.61 LACNIC Region origin ASes announcing only one prefix: 2663 LACNIC Region transit ASes present in the Internet Routing Table: 2281 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 55 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8776 Number of LACNIC addresses announced to Internet: 176175616 Equivalent to 10 /8s, 128 /16s and 58 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-273820 + 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: 28885 Total AfriNIC prefixes after maximum aggregation: 5731 AfriNIC Deaggregation factor: 5.04 Prefixes being announced from the AfriNIC address blocks: 36665 Unique aggregates announced from the AfriNIC address blocks: 12023 AfriNIC Region origin ASes present in the Internet Routing Table: 1718 AfriNIC Prefixes per ASN: 21.34 AfriNIC Region origin ASes announcing only one prefix: 605 AfriNIC Region transit ASes present in the Internet Routing Table: 331 Average AfriNIC Region AS path length visible: 5.0 Max AfriNIC Region AS path length visible: 31 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1064 Number of AfriNIC addresses announced to Internet: 108071936 Equivalent to 6 /8s, 113 /16s and 12 /24s AfriNIC AS Blocks 36864-37887, 327680-329727 & ERX transfers AfriNIC Address Blocks 41/8, 45/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 9808 9448 8884 50 CHINAMOBILE-CN China Mobile Communicati 7545 5875 786 703 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4859 4192 75 ERX-CERNET-BKB China Education and Rese 7552 3636 1331 21 VIETEL-AS-AP Viettel Group, VN 7713 3504 1043 65 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3376 1874 96 VNPT-AS-VN VNPT Corp, VN 9498 2721 499 238 BBIL-AP BHARTI Airtel Ltd., IN 4766 2528 11251 592 KIXS-AS-KR Korea Telecom, KR 24560 2363 847 437 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 45090 2184 1438 79 TENCENT-NET-AP Shenzhen Tencent Compute Complete listing at https://thyme.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 16509 7880 10722 2910 AMAZON-02, US 11492 4532 300 602 CABLEONE, US 7155 3899 265 33 VIASAT-SP-BACKBONE, US 22773 3663 3064 295 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3502 1320 63 SHAW, CA 16625 3307 1672 2421 AKAMAI-AS, US 749 3036 50571 2303 DNIC-AS-00749, US 7018 2590 24128 1572 ATT-INTERNET4, US 396982 2589 3496 365 GOOGLE-CLOUD-PLATFORM, US 30036 2567 367 356 MEDIACOM-ENTERPRISE-BUSINESS, US Complete listing at https://thyme.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 6985 1706 146 UNI2-AS, ES 9121 6106 1692 17 TTNET, TR 39891 4561 269 58 ALJAWWALSTC-AS, SA 20940 4028 3399 177 AKAMAI-ASN1, NL 8551 3895 370 37 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2941 2290 908 ROSTELECOM-AS, RU 47331 2782 409 2090 TTNET, TR 9009 2695 256 1369 M247, RO 34984 2259 359 608 TELLCOM-AS, TR 6849 2197 339 19 UKRTELNET, UA Complete listing at https://thyme.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 11072 3346 588 Uninet S.A. de C.V., MX 10620 3479 508 859 Telmex Colombia S.A., CO 11830 2262 369 64 Instituto Costarricense de Electricidad 13999 2237 371 602 Mega Cable, S.A. de C.V., MX 28573 1353 2328 263 Claro NXT Telecomunicacoes Ltda, BR 6503 1297 339 517 Axtel, S.A.B. de C.V., MX 3816 1290 742 155 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1151 369 22 Telefonica del Peru S.A.A., PE 11664 1108 181 460 Techtel LMDS Comunicaciones Interactiva 26615 1018 2466 43 TIM SA, BR Complete listing at https://thyme.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24835 1539 533 30 RAYA-AS, EG 24863 1501 393 21 LINKdotNET-AS, EG 36992 1347 1517 277 ETISALAT-MISR, EG 36903 1242 550 99 MT-MPLS, MA 29571 996 67 53 ORANGE-COTE-IVOIRE, CI 36935 884 520 42 Vodafone-, EG 6713 548 1861 34 IAM-AS, MA 15399 526 54 46 WANANCHI-, KE 37342 494 32 1 MOVITEL, MZ 24757 491 73 5 EthioNet-AS, ET Complete listing at https://thyme.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 11072 3346 588 Uninet S.A. de C.V., MX 9808 9448 8884 50 CHINAMOBILE-CN China Mobile Communicati 16509 7880 10722 2910 AMAZON-02, US 12479 6985 1706 146 UNI2-AS, ES 9121 6106 1692 17 TTNET, TR 7545 5875 786 703 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4859 4192 75 ERX-CERNET-BKB China Education and Rese 39891 4561 269 58 ALJAWWALSTC-AS, SA 11492 4532 300 602 CABLEONE, US 20940 4028 3399 177 AKAMAI-ASN1, NL Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 9808 9448 9398 CHINAMOBILE-CN China Mobile Communications Grou 12479 6985 6839 UNI2-AS, ES 9121 6106 6089 TTNET, TR 7545 5875 5172 TPG-INTERNET-AP TPG Telecom Limited, AU 16509 7880 4970 AMAZON-02, US 4538 4859 4784 ERX-CERNET-BKB China Education and Research Net 39891 4561 4503 ALJAWWALSTC-AS, SA 11492 4532 3930 CABLEONE, US 7155 3899 3866 VIASAT-SP-BACKBONE, US 8551 3895 3858 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo Complete listing at https://thyme.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 398083 UNALLOCATED 5.133.124.0/24 399587 UT, US 33123 UNALLOCATED 8.10.69.0/24 11168 SCC, US 16641 UNALLOCATED 8.10.194.0/24 3356 LEVEL3, US 16641 UNALLOCATED 8.10.210.0/24 3356 LEVEL3, US 25674 UNALLOCATED 8.12.76.0/24 3356 LEVEL3, US 16641 UNALLOCATED 8.12.250.0/24 3356 LEVEL3, US 25674 UNALLOCATED 8.14.115.0/24 3356 LEVEL3, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 25674 UNALLOCATED 8.19.146.0/24 3356 LEVEL3, US 53775 UNALLOCATED 8.20.88.0/24 7029 WINDSTREAM, US Complete listing at https://thyme.apnic.net/current/data-badAS Prefixes from the Special Purpose Address Registry (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at https://thyme.apnic.net/current/data-spar Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.131.185.0/24 Origin: 174 COGENT-174, US 23.131.185.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.131.186.0/24 Origin: 174 COGENT-174, US 23.131.186.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.131.187.0/24 Origin: 174 COGENT-174, US 23.131.187.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.131.188.0/24 Origin: 174 COGENT-174, US 23.131.188.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.136.112.0/24 Origin: 54835 UNASSIGNED 23.136.112.0/24 Transit: 21559 OSNET, PR Complete listing at https://thyme.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:16 /9:13 /10:39 /11:101 /12:295 /13:580 /14:1199 /15:2038 /16:13481 /17:8308 /18:13910 /19:25169 /20:44262 /21:52300 /22:110175 /23:98335 /24:548376 /25:807 /26:0 /27:0 /28:0 /29:0 /30:0 /31:0 /32:0 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 12479 6048 6985 UNI2-AS, ES 9121 5285 6106 TTNET, TR 8151 5079 11072 Uninet S.A. de C.V., MX 39891 3552 4561 ALJAWWALSTC-AS, SA 11492 3447 4532 CABLEONE, US 8551 3367 3895 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 6327 3310 3502 SHAW, CA 7155 2988 3899 VIASAT-SP-BACKBONE, US 22773 2706 3663 ASN-CXA-ALL-CCI-22773-RDC, US 47331 2403 2782 TTNET, TR Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1642 2:1233 3:168 4:5 5:4247 6:114 7:5 8:1554 9:1 11:172 12:1588 13:375 14:2358 15:290 16:79 17:367 18:395 20:243 21:4 22:188 23:6060 24:2497 25:4 27:2643 29:19 31:2500 32:106 34:9 35:107 36:1887 37:4589 38:4087 39:836 40:154 41:3939 42:1061 43:2332 44:302 45:16418 46:4128 47:382 49:1748 50:1835 51:382 52:1551 54:395 55:857 56:8 57:79 58:1745 59:1165 60:993 61:2428 62:2624 63:1933 64:5661 65:2317 66:4916 67:3045 68:1349 69:4154 70:1254 71:660 72:2970 74:2599 75:1457 76:599 77:2400 78:3942 79:3173 80:2070 81:1854 82:1480 83:1239 84:1521 85:3767 86:752 87:1950 88:2887 89:3565 90:594 91:7643 92:2005 93:2597 94:3527 95:4863 96:1328 97:346 98:1159 99:740 100:75 101:1067 102:2545 103:30899 104:4573 105:484 106:848 107:2513 108:920 109:4381 110:2081 111:3337 112:2044 113:1546 114:1615 115:2037 116:1906 117:2553 118:2289 119:1907 120:1770 121:1119 122:2596 123:2148 124:1605 125:2360 128:1303 129:1058 130:981 131:1988 132:802 133:406 134:1910 135:297 136:865 137:925 138:2560 139:1550 140:1183 141:1469 142:1426 143:1497 144:1197 145:351 146:1879 147:1556 148:2296 149:1890 150:869 151:1139 152:1830 153:480 154:3933 155:1400 156:1668 157:1293 158:1016 159:2268 160:2541 161:1421 162:3519 163:1490 164:1618 165:1653 166:838 167:1733 168:3890 169:916 170:4571 171:883 172:3505 173:2962 174:1025 175:1168 176:3689 177:4597 178:3556 179:2141 180:2365 181:3387 182:3277 183:1933 184:2338 185:19999 186:4666 187:3923 188:4086 189:3491 190:9112 191:1437 192:10954 193:8817 194:7240 195:5122 196:3009 197:2405 198:5953 199:6105 200:7740 201:5859 202:10635 203:10033 204:4601 205:3523 206:3865 207:3412 208:4081 209:4821 210:4436 211:2498 212:4105 213:3554 214:1096 215:56 216:6596 217:2647 218:1278 219:567 220:2026 221:969 222:844 223:2082 End of report

1 0

Re: Spectrum (legacy TWC) Infrastructure - Contact Off List
by Clayton Zekelman 03 Feb '23

03 Feb '23

At 08:43 PM 02/02/2023, Eric Kuhnke wrote: >There is "microtrenching" and then there is >microtrenching. Very different things are >sometimes described by the same name. Some of >what Google tried to go was exceedingly shallow, >like 4 inches down. Cheap microtrenching done >too quick and too shallow has given the concept a bad name. The local ILEC is doing that here - they use a spade to make a little slot in the customer's lawn and shove the cable in. If they have to cross a driveway or sidewalk, they dig out the expansion joint, shove the cable in and dump some cold patch in the gap. If they have to run multiple cables, they use a concrete saw to make the gap a bit wider. >There is microtrenched fiber in Vancouver BC >that is close to 20 years old now throughout the >downtown core that is nearly problem-free. The >difference is that it is 12+ inches down and was >installed using large, noisy, water cooled >diamond-grit concrete saws cutting deep slits >into the joints between streets and curbs, or >concrete curbs and sidewalks,Â duct inserted, >then backfilled with grouting. It's deep enough >where it crosses roads that re-paving the road >by first grinding off the top several inches of >surface is extremely unlikely to disturb the duct. I'm familiar with the slightly more robust technique deployed by companies like Teraspan. I'm sure it works much better in the milder climate in BC. There are microtrench/VIF networks in Toronto and Ottawa as well. A few years ago, they were re-building one of the roads in the downtown core in Toronto, and the entire microtrenched network (mini handholes and all) had been lifted out of the street area and laid on the sidewalk, and protected with barriers and safety cones, etc. I just shook my head... -- Clayton Zekelman Managed Network Systems Inc. (MNSi) 3363 Tecumseh Rd. E Windsor, Ontario N8W 1H4 tel. 519-985-8410 fax. 519-985-8409

1 0

Re: Spectrum (legacy TWC) Infrastructure - Contact Off List
by Clayton Zekelman 03 Feb '23

03 Feb '23

It may. We don't use it. Too many freeze/thaw cycles each winter around here. It would get destroyed in a few years. Google tried to cheap out in Louisville... didn't quite work out https://www.theverge.com/2019/2/7/18215743/google-fiber-leaving-louisville-… - although that was even more sketchy than traditional microtrenching. As for rural, the business case becomes even more difficult when you're measuring kilometers per home passed instead of homes passed per kilometer... At 07:58 PM 02/02/2023, Kevin Shymkiw wrote: >Clayton, > >Did you leverage things like micro trenching for >this project?Â I may be mislead, but I thought >micro trenching these days has helped drive the >cost of doing this down fairly significantly. > >Kevin > >On Thu, Feb 2, 2023 at 17:56 Clayton Zekelman ><<mailto:clayton@mnsi.net>clayton(a)mnsi.net> wrote: > >The cost is not low.Â Trust me on that.Â I've >been involved in a pretty massive suburban fibre >deployment for the past decade... I expect we'll >make money sometime in the 2030's... in time for me to retire. > >At 12:13 PM 02/02/2023, Forrest Christian (List Account) wrote: >>The cost to build physical layer in much of the >>suburban and somewhat rural US is low enough >>anymore that lots of smaller, independent, ISPs >>are overbuilding the incumbent with fiber and >>taking a big chunk of their customer base >>because they are local and care.ÃÂ And making money while doing it.Ã >> > -- Clayton Zekelman Managed Network Systems Inc. (MNSi) 3363 Tecumseh Rd. E Windsor, Ontario N8W 1H4 tel. 519-985-8410 fax. 519-985-8409

2 1

Calgary Internet Exchange (YYCIX) deploys world's first ASPA-filtering Route Servers
by Job Snijders 02 Feb '23

02 Feb '23

CALGARY, CA-AB, Feb. 2, 2023 - The Calgary Internet Exchange (YYCIX) is thrilled to announce the deployment of the world's first ASPA-filtering Route Servers on a public peering fabric. The YYCIX Route Servers drop ASPA-invalid BGP routes in order to protect multilateral peers. ASPA (Autonomous System Provider Authorization) is a free RPKI-based technology for detection and mitigation of BGP route leaks. ASPA enables holders of Autonomous System identifiers to securely authorize one or more other Autonomous Systems as their upstream providers, in turn enabling Relying Parties (ISPs and IXPs) to use this cryptographically verifiable information to automatically stop improbable BGP paths from spreading through the global Internet routing system. ASPA complements other routing safety & security mechanisms: RPKI-ROV helps guard against fat-finger keyboard input errors, BGPsec helps establish strong assurances about BGP message authenticity & integrity, and finally ASPA helps stop route leaks. The key to worry-free routing operations will be to use all three in tandem. The ASPA specification is in active development as a freely accessible open standard through the collaborative Internet Engineering Task Force (IETF) process. YYCIX volunteers took on a leading role as early adopters (or 'lighthouse customer') to foster an environment in which real-world feedback can be contributed to the OpenBGPD developers and ASPA specification authors in the SIDROPS working group. Our hope is that many vendors and operators will embrace ASPA in the years to come. About YYCIX Internet Exchange Community Ltd =========================================== YYCIX is incorporated as a volunteer-driven tax-exempt non-profit corporation in Canada's third-largest municipality. YYCIX provides Alberta residents with direct access to local Internet content and helps increase the transfer speed of Internet communications between Alberta companies, friends, neighbors and family members. https://www.yycix.ca/ About OpenBGPD & Rpki-client ============================ Rpki-client is an freely usable and secure implementation of the RPKI for Relying Parties to facilitate validation of BGP announcements. The program queries the global RPKI repository system, verifies all cryptographic signatures, and outputs validated data in configuration formats suitable for OpenBGPD and StayRTR. https://www.rpki-client.org/ OpenBGPD is a free implementation of the IETF's Border Gateway Protocol suitable for ISPs and IXPs. OpenBGPD allows ordinary machines to be used as routers or route servers exchanging routes with other systems. ASPA-filtering in OpenBGPD was developed with support from the German Ministry for Economic Affairs & Climate Action's Sovereign Tech Fund, and the Route Server Support Foundation (RSSF - https://www.rssf.nl/) https://www.openbgpd.org/ OpenBGPD and rpki-client are part of the OpenBSD Project; and run on a wide variety of operating systems such as Debian, Ubuntu, Alpine, CentOS, Fedora, FreeBSD, Red Hat, and of course OpenBSD!

1 0

N87 Agenda, Keynote, Hackathon + More!
by Nanog News 02 Feb '23

02 Feb '23

*Download NANOG 87 Agenda Now! * *Save Your Favorite Talks + Sync up Your Calendars * Don't miss any of your favorite talks. Check out our NANOG 87 agenda and download the full event calendar. *VIEW AGENDA <https://www.nanog.org/events/nanog-87/agenda/> * *Micheal Bailey to be a N87 Keynote Speaker* *Presenting "A Security Practitioner’s Guide to Internet Measurement"* Over the last 20 years, Bailey and his colleagues have been engaged in understanding and improving the Internet through large-scale measurement and data. *MORE INFO * <https://www.nanog.org/events/nanog-87/> *Committee Nominations will be Closing Soon! * *Nomination Form will Close 14 February 2023* Time is running out for nominations for six open NANOG Committees. If you are passionate about NANOG and/or know a strong candidate, please consider running or nominating another community member! *MORE INFO* <https://www.nanog.org/members/elections/2023-committee-nominations/> *Hackathon will Kick Off Tomorrow! * *Intro/Tutorial/Team Formation will Begin Virtually Friday, 03 Feb. * *Full Hackathon Schedule:* Friday, 03 Feb. - Hackathon welcome, introduction, infrastructure tutorial, idea-pitching, and the team-forming session will take place over Zoom. Saturday, 11 Feb. - Start of the hackathon; this day will be a hybrid day between virtual support hours and an on-site conference venue tutorial in the evening. Sunday, 12 Feb. - True hybrid day with people continuing to work virtually and with dedicated facilities (workspace, wifi, etc.) for those at the conference venue. *REGISTER NOW <https://www.nanog.org/events/nanog-87-hackathon/>* *Sponsorships Still Available for NANOG 87* *Invest in the Strength of the Community we Have Built* - Sponsorship Benefits: - Showcase your newest technologies + solutions - Increase your brand’s visibility + reach - Amplify your organization’s message - Connect with industry influencers + decision-makers - Empower people + inspire change *MORE INFO* <https://www.nanog.org/participate/nanog-sponsorship-opportunities-working/>

1 0