- Test - lists.nanog.org

202203071610.AYC Re: Making Use of 240/4 NetBlock
by Abraham Y. Chen 16 Jan '23

16 Jan '23

Dear Colleagues: 0) I was made aware of a recent discussion on this Forum that cited our work on the 240/4 NetBlock, nicknamed EzIP (Phonetic for Easy IPv4). (Please see, at the end of this MSG, the URL to the discussion and the highlighted text where the citation was made.) 1) As the lead investigator of the EzIP Project, I would like to formally introduce our solution by bringing your attention to an overview whitepaper: https://www.avinta.com/phoenix-1/home/RevampTheInternet.pdf In a nutshell, EzIP proposes to disable the program codes in current routers that have been disabling the use of the 240/4 NetBlock. The cost of this software engineering should be minimal. The EzIP deployment architecture is the same as that of the existing CG-NAT (Carrier Grade Network Address Translation). Consequently, there is no need to modify any hardware equipment. There is an online setup description (Reference II), called RAN (Regional Area Network), that demonstrates the feasibility of this approach. 2) There are additional consequential benefits by deploying EzIP, such as those mentioned by our comment to Reference III in the above whitepaper. I look forward to addressing your thoughts. Regards, Abe (2022-03-07 17:14 EST) VP Engineering Avinta Communications, Inc. Milpitas, CA 95035 USA +1(408)942-1485 Skype: Abraham.Y.Chen eMail: AYChen(a)Avinta.com WebSite: www.Avinta.com *********************** https://mailman.nanog.org/pipermail/nanog/2021-November/216766.html Class D addresses? was: Redploying most of 127/8 as unicast public *Greg Skinner* gregskinner0 at icloud.com <mailto:nanog%40nanog.org?Subject=Re%3A%20Class%20D%20addresses%3F%20was%3A%20Redploying%20most%20of%20127/8%20as%20unicast%20public&In-Reply-To=%3CFEDBF677-BC75-47F3-A92D-2611F43283BA%40icloud.com%3E> /Mon Nov 29 18:47:14 UTC 2021/ * Previous message (by thread): Class D addresses? was: Redploying most of 127/8 as unicast public <https://mailman.nanog.org/pipermail/nanog/2021-November/216640.html> * Next message (by thread): Class E addresses? 240/4 history <https://mailman.nanog.org/pipermail/nanog/2021-November/216602.html> * *Messages sorted by:* [ date ] <https://mailman.nanog.org/pipermail/nanog/2021-November/date.html#216766> [ thread ] <https://mailman.nanog.org/pipermail/nanog/2021-November/thread.html#216766> [ subject ] <https://mailman.nanog.org/pipermail/nanog/2021-November/subject.html#216766> [ author ] <https://mailman.nanog.org/pipermail/nanog/2021-November/author.html#216766> ------------------------------------------------------------------------ >/On Nov 24, 2021, at 5:08 PM, William Herrin <bill at herrin.us <https://mailman.nanog.org/mailman/listinfo/nanog>> wrote: />//>/On Wed, Nov 24, 2021 at 4:36 PM David Conrad <drc at virtualized.org <https://mailman.nanog.org/mailman/listinfo/nanog>> wrote: />>>/I like research but what would the RIRs study? The percentage of the />>//>>/Lots of people said similar things when 1.0.0.0/8 was allocated to APNIC />>/and they said similar things when 1.1.1.0/24 was stood up as an />>/experiment by Cloudflare and APNIC, yet 1.1.1.1 seems to be pretty popular. />//>/Hi David, />//>/I don't recall there being any equipment or software compatibility />/concerns with 1.0.0.0/8. If you do, feel free to refresh my memory. As />/I recall it, there were concerns with prior local use and potential />/trash traffic. It seemed likely those concerns could be addressed with />/experiments, and the experiments in fact addressed them. />//>/The prior local use worry reared its head again with 240/4 but given />/the prior experience with 1.0.0.0/8 I don't personally believe we need />/to re-run that experiment just because the numbers are part of a />/different block. />//>//>>/Seems to me that a number of folks on this list and during this />>/discussion would disagree with a blanket assertion that 240/4 />>/is “dysfunctional on the 2021 Internet” - some of them even />>/wrote a draft discussing the possibility. />//>/Line them up. Show of hands. Who really thinks that if we assign />/240.0.0.1 to a customer tomorrow without waiting for anyone to clean />/up their software and hardware, you won't get enough complaints about />/things not working that you have to take it back and assign a />/different address instead? />//>//>>/1. Move 240/4 from "reserved" to "unallocated unicast" />>//>>/OK, but this seems like a quibble. The status for 240/4 is “ />>/RESERVED: designated by the IETF for specific non-global-unicast />>/purposes as noted.” The “as noted” part is “Future Use”. />//>/It's not a quibble. Some vendors take the current status to mean />/"treat it like unicast until we're told otherwise." Others take the />/status to mean, "packets with these addresses are bogons without a />/defined routing behavior until we're told otherwise." The result is />/incompatible behavior between vendors. Changing that direction to />/"treat it like unicast" without ambiguity is not a quibble. />//>/Regards, />/Bill Herrin />//>/-- />/William Herrin />/bill at herrin.us <https://mailman.nanog.org/mailman/listinfo/nanog> />/https://bill.herrin.us/ / For what it’s worth, I’ve been tracking this issue on other netops mailing lists. There is a recent post on the LACNOG list from Leandro Bertholdo <https://mail.lacnic.net/pipermail/lacnog/2021-November/008895.html> referencing https://datatracker.ietf.org/doc/draft-chen-ati-adaptive-ipv4-address-space/ <https://datatracker.ietf.org/doc/draft-chen-ati-adaptive-ipv4-address-space/>, a draft proposing another way to make additional IPv4 address space available I haven’t had time to read the draft closely, but I noticed that it involves the use of 240/4. Subsequent googling about the draft turned up a presentation <https://www.avinta.com/phoenix-1/home/RegionalAreaNetworkArchitecture.pdf> describing how the techniques described could be deployed. I noticed that the presentation made reference to OpenWRT, so perhaps the authors are aware of the work that the authors of the IPv4 Unicast Extensions Project have done in that area. The adaptive-ipv4 draft will expire sometime next month, so anyone interested in seeing it move forward should contact the authors. —gregbo ******************* -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

