March 2025 - NANOG - lists.nanog.org

CGNAT growing pains
by Jon Lewis 17 Apr '25

17 Apr '25

We started rolling out CGNAT about 6 months ago. It was smooth sailing for the first few months, but we eventually did run into a number of issues. Our customer base is primarily FTTH with "dynamic" IP assignment via DHCP. Since connections are always-on, customer ONTs/routers get an IP assigned, and then when the lease is renewed, they request a new lease for the existing IP, and, in general, that request is granted. This gives customers the mistaken impression they have a static IP. So, my impression, from working with some customers who've needed to be moved from CGNAT back to public IP is that customers who are doing port-forwarding don't even bother with dynamic DNS. They just know they can connect to their IP as they've never seen it change. We do offer/sell static IP, but pre-CGNAT, it was strictly for business customers. i.e. A residential customer could only get static IP service by converting their account to a business account. That may change in the near future. One issue we didn't foresee has been IP Geo issues. i.e. We all knew that streaming services like Netflix use IP Geo to determine what content should be made available, but that's, AFAIK, limited by country or region. What we didn't anticipate is services like Hulu Live TV doing IP Geo down to the city level to determine which local channels are a subscriber's local channels. We're using Juniper MX gear and SPC3 cards for our CGNAT routers, each one having a single large external pool. Since we serve most of FL, one external pool can't IP Geo correctly for customers as far apart as Miami and Jacksonville hitting the same CGNAT router. We don't currently have an acceptable solution to this other than moving impacted customers off CGNAT. One of the great unknowns (at least for us) with CGNAT was what our PBA settings should be. i.e. How large each port-block should be, and how many port-blocks to allow per customer. We started with 256x4. It seemed to work. We eventually noticed that we were logging port-block exceeded errors. This is one aspect where Juniper's CGNAT support is lacking. There's a counter for these errors, and it's available via SNMP, but there's no way to attribute the errors to subscriber IPs. We're polling the mib and graphing it, so we know it's a continuing issue and can see when it's incrementing faster/slower, but Junos provides no means for determining if "PBEs" are all being caused by a single customer, a handful of customers, etc. We have a JTAC case open on this. As a quick & hopeful fix, we both increased the port-block size and block limit. That helped, but didn't stop the errors. It also cut our CGNAT ratio by more than half (64:1 -> 28:1), if we stay at this ratio, we'll need much larger external pools than originally anticipated. Tuning these settings is kind of painful as JTAC strongly recommends bouncing the CGNAT service anytime CGNAT related config changes are made. This means briefly breaking Internet access for all CGNAT'd customers. For the PBEs, JTAC's suggestions so far have been to shorten some of the timeouts in the config and to keep doing what we're doing, which is a cron job that essentially does a "show services nat source port-block", parses the output looking for subscriber IPs that have used up the ports in several of their port-blocks, then does a "show services sessions source-prefix ..." and logs all of this. This at least gives us snapshots of "who's a heavy user right now" and lets us look at how they were using all their ports. i.e. was it bittorent, are they compromised and scanning the internet for more systems to compromise, is it legit looking traffic - just lots of it, etc.? The latest CGNAT issue is a customer with a Palo Alto Networks firewall connected to our network and several of their employees are our FTTH customers. On their PANW firewall, they're doing IP Geo based filtering, limiting access to internal servers to "US IPs". Since we only CGNAT traffic to the external Internet, their on-net employees hit the firewall from their 100.64/10 IPs and get blocked. I suggested they whitelist 100.64/10, saying we block traffic from 100.64/10 from entering our network via peering and transit, so they can be assured anything from 100.64/10 came from inside our network / our customers. They say the firewall won't let them whitelist 100.64.0.0/10, giving an error that it's invalid IP space. I know we're not the first to implement CGNAT, so I'm curious if others have run into these sorts of issues, or others we haven't run into yet, and if so, how you solved them. ---------------------------------------------------------------------- Jon Lewis, MCP :) | I route Blue Stream Fiber, Sr. Neteng | therefore you are _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________

