April 2022 - Test - lists.nanog.org

Dark\Conduit Pricing
by Mike Hammett 26 Apr '22

26 Apr '22

ISP-Bandwidth used to be full of this kind of conversation. I'm not sure if anything ever replaced it. Where would be a good place to go to get the pulse of where the industry is at on dark fiber\empty conduit pricing? I understand that YMMV with supply and demand. Going into a major facility would be highly desirable, but may also have a lot of competition, depending on the Z location. In the middle of nowhere might be really expensive because no one else is there... or really cheap because it's on a competitive route. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com

1 0

Seeing a lot of ROUTING-FIB-3-UPD_MSG_TOO_BIG messages today
by Drew Weaver 25 Apr '22

25 Apr '22

Hello everyone, I've seen this a bit in the past with 1-2 routes, but today it's been happening basically all morning with several different routes. ROUTING-FIB-3-UPD_MSG_TOO_BIG I've chased it down from a vendor level and they implied that it is just informational, my question is why do these sort of updates seem to be sent to the Internet's routing table in bursts? Is that a testing thing? Is anyone else seeing this today as well?

3 4

fs.com Ethernet switches
by Richard Angeletti 25 Apr '22

25 Apr '22

Wondering if anyone on the list has any experiences with fs.com Ethernet switches that they are willing to share (good or bad)? We're looking for some cost effective L2 only 10Gb-T switches and their S58XX switches have come up as a potential option. Thanks, Rich

5 4

NANOG 85 Attendee List Announcement
by Nanog News 25 Apr '22

25 Apr '22

NANOGers, It has come to our attention that companies not affiliated with the NANOG organization are attempting to contact attendees and exhibitors offering to sell our attendee list. Should you be contacted by a company offering to sell the NANOG 85 Attendee list, be aware, this is fraudulent. If they contact you, we urge you not to engage with these companies or provide your credit card information to any such unauthorized vendor. If you have any questions about the meeting, please contact us directly at: nanog-support(a)nanog.org. We look forward to seeing you in Montréal, Quebec! Sincerely, NANOG Support nanog-support(a)nanog.org

1 0

ARIN 49 is now starting - webcast and remote participation details
by John Curran 25 Apr '22

25 Apr '22

Folks - ARIN 49 is starting now - It’s not too late to register to participate<https://www.arin.net/ARIN49>, or you can view a webcast of the meeting<https://www.arin.net/ARIN49materials>. Best wishes, /John John Curran President and CEO American Registry for Internet Numbers === ARIN 49 Begins Today<https://www.arin.net/announcements/20220425/> The ARIN 49 hybrid Public Policy and Members Meeting begins today at 9:00 AM CT! Join us today through 27 April 2022 at the Loews Vanderbilt Hotel in Nashville, Tennessee, or virtually via Zoom to discuss policy, security updates, global RIR reports and more. It’s not too late to register to participate<https://www.arin.net/ARIN49>, or you can view a webcast of the meeting<https://www.arin.net/ARIN49materials>. IPv6 Panel On Tuesday, 26 April, join our panelists for a discussion on “Why Doesn’t the Internet Migrate Entirely to IPv6?”<https://arin.swoogo.com/arin49/1957551>, moderated by ARIN President and CEO John Curran. How to Attend the Meeting Each morning during the meeting, you’ll receive a reminder email with information about that day’s session. If you’re a virtual attendee, that email will contain the link you’ll need to access the Zoom meeting as well as our planned virtual social events for that day. Virtual attendees will be allowed into the Zoom 15 minutes before the meeting starts so you can say hello and chat with other attendees. If you’re on site in Nashville, just take a seat before the meeting begins. Meeting Guides We want to make sure you are ready to participate at the meeting. Before the meeting starts, visit the ARIN 49 materials site<https://www.arin.net/participate/meetings/ARIN49> to get a sneak peek at the presentations and any additional materials and guides. ===

1 0

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 22 Apr '22

