- Test - lists.nanog.org

IPv6 filtering at network edge?
by Pete Ashdown 17 Mar '21

17 Mar '21

I'm tightening up some network-edge filters, and in the process of testing filtering with IPv6, I found that there is a lot of ICMP link-local (fe80::) to ff02:: activity at an IX. Is any of this necessary? I am wary of over-filtering that cuts down functionality and doesn't increase security. What of the IANA-reserved IPv6 addresses can be safely blocked on ingress/egress at the network edge?

4 3

SFI/SBI/Transit - Dumping
by Douglas Fischer 16 Mar '21

16 Mar '21

Hello all! I'm going a bit deeper into the study of Peering Relationships... And one of the possibilities that I'm trying to understand better on the Peering Relationships on the Internet been considered dumping(economy). The matter here is more on the economic and commercial aspects than on the technical side. On the scope of Internet Peering Interconnections(Transit, Settlement Free, Settlement Based.): - There are any public papers, or even judicial processes, about situations that the possibility of Dumping(economic) was supposed? Independently if de dumping argument was accepted or not. - Does any colleague could remember some memorable case about that? - How does it affect the Big-Traffic-Guys (OTTs, Hosting/Colo/Cloud Datacenters, CDNs) and their routing policy on PNI/MPLA, SFI/SBI? -- Douglas Fernando Fischer Engº de Controle e Automação

7 9

ARIN-NONAUTH IRR final retirement set for 31 March 2022 (was: ARIN-NONAUTH data ARIN-NONAUTH dataFwd: [ARIN-consult] ACSP Consultation 2021.1: Future of ARIN’s Unauthenticated IRR is now Closed)
by John Curran 16 Mar '21

16 Mar '21

NANOGers - FYI - Outcome of the community consultation on the Future of ARIN’s Unauthenticated IRR. /John John Curran President and CEO American Registry for Internet Numbers Begin forwarded message: From: ARIN <info(a)arin.net<mailto:info@arin.net>> Subject: [ARIN-consult] ACSP Consultation 2021.1: Future of ARIN’s Unauthenticated IRR is now Closed Date: 15 March 2021 at 4:27:04 PM EDT To: <arin-consult(a)arin.net<mailto:arin-consult@arin.net>> I would like to thank everyone who provided valuable feedback during this consultation on the future of ARIN’s unauthenticated IRR. Input provided by the community is a vital part of our planning processes at ARIN, and after reviewing responses to the consultation, we are making a few significant adjustments in our path forward. One concern raised during the consultation was that six months was not enough time for organizations that currently depend on data in ARIN’s unauthenticated IRR to make changes to their systems. As a result, we will be extending the availability of ARIN’s non-authenticated IRR for an additional six months with final retirement set for 31 March 2022. The second major suggestion was that ARIN conduct proactive engagement to notifying customers who currently use our unauthenticated IRR. We have already initiated this outreach, and for the next twelve months, we will continue this direct outreach to customers who have records in ARIN’s non-authenticated IRR to inform them of their options and provide necessary assistance. We will also provide regular reminders and updates to our community and organizations making use of the outdated and non-authenticated IRR data stream so they can be ready for when we cease publishing the ARIN-NONAUTH data stream. These reminders leading up to the retirement of ARIN’s non-authenticated IRR will include statistics on the number of records remaining in that system and related routing coverage. Thank you again to those who provided valuable feedback on this consultation. Regards, John Curran President and CEO American Registry for Internet Numbers _______________________________________________ ARIN-Consult You are receiving this message because you are subscribed to the ARIN Consult Mailing List (ARIN-consult(a)arin.net<mailto:ARIN-consult@arin.net>). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-consult Please contact the ARIN Member Services Help Desk at info(a)arin.net<mailto:info@arin.net> if you experience any issues.

3 4

Starlink terminal data acquisition for network engineers
by Eric Kuhnke 16 Mar '21

16 Mar '21