10 16

[NANOG] List admin: filter old address?
by Chris Adams 02 Apr '25

02 Apr '25

There seem to be a number of replies that CC both the old and new list address, resulting in multiple copies of lots of messages. I can filter them at my end, but it'd be better to address that at the list server. -- Chris Adams <cma(a)cmadams.net>

2 2

[NANOG] IPv6 Legacy IP Warning Stickers
by Andrew Latham 02 Apr '25

02 Apr '25

Today yet another ISP is running Fiber in the utility easement at the street. I checked and they do not offer IPv6 or have ANY IPv6 peering. I have offered the hard to find IPv6 Legacy Warning stickers on my Redbubble profile. About a month before any meeting or event I see a bulk order for Amish IPv6 stickers designed by Phil Benchoff and hard to find post Google+. I have the markup/profit set to the lowest setting and have made maybe $8 over 5+ years. Linky: https://www.redbubble.com/i/sticker/Legacy-IP-Warning-by-gringomalvado/3858… Ranting a bit as I have four ISPs boxes at the street and two of them do not have IPv6 in 2025. Converting my frustration into finding Phil and sending him some coffee money. -- - Andrew "lathama" Latham -

18 24

[NANOG] Visualizing The Rise of Hypergiants
by Hank Nussbacher 01 Apr '25

01 Apr '25

Fascinating analysis - worth the read: https://pulse.internetsociety.org/blog/visualizing-the-rise-of-hypergiants Regards, Hank

5 7

[NANOG] The Network CLI -- Love it ? Hate it? Needed?
by Mark Prosser 01 Apr '25

01 Apr '25

Hi NANOG community, I posed this question in several chat groups, but I'd like to get your opinions. Do you love the CLI? Do you hate the CLI? Would you -- or do you already -- enjoy a world where you never need to touch the CLI, to manage your network? This applies to both provisioning and troubleshooting; to which, you may have different answers. So far, I've seen a variety of replies around the usual "should/must/must not/should not". Warm regards, -- Mark Prosser // E: mark(a)zealnetworks.ca // W: https://zealnetworks.ca

29 58

[NANOG] JunOS and MX trojan and malware
by Eric Kuhnke 31 Mar '25

31 Mar '25

https://www.darkreading.com/cyberattacks-data-breaches/china-hackers-backdo… https://supportportal.juniper.net/s/article/2025-03-Reference-Advisory-The-… PDF file: https://supportportal.juniper.net/sfc/servlet.shepherd/document/download/06…

10 12

[NANOG] Verizon (Fios) Packet Loss | Philadelphia Metro Area | Possible Routing Issue?
by alexander.lembesis＠gmail.com 29 Mar '25

29 Mar '25

