August 2026 - NANOG - lists.nanog.org

Whois using these ARIN services?? (fwd: Consultation on the Future of ARIN’s Directory Services)
by John Curran 14 Aug '26

14 Aug '26

NANOGers - ARIN is undertaking a community consultation on the Future of ARIN’s Directory Services. If you are interested in this topic, please see details below, including how to join the ARIN-consult mailing list. Thanks! /John John Curran President and CEO American Registry for Internet Numbers Begin forwarded message: From: ARIN <info(a)arin.net> Subject: [ARIN-consult] Consultation on the Future of ARIN’s Directory Services Date: August 14, 2026 at 11:16:12 AM EDT To: <arin-consult(a)arin.net> ARIN is seeking feedback from the community on a proposed road map to streamline and consolidate its directory services. ARIN currently maintains four directory information protocols: Whois-RWS, RWhois, Whois (Port 43), and RDAP. Supporting multiple redundant services that provide the same information creates additional administrative and operational overhead to the organization. To reduce ARIN’s attack surface, streamline operations and lower future operational overhead, ARIN proposes retiring use of older protocols in favor of RDAP as our single, standardized directory service. This transition is an important step toward improving alignment with established IETF standards. We have already seen this transition in the domain industry with ICANN mandating the use of RDAP for directory services and dropping the requirement to support Whois. We also expect RDAP clients to become increasingly common in OS distributions in the coming years. ------ Benefits of Transition to RDAP  - Enhanced Directory Services: Future enhancements, such as geolocation, will only be implemented in RDAP.  - Standardization and Automation: RDAP’s standardized data structure will improve automation for clients and provide greater flexibility in managing future data changes.  - Reduced Technical Overhead: Removing old and redundant services will provide time and cost savings for ARIN.  ------ Timeline and Retirement Planning This consultation seeks community input for the proposed retirement timelines below. We are keenly interested in receiving specific input on any barriers and/or obstacles these changes may create for customers, as well as steps ARIN can take to ensure a smooth transition. Note that the retirement plans for each impacted directory service will be completed independently, though in some cases work may be conducted concurrently. *** Whois-RWS Retirement Plan and Timeline ARIN currently offers Whois-RWS in two formats: an API and a web interface (located at https://whois.arin.net/ui/) Because the API has the same functionality between Whois-RWS and RDAP, ARIN proposes sunsetting the Whois-RWS API following a 180-day customer outreach program. This will include updating the Whois-RWS payloads to include a notification to users, as well as a robust communication strategy that includes announcements, social promotion, and other outreach. The Whois-RWS web interface will remain available until work is completed to ensure parity, providing equivalent query capabilities to RDAP. The changeover from Whois-RWS to RDAP will be transparent to end users visiting that URL. ARIN will inform the community a minimum of 30 days before the retirement of the Whois-RWS web interface, noting the switch to RDAP will not change the end user experience. *** RWhois Retirement Plan and Timeline When RWhois server use is retired, we will provide organizations with a recommendation for an open-source RDAP server implementation. To help ease the transition and migration of data, ARIN plans to provide a conversion tool for populating that recommended RDAP server with existing RWhois data. When the tool is publicly available, ARIN proposes a 365-day sunsetting timeline for RWhois. This will allow for robust communication and direct outreach to organizations who use RWhois and plan to either convert to the RDAP client or discontinue their use of local clients and report their reassignment information directly to ARIN instead. *** Whois (Port 43) Retirement Plan and Timeline ARIN understands that Whois (Port 43) carries a high volume of queries and will require the longest timeline to retire. We propose a two-year sunsetting window, during which ARIN will engage in active outreach to users. This will include updates to Whois (Port 43) results during the sunsetting period that will contain information about the retirement deadline. Because Whois (Port 43) has been the historically preferred method of querying Internet number resource registration data, it remains heavily used by cybersecurity professionals, researchers, law enforcement, and many other types of organizations. ARIN will seek to engage beyond our community to raise awareness of the planned retirement date for Whois (Port 43). ------ After the retirement of the directory service protocols described above and listed below, ARIN will only support RDAP as our single, standardized directory service. - Whois-RWS: on or after 1 July 2027 - RWhois: dependent on migration tool release date, but no sooner than 1 January 2028 - Whois (Port 43): on or after 1 January 2029 Throughout the sunsetting process for all services, ARIN will engage with our community to ensure customers and users are well-informed about the retirement of the described services and ARIN’s transition to RDAP as its standard directory service. We look forward to your feedback on the proposed timelines for retirement for Whois-RWS, RWhois, and Whois (Port 43). We ask that you consider each service independently, with the understanding that each of these services may impact your organization differently. Please provide comments to arin-consult(a)arin.net. You can subscribe to this mailing list at https://lists.arin.net/mailman/listinfo/arin-consult. This consultation will remain open until 5:00 PM ET on 14 September 2026. ARIN seeks clear direction through community input, so your feedback is important. Thank you for your continued support in improving ARIN’s services. Regards, John Curran President and CEO ARIN ------ Relevant links: - Presentation from ARIN 56: https://www.arin.net/participate/meetings/ARIN56/materials/arin56_directory… - IETF Standard for RDAP: https://www.rfc-editor.org/info/std95 - Guide to RDAP Client Implementations: https://rdap.rcode3.com/client_implementations/index.html - ARIN RDAP Documentation: https://www.arin.net/resources/registry/whois/rdap/ _______________________________________________ ARIN-Consult

1 0

Meet your NANOG 98 keynote speakers
by NANOG News 13 Aug '26

13 Aug '26

** AT&T and HPE power NANOG 98 ------------------------------------------------------------ NANOG 98's Global Connectivity Partners are AT&T and HPE. Their support makes this gathering of North America's network operators and infrastructure leaders possible. Thank you, AT&T and HPE! https://nanog.org/events/nanog-98/ ** Find your people in Miami ------------------------------------------------------------ The program is only part of the NANOG experience. Scheduled socials, one-on-one meetups, and hallway conversations are where a lot of the real work happens. Swap operational knowledge, meet potential collaborators, and catch up with colleagues—only at NANOG. REGISTER FOR NANOG 98 (https://nanog.org/events/nanog-98/) ** Here's what's on the NANOG 98 agenda ------------------------------------------------------------ The first sessions for NANOG 98 have been accepted, and they go right to the heart of our spotlight topic, International Connectivity. On the program so far: "From Testing to Reliability: Detecting Silent Failures in Production Systems (https://nanog.org/events/nanog-98/content/5743/) ," "Affogatos: Navigating Intergenerational Working Relationships ( https://nanog.org/events/nanog-98/content/5841/) ," and "Digital Coherent Optics - Deployment and Operation ( https://nanog.org/events/nanog-98/content/5851/) ." CHECK OUT THE AGENDA (https://nanog.org/events/nanog-98/block-agenda/) ** Meet your NANOG 98 keynote speakers ------------------------------------------------------------ Day 1 opens with Paul Brodsky, Telecommunications Analyst at TeleGeography. Earlier this year, his firm testified before the House Committee on Homeland Security on foreign adversary threats to subsea cable infrastructure. At NANOG 98, he'll speak on global infrastructure and Layer 3 interconnection. Day 2 opens with John Evans, a founder with previous roles at Cisco, AWS, Cariden, and BT. His talk takes on a pointed question: self-driving cars are becoming reality at scale, so why does autonomous network operations remain an ambition? He'll cover what it actually takes to move beyond incremental automation: operational models, machine-actionable telemetry, causal reasoning, and guardrails. ** On the blog: Top 10 connectivity talks ------------------------------------------------------------ NANOG 98's spotlight topic is International Connectivity, and we put together a list of ten talks and articles from our archives worth reading before you get to Miami. From subsea cables in Africa to the internet's biggest BGP incidents to what the World Cup does to global traffic, it's a good primer on what the community has been working through. READ THE FULL POST ( https://nanog.org/stories/our-top-10-talks-and-articles-about-international… ) *** Stay Connected* ------------------------------------------------------------ http://www.facebook.com/NANOG.org/ http://www.instagram.com/nanog_org/ http://www.linkedin.com/company/nanog/ https://www.twitter.com/nanog/ https://discord.nanog.org/

1 0

Looking for third-party IXIA XG12 repair resources
by Alan Baumgartner 12 Aug '26

12 Aug '26

Hello, I'm looking for an independent repair resource for an IXIA XG12 chassis. Keysight won't service it without a support contract. Has anyone had good experiences with a third-party repair shop or former IXIA engineer? Hoping somebody has a suggestion Al B

1 0

Fwd: AS6939 (Hurricane Electric) packet loss on Helsinki/Piter-IX-bound path; Lagos, Nigeria origin
by Sina Owolabi 12 Aug '26

12 Aug '26

Apparently Ive not particpated at the list in a while. cordially yours, Sina Owolabi ---------- Forwarded message --------- From: Sina Owolabi <notify.sina(a)gmail.com> Date: Wed, Aug 12, 2026 at 3:30 PM Subject: AS6939 (Hurricane Electric) packet loss on Helsinki/Piter-IX-bound path; Lagos, Nigeria origin To: nanog(a)nanog.org list <nanog(a)nanog.org>, <outages(a)outages.org>, < deepsupport(a)qrios.com> Hi all, Sorry to bother you but we need some help We're seeing sustained, real packet loss inside Hurricane Electric's own network (AS6939) on a path from Lagos, Nigeria toward Helsinki. Loss starts at the first HE hop and persists all the way to the destination (a Hetzner Helsinki host we're trying to reach over a site-to-site IPsec tunnel). Confirmed via RDAP that the lossy hops are HE-registered space (org handle HURC), not just transiting through HE — this is on your own backbone, not further upstream. This is *not* a blanket HE issue from our vantage point: the same test toward RIPE NCC in Amsterdam, through the same HE hops (184.105.65.2 and neighbors), shows 0% loss. A test toward a Debian mirror (via Fastly) shows only minor loss (13-23%) on a couple of intermediate HE hops and 0% at the destination. So this looks specific to the segment continuing toward the Piter-IX Helsinki peering, not HE generally. mtr -n -r -i 1.5 -c 30 -s 300 run from our edge in Lagos (source 62.173.32.54) to a Hetzner Helsinki host (packet size/interval chosen to avoid ICMP rate-limit false positives): HOST Loss% Snt Last Avg Best Wrst StDev 62.173.32.49 0.0% 30 0.4 0.7 0.4 4.1 0.9 62.173.34.225 0.0% 30 0.5 0.6 0.4 2.5 0.4 41.184.211.32 0.0% 30 0.9 1.3 0.7 5.0 1.0 41.184.56.17 0.0% 30 93.3 92.0 91.3 98.9 1.5 62.173.35.222 0.0% 30 91.5 91.7 91.3 94.6 0.7 184.105.65.2 0.0% 30 99.3 98.7 98.3 102.6 0.8 184.104.192.133 26.7% 30 100.1 101.1 99.1 104.3 1.3 <- HE (AS6939) 184.104.188.218 36.7% 30 199.2 142.4 129.9 201.0 25.5 <- HE (AS6939) 184.104.198.57 36.7% 30 187.4 133.0 127.5 187.4 13.3 <- HE (AS6939) 184.104.198.147 0.0% 30 142.9 133.9 128.3 144.2 5.9 72.52.92.106 63.3% 30 196.2 146.5 126.7 199.5 31.9 <- HE (AS6939) 193.27.37.131 30.0% 30 202.8 139.7 129.1 202.8 24.9 <- Piter-IX Helsinki 213.239.224.26 33.3% 30 195.4 136.3 129.1 195.4 19.9 <- Hetzner 213.133.119.11 30.0% 30 196.9 140.4 129.1 199.1 24.3 <- Hetzner [destination] 40.0% 30 196.9 133.2 129.1 196.9 15.9 <- Hetzner (endpoint) Reproduced against a second, unrelated destination in the same Hetzner Helsinki range with the same result (same HE hops, same loss pattern). Reproducible over multiple runs across several hours. Would appreciate it if anyone from Hurricane Electric's NOC/engineering, or anyone who can point me to the right escalation path, could take a look at the segment from 184.104.192.133 onward toward the Piter-IX Helsinki peering. Happy to share full raw output, run tests at a specific time of your choosing, or provide a looking-glass-reachable source if that helps triage. Sina Owolabi

2 2

OARC 47 Call for Contribution - less than two weeks to go before the CfP closes on 24th August!
by Willem Toorop 12 Aug '26

12 Aug '26

The OARC 47 Call for Contributions is open but is closing soon - if you are planning to submit a talk, please don't leave it too late and miss the deadling! This workshop will be a hybrid event. Date - 09-10 November 2026 Location - Vancouver, British Columbia Times - approximately 10:00-17:00 PDT (Local time PDT is UTC -7; note that British Columbia has opted to remain on PDT all year round) Deadline for Submissions - 2026-08-24 23:59 UTC https://indico.dns-oarc.net/event/58/abstracts/ All DNS-related subjects and discussion topics are welcome although we're particularly keen to hear more about operational and security related experiences, best practices and practical advice; both for newcomers to the DNS arena and those who have been around for longer who want to learn more about new features and opportunities to improve resilience, security and privacy. (These topics we think will complement the usual high-quality data-based research submissions we always hope to receive!) If you have something interesting to share with the community that lies outside of the focus above, please don't be put off - if it's good, we'll be happy to include it. You can also contact us directly at submissions(a)dns-oarc.net if you would like to ask about the suitability of a potential presentation submission topic. If you'd like to offer a talk, but are not quite sure what to pick, here's a non-exhaustive list of ideas: 1. Operations & Deployment * Configuration management, deployment processes, and interoperability experiences. * Tools, tips, and making effective use of DNS software features. 2. Performance, Resilience & Scaling * Provisioning, load-balancing, and planning for resilience. * DNS performance management, efficiency improvements, and metrics. * Monitoring infrastructure: log pipelines, analytics, and anomaly detection. 3. Security, Privacy & Policy * DoS attacks, DNS abuse, DNSSEC signing and validation. * Privacy considerations, for example: encrypted transport, qname minimization, data anonymization. * Relevant global and regional policies, legislation, and compliance. 4. Research & Innovation * Data-driven testing, measurement, and analysis. * New protocols, protocol extensions, and next-generation namespace management. 5. Lessons & Learnings * Outage experiences, recovery stories, and cautionary tales For further details please see https://www.dns-oarc.net/oarc47 Willem Toorop, for the DNS-OARC Programme Committee

1 0

Spoofer Report for NANOG for Jul 2026
by CAIDA Spoofer Project 08 Aug '26

08 Aug '26

In response to feedback from operational security communities, CAIDA's source address validation measurement project (https://spoofer.caida.org) is automatically generating monthly reports of ASes originating prefixes in BGP for systems from which we received packets with a spoofed source address. We are publishing these reports to network and security operations lists in order to ensure this information reaches operational contacts in these ASes. This report summarises tests conducted within usa, can. Inferred improvements during Jul 2026: ASN Name Fixed-By 3801 MISNET 2026-07-30 Further information for the inferred remediation is available at: https://spoofer.caida.org/remedy.php Source Address Validation issues inferred during Jul 2026: ASN Name First-Spoofed Last-Spoofed 20115 CHARTER-20115 2016-06-09 2026-07-05 14051 SUREWEST 2017-10-26 2026-07-17 22883 CONDENAST 2019-05-29 2026-07-28 21804 ACCESS-SK 2019-06-09 2026-07-30 393397 LREC-LRT 2020-08-02 2026-07-31 396356 MAXIHOST 2021-02-27 2026-07-14 262287 Maxihost LTDA 2021-10-09 2026-07-15 12183 TALKIE-COMMUNICATIONS 2022-12-10 2026-07-27 400282 2023-04-27 2026-07-28 394684 AS-GOLD 2024-01-17 2026-07-26 27425 ASN-IDK-27425 2024-02-21 2026-07-28 393530 TLU 2024-05-22 2026-07-30 54334 ROYA 2025-03-13 2026-07-29 273843 2025-04-02 2026-07-28 212238 CDNEXT 2026-02-18 2026-07-30 64289 2026-06-14 2026-07-31 394456 REDBELLRE 2026-07-09 2026-07-09 54861 BFCSY 2026-07-11 2026-07-18 48266 2026-07-17 2026-07-17 Further information for these tests where we received spoofed packets is available at: https://spoofer.caida.org/recent_tests.php?country_include=usa,can&no_block… Please send any feedback or suggestions to spoofer-info(a)caida.org

1 0

Router info needed
by mike.trane＠gmail.com 07 Aug '26

07 Aug '26

Hi, New to this list. We are having excellent results in S. America with the JUNIPER ACX7348 DC powered router. We need a pair for a US project with AC power. Used or demo gear OK. Any help is appreciated! Best, Mike

1 0

IS-IS Flat Network Size
by ttaggart＠kingcounty.gov 07 Aug '26

07 Aug '26

Hello, I'm wondering what some practical/real experiences have been with building out a large flat IS-IS network. I've read a lot of threads on conjecture and older docs on what the vendors recommend but haven't found anything yet or real world examples. Two questions, 1) Is anyone running a flat IS-IS L2 network with approx 300 routers? If not, what is the higher end you've seen? 2) On aggregation routers, what is the upper end of IS-IS adj to downstream routers? Would agg routers with approx 100 connections be an issue moving to IS-IS with the addition of keeping track of that many adj? Thanks.

9 15

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 07 Aug '26

07 Aug '26

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 08 Aug, 2026 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: 1067434 Prefixes after maximum aggregation (per Origin AS): 409019 Deaggregation factor: 2.61 Unique aggregates announced (without unneeded subnets): 527192 Number of IPv4 prefixes with a valid ROA: 729400 Number of IPv4 prefixes with an invalid ROA: 1683 Number of IPv4 prefixes with no ROA: 336351 Total ASes present in the Internet Routing Table: 79012 Prefixes per ASN: 13.51 Origin-only ASes present in the Internet Routing Table: 67900 Origin ASes announcing only one prefix: 27693 Transit ASes present in the Internet Routing Table: 11112 Transit-only ASes present in the Internet Routing Table: 606 Average AS path length visible in the Internet Routing Table: 4.7 Max AS path length visible: 69 Max AS path prepend of ASN (269326) 61 Prefixes from unregistered ASNs in the Routing Table: 1287 Number of instances of unregistered ASNs: 1337 Number of 32-bit ASNs allocated by the RIRs: 50748 Number of 32-bit ASNs visible in the Routing Table: 41288 Prefixes from 32-bit ASNs in the Routing Table: 236859 Number of bogon 32-bit ASNs visible in the Routing Table: 137 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 494 Number of addresses announced to Internet: 3118732032 Equivalent to 185 /8s, 228 /16s and 19 /24s Percentage of available address space announced: 84.2 Percentage of allocated address space announced: 84.2 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: 349172 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 292789 Total APNIC prefixes after maximum aggregation: 84950 APNIC Deaggregation factor: 3.45 Prefixes being announced from the APNIC address blocks: 278558 Unique aggregates announced from the APNIC address blocks: 109120 APNIC Region origin ASes present in the Internet Routing Table: 15335 APNIC Prefixes per ASN: 18.16 APNIC Region origin ASes announcing only one prefix: 4751 APNIC Region transit ASes present in the Internet Routing Table: 2022 Average APNIC Region AS path length visible: 4.7 Max APNIC Region AS path length visible: 37 Number of APNIC region 32-bit ASNs visible in the Routing Table: 10918 Number of APNIC addresses announced to Internet: 749228928 Equivalent to 44 /8s, 168 /16s and 83 /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: 308562 Total ARIN prefixes after maximum aggregation: 138343 ARIN Deaggregation factor: 2.23 Prefixes being announced from the ARIN address blocks: 306972 Unique aggregates announced from the ARIN address blocks: 150502 ARIN Region origin ASes present in the Internet Routing Table: 19501 ARIN Prefixes per ASN: 15.74 ARIN Region origin ASes announcing only one prefix: 7151 ARIN Region transit ASes present in the Internet Routing Table: 1907 Average ARIN Region AS path length visible: 4.3 Max ARIN Region AS path length visible: 35 Number of ARIN region 32-bit ASNs visible in the Routing Table: 5715 Number of ARIN addresses announced to Internet: 1348075008 Equivalent to 80 /8s, 89 /16s and 254 /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-404380 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: 296242 Total RIPE prefixes after maximum aggregation: 146564 RIPE Deaggregation factor: 2.02 Prefixes being announced from the RIPE address blocks: 301121 Unique aggregates announced from the RIPE address blocks: 196217 RIPE Region origin ASes present in the Internet Routing Table: 29670 RIPE Prefixes per ASN: 10.15 RIPE Region origin ASes announcing only one prefix: 12274 RIPE Region transit ASes present in the Internet Routing Table: 4024 Average RIPE Region AS path length visible: 4.8 Max RIPE Region AS path length visible: 34 Number of RIPE region 32-bit ASNs visible in the Routing Table: 13683 Number of RIPE addresses announced to Internet: 749176192 Equivalent to 44 /8s, 167 /16s and 133 /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-219547 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: 130726 Total LACNIC prefixes after maximum aggregation: 31409 LACNIC Deaggregation factor: 4.16 Prefixes being announced from the LACNIC address blocks: 125104 Unique aggregates announced from the LACNIC address blocks: 51095 LACNIC Region origin ASes present in the Internet Routing Table: 11476 LACNIC Prefixes per ASN: 10.90 LACNIC Region origin ASes announcing only one prefix: 2775 LACNIC Region transit ASes present in the Internet Routing Table: 2602 Average LACNIC Region AS path length visible: 5.3 Max LACNIC Region AS path length visible: 69 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 9551 Number of LACNIC addresses announced to Internet: 168372736 Equivalent to 10 /8s, 9 /16s and 42 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-275868 + 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: 37828 Total AfriNIC prefixes after maximum aggregation: 7027 AfriNIC Deaggregation factor: 5.38 Prefixes being announced from the AfriNIC address blocks: 55185 Unique aggregates announced from the AfriNIC address blocks: 19832 AfriNIC Region origin ASes present in the Internet Routing Table: 2051 AfriNIC Prefixes per ASN: 26.91 AfriNIC Region origin ASes announcing only one prefix: 742 AfriNIC Region transit ASes present in the Internet Routing Table: 384 Average AfriNIC Region AS path length visible: 5.3 Max AfriNIC Region AS path length visible: 54 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1421 Number of AfriNIC addresses announced to Internet: 103615232 Equivalent to 6 /8s, 45 /16s and 11 /24s AfriNIC AS Blocks 36864-37887, 327680-330751 & 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 14200 8919 100 CHINAMOBILE-CN - China Mobile Communicati 7545 5837 818 450 TPG-INTERNET-AP - TPG Telecom Limited, AU 4538 5070 4192 74 ERX-CERNET-BKB - China Education and Rese 9498 5061 558 341 BBIL-AP - BHARTI Airtel Ltd., IN 18403 4651 347 24 FPT-VN - FPT Telecom Company, VN 7552 4026 1331 24 VIETEL-AS-AP - Viettel Group, VN 7713 3766 1044 63 telkomnet-as-ap - PT Telekomunikasi Indon 17561 3658 230 636 LCS-AS-AP - LARUS Limited, HK 56046 3596 887 179 CMNET-Jiangsu-AP - China Mobile communica 45899 3396 1868 99 VNPT-AS-VN - VNPT Corp, VN 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 15711 41558 5640 AMAZON-02 - Amazon.com, Inc., US 22773 4810 3182 373 ASN-CXA-ALL-CCI-22773-RDC - Cox Communica 11492 4617 307 1126 CABLEONE - CABLE ONE, INC., US 7155 3992 286 98 VIASAT-SP-BACKBONE - ViaSat,Inc., US 6327 3731 1305 75 SHAW - Shaw Communications, CA 396982 3461 4879 547 GOOGLE-CLOUD-PLATFORM - Google LLC, US 36352 3191 238 1114 AS-COLOCROSSING - HostPapa, US 749 3135 54727 2386 DNIC-AS-00749 - United States Department 7029 2718 2534 878 WINDSTREAM - Windstream Communications LL 31898 2583 1325 1141 ORACLE-BMC-31898 - Oracle Corporation, 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 7004 1711 150 UNI2-AS - Orange Espagne SA, ES 39891 4907 302 76 ALJAWWALSTC-AS - Saudi Telecom Company JS 9009 4173 378 2556 M247 - M247 Europe SRL, RO 20940 3802 3388 101 AKAMAI-ASN1 - Akamai International B.V., 212238 3508 252 2648 CDNEXT - Datacamp Limited, GB 12389 3161 2332 871 ROSTELECOM-AS - PJSC Rostelecom, RU 29355 2545 151 24 KCELL-AS - Kcell JSC, KZ 34984 2485 367 588 TELLCOM-AS - Superonline Iletisim Hizmetl 44559 1944 122 909 ITHOSTLINE - IT HOSTLINE LTD, CY 8452 1716 1852 17 TE-AS - IDDQD-AS, EG 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 12968 3289 616 AS8151 - UNINET, MX 10620 3444 451 1107 AS10620 - Telmex Colombia S.A., CO 13999 2279 499 331 AS13999 - Mega Cable, S.A. de C.V., MX 11830 1885 369 65 AS11830 - Instituto Costarricense de Elec 11664 1498 277 34 AS11664 - Techtel LMDS Comunicaciones Int 28573 1375 2429 271 AS28573 - Claro NXT Telecomunicacoes Ltda 3816 1342 768 213 AS3816 - COLOMBIA TELECOMUNICACIONES S.A. 6147 1210 371 21 AS6147 - INTEGRATEL PERU S.A.A., PE 22884 1097 70 386 AS22884 - TOTAL PLAY TELECOMUNICACIONES, 26615 1052 2384 95 AS26615 - TIM S/A, 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 1986 585 33 Vodafone Data - Vodafone Data, EG 36992 1928 1543 333 ETISALAT MISR - ETISALAT MISR, EG 36903 1350 587 104 Office National des Postes et Telecommuni 24863 1320 389 16 Link Egypt (Link.NET) - Link Egypt (Link. 36935 1277 524 47 Vodafone Data - Vodafone Data, EG 37069 1116 1100 11 The Egyptian Company for Mobile Services 29571 1086 70 18 Orange Côte d'Ivoire - Orange Côte d'Iv 328608 617 55 201 Africa on Cloud - Africa on Cloud, ZA 15399 570 58 64 Wananchi Group (Kenya) Limited - Wananchi 36914 546 82 3 Kenya Education Network - Kenya Education 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 15711 41558 5640 AMAZON-02 - Amazon.com, Inc., US 9808 14200 8919 100 CHINAMOBILE-CN - China Mobile Communicati 8151 12968 3289 616 AS8151 - UNINET, MX 12479 7004 1711 150 UNI2-AS - Orange Espagne SA, ES 7545 5837 818 450 TPG-INTERNET-AP - TPG Telecom Limited, AU 4538 5070 4192 74 ERX-CERNET-BKB - China Education and Rese 9498 5061 558 341 BBIL-AP - BHARTI Airtel Ltd., IN 39891 4907 302 76 ALJAWWALSTC-AS - Saudi Telecom Company JS 22773 4810 3182 373 ASN-CXA-ALL-CCI-22773-RDC - Cox Communica 18403 4651 347 24 FPT-VN - FPT Telecom Company, VN Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 9808 14200 14100 CHINAMOBILE-CN - China Mobile Communications Gr 8151 12968 12352 AS8151 - UNINET, MX 12479 7004 6854 UNI2-AS - Orange Espagne SA, ES 7545 5837 5387 TPG-INTERNET-AP - TPG Telecom Limited, AU 4538 5070 4996 ERX-CERNET-BKB - China Education and Research N 39891 4907 4831 ALJAWWALSTC-AS - Saudi Telecom Company JSC, SA 9498 5061 4720 BBIL-AP - BHARTI Airtel Ltd., IN 18403 4651 4627 FPT-VN - FPT Telecom Company, VN 22773 4810 4437 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7552 4026 4002 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 394928 UNALLOCATED 8.2.70.0/24 3356 LEVEL3 - Level 3 Parent 395729 UNALLOCATED 8.28.60.0/24 32787 PROLEXIC-TECHNOLOGIES-D 396894 UNALLOCATED 8.28.201.0/24 3356 LEVEL3 - Level 3 Parent 394936 UNALLOCATED 8.33.224.0/24 174 COGENT-174 - Cogent Com 396243 UNALLOCATED 8.34.113.0/24 3356 LEVEL3 - Level 3 Parent 397274 UNALLOCATED 8.36.79.0/24 3356 LEVEL3 - Level 3 Parent 396243 UNALLOCATED 8.37.112.0/24 3356 LEVEL3 - Level 3 Parent 396243 UNALLOCATED 8.37.123.0/24 3356 LEVEL3 - Level 3 Parent 395195 UNALLOCATED 8.38.115.0/24 3356 LEVEL3 - Level 3 Parent 397274 UNALLOCATED 8.40.70.0/24 3356 LEVEL3 - Level 3 Parent 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 - Hurricane Electric LLC, US Complete listing at https://thyme.apnic.net/current/data-spar Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.131.100.0/24 Origin: 401541 UNASSIGNED 23.131.100.0/24 Transit: 38733 CMCTELECOM-VN - CMC Telecom Infrastructu 23.131.156.0/24 Origin: 401541 UNASSIGNED 23.131.156.0/24 Transit: 38733 CMCTELECOM-VN - CMC Telecom Infrastructu 23.131.212.0/24 Origin: 401541 UNASSIGNED 23.131.212.0/24 Transit: 38733 CMCTELECOM-VN - CMC Telecom Infrastructu 23.133.212.0/24 Origin: 18604 UNASSIGNED 23.133.212.0/24 Transit: 394625 WHITELABELIT - WhiteLabel IT Solutions C 23.137.48.0/24 Origin: 16904 ARVIG-16904 - Arvig Enterprises Inc., US 23.137.48.0/24 Transit: 3257 GTT-BACKBONE - GTT Communications Inc., 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:14 /10:39 /11:97 /12:299 /13:586 /14:1183 /15:2125 /16:13729 /17:8378 /18:13357 /19:25730 /20:46921 /21:54011 /22:113897 /23:110485 /24:675869 /25:698 /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 8151 7156 12968 AS8151 - UNINET, MX 12479 5931 7004 UNI2-AS - Orange Espagne SA, ES 39891 3656 4907 ALJAWWALSTC-AS - Saudi Telecom Company JSC, SA 11492 3512 4617 CABLEONE - CABLE ONE, INC., US 6327 3510 3731 SHAW - Shaw Communications, CA 22773 3056 4810 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications Inc., US 16509 2994 15711 AMAZON-02 - Amazon.com, Inc., US 7155 2946 3992 VIASAT-SP-BACKBONE - ViaSat,Inc., US 10620 2248 3444 AS10620 - Telmex Colombia S.A., CO 30036 2210 2556 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communications Corp, US Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:2677 2:2855 3:1020 4:5 5:5282 6:207 7:6 8:1391 9:96 11:172 12:1103 13:825 14:2787 15:486 16:264 17:454 18:944 20:602 21:4 22:188 23:8580 24:2790 25:2 27:2806 28:6 29:19 31:3834 32:37 34:94 35:293 36:4894 37:4466 38:10306 39:1383 40:432 41:4620 42:2254 43:3343 44:477 45:20076 46:5002 47:460 48:168 49:2269 50:2018 51:838 52:1371 54:307 55:1184 56:11 57:331 58:2498 59:1421 60:1239 61:3218 62:3176 63:1749 64:6556 65:2148 66:6236 67:3334 68:1286 69:4047 70:1055 71:606 72:3265 74:3082 75:1600 76:593 77:2924 78:2117 79:1846 80:2389 81:2288 82:4310 83:1495 84:2167 85:3919 86:1114 87:2909 88:1329 89:4821 90:770 91:8518 92:2751 93:3045 94:4484 95:4732 96:1448 97:307 98:936 99:970 100:73 101:1349 102:4736 103:32434 104:5664 105:835 106:918 107:2979 108:1380 109:3929 110:2285 111:4269 112:3149 113:1932 114:2530 115:2243 116:2102 117:3686 118:3016 119:2106 120:2829 121:1720 122:3053 123:2241 124:1734 125:3030 126:157 128:1573 129:979 130:1726 131:2523 132:901 133:493 134:1788 135:647 136:1559 137:1456 138:3412 139:1811 140:1977 141:1820 142:2611 143:2192 144:1869 145:670 146:2196 147:2333 148:2822 149:3614 150:1412 151:3020 152:2452 153:1955 154:9961 155:2384 156:4660 157:2451 158:1631 159:2911 160:4003 161:2070 162:4215 163:2683 164:2386 165:2784 166:1193 167:2383 168:4242 169:908 170:5653 171:1129 172:4921 173:3484 174:890 175:1401 176:4041 177:5261 178:4564 179:2505 180:3291 181:4671 182:4060 183:2864 184:2053 185:21958 186:6554 187:5592 188:4769 189:4674 190:9981 191:1790 192:11831 193:9640 194:7972 195:5932 196:3445 197:3203 198:6364 199:6114 200:8464 201:6719 202:10758 203:10520 204:4756 205:3782 206:4449 207:4105 208:4337 209:5492 210:4905 211:2802 212:5232 213:4133 214:1021 215:47 216:7306 217:3740 218:1947 219:583 220:2267 221:1394 222:1122 223:3589 End of report

1 0

Frontier IPv6 Prefix Delegation - AS5650
by Chris Riling 07 Aug '26

07 Aug '26

Hi, Anyone here have a knowledgeable contact at Frontier? I’m on a residential fiber connection and recently started getting a v6 delegation (yay!) but they’re only handing out /64s. Obviously this doesn’t allow for proper subnetting, and forces me to use NPTv6 / ULA if I want to do things “properly”, and devices essentially ignoring their v6 interface. This also seems to be in conflict with RFC 6177 and seems to somewhat defeat the purpose of v6. Any way to get a /56 or more? Support is clueless. Thanks! Chris

8 14