- Test - lists.nanog.org

Re: HE.net problem
by Reid Fishler 04 Jul '24

04 Jul '24

After a metric ton of screaming, we did get the issue solved. Thanks everyone, and we WILL be following up with the powers that be. Reid On Thu, Jul 4, 2024, 3:31 PM Reid Fishler <rfishler(a)he.net> wrote: > Network Solutions has decided to put our domain name on Client Hold due to > a single phishing complaint about a web page, which happens to just be a > page of information about another domain from bgp.he.net. Network > Solutions has been contacted, and refuses to handle this issue in ANY > expedited manner. Executives from Hurricane have been calling and emailing > Network Solutions for HOURS trying to have this addressed. If anyone has > an escalation contact at Network Solutions, please email it to me at > redhead(a)lightning.net, or rfishler(a)he.net. Thanks. > > Reid Fishler > Sr Director > Hurricane Electric > > > On Thu, Jul 4, 2024 at 3:23 PM Jay Ashworth <jra(a)baylink.com> wrote: > >> I've been informed that the CEO of HE is on this as of 1512EDT. >> >> I approve of the scale of this response. :-) >> >> Cheers, >> -- jra >> >> >> On July 4, 2024 2:55:34 PM EDT, Jay Ashworth <jra(a)baylink.com> wrote: >> >>> We have a report on outages that he.net has been placed in ICANN client >>> hold, and people's DNS service is falling over on this Independence day. If >>> you work in DNS for HE, you might want to look into this. >>> >>> I have double checked the report, and I am seeing the status as well. >>> >>> Hurricane serves lots of dns, I would classify this as a P1 ticket. >>> >>> Cheers, >>> -- jra >>> >> -- >> Sent from my Android device with K-9 Mail. Please excuse my brevity. >> > > > -- > Reid Fishler > Senior Director > Hurricane Electric > +1-510-580-4178 >

1 0

LACNOG 2024 – Call for Presentations (Last 2 weeks)
by Hernan Moguilevsky 03 Jul '24

03 Jul '24

Hi NANOG, A friedly reminder of the CFP for LACNOG 2024. Thanks. Regards. LACNOG 2024 – Call for Presentations LACNOG, the Latin American and Caribbean Network Operators Group, will hold its LACNOG 2024 conference from 7 to 11 October 2024 together with the LACNIC 42 event. The event is scheduled to take place in hybrid format in the city of Asunción, Paraguay. The LACNOG 2024 Program Committee invites the Internet community to submit their presentation proposals for the event. In line with the spirit of LACNOG, topics should be geared towards Internet development in the region. The following is a non-exhaustive list of some of the topics of interest for the LACNOG 2024 meeting: ●Network operation and professional experiences, success stories ●Internet of Things ●MANRS ●Community networks ●IPv6 integration and deployment ●Experiences involving botnets, malware, spam, viruses, denial of service attacks and exploit techniques ●IP network architecture, sizing, configuration, and administration ●Routing and switching protocols, including unicast, multicast, anycast, SDN, etc. ●End-user applications (e.g. e-mail, HTTP, DNS, NFVs, etc.) ●Value-added services such as VPNs, distributed systems, cloud computing, etc. ●Peering, traffic exchange, IXPs ●Network data security and management, attack mitigation ●Network monitoring, performance, measurements, and telemetry ●Network automation, evolution, and convergence ●Infrastructure and physical transport, including optical and wireless networks ●Legislation, regulations, and Internet governance issues ●Research and education ●Technical aspects related to universal acceptance Presentation formats include: ●Lightning talks: Brief, 10-minute presentations (including an additional 5-minute space for questions). ●Presentations: 20-minute presentations (including an additional 5-minute space for questions). Proposals for the event will be selected following the calendar below: ●Reception of proposals: 12 May to 16 July 2024 ●Proposals will be accepted until: 16 July 2024 at 23:59 UTC-3 (Uruguay time) ●Evaluation by the Program Committee: 24 July to 7 August 2024 ●Announcement of results: 10 August 2024 ●Confirmation by selected presenters: 15 August 2024 ●Publication of the preliminary program: between 15 and 21 August 2024 ●Publication of presenters’ bios and photos on the event website: 21 August 2024 ●Submission of final presentations: 10 August to 11 September 2024 ●Final presentations will be accepted until: 11 September 2024 at 23:9 UTC-3 (Uruguay time) ●Event date: 2 to 6 October 2024 Applicants must submit a summary and a draft of the slides for their proposed presentation, along with a brief biography. These must be submitted using the form available at https://eventos.nog.lat/event/27/ If your work is selected, you authorize LACNOG and LACNIC to publish your name, photograph, biography, and final work in the event program. Speakers presenting their work at the LACNOG 2024 conference will receive a certificate acknowledging their participation. Guidelines for Submitting a Presentation for LACNOG including a description of the criteria that will be considered when evaluating each proposal, presentation format and other details are available at https://lacnog.org/seccion/postulacion-trabajos <https://lacnog.org/seccion/postulacion-trabajos> Communications with the Program Committee will be handled through pc(a)lacnog.org <mailto:pc@lacnog.org>. Thanking you in advance, we look forward to receiving your proposals for LACNOG 2024. The Program Committee