Hello, fellow NANOG members, Is there anyone from Verizon on the list that could take a look at a possible routing issue on the Fios network that could be causing loss? I have two locations, each with 1G service. Location 1 is in Quakertown, PA & has a dynamic IP on the 96.227.54.0/24 block Location 2 is in Chalfont, PA & has a dynamic IP on the 108.16.195.0/24 block They are ~11miles apart as the crow flies. I have some EdgeConnect SDWAN appliances connected at these locations and they're measuring a variable amount of loss between them (more during peak hours). I have checked everything I can on my end and posting here as a last resort. Traceroute from Quakertown to Chalfont seems to hop through two LCR nodes in Washington, DC. 1. dog-coresw01.xxxxxxxxx.net 2. ixl0-dog-opnsense01.xxxxxxxxx.NET 3. lo0-100.PHLAPA-VFTTP-346.verizon-gni.net 4. B3346.PHLAPA-LCR-21.verizon-gni.net B3346.PHLAPA-LCR-22.verizon-gni.net 5. G1-7-2-4.WASHDC-LCR-21.verizon-gni.net G1-7-2-3.WASHDC-LCR-21.verizon-gni.net 6. Chalfont, PA 108.16.195.x Unless the PTR records on hop #5 are incorrect, it seems odd that traffic from Quakertown, PA has to travel all the way down to Washington DC, then come back up to Pennsylvania. Traceroute from the opposite direction (Chalfont to Quakertown) does not show the WASHDC LCR nodes. 1. 192.168.138.1 2. ixl0-wpv-opnsense.xxxxxxxxx.NET 3. lo0-100.PHLAPA-VFTTP-354.verizon-gni.net 4. (waiting for reply) 5. Bundle-Ether1000.PHLAPA-LCR-21.VERIZON-GNI.NET Bundle-Ether1000.PHLAPA-LCR-22.VERIZON-GNI.NET Bundle-Ether1200.PHLAPA-LCR-22.VERIZON-GNI.NET HundredGigE2-0-0-3.PHLAPA-LCR-21.VERIZON-GNI.NET HundredGigE2-0-0-0.PHLAPA-LCR-21.VERIZON-GNI.NET Bundle-Ether800.PHLAPA-LCR-22.VERIZON-GNI.NET HundredGigE2-0-0-3.PHLAPA-LCR-22.VERIZON-GNI.NET 6. ae204-0.PHLAPA-VFTTP-346.verizon-gni.net ae203-0.PHLAPA-VFTTP-346.verizon-gni.net 7. Quakertown, PA 96.227.54.x I'm out of ideas on what could be causing the packet loss. If someone from Verizon could take a look, that would be GREATLY appreciated. Thank you!!!

2 1

[NANOG] Turnkey-ish Datacenter in Austin
by Izaac 28 Mar '25

28 Mar '25

Just in case any Texans are looking for some quick build out, I spotted this while looking for something else: https://realestatesales.gov/asset-details/?property_id=10 Open house on Tues 01APR. -- . ___ ___ . . ___ . \ / |\ |\ \ . _\_ /__ |-\ |-\ \__

1 0

[NANOG] Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 28 Mar '25