22 Apr '22

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 23 Apr, 2022 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: 897069 Prefixes after maximum aggregation (per Origin AS): 337713 Deaggregation factor: 2.66 Unique aggregates announced (without unneeded subnets): 430679 Total ASes present in the Internet Routing Table: 73062 Prefixes per ASN: 12.28 Origin-only ASes present in the Internet Routing Table: 62711 Origin ASes announcing only one prefix: 25747 Transit ASes present in the Internet Routing Table: 10351 Transit-only ASes present in the Internet Routing Table: 368 Average AS path length visible in the Internet Routing Table: 4.4 Max AS path length visible: 65 Max AS path prepend of ASN (267602) 58 Prefixes from unregistered ASNs in the Routing Table: 873 Number of instances of unregistered ASNs: 878 Number of 32-bit ASNs allocated by the RIRs: 39171 Number of 32-bit ASNs visible in the Routing Table: 32539 Prefixes from 32-bit ASNs in the Routing Table: 153339 Number of bogon 32-bit ASNs visible in the Routing Table: 21 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 500 Number of addresses announced to Internet: 3067462272 Equivalent to 182 /8s, 213 /16s and 194 /24s Percentage of available address space announced: 82.9 Percentage of allocated address space announced: 82.9 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: 304272 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 235509 Total APNIC prefixes after maximum aggregation: 66616 APNIC Deaggregation factor: 3.54 Prefixes being announced from the APNIC address blocks: 230404 Unique aggregates announced from the APNIC address blocks: 94659 APNIC Region origin ASes present in the Internet Routing Table: 12580 APNIC Prefixes per ASN: 18.32 APNIC Region origin ASes announcing only one prefix: 3578 APNIC Region transit ASes present in the Internet Routing Table: 1726 Average APNIC Region AS path length visible: 4.8 Max APNIC Region AS path length visible: 27 Number of APNIC region 32-bit ASNs visible in the Routing Table: 7780 Number of APNIC addresses announced to Internet: 774164736 Equivalent to 46 /8s, 36 /16s and 209 /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: 261091 Total ARIN prefixes after maximum aggregation: 119889 ARIN Deaggregation factor: 2.18 Prefixes being announced from the ARIN address blocks: 261092 Unique aggregates announced from the ARIN address blocks: 124736 ARIN Region origin ASes present in the Internet Routing Table: 19012 ARIN Prefixes per ASN: 13.73 ARIN Region origin ASes announcing only one prefix: 6900 ARIN Region transit ASes present in the Internet Routing Table: 1949 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 37 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4459 Number of ARIN addresses announced to Internet: 1295350784 Equivalent to 77 /8s, 53 /16s and 124 /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: 257187 Total RIPE prefixes after maximum aggregation: 117442 RIPE Deaggregation factor: 2.19 Prefixes being announced from the RIPE address blocks: 254558 Unique aggregates announced from the RIPE address blocks: 150612 RIPE Region origin ASes present in the Internet Routing Table: 28140 RIPE Prefixes per ASN: 9.05 RIPE Region origin ASes announcing only one prefix: 12053 RIPE Region transit ASes present in the Internet Routing Table: 3979 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 28 Number of RIPE region 32-bit ASNs visible in the Routing Table: 10699 Number of RIPE addresses announced to Internet: 713805952 Equivalent to 42 /8s, 139 /16s and 208 /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: 114636 Total LACNIC prefixes after maximum aggregation: 27630 LACNIC Deaggregation factor: 4.15 Prefixes being announced from the LACNIC address blocks: 114525 Unique aggregates announced from the LACNIC address blocks: 48486 LACNIC Region origin ASes present in the Internet Routing Table: 10953 LACNIC Prefixes per ASN: 10.46 LACNIC Region origin ASes announcing only one prefix: 2651 LACNIC Region transit ASes present in the Internet Routing Table: 2196 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 65 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8644 Number of LACNIC addresses announced to Internet: 176417024 Equivalent to 10 /8s, 131 /16s and 233 /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: 27773 Total AfriNIC prefixes after maximum aggregation: 5457 AfriNIC Deaggregation factor: 5.09 Prefixes being announced from the AfriNIC address blocks: 35990 Unique aggregates announced from the AfriNIC address blocks: 11753 AfriNIC Region origin ASes present in the Internet Routing Table: 1627 AfriNIC Prefixes per ASN: 22.12 AfriNIC Region origin ASes announcing only one prefix: 565 AfriNIC Region transit ASes present in the Internet Routing Table: 326 Average AfriNIC Region AS path length visible: 5.2 Max AfriNIC Region AS path length visible: 34 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 957 Number of AfriNIC addresses announced to Internet: 107442944 Equivalent to 6 /8s, 103 /16s and 115 /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 9147 8884 44 CHINAMOBILE-CN China Mobile Communicati 7545 5912 789 697 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4712 4192 75 ERX-CERNET-BKB China Education and Rese 7552 3592 1330 19 VIETEL-AS-AP Viettel Group, VN 7713 3502 1039 53 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3427 1880 56 VNPT-AS-VN VNPT Corp, VN 4766 2497 11121 601 KIXS-AS-KR Korea Telecom, KR 9498 2397 491 238 BBIL-AP BHARTI Airtel Ltd., IN 45090 2169 1438 79 TENCENT-NET-AP Shenzhen Tencent Compute 4755 2118 429 197 TATACOMM-AS TATA Communications formerl 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 6200 10263 2693 AMAZON-02, US 11492 4474 297 690 CABLEONE, US 22773 3942 3077 365 ASN-CXA-ALL-CCI-22773-RDC, US 7155 3900 264 31 VIASAT-SP-BACKBONE, US 16625 3615 1852 2552 AKAMAI-AS, US 6327 3431 1318 62 SHAW, CA 749 2882 50780 2138 DNIC-AS-00749, US 30036 2617 374 132 MEDIACOM-ENTERPRISE-BUSINESS, US 209 2521 4962 423 CENTURYLINK-US-LEGACY-QWEST, US 20115 2255 3051 492 CHARTER-20115, 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 6787 1730 150 UNI2-AS, ES 9121 6731 1692 17 TTNET, TR 8551 4010 374 39 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 3924 3360 201 AKAMAI-ASN1, NL 39891 3819 220 34 ALJAWWALSTC-AS, SA 12389 2952 2273 908 ROSTELECOM-AS, RU 6849 2907 355 21 UKRTELNET, UA 9009 2473 247 1284 M247, GB 34984 2238 357 632 TELLCOM-AS, TR 47331 2088 328 1598 TTNET, TR 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 10587 3392 559 Uninet S.A. de C.V., MX 10620 3469 518 748 Telmex Colombia S.A., CO 11830 2430 369 63 Instituto Costarricense de Electricidad 13999 1757 296 471 Mega Cable, S.A. de C.V., MX 6503 1452 354 523 Axtel, S.A.B. de C.V., MX 28573 1397 2333 253 CLARO S.A., BR 3816 1255 667 147 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1083 369 21 Telefonica del Peru S.A.A., PE 11664 1023 191 447 Techtel LMDS Comunicaciones Interactiva 11172 961 133 63 Alestra, S. de R.L. de C.V., MX 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 24863 1656 393 21 LINKdotNET-AS, EG 24835 1473 523 33 RAYA-AS, EG 36992 1314 1519 263 ETISALAT-MISR, EG 36903 1199 545 114 MT-MPLS, MA 29571 907 65 59 ORANGE-COTE-IVOIRE, CI 36935 773 520 42 Vodafone-, EG 6713 612 1863 34 IAM-AS, MA 15399 514 51 32 WANANCHI-, KE 37342 468 32 1 MOVITEL, MZ 23889 424 232 16 MauritiusTelecom, MU 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 10587 3392 559 Uninet S.A. de C.V., MX 9808 9147 8884 44 CHINAMOBILE-CN China Mobile Communicati 12479 6787 1730 150 UNI2-AS, ES 9121 6731 1692 17 TTNET, TR 16509 6200 10263 2693 AMAZON-02, US 7545 5912 789 697 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4712 4192 75 ERX-CERNET-BKB China Education and Rese 11492 4474 297 690 CABLEONE, US 8551 4010 374 39 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 22773 3942 3077 365 ASN-CXA-ALL-CCI-22773-RDC, US Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 9808 9147 9103 CHINAMOBILE-CN China Mobile Communications Grou 9121 6731 6714 TTNET, TR 12479 6787 6637 UNI2-AS, ES 7545 5912 5215 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4712 4637 ERX-CERNET-BKB China Education and Research Net 8551 4010 3971 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 7155 3900 3869 VIASAT-SP-BACKBONE, US 39891 3819 3785 ALJAWWALSTC-AS, SA 11492 4474 3784 CABLEONE, US 20940 3924 3723 AKAMAI-ASN1, NL 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 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 46887 LIGHTOWER, US 18604 UNALLOCATED 8.25.204.0/24 3356 LEVEL3, US 394936 UNALLOCATED 8.33.224.0/24 22442 HOU-PHONOSCOPE, US 54338 UNALLOCATED 8.33.241.0/24 6461 ZAYO-6461, US 395438 UNALLOCATED 8.42.206.0/24 3356 LEVEL3, US 395056 UNALLOCATED 8.45.133.0/24 3356 LEVEL3, US 32306 UNALLOCATED 8.46.80.0/24 33652 CMCS, 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.135.82.0/24 Origin: 206203 ASHNET-AS, US 23.135.82.0/24 Transit: 20473 AS-CHOOPA, US 23.141.0.0/24 Origin: 395350 UNASSIGNED 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, US 27.100.7.0/24 Origin: 56096 UNASSIGNED 27.100.7.0/24 Transit: 45455 TH-2S1N-AP Two S One N Co Ltd, Internet 41.57.124.0/22 Origin: 37442 UNASSIGNED 41.57.124.0/22 Transit: 37204 TELONE, ZW 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:41 /11:100 /12:303 /13:592 /14:1203 /15:2060 /16:13529 /17:8262 /18:13908 /19:25201 /20:43733 /21:52325 /22:108575 /23:95988 /24:530390 /25:830 /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 9121 5886 6731 TTNET, TR 12479 5769 6787 UNI2-AS, ES 8151 4243 10587 Uninet S.A. de C.V., MX 8551 3476 4010 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 11492 3380 4474 CABLEONE, US 6327 3243 3431 SHAW, CA 39891 3131 3819 ALJAWWALSTC-AS, SA 7155 2990 3900 VIASAT-SP-BACKBONE, US 22773 2942 3942 ASN-CXA-ALL-CCI-22773-RDC, US 6849 2758 2907 UKRTELNET, UA Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1942 2:1034 3:155 4:7 5:3790 6:103 7:5 8:1565 9:1 11:172 12:1710 13:298 14:2380 15:192 16:45 17:381 18:156 20:194 21:4 22:188 23:5625 24:2301 25:6 27:2595 29:19 31:2417 32:96 34:1 35:73 36:1755 37:4418 38:2809 39:700 40:153 41:3945 42:1076 43:2194 44:288 45:16013 46:4124 47:336 49:1693 50:1933 51:101 52:1412 54:363 55:716 56:8 57:58 58:1806 59:1204 60:957 61:2268 62:2489 63:1955 64:5511 65:2297 66:4853 67:2973 68:1192 69:4146 70:1338 71:658 72:3050 74:2664 75:1387 76:589 77:2179 78:3905 79:3112 80:1975 81:1738 82:1499 83:1209 84:1367 85:3650 86:708 87:1960 88:2734 89:3274 90:521 91:7627 92:1998 93:2594 94:3508 95:4785 96:1298 97:351 98:991 99:736 100:75 101:1041 102:2052 103:28936 104:4361 105:466 106:858 107:2515 108:836 109:4214 110:2074 111:3288 112:2033 113:1537 114:1489 115:1962 116:1901 117:2518 118:2331 119:1853 120:1690 121:1073 122:2577 123:2125 124:1591 125:2116 128:1228 129:1099 130:966 131:2048 132:766 133:373 134:1926 135:291 136:883 137:859 138:2438 139:1503 140:864 141:1403 142:1292 143:1468 144:1213 145:344 146:1814 147:1496 148:2214 149:1731 150:854 151:1083 152:1855 153:458 154:3570 155:1428 156:1859 157:1227 158:1038 159:2110 160:2471 161:1325 162:3459 163:1253 164:1636 165:1613 166:700 167:1712 168:3805 169:833 170:4452 171:831 172:3140 173:3089 174:1022 175:1127 176:3523 177:4636 178:3506 179:2011 180:2277 181:2973 182:3240 183:1954 184:2390 185:19460 186:4360 187:3703 188:3866 189:3205 190:8897 191:1318 192:10993 193:8618 194:6978 195:4965 196:2974 197:2391 198:6030 199:6036 200:7489 201:5675 202:10489 203:10035 204:4559 205:3406 206:3769 207:3393 208:4067 209:4657 210:4267 211:2453 212:4033 213:3424 214:1153 215:67 216:6439 217:2656 218:1274 219:572 220:1950 221:980 222:843 223:2149 End of report