1 0

charging for config changess
by Randy Bush 02 Jul '24

02 Jul '24

has charging for config changes a la https://www.arelion.com/customer-excellence/customer-support/online-technic… become common while i was not looking? admittedly, i have not looked for a long time. randy

9 8

Any representitives from ip2location lurking
by Jim Bonnet 02 Jul '24

02 Jul '24

Hello folks, Are there any folks from ip2location lurking on the list? Could you ping me directly. We have a geofeed issue I'd like to ask about. Thank you. Jim Bonnet Broadcom CloudOPS -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.

2 1

Geolocation IP - www.firstinterstatebank.com
by Jarek Kasjaniuk 01 Jul '24

01 Jul '24

Hello, does anyone have contact to someone from www.firstinterstatebank.com ? Some IP addessess from ASN 31998 can't access their website. We see information like: "we have limited website access for IP addresses outside of the United States and Canada to online banking platforms only." I have sent e-mails to contacts found in ARIN, but no response. Thanks -- Jarek Kasjaniuk

3 3

Re: Looking for DISA/DOD contact
by Mike Tindor 30 Jun '24

30 Jun '24

I guess I could try that. My fear is that it would simply end up being read by the same people you get when you call the DISA helpdesk, and that they would see who it was from, tie it to a closed ticket where they already told me they couldn't help me because I wasn't military or a government contractor. On the other hand, that would at least give me a chance to send all of the truly relevant information that I was not allowed to have added to the ticket when they originally opened it -- all of the network related information, traceroutes, etc. I've been given quite a few suggestions, including this one from you. I'll need to start going through them one by one tomorrow. Thanks Mike On Sun, Jun 30, 2024 at 8:56 PM Brad Knowles <brad(a)his.com> wrote: > Years ago, I was the DISA.MIL Technical POC. And I was a government > civilian, not in the military. I was also the postmaster for DISA.mil. > > I don’t know how they do things these days, but back when I worked there, > a real human being monitored the postmaster(a)disa.mil mailbox, and if they > weren’t the correct party to handle the situation, then they would find out > who the correct party was and forward the e-mail to them. > > Sent from my iPhone > > On Jun 30, 2024, at 7:49 PM, Mike Tindor <mtindor(a)gmail.com> wrote: > > > Thank you. That is helpful. > > Mike > > On Sun, Jun 30, 2024 at 12:31 AM <nanog.org(a)junk-mail.us> wrote: > >> The people at DISA you were dealing w/ aren't a Tier I service desk, >> they're the service desk that lower service desks open tickets w/. >> >> Think of DISA as a Tier I ISP and the normal .mil user as a residential >> user. >> >> See if one of your customers can put you in contact w/ their IT people >> (Usually a S6/G6/N6/A6/J6). 6 means IT or communications, the letter >> prefix is determined by the Military branch and level of the unit (A is Air >> Force, N is Navy, J is Joint, G is Army General Staff, and S is Army Staff). >> >> On Sat, Jun 29, 2024 at 6:25 PM Mike Tindor - mtindor at gmail.com < >> mtindor_at_gmail_com_rgphbc(a)simplelogin.co> wrote: >> >>> Thanks. That makes a little more sense to me. I know the questions >>> DISA asked me when I called them, and I couldn't imagine just having the >>> MIL-side email correspondent open a ticket directly with DISA. They would >>> likely be more overwhelmed than I was. I'll talk to a couple of my >>> customers who do biz with DOD on Monday and will ask them to reach out to >>> their MIL contacts and request that the MIL contacts open a ticket with >>> their IT. >>> >>> Since this has been going on now, some of my customers have switched >>> temporarily to using Gmail/Yahoo just to stay in touch with their MIL >>> contacts. So I know they can get the message through. >>> >>> Mike >>> >>> On Sat, Jun 29, 2024 at 12:55 PM Mike Tindor <mtindor(a)gmail.com> wrote: >>> >>>> Thanks again,Scott. I'll be patient! >>>> >>>> Mike Tindor >>>> >>>> >>>> On Sat, Jun 29, 2024 at 12:18 PM Scott Q. <qmail(a)top-consulting.net> >>>> wrote: >>>> >>>>> All that sounds very familiar, I'm 100% sure it's the same issue. >>>>> >>>>> As I said, there are DISA folks here, they might reach out and give >>>>> you further steps. They did in my case, you just have to be more patient / >>>>> on the ball than I was... >>>>> >>>>> Good luck! >>>>> >>>>> >>>>> On Saturday, 29/06/2024 at 11:44 Mike Tindor wrote: >>>>> >>>>> Scott, >>>>> >>>>> Thanks for responding. Unfortunately, I think my situation is a >>>>> little more dire, or at least involved. I probably should have said this >>>>> before, but I had done TCP 25 outbound testing from our /23 to various .MIL >>>>> MX's that I know were responding and could not establish a connection / get >>>>> an SMTP banner. I could then go to Azure, or Digital Ocean, or somewhere >>>>> else that I have a box and am able to make the outbound connection to the >>>>> same MIL MXs that wouldn't respond to me from our /23. >>>>> >>>>> So it isn't a simple case of DNS not resolving, although we certainly >>>>> did notice that issue. Fortunately, we do have nameservers in place that >>>>> are external to our /23 and which are able to actually do the resolving. >>>>> But your comment does remind that this definitely is not just a TCP 25 >>>>> issue, as the MIL DNS servers are not responding to queries from our /23 >>>>> hosts. >>>>> >>>>> The situation is difficult for multiple reasons: >>>>> >>>>> 1. inabiity to engage somebody from the other end - DISA >>>>> 2. Unwillingness on my part to stab at a hornets nest and poke around >>>>> trying to verify connections (other than TCP 25 to known MIL MXs) in >>>>> DOD-land. >>>>> 3. Not knowing exactly where to go from here >>>>> >>>>> The latest/last thing DISA told me was that I would have to get one of >>>>> the people with MIL email addresses who can't email our customers to >>>>> actually open a ticket with DISA. And that is fraught with problems since >>>>> even if a MIL email user did open a ticket, they would not have any >>>>> information about our network to convey to the Helpdesk -- and would have >>>>> no way of answering questions that the Helpdesk asked, and also wouldn't be >>>>> able to do any troubleshooting. >>>>> >>>>> I did realize a few days ago we had no ROA for the specific /23, and >>>>> so I created one at ARIN. And we had no specific route object published >>>>> for our /23, and I got one added. Been trying to clean up some old (and >>>>> invalid) stuff that is in RADB from our larger /19, since we don't even own >>>>> all the space in the /19 anymore and are only actively using a /23 from >>>>> what we have left. Hoping to get that taken care of Monday. >>>>> >>>>> Everything has worked fine for 26 years, until Jun 1. But things >>>>> change, and I'm obviously behind the times given that I didn't have proper >>>>> ROA and route object in place. >>>>> >>>>> Mike Tindor >>>>> >>>>> On Sat, Jun 29, 2024 at 11:26 AM Scott Q. <qmail(a)top-consulting.net> >>>>> wrote: >>>>> >>>>>> There are DISA folks lurking here. >>>>>> >>>>>> I had a similar issue where our block was labeled as residential by >>>>>> their new firewall, and DISA front-desk isn't yet trained on this mechanism >>>>>> so they can't help. >>>>>> >>>>>> I escalated the issue to a lot of groups but in the end I gave up, >>>>>> too much bureaucracy. The issue is simply DNS - their DNS servers don't let >>>>>> you resolve. So I simply set 8.8.8.8 as the resolver for *.mil and it temp >>>>>> (permanently) fixed the problem. >>>>>> >>>>>> Scott >>>>>> >>>>>> >>>>>> On Saturday, 29/06/2024 at 09:16 Mike Tindor wrote: >>>>>> >>>>>> Hi folks, >>>>>> >>>>>> I'm looking for a DISA/DOD contact who feels that my issue has >>>>>> merit. I've tried the DISA Helpdesk and have been told since I'm a >>>>>> commercial entity with no affiliation with the DOD, they can't help me. >>>>>> >>>>>> The issue at hand is that our /23 netblock has lost communication (at >>>>>> least email TCP 25) with AS345 / AS721 as of May 31, 2024 and I cannot >>>>>> figure out why. We are in a Flexential datacenter in Richmond VA and use >>>>>> Flexential for transport. We cannot send emails to .MIL or receive emails >>>>>> from .MIL. It is not that they are being rejected on either end. The >>>>>> deliveries are timing out and being returned to sender, from both sides. >>>>>> >>>>>> I don't know if DISA/DOD has a block on our ASN and-or /23, or if >>>>>> there is a routing issue somewhere between us and AS345 / AS721. I had >>>>>> asked the Flexential folks to look into it from their side, and they >>>>>> indicated that historic data does indeed show that there TCP 25 >>>>>> communications to and fro between us and AS345 prior to June 1, but nothing >>>>>> from June 1 onward. And all they could say was that they (Flex) were not >>>>>> in any way blocking. And I'd agree with that. >>>>>> >>>>>> As you can imagine, my customers are not happy with not being able to >>>>>> communicate with their family / friends via email in the MIL domains, and >>>>>> our customers who are vendors / contractors cannot do business with the >>>>>> military effectively if they cannot send/receive emails. >>>>>> >>>>>> us --> Flexential --> GTT --> Level3 --> Qwest --> ? --> AS345 / >>>>>> AS721 >>>>>> >>>>>> Any idea where one would go next? Is it likely that any of those >>>>>> entities further upstream like GTT / Level3 / Qwest would even assist since >>>>>> we are not their customer? >>>>>> >>>>>> Thanks for your time! >>>>>> >>>>>> Mike Tindor >>>>>> >>>>>>