I thought about posting this to only NANOG, but since a great concentration of beta testers of a technical/network engineering inclination are located in the Pacific NW, decided to also include the SIX chat list. You may have seen the Starlink android or ios consumer-friendly app, which displays network traffic, uptime/downtime, and other link stats. I believe this to be polled directly from the antenna unit itself over grpc. The beta antennas are always 192.168.100.1. If you are using your own router with the starlink beta system, in addition to its WAN interface being an ordinary DHCP client in cgnat IP space, you'll need to manually give it an address in that /24 and set up routing to reach the .1 IP as needed. reference: https://github.com/sparky8512/starlink-grpc-tools reference: https://github.com/fullstorydev/grpcui you'll need a fairly normal Linux or BSD box with: git go python3 pip use pip to install grpcio and grpcio-tools install grpcurl: https://github.com/fullstorydev/grpcurl do a git clone of the starlink-grpc-tools url above, also take a look at its readme info get the dish's protoset file and write it to new file dish.protoset , this is an index of all data that can be polled cd /home/eric/starlink-grpc-tools /home/eric/go/bin/grpcurl -plaintext \ -protoset-out dish.protoset \ 192.168.100.1:9200 \ describe SpaceX.API.Device.Device /home/eric/go/bin/grpcurl \ -plaintext \ -d {\"get_history\":{}} \ 192.168.100.1:9200 \ SpaceX.API.Device.Device/Handle | python parseJsonHistory.py output of the above looks like this: 2021-02-06T08:15:56,3600,19.92034332,14,2,0.3125,0,0,0.0,0 full CSV header for the above: datetimestamp_utc,samples,total_ping_drop,count_full_ping_drop,count_obstructed,total_obstructed_ping_drop,count_full_obstructed_ping_drop,count_unscheduled,total_unscheduled_ping_drop,count_full_unscheduled_ping_drop since we are able to acquire the above in a comma-delimited csv format, it's fairly easy to write a script storing the integers from any one of those particular columns into a mariadb db, sqlite, influxdb, or whatever. the following will output about 3.8MB of text for the full history (I believe this to be the full copy of the ring buffer stored in RAM for the terminal's statistics) , pipe it into a text file if you want to manually look at it. /home/eric/go/bin/grpcurl -plaintext -d {\"get_history\":{}} 192.168.100.1:9200 SpaceX.API.Device.Device/Handle same as the above but human readable output /home/eric/go/bin/grpcurl \ -plaintext \ -d {\"get_history\":{}} \ 192.168.100.1:9200 \ SpaceX.API.Device.Device/Handle | python parseJsonHistory.py -v current counter: 299673 All samples: 43200 Valid samples: 43200 Parsed samples: 3600 Total ping drop: 20.03700998 Count of drop == 1: 14 Obstructed: 2 Obstructed ping drop: 0.3125 Obstructed drop == 1: 0 Unscheduled: 0 Unscheduled ping drop: 0.0 Unscheduled drop == 1: 0 see the get_history_notes.txt file for more info SOME EXAMPLE QUERIES these should match with what the json query is in the grpc GUI # get status /home/eric/go/bin/grpcurl \ -plaintext \ -d {\"getStatus\":{}} \ 192.168.100.1:9200 \ SpaceX.API.Device.Device/Handle # get device info /home/eric/go/bin/grpcurl \ -plaintext \ -d {\"getDeviceInfo\":{}} \ 192.168.100.1:9200 \ SpaceX.API.Device.Device/Handle # get history, this outputs a huge amount of data /home/eric/go/bin/grpcurl \ -plaintext \ -d {\"getHistory\":{}} \ 192.168.100.1:9200 \ SpaceX.API.Device.Device/Handle The following is copied/pasted from my notes file on things we can acquire, and then use a tiny shell script with awk, sed, regex, whatever as needed to trim out just the numbers, and put them somewhere else for polling by snmp extend /home/eric/go/bin/grpcurl \ -plaintext \ -d {\"getStatus\":{}} \ 192.168.100.1:9200 \ SpaceX.API.Device.Device/Handle notes on what's what: figures we care about to parse out and turn into just the integers snr can never be higher than 9 fractionobstructed appears to be the percentage of the time that the view is obstructed, as long as the view remains unobstructed, this number appears to slowly decrement over time validS is valid seconds? i think the S is almost likely always Seconds of time "uptimeS": "304439" "snr": 9, "fractionObstructed": 0.0013524292, "validS": 61815.74, "last24hObstructedS": 53 "downlinkThroughputBps": 47915.73, "uplinkThroughputBps": 34980.496, "popPingLatencyMs": 29.266666 example of running the command above twice, the second time a few minutes after the first, to see that fractionObstructed does decrement itself over time first run: 0.0013524292 second run: 0.0013467998