28 Mar '25

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 UKNOF, 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 29 Mar, 2025 IPv4 BGP Table (Global) as seen at Japan. Report Website: https://thyme.apnic.net Detailed Analysis: https://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 980089 Prefixes after maximum aggregation (per Origin AS): 375410 Deaggregation factor: 2.61 Unique aggregates announced (without unneeded subnets): 476692 Number of IPv4 prefixes with a valid ROA: 533951 Number of IPv4 prefixes with an invalid ROA: 1289 Number of IPv4 prefixes with no ROA: 444849 Total ASes present in the Internet Routing Table: 76772 Prefixes per ASN: 12.77 Origin-only ASes present in the Internet Routing Table: 65730 Origin ASes announcing only one prefix: 26875 Transit ASes present in the Internet Routing Table: 11042 Transit-only ASes present in the Internet Routing Table: 555 Average AS path length visible in the Internet Routing Table: 5.2 Max AS path length visible: 65 Max AS path prepend of ASN ( 37447) 57 Prefixes from unregistered ASNs in the Routing Table: 1039 Number of instances of unregistered ASNs: 1043 Number of 32-bit ASNs allocated by the RIRs: 46110 Number of 32-bit ASNs visible in the Routing Table: 38041 Prefixes from 32-bit ASNs in the Routing Table: 200390 Number of bogon 32-bit ASNs visible in the Routing Table: 30 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 470 Number of addresses announced to Internet: 3108548352 Equivalent to 185 /8s, 72 /16s and 175 /24s Percentage of available address space announced: 84.0 Percentage of allocated address space announced: 84.0 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: 322024 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 256946 Total APNIC prefixes after maximum aggregation: 76948 APNIC Deaggregation factor: 3.34 Prefixes being announced from the APNIC address blocks: 248687 Unique aggregates announced from the APNIC address blocks: 102751 APNIC Region origin ASes present in the Internet Routing Table: 14582 APNIC Prefixes per ASN: 17.05 APNIC Region origin ASes announcing only one prefix: 4445 APNIC Region transit ASes present in the Internet Routing Table: 1965 Average APNIC Region AS path length visible: 5.4 Max APNIC Region AS path length visible: 50 Number of APNIC region 32-bit ASNs visible in the Routing Table: 10065 Number of APNIC addresses announced to Internet: 749451264 Equivalent to 44 /8s, 171 /16s and 184 /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-155961 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: 289957 Total ARIN prefixes after maximum aggregation: 128840 ARIN Deaggregation factor: 2.25 Prefixes being announced from the ARIN address blocks: 290637 Unique aggregates announced from the ARIN address blocks: 137225 ARIN Region origin ASes present in the Internet Routing Table: 19244 ARIN Prefixes per ASN: 15.10 ARIN Region origin ASes announcing only one prefix: 7028 ARIN Region transit ASes present in the Internet Routing Table: 1994 Average ARIN Region AS path length visible: 4.6 Max ARIN Region AS path length visible: 34 Number of ARIN region 32-bit ASNs visible in the Routing Table: 5174 Number of ARIN addresses announced to Internet: 1350009600 Equivalent to 80 /8s, 119 /16s and 131 /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-402332 ARIN Address Blocks 3/8, 4/8, 6/8, 7/8, 8/8, 9/8, 11/8, 12/8, 13/8, 15/8, 16/8, 17/8, 18/8, 19/8, 20/8, 21/8, 22/8, 23/8, 24/8, 26/8, 28/8, 29/8, 30/8, 32/8, 33/8, 34/8, 35/8, 38/8, 40/8, 44/8, 45/8, 47/8, 48/8, 50/8, 52/8, 54/8, 55/8, 56/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: 273086 Total RIPE prefixes after maximum aggregation: 132977 RIPE Deaggregation factor: 2.05 Prefixes being announced from the RIPE address blocks: 271282 Unique aggregates announced from the RIPE address blocks: 173822 RIPE Region origin ASes present in the Internet Routing Table: 28881 RIPE Prefixes per ASN: 9.39 RIPE Region origin ASes announcing only one prefix: 12050 RIPE Region transit ASes present in the Internet Routing Table: 4003 Average RIPE Region AS path length visible: 5.3 Max RIPE Region AS path length visible: 45 Number of RIPE region 32-bit ASNs visible in the Routing Table: 12350 Number of RIPE addresses announced to Internet: 732242688 Equivalent to 43 /8s, 165 /16s and 35 /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-216475 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/8, 53/8, 57/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: 124001 Total LACNIC prefixes after maximum aggregation: 29268 LACNIC Deaggregation factor: 4.24 Prefixes being announced from the LACNIC address blocks: 120650 Unique aggregates announced from the LACNIC address blocks: 48828 LACNIC Region origin ASes present in the Internet Routing Table: 11224 LACNIC Prefixes per ASN: 10.75 LACNIC Region origin ASes announcing only one prefix: 2660 LACNIC Region transit ASes present in the Internet Routing Table: 2490 Average LACNIC Region AS path length visible: 5.9 Max LACNIC Region AS path length visible: 56 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 9180 Number of LACNIC addresses announced to Internet: 171669248 Equivalent to 10 /8s, 59 /16s and 119 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-274844 + 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: 35060 Total AfriNIC prefixes after maximum aggregation: 6737 AfriNIC Deaggregation factor: 5.20 Prefixes being announced from the AfriNIC address blocks: 48363 Unique aggregates announced from the AfriNIC address blocks: 13662 AfriNIC Region origin ASes present in the Internet Routing Table: 1910 AfriNIC Prefixes per ASN: 25.32 AfriNIC Region origin ASes announcing only one prefix: 692 AfriNIC Region transit ASes present in the Internet Routing Table: 383 Average AfriNIC Region AS path length visible: 6.0 Max AfriNIC Region AS path length visible: 65 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1272 Number of AfriNIC addresses announced to Internet: 104938752 Equivalent to 6 /8s, 65 /16s and 61 /24s AfriNIC AS Blocks 36864-37887, 327680-329727 & ERX transfers AfriNIC Address Blocks 41/8, 102/8, 105/8, 154/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 9808 10316 8754 94 CHINAMOBILE-CN China Mobile Communication 7545 6218 843 656 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4780 4192 76 ERX-CERNET-BKB China Education and Resear 9498 4293 530 278 BBIL-AP BHARTI Airtel Ltd., IN 7552 3871 1332 26 VIETEL-AS-AP Viettel Group, VN 7713 3676 1044 66 TELKOMNET-AS-AP PT Telekomunikasi Indones 45899 3278 1869 103 VNPT-AS-VN VNPT Corp, VN 24560 2847 848 537 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd., 4766 2357 11521 605 KIXS-AS-KR Korea Telecom, KR 45090 2205 1439 86 TENCENT-NET-AP Shenzhen Tencent Computer 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 12938 39643 3971 AMAZON-02, US 11492 4676 310 586 CABLEONE, US 7155 4173 286 83 VIASAT-SP-BACKBONE, US 6327 3623 1320 81 SHAW, CA 174 3549 8766 958 COGENT-174, US 22773 3378 3033 180 ASN-CXA-ALL-CCI-22773-RDC, US 749 3254 54879 2505 DNIC-AS-00749, US 16625 3032 1271 2217 AKAMAI-AS, US 396982 2945 3649 459 GOOGLE-CLOUD-PLATFORM, US 36352 2575 213 794 AS-COLOCROSSING, 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 7722 1714 145 UNI2-AS, ES 39891 4797 293 62 ALJAWWALSTC-AS, SA 20940 3938 3395 130 AKAMAI-ASN1, NL 9009 3774 326 1963 M247, RO 12389 3042 2303 890 ROSTELECOM-AS, RU 34984 2365 360 583 TELLCOM-AS, TR 212238 2070 147 1527 CDNEXT, GB 8452 1615 1852 14 TE-AS TE-AS, EG 13188 1606 100 34 TRIOLAN, UA 62240 1491 98 749 CLOUVIDER Clouvider - Global ASN, GB 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 11896 3243 582 UNINET, MX 10620 3522 486 971 Telmex Colombia S.A., CO 13999 2499 538 372 Mega Cable, S.A. de C.V., MX 11830 1991 369 64 Instituto Costarricense de Electricidad y 28573 1351 2437 265 Claro NXT Telecomunicacoes Ltda, BR 3816 1330 782 208 COLOMBIA TELECOMUNICACIONES S.A. ESP BIC, 6147 1193 371 22 Telefonica del Peru S.A.A., PE 11664 1163 278 33 Techtel LMDS Comunicaciones Interactivas 22884 1051 67 377 TOTAL PLAY TELECOMUNICACIONES SA DE CV, M 6503 1048 359 174 Axtel, S.A.B. 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 24835 1703 599 30 RAYA-AS, EG 24863 1620 389 18 LINKdotNET-AS, EG 29571 1567 102 23 ORANGE-COTE-IVOIRE, CI 36992 1428 1518 287 ETISALAT-MISR, EG 36903 1249 554 96 MT-MPLS, MA 36935 1006 521 42 Vodafone-, EG 20011 980 183 284 INTERNET-SOLUTIONS, ZA 37069 903 1083 15 MOBINIL, EG 6713 560 1861 35 IAM-AS, MA 36914 546 82 3 KENET-AS, KE 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 16509 12938 39643 3971 AMAZON-02, US 8151 11896 3243 582 UNINET, MX 9808 10316 8754 94 CHINAMOBILE-CN China Mobile Communication 12479 7722 1714 145 UNI2-AS, ES 7545 6218 843 656 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 4797 293 62 ALJAWWALSTC-AS, SA 4538 4780 4192 76 ERX-CERNET-BKB China Education and Resear 11492 4676 310 586 CABLEONE, US 9498 4293 530 278 BBIL-AP BHARTI Airtel Ltd., IN 7155 4173 286 83 VIASAT-SP-BACKBONE, US Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 8151 11896 11314 UNINET, MX 9808 10316 10222 CHINAMOBILE-CN China Mobile Communications Grou 12479 7722 7577 UNI2-AS, ES 7545 6218 5562 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 4797 4735 ALJAWWALSTC-AS, SA 4538 4780 4704 ERX-CERNET-BKB China Education and Research Net 11492 4676 4090 CABLEONE, US 7155 4173 4090 VIASAT-SP-BACKBONE, US 9498 4293 4015 BBIL-AP BHARTI Airtel Ltd., IN 7552 3871 3845 VIETEL-AS-AP Viettel Group, VN 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 212032 UNALLOCATED 5.59.105.0/24 35168 TNS-PLUS-CORE, KZ 22542 UNALLOCATED 8.7.205.0/24 3356 LEVEL3, US 33123 UNALLOCATED 8.10.69.0/24 174 COGENT-174, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-D 46639 UNALLOCATED 8.17.66.0/24 701 UUNET, US 53775 UNALLOCATED 8.20.88.0/24 7029 WINDSTREAM, US 393266 UNALLOCATED 8.23.52.0/24 46887 CROWNCASTLE-AS46887, US 396894 UNALLOCATED 8.28.201.0/24 46887 CROWNCASTLE-AS46887, US 394936 UNALLOCATED 8.33.224.0/24 22442 HOU-PHONOSCOPE, US 54338 UNALLOCATED 8.33.241.0/24 3356 LEVEL3, 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 14.192.20.0/22 Origin: 26658 HENGTONG-IDC-LLC, US 14.192.20.0/22 Transit: 6939 HURRICANE, US 23.136.140.0/24 Origin: 11832 BANDB-ROUTING, ZZ 23.136.140.0/24 Transit: 20473 AS-VULTR, US 23.140.216.0/24 Origin: 27176 DATAWAGON, US 23.140.216.0/24 Transit: 20278 NEXEON, US 23.141.0.0/24 Origin: 395350 RESERVED, ZZ 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, US 23.152.48.0/24 Origin: 46167 RESERVED, ZZ 23.152.48.0/24 Transit: 7018 ATT-INTERNET4, US 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:16 /10:41 /11:93 /12:302 /13:582 /14:1217 /15:2146 /16:13979 /17:8360 /18:13833 /19:24837 /20:44549 /21:52243 /22:112488 /23:101572 /24:603016 /25:799 /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 6654 7722 UNI2-AS, ES 8151 6096 11896 UNINET, MX 11492 3529 4676 CABLEONE, US 39891 3489 4797 ALJAWWALSTC-AS, SA 6327 3418 3623 SHAW, CA 7155 3120 4173 VIASAT-SP-BACKBONE, US 22773 2516 3378 ASN-CXA-ALL-CCI-22773-RDC, US 16509 2329 12938 AMAZON-02, US 30036 2218 2559 MEDIACOM-ENTERPRISE-BUSINESS, US 10620 2184 3522 Telmex Colombia S.A., CO Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1694 2:1518 3:600 4:6 5:4552 6:163 7:6 8:1555 9:1 11:172 12:1372 13:351 14:2556 15:351 16:279 17:363 18:911 20:446 21:4 22:188 23:7346 24:3024 25:2 27:2686 29:19 31:3223 32:40 34:80 35:204 36:2413 37:4741 38:8899 39:899 40:154 41:4217 42:949 43:2551 44:359 45:18503 46:4927 47:290 49:1993 50:1897 51:591 52:1554 54:301 55:1075 56:11 57:250 58:2132 59:1343 60:1171 61:2790 62:2920 63:1832 64:5489 65:2176 66:4600 67:3022 68:1121 69:3959 70:1111 71:614 72:2850 74:2807 75:1660 76:616 77:2711 78:1860 79:1718 80:2209 81:2014 82:2985 83:1416 84:1821 85:3374 86:1046 87:2402 88:1283 89:4328 90:778 91:8318 92:2799 93:2876 94:4092 95:4274 96:1422 97:313 98:993 99:739 100:71 101:1168 102:3704 103:32205 104:4801 105:749 106:994 107:2590 108:1209 109:4045 110:2232 111:3348 112:2041 113:1532 114:1958 115:2098 116:2037 117:2733 118:2417 119:1926 120:1890 121:1413 122:2751 123:2175 124:1617 125:2883 126:88 128:1567 129:959 130:1275 131:1905 132:781 133:451 134:1528 135:329 136:1280 137:1159 138:2892 139:1618 140:1572 141:1495 142:1822 143:1659 144:1061 145:515 146:2155 147:2097 148:2628 149:2904 150:1250 151:2038 152:2106 153:504 154:7888 155:1617 156:3283 157:1893 158:1267 159:2430 160:3526 161:1929 162:3709 163:1957 164:1696 165:2205 166:1424 167:1886 168:4061 169:797 170:5095 171:1003 172:4466 173:3230 174:911 175:1283 176:3687 177:4765 178:3818 179:2337 180:2579 181:4062 182:3374 183:1808 184:2294 185:21489 186:5119 187:4412 188:4202 189:4209 190:9631 191:1521 192:11186 193:9422 194:7793 195:5534 196:3287 197:3674 198:6194 199:8434 200:8186 201:6300 202:10560 203:10520 204:4546 205:3683 206:4628 207:3559 208:4191 209:5236 210:4802 211:2630 212:4507 213:3757 214:1046 215:48 216:6585 217:3084 218:1381 219:538 220:2087 221:1071 222:850 223:2339 End of report