1 0

Looking for DISA/DOD contact
by Mike Tindor 30 Jun '24

30 Jun '24

Hi folks, I'm looking for a DISA/DOD contact who feels that my issue has merit. I've tried the DISA Helpdesk and have been told since I'm a commercial entity with no affiliation with the DOD, they can't help me. The issue at hand is that our /23 netblock has lost communication (at least email TCP 25) with AS345 / AS721 as of May 31, 2024 and I cannot figure out why. We are in a Flexential datacenter in Richmond VA and use Flexential for transport. We cannot send emails to .MIL or receive emails from .MIL. It is not that they are being rejected on either end. The deliveries are timing out and being returned to sender, from both sides. I don't know if DISA/DOD has a block on our ASN and-or /23, or if there is a routing issue somewhere between us and AS345 / AS721. I had asked the Flexential folks to look into it from their side, and they indicated that historic data does indeed show that there TCP 25 communications to and fro between us and AS345 prior to June 1, but nothing from June 1 onward. And all they could say was that they (Flex) were not in any way blocking. And I'd agree with that. As you can imagine, my customers are not happy with not being able to communicate with their family / friends via email in the MIL domains, and our customers who are vendors / contractors cannot do business with the military effectively if they cannot send/receive emails. us --> Flexential --> GTT --> Level3 --> Qwest --> ? --> AS345 / AS721 Any idea where one would go next? Is it likely that any of those entities further upstream like GTT / Level3 / Qwest would even assist since we are not their customer? Thanks for your time! Mike Tindor