70 306

Ticketmaster contact
by Alex Buie 14 Jan '23

14 Jan '23

Hi NANOG, We're an ISP providing residential and business fixed internet services, and all of our ranges are blocked from accessing ticketmaster with the attached "Pardon the interruption, you are superhuman or a bot" message and have been for some time; customer complaint velocity has increased especially as of late so it's been a priority to try and get this working. We've done extensive checking to ensure there is no bot activity or scalping transiting our network, we aren't using cgNAT - each IP is a specific customer end installation (home/office), and we have rPKI set up. Is there anyone from Ticketmaster on list who'd be willing to contact me for a conversation to see if we can resolve this for our mutual customers? Or could anyone provide me with a decent technical contact if they might have one? I would be eternally grateful. I have tried "fan support" numerous times, which provided helpful (/s) suggestions like "try purchasing tickets over LTE", or "use a different internet connection, like at a coffee shop", or "contact your ISP" (myself? lol), depending on the day. Also tried their "Global Monitoring Support" organization by phone and by email with little success. ARIN contacts bounce back as a 550 5.7.133 RESOLVER.RST.SenderNotAuthenticatedForGroup, looks like o365 configured to not accept external messages. If you've successfully managed to work this out with them, have any tips, or recognize what WAF/engine they're using from the page layout with UUID at the bottom to help me identify who else I might try contacting to see about getting recategorized, I would really appreciate hearing from you. Thanks a bunch! Alex Buie Senior Cloud Operations Engineer 450 Century Pkwy # 100 Allen, TX 75013 D: 469-884-0225 | www.cytracom.com

2 2

starlink downlink/internet access
by Ong Beng Hui 13 Jan '23