1 0

Re: Geolocation data management practices?
by Justin Krejci 21 Apr '22

21 Apr '22

For corrections/updates, what I have found to be generally successful is 1. make sure to advertise the IP blocks into the DFZ from your ASN as soon as possible 2. make sure ARIN data is accurate (we use ARIN, you may use one of the other registries) 3. update my geofeed, as referenced already in this thread 4. directly contact organizations that have geolocation services but don't subscribe to my geofeed If anyone has any additional geolocation organizations I didn't list, I would be happy to hear about them. Geofeed subscriptions are in place with these organizations IP Info https://ipinfo.io/ https://ipinfo.io/faq/article/49-how-can-i-submit-a-correction https://ipinfo.io/corrections dbip https://db-ip.com/ https://db-ip.com/contact/ support <at> db-ip.com IPGeolocation https://ipgeolocation.io/ support <at> ipgeolocation.io Maxmind https://www.maxmind.com/en/geoip-demo https://support.maxmind.com/geoip-data-correction-request/ Neustar https://www.home.neustar/resources/tools/ip-geolocation-lookup-tool https://www.home.neustar/resources/tools/submit-to-global-ip-database ipintel <at> support.neustar BigDataCloud https://www.bigdatacloud.com/ip-geolocation/ Digital Element https://www.digitalelement.com/geolocation/ https://www.digitalelement.com/contact-us/ ip-data <at> digitalelement.com ip2location https://www.ip2location.com/demo support <at> ip2location.com Only accepts feeds when all entries have a city defined Google https://isp.google.com Set geofeed URL within their ISP portal No geofeed subscriptions in place for these organizations and require individual contact for corrections/updates ipstack https://ipstack.com/ https://ipstack.com/contact Geo IP View https://www.geoipview.com/ andrew <at> geoipview.com email address is not currently receiving mail, as such I assume not many are using this service IPligence http://www.ipligence.com/geolocation https://www.ipligence.com/contact ipdata https://ipdata.co/?ref=iplocation https://ipdata.co/corrections.html corrections <at> ipdata.co working on adding geofeed support IPIP https://en.ipip.net/ip.html sarah <at> ipip.net IPHub https://iphub.info/ IPinsight https://ipinsight.io/ william <at> ipinsight.io Info Sniper https://infosniper.net/ https://infosniper.net/geoip-data-correction.php GeoGuard https://www.geocomply.com/products/geoguard/ ipintelligence <at> geoguard.com More of a "are they using a VPN/hiding service" and not so much of a "Where are they" service. ________________________________ From: NANOG <nanog-bounces+jkrejci=usinternet.com(a)nanog.org> on behalf of Josh Luthman <josh(a)imaginenetworksllc.com> Sent: Thursday, April 21, 2022 9:24 AM To: Rubens Kuhl Cc: Nanog Subject: Re: Geolocation data management practices? Go through this list: https://thebrotherswisp.com/index.php/geo-and-vpn/<https://url-shield.securence.com/?p=1.0&r=jkrejci@usinternet.com&sid=165055…> The RFC only works if they're pulling your feed and they'd only know that if you contact them in the first place. On Thu, Apr 21, 2022 at 9:14 AM Rubens Kuhl < rubensk(a)gmail.com<mailto:rubensk@gmail.com>> wrote: Besides geofeed, there are also geoidx records in IRRs but whether geolocation services actually use geofeed or geoidx remains to be seen. You can see some geoidx: at this IRR entry in TC: https://bgp.net.br/whois/?q=-s%20TC%20-i%20mnt-by%20MAINT-AS271761<https://url-shield.securence.com/?p=1.0&r=jkrejci@usinternet.com&sid=165055…> Regarding LACNIC, what LACNIC, NIC.mx and NIC.br do is to select which RIR or NIR services requests depending on the organisation's country. Rubens On Thu, Apr 21, 2022 at 9:53 AM Shawn < mailman.nanog.org(a)kleinart.net<mailto:mailman.nanog.org@kleinart.net>> wrote: > > Aloha NANOG, > > What is the best practice (or peoples preferred methods) to > update/correct/maintain geolocation data? > Do most people start with description field info in route/route6 objects? > > > Also, thoughts and considerations on using IPv4 space from one RIR in > countries belonging to another RIR? > > With IPv4 exhaustion and inter-RIR IPv4 transfers, and geolocation data, it > seems less applicable than it had been (a decade ago). The IP's will be > used for CDN, not by end-users/subscribers. > Context: trying to work through an administrative "challenge" with LACNIC > regarding an IPv4 transfer, considering transferring to ARIN and then using > in LACNIC (then once resolved, transfer from ARIN to LACNIC). Or just using > existing ARIN space in Brazil. > LACNIC is making things more difficult than they need to be. I know this is > NANOG... but seeking advice, working on a global network, US HQ, currently > no active "registration" in LACNIC (except Brazil), but we operate in 5 > countries in the region (data center/colo). We would use Brazil, but very > hesitant to use their NIC ( nic.br<http://nic.br>); LACNIC is saying we cannot maintain our > relationship with them using our Brazil organization (our only formal > subsidiary in the region). LACNIC does not really define the "entity" > operating in their region well. We use our US entity with RIPE and APNIC, > simply showing documentation (contracts) that we operate in their region. > Maybe I am not using the magic word? > >