3 8

Azure Looking Glass
by John Alcock 28 Jun '24

28 Jun '24

I have gotten pretty close to figuring out my issue with the Azure Cloud. When I advertise my routes through one specific upstream provider, I have an issue. If I pull my routes from them, all works well. I believe this is some type of MTU issue. Could be filtering, but I doubt it. Is there an Azure Looking glass that I can use to originate pings and traceroutes? My googlefu is weak and I haven't found it yet. With that information, I think I can help my upstream provider know where the problem lies. John Acock AS395437

2 2

Verizon (uu.net) DNS managers out there?
by Joel M Snyder 28 Jun '24

28 Jun '24

If there's anyone out there who is responsible for the UU.NET nameservers (authxx.ns.uu.net) can you please contact me off-list? I have a customer who is trying to move their DNS off of UU.NET and of course everyone they used to know as a technical contact is no longer available. The NIC side is done; we just need to get those nameservers to stop doing zone transfers and stop thinking that they are authoritative for the zone. Thanks, jms -- Joel M Snyder, 1404 East Lind Road, Tucson, AZ, 85719 Senior Partner, Opus One Phone: +1 520 324 0494 jms(a)Opus1.COM http://www.opus1.com/jms

1 0

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 28 Jun '24

28 Jun '24

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 Jun, 2024 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: 954419 Prefixes after maximum aggregation (per Origin AS): 363407 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 464995 Total ASes present in the Internet Routing Table: 75907 Prefixes per ASN: 12.57 Origin-only ASes present in the Internet Routing Table: 65039 Origin ASes announcing only one prefix: 26699 Transit ASes present in the Internet Routing Table: 10868 Transit-only ASes present in the Internet Routing Table: 527 Average AS path length visible in the Internet Routing Table: 4.4 Max AS path length visible: 60 Max AS path prepend of ASN ( 53153) 57 Prefixes from unregistered ASNs in the Routing Table: 998 Number of instances of unregistered ASNs: 1000 Number of 32-bit ASNs allocated by the RIRs: 44897 Number of 32-bit ASNs visible in the Routing Table: 36638 Prefixes from 32-bit ASNs in the Routing Table: 188462 Number of bogon 32-bit ASNs visible in the Routing Table: 14 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 555 Number of addresses announced to Internet: 3025151616 Equivalent to 180 /8s, 80 /16s and 38 /24s Percentage of available address space announced: 81.7 Percentage of allocated address space announced: 81.7 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: 312557 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 255374 Total APNIC prefixes after maximum aggregation: 74242 APNIC Deaggregation factor: 3.44 Prefixes being announced from the APNIC address blocks: 247350 Unique aggregates announced from the APNIC address blocks: 101104 APNIC Region origin ASes present in the Internet Routing Table: 14220 APNIC Prefixes per ASN: 17.39 APNIC Region origin ASes announcing only one prefix: 4328 APNIC Region transit ASes present in the Internet Routing Table: 1906 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 55 Number of APNIC region 32-bit ASNs visible in the Routing Table: 9628 Number of APNIC addresses announced to Internet: 761694592 Equivalent to 45 /8s, 102 /16s and 137 /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-153913 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: 277700 Total ARIN prefixes after maximum aggregation: 125420 ARIN Deaggregation factor: 2.21 Prefixes being announced from the ARIN address blocks: 282299 Unique aggregates announced from the ARIN address blocks: 134685 ARIN Region origin ASes present in the Internet Routing Table: 19137 ARIN Prefixes per ASN: 14.75 ARIN Region origin ASes announcing only one prefix: 6948 ARIN Region transit ASes present in the Internet Routing Table: 1989 Average ARIN Region AS path length visible: 3.7 Max ARIN Region AS path length visible: 27 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4933 Number of ARIN addresses announced to Internet: 1266881792 Equivalent to 75 /8s, 131 /16s and 21 /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, 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: 266279 Total RIPE prefixes after maximum aggregation: 127592 RIPE Deaggregation factor: 2.09 Prefixes being announced from the RIPE address blocks: 261045 Unique aggregates announced from the RIPE address blocks: 165134 RIPE Region origin ASes present in the Internet Routing Table: 28665 RIPE Prefixes per ASN: 9.11 RIPE Region origin ASes announcing only one prefix: 12123 RIPE Region transit ASes present in the Internet Routing Table: 3986 Average RIPE Region AS path length visible: 4.5 Max RIPE Region AS path length visible: 41 Number of RIPE region 32-bit ASNs visible in the Routing Table: 11869 Number of RIPE addresses announced to Internet: 713697024 Equivalent to 42 /8s, 138 /16s and 39 /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, 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: 122256 Total LACNIC prefixes after maximum aggregation: 29258 LACNIC Deaggregation factor: 4.18 Prefixes being announced from the LACNIC address blocks: 120330 Unique aggregates announced from the LACNIC address blocks: 50028 LACNIC Region origin ASes present in the Internet Routing Table: 11112 LACNIC Prefixes per ASN: 10.83 LACNIC Region origin ASes announcing only one prefix: 2640 LACNIC Region transit ASes present in the Internet Routing Table: 2425 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 60 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8993 Number of LACNIC addresses announced to Internet: 176774144 Equivalent to 10 /8s, 137 /16s and 92 /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: 31812 Total AfriNIC prefixes after maximum aggregation: 6233 AfriNIC Deaggregation factor: 5.10 Prefixes being announced from the AfriNIC address blocks: 42840 Unique aggregates announced from the AfriNIC address blocks: 13592 AfriNIC Region origin ASes present in the Internet Routing Table: 1852 AfriNIC Prefixes per ASN: 23.13 AfriNIC Region origin ASes announcing only one prefix: 660 AfriNIC Region transit ASes present in the Internet Routing Table: 361 Average AfriNIC Region AS path length visible: 5.1 Max AfriNIC Region AS path length visible: 28 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1215 Number of AfriNIC addresses announced to Internet: 105737728 Equivalent to 6 /8s, 77 /16s and 110 /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 9875 8746 77 CHINAMOBILE-CN China Mobile Communicati 7545 5645 777 672 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4932 4192 74 ERX-CERNET-BKB China Education and Rese 18403 4207 347 23 FPT-AS-AP FPT Telecom Company, VN 7552 3943 1331 21 VIETEL-AS-AP Viettel Group, VN 9498 3783 511 265 BBIL-AP BHARTI Airtel Ltd., IN 7713 3621 1036 71 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3265 1841 105 VNPT-AS-VN VNPT Corp, VN 24560 2824 862 401 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 4766 2285 11522 578 KIXS-AS-KR Korea Telecom, KR 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 10104 11533 3638 AMAZON-02, US 11492 4641 308 547 CABLEONE, US 7155 4166 287 88 VIASAT-SP-BACKBONE, US 174 3705 8790 898 COGENT-174, US 6327 3594 1320 79 SHAW, CA 22773 3445 3037 212 ASN-CXA-ALL-CCI-22773-RDC, US 749 3249 54901 2501 DNIC-AS-00749, US 16625 3159 1339 2229 AKAMAI-AS, US 7018 2898 23669 1825 ATT-INTERNET4, US 396982 2767 3611 414 GOOGLE-CLOUD-PLATFORM, 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 7714 1708 145 UNI2-AS, ES 39891 4758 286 60 ALJAWWALSTC-AS, SA 20940 3834 3396 134 AKAMAI-ASN1, NL 9009 3595 306 1819 M247, RO 12389 2980 2304 897 ROSTELECOM-AS, RU 34984 2347 361 579 TELLCOM-AS, TR 8551 1778 368 35 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 212238 1710 123 1242 CDNEXT, GB 13188 1607 100 26 TRIOLAN, UA 8452 1567 1852 14 TE-AS TE-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 11857 3310 502 UNINET, MX 10620 3518 492 938 Telmex Colombia S.A., CO 13999 2553 357 677 Mega Cable, S.A. de C.V., MX 11830 2003 369 64 Instituto Costarricense de Electricidad 28573 1343 2311 258 Claro NXT Telecomunicacoes Ltda, BR 3816 1315 775 191 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6503 1128 314 478 Axtel, S.A.B. de C.V., MX 6147 1093 369 22 Telefonica del Peru S.A.A., PE 26615 1081 2503 53 TIM SA, BR 22884 1056 97 363 TOTAL PLAY TELECOMUNICACIONES SA DE CV, Complete listing at https://thyme.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1622 389 16 LINKdotNET-AS, EG 24835 1570 593 29 RAYA-AS, EG 36992 1380 1520 283 ETISALAT-MISR, EG 36903 1249 554 96 MT-MPLS, MA 29571 1235 78 74 ORANGE-COTE-IVOIRE, CI 36935 940 521 43 Vodafone-, EG 6713 555 1861 35 IAM-AS, MA 36914 531 82 3 KENET-AS, KE 15399 518 56 56 WANANCHI-, KE 37342 478 32 1 MOVITEL, MZ 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 11857 3310 502 UNINET, MX 16509 10104 11533 3638 AMAZON-02, US 9808 9875 8746 77 CHINAMOBILE-CN China Mobile Communicati 12479 7714 1708 145 UNI2-AS, ES 7545 5645 777 672 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4932 4192 74 ERX-CERNET-BKB China Education and Rese 39891 4758 286 60 ALJAWWALSTC-AS, SA 11492 4641 308 547 CABLEONE, US 18403 4207 347 23 FPT-AS-AP FPT Telecom Company, VN 7155 4166 287 88 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 9808 9875 9798 CHINAMOBILE-CN China Mobile Communications Grou 12479 7714 7569 UNI2-AS, ES 16509 10104 6466 AMAZON-02, US 7545 5645 4973 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4932 4858 ERX-CERNET-BKB China Education and Research Net 39891 4758 4698 ALJAWWALSTC-AS, SA 18403 4207 4184 FPT-AS-AP FPT Telecom Company, VN 11492 4641 4094 CABLEONE, US 7155 4166 4078 VIASAT-SP-BACKBONE, US 7552 3943 3922 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 33123 UNALLOCATED 8.10.69.0/24 174 COGENT-174, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 40493 UNALLOCATED 8.17.26.0/24 3356 LEVEL3, US 46639 UNALLOCATED 8.17.66.0/24 701 UUNET, US 53775 UNALLOCATED 8.20.88.0/24 7029 WINDSTREAM, US 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, 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.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.170.224.0/24 Origin: 30168 RESERVED, ZZ 23.170.224.0/24 Transit: 397095 SETSONLLC, US 23.189.192.0/24 Origin: 27593 RESERVED, ZZ 23.189.192.0/24 Transit: 174 COGENT-174, 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:14 /10:37 /11:93 /12:296 /13:573 /14:1171 /15:2064 /16:13268 /17:8269 /18:13767 /19:24728 /20:44343 /21:51904 /22:111747 /23:99963 /24:581472 /25:694 /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 6802 7714 UNI2-AS, ES 8151 5939 11857 UNINET, MX 11492 3548 4641 CABLEONE, US 39891 3440 4758 ALJAWWALSTC-AS, SA 6327 3390 3594 SHAW, CA 7155 3111 4166 VIASAT-SP-BACKBONE, US 22773 2558 3445 ASN-CXA-ALL-CCI-22773-RDC, US 30036 2148 2488 MEDIACOM-ENTERPRISE-BUSINESS, US 10620 2147 3518 Telmex Colombia S.A., CO 16509 2123 10104 AMAZON-02, US Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:2324 2:1539 3:364 4:6 5:4358 6:164 7:6 8:1518 9:1 11:172 12:1446 13:360 14:2400 15:318 16:219 17:369 18:770 20:387 21:4 22:188 23:6893 24:2716 25:2 27:2560 29:19 31:2583 32:48 34:63 35:135 36:2337 37:4478 38:7964 39:899 40:143 41:4079 42:2001 43:2370 44:323 45:17278 46:4498 47:303 49:1976 50:1882 51:582 52:1583 54:313 55:910 56:8 57:213 58:2166 59:1253 60:1039 61:2597 62:2749 63:1875 64:5481 65:2309 66:4617 67:2993 68:1299 69:4075 70:1174 71:577 72:2877 74:2593 75:1550 76:624 77:2500 78:1862 79:1782 80:2188 81:2020 82:1643 83:1355 84:1686 85:3179 86:911 87:2302 88:1228 89:4163 90:684 91:8150 92:2337 93:2702 94:3730 95:4196 96:1286 97:317 98:1022 99:738 100:73 101:1175 102:3522 103:32352 104:4822 105:701 106:1002 107:2503 108:1153 109:4048 110:2129 111:3268 112:2047 113:1826 114:1824 115:2087 116:1899 117:2657 118:2799 119:1967 120:1805 121:1364 122:2697 123:2242 124:1627 125:2874 126:32 128:1434 129:933 130:1176 131:1861 132:818 133:413 134:1735 135:323 136:1123 137:1081 138:2873 139:1514 140:1408 141:1375 142:1667 143:1554 144:999 145:372 146:2095 147:1984 148:2536 149:2753 150:1033 151:1367 152:2228 153:520 154:6989 155:1490 156:2292 157:1872 158:1164 159:2314 160:2759 161:1693 162:3539 163:1698 164:1663 165:2145 166:1278 167:1813 168:4059 169:797 170:4951 171:1046 172:3870 173:3049 174:893 175:1230 176:3462 177:4811 178:3680 179:2240 180:2410 181:3782 182:3346 183:1988 184:2257 185:20883 186:5028 187:4415 188:4062 189:4203 190:9455 191:1490 192:11044 193:9159 194:7509 195:5314 196:3186 197:2713 198:6040 199:7952 200:8132 201:6314 202:10454 203:10207 204:4577 205:3689 206:4479 207:3607 208:4155 209:5049 210:4647 211:2623 212:4356 213:3566 214:1057 215:49 216:6750 217:3048 218:1361 219:585 220:2024 221:1038 222:853 223:2248 End of report

1 0