- NANOG - lists.nanog.org

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

AS3491 Contact
by aaron＠digitalcrossroad.org 11 Jan '23

11 Jan '23

Hi, Would someone from AS3491 please contact me off-list? Been trying to fix a prefix acceptance issue for weeks and am getting nowhere. Thanks, Aaron

2 1

SDN Internet Router (sir)
by Mike Hammett 11 Jan '23

11 Jan '23

https://github.com/dbarrosop/sir I came across this over the weekend. Given that the project was abandoned six years ago, are there any other efforts with a similar goal (more intelligently placing routes into FIBs of low-FIB capacity devices? ----- Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP

12 43

Re: SDN Internet Router (sir)
by Mel Beckman 10 Jan '23

10 Jan '23

Mike, Your original question was: “Given that the project was abandoned six years ago, are there any other efforts with a similar goal (more intelligently placing routes into FIBs of low-FIB capacity devices?” People then, respectfully, tried to clarify your request or explain why placing routes in a low-FIB capacity device isn’t seen as being beneficial. Only now have you added the desire to simply have “more than a default route” in such a router. You can, of course, have more than a default route today - e.g., through local pref and BGP communities for things such as company routes. You haven’t said what you define as “more intelligently”, so perhaps you can more clearly explain the problem you see with the current BGP capabilities via some examples. -mel On Jan 5, 2023, at 8:02 AM, Mike Hammett <nanog(a)ics-il.net> wrote: Then please bless the world with the right way. You acknowledge that not every router in a network needs to be fully DFZ capable, but then crap on my desire to have more than a default route in one. ----- Mike Hammett Intelligent Computing Solutions<http://www.ics-il.com/> [http://www.ics-il.com/images/fbicon.png]<https://www.facebook.com/ICSIL>[http://www.ics-il.com/images/googleicon.png]<https://plus.google.com/+IntelligentComputingSolutionsDeKalb>[http://www.ics-il.com/images/linkedinicon.png]<https://www.linkedin.com/company/intelligent-computing-solutions>[http://www.ics-il.com/images/twittericon.png]<https://twitter.com/ICSIL> Midwest Internet Exchange<http://www.midwest-ix.com/> [http://www.ics-il.com/images/fbicon.png]<https://www.facebook.com/mdwestix>[http://www.ics-il.com/images/linkedinicon.png]<https://www.linkedin.com/company/midwest-internet-exchange>[http://www.ics-il.com/images/twittericon.png]<https://twitter.com/mdwestix> The Brothers WISP<http://www.thebrotherswisp.com/> [http://www.ics-il.com/images/fbicon.png]<https://www.facebook.com/thebrotherswisp>[http://www.ics-il.com/images/youtubeicon.png]<https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg> ________________________________ From: "Tom Beecher" <beecher(a)beecher.cc> To: "Mike Hammett" <nanog(a)ics-il.net> Cc: "Mel Beckman" <mel(a)beckman.org>, "NANOG" <nanog(a)nanog.org> Sent: Thursday, January 5, 2023 9:55:38 AM Subject: Re: SDN Internet Router (sir) "The right tool for the job" gets into a religious argument in assuming that one's way to do the job is the only reasonable way to do the job I disagree that it's religious. I completely agree there are locations in networks that having full DFZ capable routers doesn't make technical or economic sense. But there have long been different products for those different use cases. To perhaps explain my viewpoint better,(and perhaps I didn't properly comprehend the problem you're aiming to solve) : If you are trying to use SDN stuff to shuffle routes on and off a box because you have the wrong sized routers in place, then I would argue you're doing it wrong. If you are trying to use SDN stuff to (as Christopher mentioned) make decisions that are not strictly LPM, and the equipment you have cannot do that, then that's different and entirely reasonable. If the second use case is more of what you were asking, then I apologize for misunderstanding. On Thu, Jan 5, 2023 at 9:57 AM Mike Hammett <nanog(a)ics-il.net<mailto:nanog@ics-il.net>> wrote: "The right tool for the job" gets into a religious argument in assuming that one's way to do the job is the only reasonable way to do the job. Large networks historically have a very poor (IMO) model of gigantic iron in a few locations, which results in sub-optimal routing for the rest of their network between those large POPs. I've heard time and time again that someone buying service from a major network in say New Orleans has a first hop of Dallas or Atlanta. I agree that full-route capable routers need to be in the large, central locations, but it isn't cost effective to have them at every POP, especially if you're a last-mile provider. I'd go into more examples of where it doesn't make sense to have full-route routers everywhere, but I'm afraid that the Internet would then focus on the examples instead of the core idea of intelligently putting routes into the FIBs of low-FIB routers throughout my network. ----- Mike Hammett Intelligent Computing Solutions<http://www.ics-il.com/> [http://www.ics-il.com/images/fbicon.png]<https://www.facebook.com/ICSIL>[http://www.ics-il.com/images/googleicon.png]<https://plus.google.com/+IntelligentComputingSolutionsDeKalb>[http://www.ics-il.com/images/linkedinicon.png]<https://www.linkedin.com/company/intelligent-computing-solutions>[http://www.ics-il.com/images/twittericon.png]<https://twitter.com/ICSIL> Midwest Internet Exchange<http://www.midwest-ix.com/> [http://www.ics-il.com/images/fbicon.png]<https://www.facebook.com/mdwestix>[http://www.ics-il.com/images/linkedinicon.png]<https://www.linkedin.com/company/midwest-internet-exchange>[http://www.ics-il.com/images/twittericon.png]<https://twitter.com/mdwestix> The Brothers WISP<http://www.thebrotherswisp.com/> [http://www.ics-il.com/images/fbicon.png]<https://www.facebook.com/thebrotherswisp>[http://www.ics-il.com/images/youtubeicon.png]<https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg> ________________________________ From: "Tom Beecher" <beecher(a)beecher.cc<mailto:beecher@beecher.cc>> To: "Mike Hammett" <nanog(a)ics-il.net<mailto:nanog@ics-il.net>> Cc: "Mel Beckman" <mel(a)beckman.org<mailto:mel@beckman.org>>, "NANOG" <nanog(a)nanog.org<mailto:nanog@nanog.org>> Sent: Wednesday, January 4, 2023 7:36:58 AM Subject: Re: SDN Internet Router (sir) Disagree that it’s a line in the sand. It’s use the right tool for the job. If a device is low FIB, it’s that way for a reason. There are plenty of ways to massage that with policy and software, depending on capabilities , but at the end of the day, trying to sort 10 pounds of shit to store in a 5 pound bag is eventually going to end up the same way. On Tue, Jan 3, 2023 at 13:18 Mike Hammett <nanog(a)ics-il.net<mailto:nanog@ics-il.net>> wrote: There are likely more networks with 10 gigabit or less total external capacity than there are with more. Creating imaginary lines in the sand doesn't really help anyone. ----- Mike Hammett Intelligent Computing Solutions<http://www.ics-il.com/> [http://www.ics-il.com/images/fbicon.png]<https://www.facebook.com/ICSIL>[http://www.ics-il.com/images/googleicon.png]<https://plus.google.com/+IntelligentComputingSolutionsDeKalb>[http://www.ics-il.com/images/linkedinicon.png]<https://www.linkedin.com/company/intelligent-computing-solutions>[http://www.ics-il.com/images/twittericon.png]<https://twitter.com/ICSIL> Midwest Internet Exchange<http://www.midwest-ix.com/> [http://www.ics-il.com/images/fbicon.png]<https://www.facebook.com/mdwestix>[http://www.ics-il.com/images/linkedinicon.png]<https://www.linkedin.com/company/midwest-internet-exchange>[http://www.ics-il.com/images/twittericon.png]<https://twitter.com/mdwestix> The Brothers WISP<http://www.thebrotherswisp.com/> [http://www.ics-il.com/images/fbicon.png]<https://www.facebook.com/thebrotherswisp>[http://www.ics-il.com/images/youtubeicon.png]<https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg> ________________________________ From: "Mel Beckman" <mel(a)beckman.org<mailto:mel@beckman.org>> To: "Mike Hammett" <nanog(a)ics-il.net<mailto:nanog@ics-il.net>> Cc: "NANOG" <nanog(a)nanog.org<mailto:nanog@nanog.org>> Sent: Tuesday, January 3, 2023 10:57:34 AM Subject: Re: SDN Internet Router (sir) It’s not a problem, due to cheap, plentiful high-speed memory and rapid prefix search silicon in backbone routers. The entire Internet routing table consumes at most a few gigabytes when fully structured (and only a few hundred Mbytes stored flat). That’s less memory than your average laptop sports. Even in the worst case scenario, where every network decides to announce only its most specific prefixes, the BGP backbone would temporarily enter an oscillating state that generates a large number of routing updates into the inter-domain routing space. In this case, BGP route damping will quickly suppress the crazies while the backbone stabilizes. Small routers should not be taking full tables, since there is no point to them being in the default free zone. For large routers, neither memory nor CPU speed are an issue. High-speed routers operating in the default-free zone have a critical path in the forwarding decision for each packet: it needs to take less than the inter-packet arrival time for minimum-sized IP packets. This is easy to achieve with today’s hardware. A router line card with an aggregate line rate across all of its point-to-point interfaces of 10Tbps (readily available in today’s gear) can process packets with just a handful of cycles in the FIB Ternary Content Addressable Memory (TCAM) using ASIC-assisted lookups. TCAM is the most expensive component you’re paying for in such a router. It’s not cheap, but backbone routers don’t need to be cheap. They just need to not be memory-constrained. -mel via cell On Jan 3, 2023, at 7:47 AM, Mike Hammett <nanog(a)ics-il.net<mailto:nanog@ics-il.net>> wrote: https://github.com/dbarrosop/sir I came across this over the weekend. Given that the project was abandoned six years ago, are there any other efforts with a similar goal (more intelligently placing routes into FIBs of low-FIB capacity devices? ----- Mike Hammett Intelligent Computing Solutions<http://www.ics-il.com/> [http://www.ics-il.com/images/fbicon.png]<https://www.facebook.com/ICSIL>[http://www.ics-il.com/images/googleicon.png]<https://plus.google.com/+IntelligentComputingSolutionsDeKalb>[http://www.ics-il.com/images/linkedinicon.png]<https://www.linkedin.com/company/intelligent-computing-solutions>[http://www.ics-il.com/images/twittericon.png]<https://twitter.com/ICSIL> Midwest Internet Exchange<http://www.midwest-ix.com/> [http://www.ics-il.com/images/fbicon.png]<https://www.facebook.com/mdwestix>[http://www.ics-il.com/images/linkedinicon.png]<https://www.linkedin.com/company/midwest-internet-exchange>[http://www.ics-il.com/images/twittericon.png]<https://twitter.com/mdwestix> The Brothers WISP<http://www.thebrotherswisp.com/> [http://www.ics-il.com/images/fbicon.png]<https://www.facebook.com/thebrotherswisp>[http://www.ics-il.com/images/youtubeicon.png]<https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg>

5 7

Fwd: [arin-announce] Reminder — Set Up 2FA On Your ARIN Online Account Before 1 February
by John Curran 09 Jan '23

09 Jan '23

Reminder - Only Two-factor access for ARIN Online as of 1 February 2023. FYI, /John John Curran President and CEO American Registry for Internet Numbers Begin forwarded message: From: ARIN <info(a)arin.net> Date: January 9, 2023 at 10:54:22 AM PST To: arin-announce(a)arin.net Subject: [arin-announce] Reminder — Set Up 2FA On Your ARIN Online Account Before 1 February Beginning 1 February 2023, ARIN will require two-factor authentication (2FA) on all ARIN Online accounts. Customers can choose between Time-Based One-Time password (TOTP), SMS-based, and Fast Identity Online 2 (FIDO2/Passkey). We had initially planned to enforce 2FA following the deployment of SMS-based 2FA, but we opted to delay the implementation of enforcing 2FA for all ARIN Online accounts until we were able to complete implementation of FIDO2 due to significant community feedback received during our community consultation on this change. FIDO2/Passkey support is now available. You can learn more about your 2FA options by visiting our website: https://www.arin.net/reference/materials/security/twofactor/ By requiring 2FA for ARIN Online accounts that control number resources, the ARIN community should see stronger security for the registry, reduced risk of account fraud attempts, and increased confidence in the integrity of their ARIN resources. We strongly encourage account holders to set up 2FA in advance of the flag day for enforcement so that this change is not interruptive to your account access after 1 February 2023. Regards, John Curran President and CEO American Registry for Internet Numbers (ARIN) ---------------------- Helpful Resources: Need help setting up your 2FA? Visit https://www.arin.net/2fa to get started. You’ll find guides on enabling 2FA via an authenticator application such as Google Authenticator, SMS, and FIDO2/Passkey. Please note that voice call authentication is not available for new activations, but voice authentication is still available for those previously signed up and approved. We are working to restore this option. We also provide information on how to receive and save your 2FA recovery codes, as well as what to do if you’ve lost access to your authenticator or SMS/Voice phone number.

1 0

Spoofer Report for NANOG for Dec 2022
by CAIDA Spoofer Project 08 Jan '23

08 Jan '23

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 Dec 2022: ASN Name Fixed-By 400328 2022-12-25 208287 BAK 2022-12-26 Further information for the inferred remediation is available at: https://spoofer.caida.org/remedy.php Source Address Validation issues inferred during Dec 2022: ASN Name First-Spoofed Last-Spoofed 209 CENTURYLINK-US-LEGACY-QWEST 2016-08-16 2022-12-28 6128 CABLE-NET-1 2016-09-03 2022-12-22 20412 CLARITY-TELECOM 2016-09-30 2022-12-31 6181 FUSE-NET 2016-10-10 2022-12-31 271 BCNET 2016-10-24 2022-12-30 12083 WOW-INTERNET 2016-11-09 2022-12-30 14576 HOSTING-SOLUTIONS 2016-11-20 2022-12-28 852 ASN852 2017-04-16 2022-12-29 33452 RW 2018-09-19 2022-12-31 21804 ACCESS-SK 2019-06-09 2022-12-31 398836 NP-NETWORKS 2021-03-12 2022-12-25 22773 ASN-CXA-ALL-CCI-22773-RDC 2021-10-24 2022-12-28 397086 LAYER-HOST-HOUSTON 2022-06-16 2022-12-18 400517 2022-10-03 2022-12-07 11976 FIDN 2022-11-16 2022-12-31 12183 TALKIE-COMMUNICATIONS 2022-12-10 2022-12-27 33185 HIVE-DATA-CENTER 2022-12-11 2022-12-25 399296 2022-12-30 2022-12-30 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

FCC Proposes Updated Data Breach Reporting Requirements
by Sean Donelan 06 Jan '23

06 Jan '23

The Federal Communications Commission today launched a proceeding to strengthen the Commission’s rules for notifying customers and federal law enforcement of breaches of customer proprietary network information (CPNI). The Commission will look to better align its rules with recent developments in federal and state data breach laws covering other sectors. https://www.fcc.gov/document/fcc-proposes-updated-data-breach-reporting-req…

1 0

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

06 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 07 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: 918506 Prefixes after maximum aggregation (per Origin AS): 347602 Deaggregation factor: 2.64 Unique aggregates announced (without unneeded subnets): 444924 Total ASes present in the Internet Routing Table: 74024 Prefixes per ASN: 12.41 Origin-only ASes present in the Internet Routing Table: 63539 Origin ASes announcing only one prefix: 26133 Transit ASes present in the Internet Routing Table: 10485 Transit-only ASes present in the Internet Routing Table: 427 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: 987 Number of instances of unregistered ASNs: 997 Number of 32-bit ASNs allocated by the RIRs: 41026 Number of 32-bit ASNs visible in the Routing Table: 33986 Prefixes from 32-bit ASNs in the Routing Table: 165664 Number of bogon 32-bit ASNs visible in the Routing Table: 29 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 505 Number of addresses announced to Internet: 3064057600 Equivalent to 182 /8s, 161 /16s and 207 /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: 312021 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 240104 Total APNIC prefixes after maximum aggregation: 68678 APNIC Deaggregation factor: 3.50 Prefixes being announced from the APNIC address blocks: 234949 Unique aggregates announced from the APNIC address blocks: 97638 APNIC Region origin ASes present in the Internet Routing Table: 13227 APNIC Prefixes per ASN: 17.76 APNIC Region origin ASes announcing only one prefix: 3858 APNIC Region transit ASes present in the Internet Routing Table: 1772 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 25 Number of APNIC region 32-bit ASNs visible in the Routing Table: 8485 Number of APNIC addresses announced to Internet: 773793408 Equivalent to 46 /8s, 31 /16s and 38 /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: 267526 Total ARIN prefixes after maximum aggregation: 121772 ARIN Deaggregation factor: 2.20 Prefixes being announced from the ARIN address blocks: 269111 Unique aggregates announced from the ARIN address blocks: 129742 ARIN Region origin ASes present in the Internet Routing Table: 19061 ARIN Prefixes per ASN: 14.12 ARIN Region origin ASes announcing only one prefix: 6981 ARIN Region transit ASes present in the Internet Routing Table: 1947 Average ARIN Region AS path length visible: 3.7 Max ARIN Region AS path length visible: 34 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4717 Number of ARIN addresses announced to Internet: 1286404864 Equivalent to 76 /8s, 172 /16s and 251 /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: 263977 Total RIPE prefixes after maximum aggregation: 122240 RIPE Deaggregation factor: 2.16 Prefixes being announced from the RIPE address blocks: 260781 Unique aggregates announced from the RIPE address blocks: 156113 RIPE Region origin ASes present in the Internet Routing Table: 28211 RIPE Prefixes per ASN: 9.24 RIPE Region origin ASes announcing only one prefix: 12029 RIPE Region transit ASes present in the Internet Routing Table: 3975 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: 10963 Number of RIPE addresses announced to Internet: 719491968 Equivalent to 42 /8s, 226 /16s and 147 /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: 117339 Total LACNIC prefixes after maximum aggregation: 28468 LACNIC Deaggregation factor: 4.12 Prefixes being announced from the LACNIC address blocks: 116575 Unique aggregates announced from the LACNIC address blocks: 48948 LACNIC Region origin ASes present in the Internet Routing Table: 11002 LACNIC Prefixes per ASN: 10.60 LACNIC Region origin ASes announcing only one prefix: 2670 LACNIC Region transit ASes present in the Internet Routing Table: 2272 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: 8768 Number of LACNIC addresses announced to Internet: 176031232 Equivalent to 10 /8s, 126 /16s and 6 /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: 28573 Total AfriNIC prefixes after maximum aggregation: 5696 AfriNIC Deaggregation factor: 5.02 Prefixes being announced from the AfriNIC address blocks: 36585 Unique aggregates announced from the AfriNIC address blocks: 12072 AfriNIC Region origin ASes present in the Internet Routing Table: 1710 AfriNIC Prefixes per ASN: 21.39 AfriNIC Region origin ASes announcing only one prefix: 595 AfriNIC Region transit ASes present in the Internet Routing Table: 328 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: 1053 Number of AfriNIC addresses announced to Internet: 108043008 Equivalent to 6 /8s, 112 /16s and 155 /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 9269 8884 50 CHINAMOBILE-CN China Mobile Communicati 7545 5941 786 700 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4860 4192 75 ERX-CERNET-BKB China Education and Rese 7552 3630 1331 21 VIETEL-AS-AP Viettel Group, VN 7713 3507 1043 63 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3375 1874 95 VNPT-AS-VN VNPT Corp, VN 9498 2687 499 238 BBIL-AP BHARTI Airtel Ltd., IN 4766 2528 11251 593 KIXS-AS-KR Korea Telecom, KR 24560 2358 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 7729 10631 2940 AMAZON-02, US 11492 4548 301 565 CABLEONE, US 7155 3894 265 33 VIASAT-SP-BACKBONE, US 22773 3688 3062 319 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3520 1320 63 SHAW, CA 16625 3476 1802 2509 AKAMAI-AS, US 749 3024 50575 2291 DNIC-AS-00749, US 7018 2603 24131 1574 ATT-INTERNET4, US 396982 2574 3493 369 GOOGLE-CLOUD-PLATFORM, US 30036 2572 369 359 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 6955 1706 146 UNI2-AS, ES 9121 6127 1692 17 TTNET, TR 39891 4556 268 59 ALJAWWALSTC-AS, SA 20940 4062 3400 183 AKAMAI-ASN1, NL 8551 3910 374 38 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2941 2290 908 ROSTELECOM-AS, RU 47331 2807 411 2115 TTNET, TR 9009 2643 251 1356 M247, RO 34984 2255 358 611 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 10937 3332 596 Uninet S.A. de C.V., MX 10620 3466 507 852 Telmex Colombia S.A., CO 11830 2262 369 64 Instituto Costarricense de Electricidad 13999 2200 361 591 Mega Cable, S.A. de C.V., MX 28573 1346 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 1135 186 467 Techtel LMDS Comunicaciones Interactiva 26615 991 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 1464 393 21 LINKdotNET-AS, EG 36992 1319 1517 275 ETISALAT-MISR, EG 36903 1242 550 99 MT-MPLS, MA 29571 1013 67 43 ORANGE-COTE-IVOIRE, CI 36935 882 520 42 Vodafone-, EG 6713 611 1861 34 IAM-AS, MA 15399 519 53 42 WANANCHI-, KE 37342 494 32 1 MOVITEL, MZ 2018 374 319 72 TENET-1, ZA 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 10937 3332 596 Uninet S.A. de C.V., MX 9808 9269 8884 50 CHINAMOBILE-CN China Mobile Communicati 16509 7729 10631 2940 AMAZON-02, US 12479 6955 1706 146 UNI2-AS, ES 9121 6127 1692 17 TTNET, TR 7545 5941 786 700 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4860 4192 75 ERX-CERNET-BKB China Education and Rese 39891 4556 268 59 ALJAWWALSTC-AS, SA 11492 4548 301 565 CABLEONE, US 20940 4062 3400 183 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 9269 9219 CHINAMOBILE-CN China Mobile Communications Grou 12479 6955 6809 UNI2-AS, ES 9121 6127 6110 TTNET, TR 7545 5941 5241 TPG-INTERNET-AP TPG Telecom Limited, AU 16509 7729 4789 AMAZON-02, US 4538 4860 4785 ERX-CERNET-BKB China Education and Research Net 39891 4556 4497 ALJAWWALSTC-AS, SA 11492 4548 3983 CABLEONE, US 20940 4062 3879 AKAMAI-ASN1, NL 8551 3910 3872 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo Complete listing at https://thyme.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 398083 UNALLOCATED 5.133.124.0/24 399587 UT, US 33123 UNALLOCATED 8.10.69.0/24 11168 SCC, US 16641 UNALLOCATED 8.10.194.0/24 3356 LEVEL3, US 16641 UNALLOCATED 8.10.210.0/24 3356 LEVEL3, US 25674 UNALLOCATED 8.12.76.0/24 3356 LEVEL3, US 16641 UNALLOCATED 8.12.250.0/24 3356 LEVEL3, US 25674 UNALLOCATED 8.14.115.0/24 3356 LEVEL3, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 25674 UNALLOCATED 8.19.146.0/24 3356 LEVEL3, US 53775 UNALLOCATED 8.20.88.0/24 7029 WINDSTREAM, US Complete listing at https://thyme.apnic.net/current/data-badAS Prefixes from the Special Purpose Address Registry (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at https://thyme.apnic.net/current/data-spar Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.131.185.0/24 Origin: 174 COGENT-174, US 23.131.185.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.131.186.0/24 Origin: 174 COGENT-174, US 23.131.186.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.131.187.0/24 Origin: 174 COGENT-174, US 23.131.187.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.136.112.0/24 Origin: 54835 UNASSIGNED 23.136.112.0/24 Transit: 21559 OSNET, PR 23.139.232.0/24 Origin: 211619 MAXKO, HR 23.139.232.0/24 Transit: 42864 GIGANET-HU GigaNet Internet Service Prov 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:1204 /15:2045 /16:13500 /17:8308 /18:13927 /19:25195 /20:44304 /21:52349 /22:110197 /23:98163 /24:547455 /25:813 /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 6002 6955 UNI2-AS, ES 9121 5302 6127 TTNET, TR 8151 4953 10937 Uninet S.A. de C.V., MX 39891 3547 4556 ALJAWWALSTC-AS, SA 11492 3455 4548 CABLEONE, US 8551 3375 3910 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 6327 3328 3520 SHAW, CA 7155 2983 3894 VIASAT-SP-BACKBONE, US 22773 2723 3688 ASN-CXA-ALL-CCI-22773-RDC, US 47331 2428 2807 TTNET, TR Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1637 2:1241 3:168 4:5 5:4104 6:110 7:5 8:1575 9:1 11:172 12:1596 13:368 14:2370 15:284 16:76 17:370 18:412 20:243 21:4 22:188 23:6046 24:2465 25:4 27:2706 29:19 31:2494 32:104 34:8 35:95 36:1839 37:4595 38:4004 39:823 40:144 41:3921 42:1058 43:2317 44:302 45:16490 46:4217 47:381 49:1725 50:1936 51:378 52:1544 54:395 55:798 56:8 57:78 58:1746 59:1157 60:1006 61:2427 62:2632 63:1935 64:5612 65:2324 66:4896 67:3046 68:1335 69:4139 70:1256 71:656 72:2984 74:2592 75:1465 76:597 77:2372 78:3960 79:3159 80:2058 81:1834 82:1479 83:1229 84:1514 85:3749 86:751 87:1925 88:2875 89:3556 90:587 91:7653 92:1984 93:2578 94:3531 95:4849 96:1315 97:344 98:1162 99:738 100:75 101:1061 102:2506 103:30736 104:4598 105:484 106:847 107:2533 108:916 109:4393 110:2047 111:3321 112:2029 113:1555 114:1611 115:2047 116:1895 117:2512 118:2288 119:1894 120:1749 121:1110 122:2584 123:2146 124:1576 125:2335 128:1294 129:1060 130:968 131:2013 132:801 133:405 134:1900 135:297 136:891 137:921 138:2583 139:1515 140:1036 141:1482 142:1419 143:1434 144:1189 145:352 146:1895 147:1543 148:2278 149:1870 150:862 151:1136 152:1850 153:477 154:3883 155:1410 156:1644 157:1294 158:1047 159:2252 160:2570 161:1432 162:3542 163:1488 164:1672 165:1650 166:835 167:1738 168:3880 169:919 170:4568 171:889 172:3495 173:3059 174:1028 175:1149 176:3718 177:4754 178:3551 179:2146 180:2377 181:3387 182:3279 183:1936 184:2350 185:19995 186:4615 187:3920 188:4110 189:3432 190:9042 191:1460 192:10978 193:8848 194:7214 195:5095 196:2982 197:2403 198:5993 199:6086 200:7721 201:5875 202:10636 203:10050 204:4600 205:3503 206:3856 207:3403 208:4102 209:4812 210:4431 211:2497 212:4093 213:3547 214:1103 215:55 216:6579 217:2636 218:1276 219:575 220:2027 221:965 222:842 223:2007 End of report

1 0

hosteurope.de routing loop
by Frank Pedersen 06 Jan '23

06 Jan '23

Hello, Anyone here from hosteurope.de? Seems they have a routing loop !? Tracing to 5.175.2.171: 12 29 ms 29 ms 31 ms rsn2532.rs1.hosteurope.de [62.138.178.82] 13 37 ms 28 ms 34 ms 5.35.224.2 14 31 ms 28 ms 29 ms rsn2532.rs1.hosteurope.de [62.138.178.82] 15 39 ms 30 ms 36 ms 5.35.224.2 16 31 ms 28 ms 28 ms rsn2532.rs1.hosteurope.de [62.138.178.82] 17 33 ms 33 ms 36 ms 5.35.224.2 18 29 ms 33 ms 30 ms rsn2532.rs1.hosteurope.de [62.138.178.82] 19 32 ms 33 ms 31 ms 5.35.224.2 20 27 ms 29 ms 33 ms rsn2532.rs1.hosteurope.de [62.138.178.82] 21 28 ms 38 ms 32 ms 5.35.224.2 22 34 ms 30 ms 29 ms rsn2532.rs1.hosteurope.de [62.138.178.82] 23 32 ms 31 ms 36 ms 5.35.224.2 24 34 ms 33 ms 35 ms rsn2532.rs1.hosteurope.de [62.138.178.82] 25 35 ms 30 ms 29 ms 5.35.224.2 26 29 ms 32 ms 31 ms rsn2532.rs1.hosteurope.de [62.138.178.82] 27 34 ms 31 ms 40 ms 5.35.224.2 28 33 ms 33 ms 29 ms rsn2532.rs1.hosteurope.de [62.138.178.82] 29 34 ms 35 ms 36 ms 5.35.224.2 30 36 ms 30 ms 30 ms rsn2532.rs1.hosteurope.de [62.138.178.82] Tried from various sources. Kind regards, Frank

1 0