13 Jan '23

Hi folks, Anyone know/advise if Starlink internet downlink is in US Google fiber ? I thought I saw a message before that Starlink was using Google fiber. I was referring to the actual internet transit, not the Satellite downlink station. Please advise.

6 6

NANOG Committee Nominations are Open!
by Valerie Wittkop 13 Jan '23

13 Jan '23

Dear NANOG Community, Nominations <https://www.nanog.org/members/elections/committee-nomination-process/> are now open for six NANOG Committees! We are looking for volunteers to serve on the Program Committee, Diversity Equity and Inclusion Committee, Education Committee, Elections Committee, Mentorship Committee, and Scholarship Committee. Specific committee charters and member responsibilities are linked here <https://www.nanog.org/members/elections/committee-nomination-process/> and appointments are 2-year terms, except if appointed to complete a mid-appointment term. Committee nominations will close at 9:00pm EST on Tuesday, 14 February, 2023. The NANOG Board of Directors will make appointments within the week. Emails detailing the selection results will be sent to candidates shortly thereafter, and a full announcement will be sent during the following week. Volunteer participation by members on NANOG committees is part of the essential fabric of the NANOG organization. Committee members have developed new programs, brought new ideas and new methods into practice, and helped to evolve the NANOG organization. Please consider running for a NANOG committee if you are passionate about NANOG and can commit to participating! If you know someone that you believe would be interested, please nominate them. The nomination form is linked from the 2023 Committee Nominations webpage <https://www.nanog.org/members/elections/2023-committee-nominations/> and accepts either self or 3rd party nominations. Board members are available to discuss the opportunities, so do not hesitate to reach out to them if you are interested and want to learn more. As always, you can reach us through our website contact form here <https://www.nanog.org/contact/>, or by email to either nanog-support(a)nanog.org or member-support(a)nanog.org Cheers, *Valerie Wittkop* Program Directorvwittkop(a)nanog.org | +1 734-730-0225 <+15038199432> (mobile) | www.nanog.org NANOG | 305 E. Eisenhower Pkwy, Suite 100 | Ann Arbor, MI 48108, USA ASN 19230

1 0

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 13 Jan '23

