- NANOG - lists.nanog.org

scalematrix network access
by Mark Stevens 08 Mar '17

08 Mar '17

Good Morning, Is anyone having access issues into sites within scalematrix.net network? Our traces make it out of Cogent and into Level3 and either die in Level3 or a couple hops past Level3 into scalematrix.net network. If someone from Scalmatrix or Level3 reads this, can you email me offline to discuss? Thanks Mark

1 0

RE: WEBINAR TUESDAY: Can We Make IPv4 Great Again?
by Jakob Heitz (jheitz) 08 Mar '17

08 Mar '17

1.1.1.1.e.f and 2.2.2.2.e.f both get translated to 192.168.e.f. Some higher layer protocols embed IP addresses into their data. These points make changing IP so difficult. In addition, IPv6 has link local addresses. This one seemingly insignificant detail causes so much code churn and is probably responsible for 10 years of the IPv6 drag. Thakfully, site local was deprecated. Thanks, Jakob. > Date: Mon, 6 Mar 2017 22:00:45 +0100 > From: Baldur Norddahl <baldur.norddahl(a)gmail.com> > To: nanog(a)nanog.org > Subject: Re: WEBINAR TUESDAY: Can We Make IPv4 Great Again? > Message-ID: <5645714e-e468-4655-34cf-6e70aa7cfa26(a)gmail.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > That proposal is far too wordy. Here is the executive summary: > > Encode extra address bits in extension headers. Add a network element > near the destination that converts such that the destination IP of a > packet to IP a.b.c.d with extension header containing e.f is translated > to 192.168.e.f. In the reverse direction translate source address > 192.168.e.f to a.b.c.d and add option header with e.f. > > Executive summary end. > > As far as I can tell, the only advantage of this proposal over IPv6 is > that the network core does not need to be changed. You could communicate > with someone that had an EZIP address regardless that your ISP did > nothing to support EZIP. > > The disadvantage is that every single server out there would need to be > changed so it does not just drop the option headers on the reply > packets. All firewalls updated so they do not block packets with option > headers. All applications updated so they understand a new address format. > > Servers and applications could also confuse TCP or UDP streams that are > apparently from the same source, same port numbers, only thing that > differentiates the streams is some option header that the server does > not understand. > > The customers of the ISP that deploys EZIP would not need to update > anything (unless they need to communicate with other poor souls that got > assigned EZIP addresses), however everyone else would. This is not a > good balance. The customers would experience an internet where almost > nothing works. It would be magnitudes worse than the experience of an > IPv6 only network with NAT64. > > It is a fix for the wrong problem. Major ISPs have IPv6 support now. It > is the sites (=servers) that are lacking. If Twitter did not deploy IPv6 > why would you expect them to deploy EZIP? Why would some old forgotten > site with old song texts in some backwater country somewhere? > > We already have better solutions such as CGN with dual stack, NAT64, > DS-Lite, MAP etc. > > None of that is discussed in the RFC. Is the author aware of it? > > Regards, > > Baldur >

5 5

WEBINAR TUESDAY: Can We Make IPv4 Great Again?
by Joly MacFie 07 Mar '17

07 Mar '17

To say that Mr. Chen's EZIP proposal has not, thus far, been received with open arms by the networking community would be an understatement. It is seen as delaying the inevitable and introducing an impractical extra routing hardware layer that will be hit & miss. Nevertheless, since much of the world is still IPv4 dependent, it just could take off. ISOC-NY is happy to give him the opportunity to expound on its merits. We'd welcome some expert respondents. See: https://tools.ietf.org/html/draft-chen-ati-ipv4-with-adaptive-address-space… ================================================================== WEBINAR TUESDAY: Can We Make IPv4 Great Again? w/ @AbrahamYChen On Tuesday March 8 2017 at noon EST the Internet Society New York Chapter (ISOC-NY) presents a webinar Can We Make IPv4 Great Again?. Abraham Y. Chen, VP of Engineering, Avinta Communications, will present his EzIP proposal to reinvigorate the diminishing pool of IPv4 addresses. Optional registration at the link below. This will be recorded. What: WEBINAR: Can We Make IPv4 Great Again? When: Tuesday March 8 2017 Noon EST | 17:00 UTC Register + info: https://www.meetup.com/isoc-ny/events/238164448/ Computer: https://zoom.us/j/914492141 Phone: http://bit.ly/zoomphone ID: 914 492 141 Twitter: #ezip ==================================================================== Permalink http://isoc-ny.org/p2/9031 -- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -

11 15

Re: google ipv6 routes via cogent
by Baldur Norddahl 07 Mar '17

07 Mar '17

That will have the effect of prioritizing Cogent routes as that would be more specific than the default routes from the other providers. Cogent are not that good that you would want to do that. Den 2. mar. 2017 20.16 skrev "Jeff Waddell" <jeff+nanog(a)waddellsolutions.com >: Or at least ask for a full view from Cogent - then you won't get any routes they don't have On Thu, Mar 2, 2017 at 1:58 PM, Alarig Le Lay <alarig(a)swordarmor.fr> wrote: > On jeu. 2 mars 12:36:04 2017, Aaron Gould wrote: > > Well, I asked my (3) upstream providers to only send me a ipv6 default > > route and they sent me ::/0...here's one of them... > > Why did you don’t ask for a full view? With that, you can easily deal > with that kind of problem. > > -- > alarig >

13 15

Re: WWV Broadcast Outages
by Hal Murray 06 Mar '17

06 Mar '17

"Majdi S. Abbas" <msa(a)latt.net> said: > That said, I and many others "still use" WWV -- there aren't exactly a > surplus of suitable backup methods to GPS these days. Any suggestions for gear and/or software that works with WWV (or CHU)? Or general suggestions for non GPS sources of time? Dave Mills had a driver in ntpd that used a PC audio port to listen to WWV. I don't know anybody who ever used it. I think there was code to tell some brand of receiver with a serial/USB port how to change frequencies so you could use the one that worked best for that time of day. There used to be WWVB (60 KHz) receivers. The good ones phase locked to the carrier. The general rise in EMI made those close to useless in most locations. NIST finished the job when they changed the modulation format a few years ago. As far as I know, there aren't any replacements for the old gear that take advantage of the new modulation format. GPS works too well. There are some boxes that recover the time from nearby cell phone towers. I think they will stop working as the towers get upgraded to the newer protocols that use a different form of timing. That will probably take many years. But the cell phone towers depend on GPS. (You can ususlly spot the conical antenna(s) if you look around a bit.) -- These are my opinions. I hate spam.

4 3

2nd call for presentations RIPE 74
by Benno Overeinder 05 Mar '17

05 Mar '17

Dear colleagues, Please note the approaching deadline of *12 March 2017* for RIPE 74 plenary programme submissions. You can find the CFP for RIPE 74 below or at https://ripe74.ripe.net/submit-topic/cfp/, for your proposals for plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. Kind regards, Benno Overeinder RIPE PC Chair https://ripe74.ripe.net/programme/ripe-pc/ -------------------->>><<<-------------------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. RIPE 74 will take place from 8-12 May 2017 in Budapest, Hungary. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 74. See the full descriptions of the different presentation formats, https://ripe74.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 12 March 2017. Proposals submitted after this date will be considered depending on the remaining available space in the programme. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange - Connected Things (aka. Internet of Things - IoT) Submissions RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour - Lightning talks: 10 minutes total for both presentation and any discussion The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe74.ripe.net/submit-topic/submission-form/. - Lightning talks should also be submitted using the meeting submission system (https://ripe74.ripe.net/submit-topic/submission-form/) and can be submitted any time up to and including the meeting week. Allocation of lightning talks will start a few days before the meeting, and will continue throughout the meeting. During the meeting, they may be announced on the day before the talk or even on the same day as the talk. - Lightning talks should also be submitted using the meeting submission system (https://ripe74.ripe.net/submit-topic/submission-form/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice, in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. - Due to potential technical issues, presenters/panellists should be physically present at the RIPE Meeting. If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0

IANA IPv4 Recovered Address Space registry updated
by Paula Wang 05 Mar '17

05 Mar '17