1 0

[NANOG] ** Reminder! NANOG 94 Call for Presentations + More
by Nanog News 27 Mar '25

27 Mar '25

*** Reminder! NANOG 94 Call for Presentations* ------------------------------------------------------------ *Transform Your Research, Ideas, and Best Practices into a NANOG Talk* NANOG 94 will spotlight Data Center Operations, but we encourage proposals on any relevant topic. To be considered, please submit your presentation proposal—along with draft slides—by Monday, April 28. *MORE INFO <https://nanog.org/program/call-presentations/> *( https://nanog.org/program/call-presentations/) *** NANOG 94 Beer ‘N Gear Sponsorships Available!* ------------------------------------------------------------ *Elevate Your Brand at NANOG’s Signature Event* Beer 'N Gear offers a trade show experience in a social setting. Reserve your table today + connect with fellow conference attendees in a meaningful way. *Contact Shawn Winstead swinstead(a)nanog.org <swinstead(a)nanog.org> for more details.* *** Video of the Week!* ------------------------------------------------------------ *Datacenter Optics: Demand Explosion + Tech Acceleration Beyond 400G w/ Scott Wilkinson - Cignal AI* Driven largely by the surge in AI applications, demand for datacenter optics has skyrocketed, with 400GbE shipments exceeding 3 million per quarter, 800GbE rapidly rising, and 1.6TbE on the horizon as infrastructure catches up—meanwhile, inter-datacenter optics are gaining traction due to space and power constraints. *WATCH NOW <https://www.youtube.com/watch?v=gW01quQD-YY> *( https://www.youtube.com/watch?v=gW01quQD-YY) *** Stay Connected* ------------------------------------------------------------ http://www.facebook.com http://www.instagram.com/nanog_org/ http://www.linkedin.com/company/nanog/ https://www.twitter.com/nanog/ http://nanog.org .

1 0