13 Jan '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 14 Jan, 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: 919061 Prefixes after maximum aggregation (per Origin AS): 347675 Deaggregation factor: 2.64 Unique aggregates announced (without unneeded subnets): 445061 Total ASes present in the Internet Routing Table: 74077 Prefixes per ASN: 12.41 Origin-only ASes present in the Internet Routing Table: 63583 Origin ASes announcing only one prefix: 26147 Transit ASes present in the Internet Routing Table: 10494 Transit-only ASes present in the Internet Routing Table: 429 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: 994 Number of instances of unregistered ASNs: 1003 Number of 32-bit ASNs allocated by the RIRs: 41044 Number of 32-bit ASNs visible in the Routing Table: 34030 Prefixes from 32-bit ASNs in the Routing Table: 166103 Number of bogon 32-bit ASNs visible in the Routing Table: 28 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 506 Number of addresses announced to Internet: 3064089600 Equivalent to 182 /8s, 162 /16s and 76 /24s Percentage of available address space announced: 82.8 Percentage of allocated address space announced: 82.8 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: 312162 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 240102 Total APNIC prefixes after maximum aggregation: 68700 APNIC Deaggregation factor: 3.49 Prefixes being announced from the APNIC address blocks: 235168 Unique aggregates announced from the APNIC address blocks: 97635 APNIC Region origin ASes present in the Internet Routing Table: 13228 APNIC Prefixes per ASN: 17.78 APNIC Region origin ASes announcing only one prefix: 3846 APNIC Region transit ASes present in the Internet Routing Table: 1771 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 27 Number of APNIC region 32-bit ASNs visible in the Routing Table: 8486 Number of APNIC addresses announced to Internet: 773797504 Equivalent to 46 /8s, 31 /16s and 54 /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: 267585 Total ARIN prefixes after maximum aggregation: 121726 ARIN Deaggregation factor: 2.20 Prefixes being announced from the ARIN address blocks: 269035 Unique aggregates announced from the ARIN address blocks: 129786 ARIN Region origin ASes present in the Internet Routing Table: 19078 ARIN Prefixes per ASN: 14.10 ARIN Region origin ASes announcing only one prefix: 6985 ARIN Region transit ASes present in the Internet Routing Table: 1958 Average ARIN Region AS path length visible: 3.7 Max ARIN Region AS path length visible: 37 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4730 Number of ARIN addresses announced to Internet: 1286418688 Equivalent to 76 /8s, 173 /16s and 49 /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: 264097 Total RIPE prefixes after maximum aggregation: 122331 RIPE Deaggregation factor: 2.16 Prefixes being announced from the RIPE address blocks: 260772 Unique aggregates announced from the RIPE address blocks: 156173 RIPE Region origin ASes present in the Internet Routing Table: 28235 RIPE Prefixes per ASN: 9.24 RIPE Region origin ASes announcing only one prefix: 12065 RIPE Region transit ASes present in the Internet Routing Table: 3970 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: 10989 Number of RIPE addresses announced to Internet: 719307136 Equivalent to 42 /8s, 223 /16s and 193 /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: 117520 Total LACNIC prefixes after maximum aggregation: 28456 LACNIC Deaggregation factor: 4.13 Prefixes being announced from the LACNIC address blocks: 116752 Unique aggregates announced from the LACNIC address blocks: 48964 LACNIC Region origin ASes present in the Internet Routing Table: 11006 LACNIC Prefixes per ASN: 10.61 LACNIC Region origin ASes announcing only one prefix: 2660 LACNIC Region transit ASes present in the Internet Routing Table: 2277 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: 8775 Number of LACNIC addresses announced to Internet: 176079360 Equivalent to 10 /8s, 126 /16s and 194 /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: 28763 Total AfriNIC prefixes after maximum aggregation: 5705 AfriNIC Deaggregation factor: 5.04 Prefixes being announced from the AfriNIC address blocks: 36828 Unique aggregates announced from the AfriNIC address blocks: 12091 AfriNIC Region origin ASes present in the Internet Routing Table: 1708 AfriNIC Prefixes per ASN: 21.56 AfriNIC Region origin ASes announcing only one prefix: 591 AfriNIC Region transit ASes present in the Internet Routing Table: 324 Average AfriNIC Region AS path length visible: 4.9 Max AfriNIC Region AS path length visible: 30 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1050 Number of AfriNIC addresses announced to Internet: 108193280 Equivalent to 6 /8s, 114 /16s and 230 /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 9358 8884 50 CHINAMOBILE-CN China Mobile Communicati 7545 5940 786 699 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4861 4192 75 ERX-CERNET-BKB China Education and Rese 7552 3626 1331 21 VIETEL-AS-AP Viettel Group, VN 7713 3507 1043 63 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3381 1874 96 VNPT-AS-VN VNPT Corp, VN 9498 2697 499 237 BBIL-AP BHARTI Airtel Ltd., IN 4766 2508 11250 592 KIXS-AS-KR Korea Telecom, KR 24560 2360 849 436 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 45090 2180 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 7739 10695 2936 AMAZON-02, US 11492 4548 301 578 CABLEONE, US 7155 3895 265 33 VIASAT-SP-BACKBONE, US 22773 3690 3062 320 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3523 1320 63 SHAW, CA 16625 3467 1791 2516 AKAMAI-AS, US 749 3023 50575 2290 DNIC-AS-00749, US 7018 2621 24133 1589 ATT-INTERNET4, US 396982 2577 3493 370 GOOGLE-CLOUD-PLATFORM, US 30036 2569 368 361 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 6965 1706 146 UNI2-AS, ES 9121 6111 1692 17 TTNET, TR 39891 4556 268 59 ALJAWWALSTC-AS, SA 20940 4060 3400 181 AKAMAI-ASN1, NL 8551 3908 374 38 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2941 2290 908 ROSTELECOM-AS, RU 47331 2802 411 2109 TTNET, TR 9009 2656 253 1364 M247, RO 34984 2254 358 610 TELLCOM-AS, TR 6849 2194 339 20 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 10924 3337 589 Uninet S.A. de C.V., MX 10620 3469 507 852 Telmex Colombia S.A., CO 11830 2261 369 64 Instituto Costarricense de Electricidad 13999 2208 362 594 Mega Cable, S.A. de C.V., MX 28573 1345 2328 258 Claro NXT Telecomunicacoes Ltda, BR 6503 1295 339 517 Axtel, S.A.B. de C.V., MX 3816 1291 740 156 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1151 370 22 Telefonica del Peru S.A.A., PE 11664 1136 186 465 Techtel LMDS Comunicaciones Interactiva 26615 1006 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 1538 533 30 RAYA-AS, EG 24863 1477 393 21 LINKdotNET-AS, EG 36992 1327 1517 275 ETISALAT-MISR, EG 36903 1242 550 99 MT-MPLS, MA 29571 1005 67 46 ORANGE-COTE-IVOIRE, CI 36935 884 520 42 Vodafone-, EG 6713 611 1861 34 IAM-AS, MA 15399 517 53 42 WANANCHI-, KE 37342 494 32 1 MOVITEL, MZ 24757 493 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 10924 3337 589 Uninet S.A. de C.V., MX 9808 9358 8884 50 CHINAMOBILE-CN China Mobile Communicati 16509 7739 10695 2936 AMAZON-02, US 12479 6965 1706 146 UNI2-AS, ES 9121 6111 1692 17 TTNET, TR 7545 5940 786 699 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4861 4192 75 ERX-CERNET-BKB China Education and Rese 39891 4556 268 59 ALJAWWALSTC-AS, SA 11492 4548 301 578 CABLEONE, US 20940 4060 3400 181 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 9358 9308 CHINAMOBILE-CN China Mobile Communications Grou 12479 6965 6819 UNI2-AS, ES 9121 6111 6094 TTNET, TR 7545 5940 5241 TPG-INTERNET-AP TPG Telecom Limited, AU 16509 7739 4803 AMAZON-02, US 4538 4861 4786 ERX-CERNET-BKB China Education and Research Net 39891 4556 4497 ALJAWWALSTC-AS, SA 11492 4548 3970 CABLEONE, US 20940 4060 3879 AKAMAI-ASN1, NL 8551 3908 3870 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 3402 UNALLOCATED 8.2.200.0/21 6939 HURRICANE, US 3402 UNALLOCATED 8.2.207.0/24 2914 NTT-LTD-2914, 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 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:582 /14:1200 /15:2039 /16:13497 /17:8317 /18:13928 /19:25206 /20:44302 /21:52313 /22:110293 /23:98297 /24:547814 /25:809 /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 6025 6965 UNI2-AS, ES 9121 5290 6111 TTNET, TR 8151 4973 10924 Uninet S.A. de C.V., MX 39891 3547 4556 ALJAWWALSTC-AS, SA 11492 3455 4548 CABLEONE, US 8551 3373 3908 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 6327 3331 3523 SHAW, CA 7155 2984 3895 VIASAT-SP-BACKBONE, US 22773 2724 3690 ASN-CXA-ALL-CCI-22773-RDC, US 47331 2423 2802 TTNET, TR Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1640 2:1243 3:168 4:5 5:4116 6:109 7:5 8:1572 9:1 11:172 12:1595 13:370 14:2368 15:285 16:79 17:370 18:412 20:243 21:4 22:188 23:6049 24:2467 25:4 27:2646 29:19 31:2500 32:99 34:8 35:100 36:1862 37:4605 38:4005 39:831 40:155 41:3951 42:1051 43:2316 44:303 45:16420 46:4182 47:381 49:1743 50:1917 51:378 52:1543 54:393 55:863 56:8 57:77 58:1744 59:1158 60:1006 61:2421 62:2633 63:1941 64:5658 65:2328 66:4903 67:3054 68:1343 69:4120 70:1256 71:657 72:2980 74:2592 75:1465 76:597 77:2373 78:3955 79:3161 80:2062 81:1825 82:1480 83:1229 84:1514 85:3745 86:747 87:1929 88:2876 89:3563 90:591 91:7643 92:1983 93:2574 94:3519 95:4864 96:1307 97:346 98:1166 99:738 100:75 101:1061 102:2521 103:30793 104:4591 105:484 106:843 107:2538 108:916 109:4376 110:2046 111:3304 112:2045 113:1554 114:1611 115:2043 116:1904 117:2537 118:2293 119:1898 120:1767 121:1113 122:2586 123:2158 124:1600 125:2346 128:1306 129:1062 130:972 131:2014 132:800 133:405 134:1902 135:298 136:886 137:921 138:2579 139:1541 140:1025 141:1478 142:1425 143:1420 144:1184 145:350 146:1900 147:1549 148:2296 149:1875 150:863 151:1132 152:1857 153:478 154:3897 155:1405 156:1649 157:1300 158:1048 159:2267 160:2560 161:1423 162:3536 163:1489 164:1688 165:1655 166:831 167:1737 168:3870 169:921 170:4586 171:886 172:3491 173:3011 174:1026 175:1149 176:3721 177:4743 178:3556 179:2146 180:2379 181:3366 182:3276 183:1929 184:2345 185:19970 186:4654 187:3930 188:4100 189:3451 190:9065 191:1425 192:10955 193:8858 194:7233 195:5116 196:3006 197:2412 198:5994 199:6098 200:7724 201:5887 202:10647 203:10037 204:4609 205:3500 206:3860 207:3416 208:4091 209:4821 210:4437 211:2498 212:4111 213:3569 214:1101 215:55 216:6585 217:2638 218:1279 219:577 220:2019 221:969 222:845 223:1998 End of report