12 12

Letters of Authorization still aren't worth the paper they aren't printed
by Sean Donelan 15 Mar '21

15 Mar '21

Its amazing the telecommunications industry still uses or relies on "Letter of Authorization". Its less secure than faxing a piece of paper on "letterhead." I've said this before, check the archives. https://www.vice.com/en/article/y3g8wb/hacker-got-my-texts-16-dollars-sakar… While adding a number, Sakari provides the Letter of Authorization for the user to sign. Sakari's LOA says that the user should not conduct any unlawful, harassing, or inappropriate behaviour with the text messaging service and phone number. But as Lucky225 showed, a user can just sign up with someone else's number and receive their text messages instead.

2 1

OVH datacenter SBG2 in Strasbourg on fire 🔥
by Fredy Kuenzler 13 Mar '21

13 Mar '21

Very sad day for our colleagues at OVH AS16276 as they lost their datacenter SBG-2 in Strasbourg/France completly („everything is destroyed“) in a fire 🔥 and the neighboring SBG1/SBG3/SBG4 at least temporary. https://www.dna.fr/amp/faits-divers-justice/2021/03/10/strasbourg-important… -- Fredy Künzler Init7 (Switzerland) Ltd. Technoparkstrasse 5 CH-8406 Winterthur https://www.init7.net/

31 49

Seattle/LA 100 Gig Wave
by Rod Beck 12 Mar '21

12 Mar '21

A point: Westin House, Seattle. Z point: 1 Wilshire, LA. Routing: Seattle/Boise/Ogden/Salt Lake City/LA. Term: 3 years. Need help on this circuit. Contact me off-list. Regards, Roderick. Roderick Beck Global Network Capacity Procurement United Cable Company www.unitedcablecompany.com<http://www.unitedcablecompany.com> https://unitedcablecompany.com/video/ New York City & Budapest rod.beck(a)unitedcablecompany.com Budapest: 36-70-605-5144 NJ: 908-452-8183 [1467221477350_image005.png]

1 0

Weekly Routing Table Report
by cscora＠apnic.net 12 Mar '21

12 Mar '21