1 0

Fall 2022 NANOG Registration Price Increase
by Edward McNair 21 Apr '22

21 Apr '22

NANOG Community, Due to rising costs, it has become necessary to increase registration fees. Beginning Monday, July 11, 2022, the price increase will go into effect. This will impact NANOG 86 and beyond. The new fee structure will be as follows: Member Pricing - Early: $675 - Standard: $775 - Late: $875 - Onsite: $1075 Non-Member Pricing - Early: $700 - Standard: $800 - Late: $900 - Onsite: $1100 Student Pricing - Early: $100 - Standard: $100 - Late: $100 - Onsite: $100 Virtual Pricing - Standard: $100 - Complementary: $0 We are committed to delivering a quality program and meeting experience for our community. We appreciate your understanding in this matter, and we look forward to your continued support and participation. Sincerely, Edward McNair NANOG Executive Director

1 0

Geolocation data management practices?
by Shawn 21 Apr '22

21 Apr '22

Aloha NANOG, What is the best practice (or peoples preferred methods) to update/correct/maintain geolocation data? Do most people start with description field info in route/route6 objects? Also, thoughts and considerations on using IPv4 space from one RIR in countries belonging to another RIR? With IPv4 exhaustion and inter-RIR IPv4 transfers, and geolocation data, it seems less applicable than it had been (a decade ago). The IP's will be used for CDN, not by end-users/subscribers. Context: trying to work through an administrative "challenge" with LACNIC regarding an IPv4 transfer, considering transferring to ARIN and then using in LACNIC (then once resolved, transfer from ARIN to LACNIC). Or just using existing ARIN space in Brazil. LACNIC is making things more difficult than they need to be. I know this is NANOG... but seeking advice, working on a global network, US HQ, currently no active "registration" in LACNIC (except Brazil), but we operate in 5 countries in the region (data center/colo). We would use Brazil, but very hesitant to use their NIC (nic.br); LACNIC is saying we cannot maintain our relationship with them using our Brazil organization (our only formal subsidiary in the region). LACNIC does not really define the "entity" operating in their region well. We use our US entity with RIPE and APNIC, simply showing documentation (contracts) that we operate in their region. Maybe I am not using the magic word?

5 4

Direct fibre between Digital Realty ATL2 and Equinox AT1
by Stefan Funke 21 Apr '22

21 Apr '22

Good morning NANOG! I am looking for direct fiber providers between ATL2 and AT1, or 100g wavelengths. Any recommendations? Off-List replies are fine! TIA, -Stefan

1 0