1 0

AS3257 / AS4436 / GTT Contact re route hijack
by Adam Blackington 12 Jan '23

12 Jan '23

Can someone from GTT contact me off-list about this? GTT is not an upstream carrier for me and the NOC doesn't seem to understand the issue.... Thank for your help. :) Adam On Thu, Jan 12, 2023 at 8:47 AM GTT NOC <noc(a)gtt.net> wrote: > Hello Team, > > As part of our ongoing improvements to enhance security measures for our > customers, we no longer accept Request tickets via email. We request you to > please log into our EtherVision <https://ethervision.gtt.net/> portal to > open your ticket, it will then be picked up accordingly by our engineers. > You can view a quick tutorial  on our Ethervision portal here > <https://learn.gtt.net/EV_Focus_On_Ticketing.html>. > > > > EtherVision <https://ethervision.gtt.net/> also allows > you to check the status of existing tickets as well as access our Service > Assurance contact information. > > > If you do not have an EtherVision <https://ethervision.gtt.net/> login, please contact > your GTT account administrator or submit a request through our website > <https://ethervision.gtt.net/sign-in>. > > > > Thanks & Regards, > > Danish Aga > > Service Desk Analyst > > Client Portal: https://ethervision.gtt.net/ > > GTT NOC: noc(a)gtt.net > > [image: image] > > ------------------------------ > *From:* LionLink NOC <noc(a)lionlink.net> > *Sent:* 12 January 2023 07:02 > *To:* GTT NOC <noc(a)gtt.net> > *Subject:* Route Hijack - 23.29.58.0/24 > > *NOTE:* This is an external message. Please use caution when replying, > opening attachments or clicking on any links in this e-mail. > Hello GTT NOC, > > I am unsure why, but it appears you are advertising a netblock that I am > assigned (199.116.84.0/24). Can you please stop advertising my netbook > <https://whois.arin.net/rest/net/NET-199-116-84-0-2/pft?s=199.116.84.1>? > > > > [image: Screen Shot 2023-01-12 at 1.50.35 AM.png] > [image: Screen Shot 2023-01-12 at 1.51.07 AM.png] > > > *NOTICE: This e-mail is only intended for the person(s) to whom it is > addressed and may contain confidential information. Unless stated to the > contrary, any opinions or comments are personal to the writer and do not > represent the official view of GTT Communications Inc or any of its > affiliates. If you have received this e-mail in error, please notify us > immediately by reply e-mail and then delete this message from your system. > Please do not copy it or use it for any purposes, or disclose its contents > to any other person. All quotes, offers, proposals and any other > information in the body of this email is subject to, and limited by, the > terms and conditions, signed service agreement and/or statement of work* > Very Best Regards, Adam *Adam Blackington, PSM, NSA* Managing Partner *LionLink Networks | *Infrastructure Solutions That Power The Enterprise ablackington(a)lionlink.net email *| * (571) 482.1490 direct Service Desk: (844) DATA-CENTER, Option 2 or support(a)lionlink.net