This is an automated weekly mailing describing the state of the Internet 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 http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 13 Mar, 2021 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 849542 Prefixes after maximum aggregation (per Origin AS): 322940 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 405118 Total ASes present in the Internet Routing Table: 70782 Prefixes per ASN: 12.00 Origin-only ASes present in the Internet Routing Table: 60922 Origin ASes announcing only one prefix: 25123 Transit ASes present in the Internet Routing Table: 9860 Transit-only ASes present in the Internet Routing Table: 296 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 47 Max AS path prepend of ASN ( 17747) 41 Prefixes from unregistered ASNs in the Routing Table: 996 Number of instances of unregistered ASNs: 1000 Number of 32-bit ASNs allocated by the RIRs: 35352 Number of 32-bit ASNs visible in the Routing Table: 29397 Prefixes from 32-bit ASNs in the Routing Table: 136778 Number of bogon 32-bit ASNs visible in the Routing Table: 27 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 538 Number of addresses announced to Internet: 2916667008 Equivalent to 173 /8s, 216 /16s and 206 /24s Percentage of available address space announced: 78.8 Percentage of allocated address space announced: 78.8 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.5 Total number of prefixes smaller than registry allocations: 289248 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 223226 Total APNIC prefixes after maximum aggregation: 65172 APNIC Deaggregation factor: 3.43 Prefixes being announced from the APNIC address blocks: 219346 Unique aggregates announced from the APNIC address blocks: 89061 APNIC Region origin ASes present in the Internet Routing Table: 11360 APNIC Prefixes per ASN: 19.31 APNIC Region origin ASes announcing only one prefix: 3234 APNIC Region transit ASes present in the Internet Routing Table: 1602 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 47 Number of APNIC region 32-bit ASNs visible in the Routing Table: 6510 Number of APNIC addresses announced to Internet: 770758400 Equivalent to 45 /8s, 240 /16s and 215 /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-143673 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: 244378 Total ARIN prefixes after maximum aggregation: 112352 ARIN Deaggregation factor: 2.18 Prefixes being announced from the ARIN address blocks: 245021 Unique aggregates announced from the ARIN address blocks: 116945 ARIN Region origin ASes present in the Internet Routing Table: 18742 ARIN Prefixes per ASN: 13.07 ARIN Region origin ASes announcing only one prefix: 6804 ARIN Region transit ASes present in the Internet Routing Table: 1920 Average ARIN Region AS path length visible: 3.9 Max ARIN Region AS path length visible: 24 Number of ARIN region 32-bit ASNs visible in the Routing Table: 3758 Number of ARIN addresses announced to Internet: 1152549376 Equivalent to 68 /8s, 178 /16s and 130 /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: 242680 Total RIPE prefixes after maximum aggregation: 113223 RIPE Deaggregation factor: 2.14 Prefixes being announced from the RIPE address blocks: 238433 Unique aggregates announced from the RIPE address blocks: 140429 RIPE Region origin ASes present in the Internet Routing Table: 27784 RIPE Prefixes per ASN: 8.58 RIPE Region origin ASes announcing only one prefix: 11914 RIPE Region transit ASes present in the Internet Routing Table: 3892 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 33 Number of RIPE region 32-bit ASNs visible in the Routing Table: 10008 Number of RIPE addresses announced to Internet: 710411904 Equivalent to 42 /8s, 88 /16s and 6 /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: 112974 Total LACNIC prefixes after maximum aggregation: 26529 LACNIC Deaggregation factor: 4.26 Prefixes being announced from the LACNIC address blocks: 114120 Unique aggregates announced from the LACNIC address blocks: 48144 LACNIC Region origin ASes present in the Internet Routing Table: 10731 LACNIC Prefixes per ASN: 10.63 LACNIC Region origin ASes announcing only one prefix: 2664 LACNIC Region transit ASes present in the Internet Routing Table: 2009 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 33 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8331 Number of LACNIC addresses announced to Internet: 174675456 Equivalent to 10 /8s, 105 /16s and 86 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-272796 + 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: 25287 Total AfriNIC prefixes after maximum aggregation: 4897 AfriNIC Deaggregation factor: 5.16 Prefixes being announced from the AfriNIC address blocks: 32084 Unique aggregates announced from the AfriNIC address blocks: 10069 AfriNIC Region origin ASes present in the Internet Routing Table: 1449 AfriNIC Prefixes per ASN: 22.14 AfriNIC Region origin ASes announcing only one prefix: 507 AfriNIC Region transit ASes present in the Internet Routing Table: 288 Average AfriNIC Region AS path length visible: 5.1 Max AfriNIC Region AS path length visible: 38 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 790 Number of AfriNIC addresses announced to Internet: 107830784 Equivalent to 6 /8s, 109 /16s and 94 /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 7545 5717 783 669 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4834 4192 74 ERX-CERNET-BKB China Education and Rese 9808 4009 9045 60 CMNET-GD Guangdong Mobile Communication 7552 3529 1330 21 VIETEL-AS-AP Viettel Group, VN 7713 3515 1014 54 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 2900 1896 55 VNPT-AS-VN VNPT Corp, VN 4766 2444 11104 567 KIXS-AS-KR Korea Telecom, KR 9498 2317 483 235 BBIL-AP BHARTI Airtel Ltd., IN 4755 2144 441 192 TATACOMM-AS TATA Communications formerl 45090 2080 1045 63 CNNIC-TENCENT-NET-AP Shenzhen Tencent C Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 16509 4893 9229 2214 AMAZON-02, US 11492 4743 315 723 CABLEONE, US 7155 4030 264 32 VIASAT-SP-BACKBONE, US 22773 3926 2999 252 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3348 1317 72 SHAW, CA 16625 3309 1725 2354 AKAMAI-AS, US 30036 2527 371 87 MEDIACOM-ENTERPRISE-BUSINESS, US 209 2511 5057 499 CENTURYLINK-US-LEGACY-QWEST, US 5650 2350 3000 1642 FRONTIER-FRTR, US 5972 2201 445 781 DNIC-ASBLK-05800-06055, US Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 47331 7701 1038 3474 TTNET, TR 12479 6363 1700 146 UNI2-AS, ES 20940 3534 3347 207 AKAMAI-ASN1, NL 39891 3266 187 22 ALJAWWALSTC-AS, SA 8551 3132 379 41 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2882 2284 894 ROSTELECOM-AS, RU 9009 2454 252 1323 M247, GB 34984 2180 355 579 TELLCOM-AS, TR 13188 1611 100 26 TRIOLAN, UA 58224 1552 878 557 TCI, IR Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 8435 3470 581 Uninet S.A. de C.V., MX 10620 3405 527 612 Telmex Colombia S.A., CO 11830 2563 369 63 Instituto Costarricense de Electricidad 13999 1659 436 421 Mega Cable, S.A. de C.V., MX 7303 1637 1289 291 Telecom Argentina S.A., AR 6503 1442 311 475 Axtel, S.A.B. de C.V., MX 28573 1407 2266 221 CLARO S.A., BR 3816 1212 623 152 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1128 377 39 Telefonica del Peru S.A.A., PE 11664 996 211 403 Techtel LMDS Comunicaciones Interactiva Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1578 393 22 LINKdotNET-AS, EG 24835 1435 482 29 RAYA-AS, EG 36992 1192 1537 174 ETISALAT-MISR, EG 36903 977 510 104 MT-MPLS, MA 29571 705 68 11 ORANGE-COTE-IVOIRE, CI 6713 539 1863 34 IAM-AS, MA 36935 500 522 40 Vodafone-, EG 37342 482 32 1 MOVITEL, MZ 15399 453 47 17 WANANCHI-, KE 23889 446 232 15 MauritiusTelecom, MU Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 8435 3470 581 Uninet S.A. de C.V., MX 47331 7701 1038 3474 TTNET, TR 12479 6363 1700 146 UNI2-AS, ES 7545 5717 783 669 TPG-INTERNET-AP TPG Telecom Limited, AU 16509 4893 9229 2214 AMAZON-02, US 4538 4834 4192 74 ERX-CERNET-BKB China Education and Rese 11492 4743 315 723 CABLEONE, US 7155 4030 264 32 VIASAT-SP-BACKBONE, US 9808 4009 9045 60 CMNET-GD Guangdong Mobile Communication 22773 3926 2999 252 ASN-CXA-ALL-CCI-22773-RDC, US Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 12479 6363 6217 UNI2-AS, ES 7545 5717 5048 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4834 4760 ERX-CERNET-BKB China Education and Research Net 47331 7701 4227 TTNET, TR 11492 4743 4020 CABLEONE, US 7155 4030 3998 VIASAT-SP-BACKBONE, US 9808 4009 3949 CMNET-GD Guangdong Mobile Communication Co.Ltd. 22773 3926 3674 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3529 3508 VIETEL-AS-AP Viettel Group, VN 7713 3515 3461 TELKOMNET-AS-AP PT Telekomunikasi Indonesia, ID Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 174 COGENT-174, US 18604 UNALLOCATED 8.25.204.0/24 3356 LEVEL3, US 32985 UNALLOCATED 8.28.31.0/24 3356 LEVEL3, US 394936 UNALLOCATED 8.33.224.0/24 174 COGENT-174, US 23061 UNALLOCATED 8.39.119.0/24 3356 LEVEL3, US 395438 UNALLOCATED 8.42.206.0/24 3356 LEVEL3, US 46766 UNALLOCATED 8.44.208.0/24 3356 LEVEL3, US 40544 UNALLOCATED 12.0.33.0/24 6461 ZAYO-6461, US 46505 UNALLOCATED 12.7.131.0/24 7018 ATT-INTERNET4, US Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.141.0.0/24 Origin: 395350 UNASSIGNED Transit: 11426 TWC-11426-CAROLINAS, US 23.142.80.0/24 Origin: 397881 STINGERS, US Transit: 398481 REDMERCURY, US 23.226.240.0/20 Origin: 40430 UNASSIGNED Transit: 174 COGENT-174, US 27.100.7.0/24 Origin: 56096 UNASSIGNED Transit: 45455 TH-2S1N-AP Two S One N Co Ltd, Internet 27.126.156.0/22 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad No. 14, Jala Complete listing at http://thyme.rand.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:11 /9:12 /10:41 /11:102 /12:291 /13:575 /14:1181 /15:1940 /16:13497 /17:8294 /18:13778 /19:25641 /20:42024 /21:50958 /22:105588 /23:89954 /24:494234 /25:1421 /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 47331 6880 7701 TTNET, TR 12479 5321 6363 UNI2-AS, ES 11492 3798 4743 CABLEONE, US 6327 3153 3348 SHAW, CA 7155 3118 4030 VIASAT-SP-BACKBONE, US 8151 3014 8435 Uninet S.A. de C.V., MX 22773 2961 3926 ASN-CXA-ALL-CCI-22773-RDC, US 39891 2801 3266 ALJAWWALSTC-AS, SA 8551 2596 3132 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 30036 2238 2527 MEDIACOM-ENTERPRISE-BUSINESS, US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1883 2:1160 3:94 4:18 5:3532 6:64 7:5 8:1501 9:1 11:36 12:1750 13:360 14:2347 15:77 16:15 17:318 18:93 20:130 22:188 23:4557 24:2387 25:2 27:2504 31:2261 32:113 34:3 35:40 36:1147 37:3722 38:2064 39:559 40:151 41:3826 42:918 43:2118 44:240 45:15017 46:3648 47:319 49:1624 50:1741 51:91 52:1206 54:219 55:783 56:6 57:56 58:1742 59:1210 60:886 61:2411 62:2257 63:1971 64:5291 65:2384 66:5152 67:2915 68:1173 69:4076 70:1405 71:685 72:3220 74:2572 75:1479 76:687 77:2010 78:3639 79:2353 80:1823 81:1626 82:1316 83:1105 84:1251 85:3219 86:718 87:1780 88:2701 89:2988 90:433 91:7250 92:1759 93:2545 94:3031 95:4405 96:1252 97:345 98:992 99:970 100:89 101:1046 102:1280 103:25599 104:3714 105:424 106:721 107:2227 108:702 109:3929 110:2003 111:2624 112:1888 113:1652 114:1464 115:1874 116:1885 117:2201 118:2294 119:1917 120:1055 121:1087 122:2313 123:2196 124:1592 125:2098 128:1362 129:949 130:818 131:2019 132:765 133:354 134:1558 135:291 136:734 137:908 138:2297 139:1202 140:731 141:1185 142:1105 143:1278 144:1255 145:323 146:1391 147:1264 148:2181 149:1446 150:779 151:1087 152:1546 153:387 154:2235 155:1367 156:1496 157:1158 158:924 159:2045 160:2070 161:1151 162:3231 163:969 164:1434 165:1336 166:598 167:1775 168:3542 169:661 170:4278 171:761 172:2106 173:2965 174:980 175:1100 176:3041 177:4363 178:2890 179:1954 180:2274 181:2625 182:3200 183:1643 184:2455 185:17996 186:4199 187:3129 188:3311 189:2809 190:8953 191:1480 192:10580 193:7935 194:6538 195:4678 196:2888 197:2322 198:6032 199:5991 200:7420 201:5344 202:10575 203:10113 204:4646 205:3307 206:3491 207:3334 208:3990 209:4628 210:4260 211:2178 212:3672 213:3323 214:1208 215:61 216:6165 217:2520 218:1053 219:699 220:2067 221:935 222:996 223:1771 End of report

1 0

NOAA/NWS data center water pipe burst
by Sean Donelan 12 Mar '21

12 Mar '21

At 10:30 a.m. on March 9, 2021, the National Weather Service (NWS) Headquarters building located in Silver Spring, Maryland, known as Silver Spring Metro Complex 2 (SSMC-2), experienced a ruptured water pipe, which caused significant and widespread flooding on the 7th floor and below. NWS maintains a data center on one of the affected floors. When flooding was discovered, power to the data center was turned off to protect the equipment and personnel who were onsite.

1 0

Any Godaddy DNS / Firewall Admins here?
by DurgaPrasad - DatasoftComnet 12 Mar '21

12 Mar '21

Hello all, Are there any Godaddy DNS / Firewall Admins here? We are getting no response to our DNS servers 123.108.200.180, 123.108.201.51 from Godaddy DNS servers randomly for their DNS hosted domains. We use root.hints that are updated. We have tried with powerdns recursor, unbound and also named with same result. We have checked we are not openrelay/We don't respond to IPs outside our customer pools. Can anyone help urgently. Regards DP -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

1 0