Hi, An update has been made to the IANA IPv4 Recovered Address Space registry according to the Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA (https://www.icann.org/resources/pages/allocation-ipv4-post-exhaustion-2012-…) The list of allocations can be found at: https://www.iana.org/assignments/ipv4-recovered-address-space/ Kind regards, Paula Wang IANA Services Specialist PTI

3 2

Re: google ipv6 routes via cogent
by Baldur Norddahl 04 Mar '17

04 Mar '17

In general I would not be single homed to a tier 1 ISP. You are better off using an ISP that has N upstream transit providers. That way they have multiple choices to select the best route. If you accept a default route from multiple upstreams you will be multi homed for inbound traffic but effectively single homed for outbound. Your router will select one default route and send 100% of the traffic that way. Instead of letting the router select a random default route, you should evaluate and rank your upstreams. Use a route map to set priority on the routes. Nobody has the best routes for all destinations, so you will have to find the one with the best average or perhaps the one that avoids bad routes. And that brings me to the point about Cogent. We used to have two upstreams. One was a local tier 2 ISP and the other was Cogent. Our quality was OK but if the tier 2 ISP link was down our customers would immediately call to claim downtime. We would not actually be down but quality was so low that people thought we were. The reason is that some major destinations from the Cogent network is routed from Europe to USA and back again. Latency go from a few milliseconds to 100 times worse. Available bandwidth is very reduced. Video from major streaming services will not play or only in lowest quality setting. I will claim that it is impossible to be single homed on Cogent in Denmark as an eyeball network. It is probably different if you are in the USA. This does not mean Cogent are useless. We were happy with the quality of the network and the price is good. What we experienced was bad peering. You just can't have them as your only transit. Regards Baldur Den 2. mar. 2017 21.02 skrev "Chuck Anderson" <cra(a)wpi.edu>: Define "good" vs. "bad" transport of bits. As long as there is adequate bandwidth and low latency, who cares? On Thu, Mar 02, 2017 at 08:30:37PM +0100, Baldur Norddahl wrote: > That will have the effect of prioritizing Cogent routes as that would be > more specific than the default routes from the other providers. Cogent are > not that good that you would want to do that. > > Den 2. mar. 2017 20.16 skrev "Jeff Waddell" <jeff+nanog@waddellsolutions. com > >: > > Or at least ask for a full view from Cogent - then you won't get any routes > they don't have > > On Thu, Mar 2, 2017 at 1:58 PM, Alarig Le Lay <alarig(a)swordarmor.fr> wrote: > > > On jeu. 2 mars 12:36:04 2017, Aaron Gould wrote: > > > Well, I asked my (3) upstream providers to only send me a ipv6 default > > > route and they sent me ::/0...here's one of them... > > > > Why did you don’t ask for a full view? With that, you can easily deal > > with that kind of problem.

1 0

FCC emergency waiver: Jewish Community Centers Calling Party Number Identification
by Sean Donelan 04 Mar '17

04 Mar '17

The FCC granted an emergency temporary waiver to telecommunication carriers serving Jewish Community Centers, allowing access to the Caller-ID (Calling Party Number Identification) normally blocked at the calling party's request (i.e. star-67). Although per call Call-Trace (i.e. star-57) and permanent Trap-and-Trace court orders also report the Caller-ID and other call information, such as ANI to law enforcement; the FCC occasionally granted similar waivers in the past. Obviously this doesn't help with spoofed calling numbers. https://www.fcc.gov/document/fcc-grants-emergency-waiver-help-protect-jewis…

1 0

Weekly Routing Table Report
by cscora＠apnic.net 03 Mar '17

03 Mar '17

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, AusNOG, SANOG, PacNOG, MENOG, SAFNOG, SdNOG, BJNOG, CaribNOG 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 04 Mar, 2017 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 639225 Prefixes after maximum aggregation (per Origin AS): 248678 Deaggregation factor: 2.57 Unique aggregates announced (without unneeded subnets): 307752 Total ASes present in the Internet Routing Table: 56403 Prefixes per ASN: 11.33 Origin-only ASes present in the Internet Routing Table: 48853 Origin ASes announcing only one prefix: 21709 Transit ASes present in the Internet Routing Table: 7550 Transit-only ASes present in the Internet Routing Table: 207 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 42 Max AS path prepend of ASN ( 22394) 39 Prefixes from unregistered ASNs in the Routing Table: 68 Numnber of instances of unregistered ASNs: 69 Number of 32-bit ASNs allocated by the RIRs: 17548 Number of 32-bit ASNs visible in the Routing Table: 13633 Prefixes from 32-bit ASNs in the Routing Table: 55318 Number of bogon 32-bit ASNs visible in the Routing Table: 44 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 397 Number of addresses announced to Internet: 2836585604 Equivalent to 169 /8s, 18 /16s and 220 /24s Percentage of available address space announced: 76.6 Percentage of allocated address space announced: 76.6 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.5 Total number of prefixes smaller than registry allocations: 213156 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 174750 Total APNIC prefixes after maximum aggregation: 49968 APNIC Deaggregation factor: 3.50 Prefixes being announced from the APNIC address blocks: 174086 Unique aggregates announced from the APNIC address blocks: 71703 APNIC Region origin ASes present in the Internet Routing Table: 7887 APNIC Prefixes per ASN: 22.07 APNIC Region origin ASes announcing only one prefix: 2205 APNIC Region transit ASes present in the Internet Routing Table: 1123 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 41 Number of APNIC region 32-bit ASNs visible in the Routing Table: 2726 Number of APNIC addresses announced to Internet: 760850308 Equivalent to 45 /8s, 89 /16s and 167 /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-137529 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: 194786 Total ARIN prefixes after maximum aggregation: 93195 ARIN Deaggregation factor: 2.09 Prefixes being announced from the ARIN address blocks: 197227 Unique aggregates announced from the ARIN address blocks: 90282 ARIN Region origin ASes present in the Internet Routing Table: 17817 ARIN Prefixes per ASN: 11.07 ARIN Region origin ASes announcing only one prefix: 6647 ARIN Region transit ASes present in the Internet Routing Table: 1771 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 42 Number of ARIN region 32-bit ASNs visible in the Routing Table: 1813 Number of ARIN addresses announced to Internet: 1106472928 Equivalent to 65 /8s, 243 /16s and 111 /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-397212 ARIN Address Blocks 3/8, 4/8, 6/8, 7/8, 8/8, 9/8, 11/8, 12/8, 13/8, 15/8, 16/8, 17/8, 18/8, 19/8, 20/8, 21/8, 22/8, 23/8, 24/8, 26/8, 28/8, 29/8, 30/8, 32/8, 33/8, 34/8, 35/8, 38/8, 40/8, 44/8, 45/8, 47/8, 48/8, 50/8, 52/8, 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: 170475 Total RIPE prefixes after maximum aggregation: 84124 RIPE Deaggregation factor: 2.03 Prefixes being announced from the RIPE address blocks: 165696 Unique aggregates announced from the RIPE address blocks: 100287 RIPE Region origin ASes present in the Internet Routing Table: 23765 RIPE Prefixes per ASN: 6.97 RIPE Region origin ASes announcing only one prefix: 10985 RIPE Region transit ASes present in the Internet Routing Table: 3355 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 28 Number of RIPE region 32-bit ASNs visible in the Routing Table: 5601 Number of RIPE addresses announced to Internet: 710371200 Equivalent to 42 /8s, 87 /16s and 103 /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-207259 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: 82580 Total LACNIC prefixes after maximum aggregation: 17633 LACNIC Deaggregation factor: 4.68 Prefixes being announced from the LACNIC address blocks: 83764 Unique aggregates announced from the LACNIC address blocks: 38289 LACNIC Region origin ASes present in the Internet Routing Table: 5677 LACNIC Prefixes per ASN: 14.75 LACNIC Region origin ASes announcing only one prefix: 1546 LACNIC Region transit ASes present in the Internet Routing Table: 1028 Average LACNIC Region AS path length visible: 5.3 Max LACNIC Region AS path length visible: 36 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 3200 Number of LACNIC addresses announced to Internet: 171328672 Equivalent to 10 /8s, 54 /16s and 68 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-266652 + 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: 16532 Total AfriNIC prefixes after maximum aggregation: 3700 AfriNIC Deaggregation factor: 4.47 Prefixes being announced from the AfriNIC address blocks: 18055 Unique aggregates announced from the AfriNIC address blocks: 6840 AfriNIC Region origin ASes present in the Internet Routing Table: 1024 AfriNIC Prefixes per ASN: 17.63 AfriNIC Region origin ASes announcing only one prefix: 326 AfriNIC Region transit ASes present in the Internet Routing Table: 198 Average AfriNIC Region AS path length visible: 4.7 Max AfriNIC Region AS path length visible: 22 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 293 Number of AfriNIC addresses announced to Internet: 87054848 Equivalent to 5 /8s, 48 /16s and 90 /24s AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 102/8, 105/8, 154/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4538 5556 4190 74 ERX-CERNET-BKB China Education and Rese 7545 3735 391 256 TPG-INTERNET-AP TPG Telecom Limited, AU 17974 2985 905 72 TELKOMNET-AS2-AP PT Telekomunikasi Indo 4766 2743 11133 744 KIXS-AS-KR Korea Telecom, KR 9829 2722 1501 541 BSNL-NIB National Internet Backbone, IN 9808 2295 8698 33 CMNET-GD Guangdong Mobile Communication 4755 2067 421 219 TATACOMM-AS TATA Communications formerl 45899 1875 1307 103 VNPT-AS-VN VNPT Corp, VN 4808 1658 1786 448 CHINA169-BJ China Unicom Beijing Provin 24560 1562 580 254 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 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 22773 3660 2968 148 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 6327 3300 1333 83 SHAW - Shaw Communications Inc., CA 18566 2187 405 109 MEGAPATH5-US - MegaPath Corporation, US 6389 2063 3671 39 BELLSOUTH-NET-BLK - BellSouth.net Inc., 20115 1976 2050 405 CHARTER-NET-HKY-NC - Charter Communicat 209 1727 5067 640 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 30036 1705 318 426 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 16509 1704 3321 559 AMAZON-02 - Amazon.com, Inc., US 6983 1683 852 227 ITCDELTA - Earthlink, Inc., US 701 1581 10599 653 UUNET - MCI Communications Services, In 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 39891 3334 171 18 ALJAWWALSTC-AS , SA 20940 3009 1124 2140 AKAMAI-ASN1 , US 9121 2644 1691 18 TTNET , TR 34984 1994 328 383 TELLCOM-AS , TR 13188 1654 99 58 TRIOLAN , UA 8551 1633 377 40 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12479 1498 1033 49 UNI2-AS , ES 12389 1274 1216 495 ROSTELECOM-AS , RU 9198 1270 352 22 KAZTELECOM-AS , KZ 6849 1268 355 22 UKRTELNET , UA 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 10620 3541 545 164 Telmex Colombia S.A., CO 26615 3018 2330 44 Tim Celular S.A., BR 8151 2500 3379 543 Uninet S.A. de C.V., MX 11830 1800 368 66 Instituto Costarricense de Electricidad 6503 1556 437 53 Axtel, S.A.B. de C.V., MX 7303 1552 999 251 Telecom Argentina S.A., AR 6147 1166 377 27 Telefonica del Peru S.A.A., PE 28573 1086 2285 180 CLARO S.A., BR 3816 1004 479 186 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11664 978 280 35 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 1299 399 42 LINKdotNET-AS, EG 36903 718 361 122 MT-MPLS, MA 37611 693 67 6 Afrihost, ZA 36992 600 1375 26 ETISALAT-MISR, EG 24835 491 722 14 RAYA-AS, EG 8452 417 1474 16 TE-AS TE-AS, EG 37492 393 316 74 ORANGE-TN, TN 29571 368 36 10 CITelecom-AS, CI 15399 334 35 7 WANANCHI-KE, KE 2018 272 327 74 TENET-1, ZA 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 4538 5556 4190 74 ERX-CERNET-BKB China Education and Rese 7545 3735 391 256 TPG-INTERNET-AP TPG Telecom Limited, AU 22773 3660 2968 148 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 10620 3541 545 164 Telmex Colombia S.A., CO 39891 3334 171 18 ALJAWWALSTC-AS , SA 6327 3300 1333 83 SHAW - Shaw Communications Inc., CA 26615 3018 2330 44 Tim Celular S.A., BR 20940 3009 1124 2140 AKAMAI-ASN1 , US 17974 2985 905 72 TELKOMNET-AS2-AP PT Telekomunikasi Indo 4766 2743 11133 744 KIXS-AS-KR Korea Telecom, KR Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 22773 3660 3512 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7545 3735 3479 TPG-INTERNET-AP TPG Telecom Limited, AU 10620 3541 3377 Telmex Colombia S.A., CO 39891 3334 3316 ALJAWWALSTC-AS , SA 6327 3300 3217 SHAW - Shaw Communications Inc., CA 26615 3018 2974 Tim Celular S.A., BR 17974 2985 2913 TELKOMNET-AS2-AP PT Telekomunikasi Indonesia, I 9121 2644 2626 TTNET , TR 9808 2295 2262 CMNET-GD Guangdong Mobile Communication Co.Ltd. 9829 2722 2181 BSNL-NIB National Internet Backbone, IN Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 65001 PRIVATE 5.143.176.0/20 15468 KLGELECS-AS 38, Teatralnaya st 65602 UNALLOCATED 8.225.192.0/24 30372 SUNESYS2 - Sunesys, LLC, US 65001 PRIVATE 31.172.192.0/20 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.192.0/21 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.200.0/21 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.208.0/21 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.216.0/21 15468 KLGELECS-AS 38, Teatralnaya st 65000 PRIVATE 31.219.177.0/25 8966 ETISALAT-AS P.O. Box 1150, Dub 65000 PRIVATE 31.219.177.128/25 8966 ETISALAT-AS P.O. Box 1150, Dub 65555 UNALLOCATED 37.142.172.0/24 21450 MIRS-AS , IL Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 23.157.128.0/17 393899 -Reserved AS-, ZZ 23.161.128.0/17 393899 -Reserved AS-, ZZ 27.100.7.0/24 56096 UNKNOWN 41.73.16.0/24 37004 Suburban-Broadband-AS, NG 41.73.17.0/24 37004 Suburban-Broadband-AS, NG 41.73.18.0/24 37004 Suburban-Broadband-AS, NG 41.73.19.0/24 37004 Suburban-Broadband-AS, NG 41.73.20.0/24 37004 Suburban-Broadband-AS, NG 41.73.21.0/24 37004 Suburban-Broadband-AS, NG 41.73.22.0/24 37004 Suburban-Broadband-AS, NG 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:16 /9:13 /10:36 /11:103 /12:278 /13:537 /14:1046 /15:1794 /16:13200 /17:7788 /18:13239 /19:24772 /20:38244 /21:41013 /22:74772 /23:63160 /24:357847 /25:554 /26:415 /27:293 /28:34 /29:18 /30:26 /31:1 /32:26 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6327 3096 3300 SHAW - Shaw Communications Inc., CA 39891 2896 3334 ALJAWWALSTC-AS , SA 22773 2839 3660 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 26615 2534 3018 Tim Celular S.A., BR 18566 2080 2187 MEGAPATH5-US - MegaPath Corporation, US 9121 1856 2644 TTNET , TR 30036 1516 1705 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 10620 1457 3541 Telmex Colombia S.A., CO 13188 1378 1654 TRIOLAN , UA 6389 1372 2063 BELLSOUTH-NET-BLK - BellSouth.net Inc., US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1609 2:837 4:25 5:2454 6:34 8:1051 12:1812 13:85 14:1779 15:22 16:2 17:109 18:129 19:1 20:53 23:2375 24:1857 25:2 27:2373 31:1856 32:89 33:5 34:1 35:3 36:375 37:2560 38:1345 39:44 40:99 41:2811 42:463 43:1895 44:62 45:2389 46:2626 47:112 49:1224 50:965 51:18 52:746 54:356 55:5 56:4 57:41 58:1622 59:990 60:387 61:1935 62:1510 63:1921 64:4568 65:2182 66:4479 67:2263 68:1191 69:3339 70:1303 71:574 72:2141 74:2622 75:396 76:413 77:1429 78:1668 79:1311 80:1358 81:1403 82:964 83:727 84:861 85:1737 86:483 87:1137 88:804 89:2055 90:205 91:6130 92:994 93:2367 94:2369 95:2824 96:565 97:358 98:938 99:83 100:153 101:1243 103:13830 104:2776 105:165 106:484 107:1545 108:829 109:2594 110:1290 111:1722 112:1158 113:1309 114:1042 115:1733 116:1753 117:1660 118:2073 119:1604 120:946 121:1095 122:2335 123:2113 124:1538 125:1820 128:707 129:620 130:409 131:1383 132:522 133:190 134:528 135:215 136:512 137:420 138:1858 139:500 140:372 141:524 142:790 143:906 144:764 145:168 146:1036 147:710 148:1380 149:569 150:695 151:945 152:729 153:302 154:760 155:970 156:552 157:616 158:454 159:1424 160:564 161:737 162:2478 163:535 164:787 165:1156 166:385 167:1225 168:2577 169:749 170:2899 171:281 172:1012 173:1838 174:801 175:725 176:1775 177:4256 178:2476 179:1603 180:2184 181:2018 182:2218 183:1055 184:833 185:8884 186:3181 187:2664 188:2421 189:1814 190:8102 191:1885 192:9287 193:5768 194:4650 195:3836 196:1955 197:1283 198:5566 199:5838 200:7396 201:4096 202:10206 203:9813 204:4460 205:2773 206:2998 207:3130 208:3975 209:3971 210:3945 211:2116 212:2811 213:2477 214:864 215:65 216:5878 217:2008 218:839 219:615 220:1693 221:893 222:723 223:1152 End of report

1 0