1 0

AS8075(Microsoft) Contact
by netops Network Operations 12 Jan '23

12 Jan '23

Hi, Is anybody from AS8075(Microsoft) on the list ? We are trying to establish BGP Public/Exchange Peering Sessions for almost 3 months... Multiple emails sent to peering(a)microsoft.com and inter-x(a)microsoft.com, but never heard back. Later we followed the guide and created all the connections via Azure PowerShell and again, it is in PendingApproval State for more then 1 month. Does everybody has the same experience establishing BGP Peering Sessions with Microsoft ?

2 1

AKAMAI CDN
by Nielsen Kaezer 12 Jan '23

12 Jan '23

I'm interested ASN 53172

1 0

AKAMAI CDN
by Pascal Masha 12 Jan '23

12 Jan '23

Hello, Anyone from Akamai responsible for making decisions on cluster scaling /refresh here? Kindly contact me offlist. Regards Paschal Masha

2 1

N87: Experience Atlanta, Hackathon Kicks-Off 3, Feb + More
by Nanog News 11 Jan '23

11 Jan '23

*Experience Atlanta at NANOG 87! * *Special Offers, Things To Do, Transportation, Dining, + More * NANOG 87 will take place in Atlanta, GA 13 - 15 February. *The City of Atlanta* will provide discounts for dining and activities for our NANOG community. Discover Atlanta, check out the best ways to get around the city, and make the most of your experience at NANOG 87! *EXPERIENCE ATL <https://experienceatl.com/attendconference?content_uid=146897>* *Still Time to Register for Hackathon 87! * *Hackathon Kicks-Off Friday, 3 Feb 2023!* *👉 Theme: Interacting With Sources of Truth* The NANOG 87 Hackathon will focus on Interacting With Sources of Truth, whether it’s a single database or a collection of correlated data from multiple sources. Such examples could include PAM, Configuration Databases, Datacenter Infrastructure Management Databases, Configuration Templates/Models, RPKI Validators, etc. You could develop a feature, fix a bug for an existing open-source solution or roll your own! *REGISTER NOW * <https://nanog.org/events/nanog-87-hackathon/> OARC-40 to Take Place After NANOG 87 *OARC-40 in Same Venue as NANOG 87* OARC’s 40th Workshop will be a hybrid online and in-person meeting at the Atlanta Marriott Marquis 16 - 17 Feb. — immediately after NANOG 87 in the same venue. NANOG 87 attendees are especially welcome as both meetings will have complementary and non-overlapping content. *REGISTER NOW <https://indico.dns-oarc.net/event/46/page/225-registration>* *FEATURED on NANOG TV* *Weekly NANOG TV Spotlighted Content * 🎥 This week's featured NANOG TV video (171,777 views): 👉 ▶️ Tutorial: Tutorial Everything You Always Wanted to Know About Optical Networking with Richard Steenbergen, PacketFabric *Topics include:* * - How Fiber Works - Optical Power - Working with Optics - DWDM - Dispersion and other Impairments - Optical Myths - + More* *WATCH NOW <https://www.youtube.com/watch?v=_KFpXuHqHQg&t=2s>*

1 0