[afnog] afnog Digest, Vol 70, Issue 10
Global One Solutions
malabow at gmail.com
Fri Jan 8 19:15:35 UTC 2010
It almost impossible to truely load-balance (per flow or per packet) when
the port come from different ISP, you might be able to influence your
outbound traffic, but you return path will be chosen by BGP (assuming you
are running BGP). What is your goal of bundling your BW? are you using one
link more where the others sit on idle? Mark has pointed out some good
advice, so read up the link he send you. What protocol are you running with
your ISP, do you have any load-balancer in your LAN? is this Dedicated
Internet Access (DIA) or MPLS-VPN? Ethernet? E-1? etc
Thanks,
On Fri, Jan 8, 2010 at 1:44 PM, <afnog-request at afnog.org> wrote:
> Send afnog mailing list submissions to
> afnog at afnog.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://afnog.org/mailman/listinfo/afnog
> or, via email, send a message with subject or body 'help' to
> afnog-request at afnog.org
>
> You can reach the person managing the list at
> afnog-owner at afnog.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of afnog digest..."
>
>
> Today's Topics:
>
> 1. Adding Bandwidth (Pamela Pomary)
> 2. Re: Routing - Adding Bandwidth (Mukom TAMON)
> 3. Re: Adding Bandwidth (Mark Tinka)
> 4. Weekly Routing Table Report (Routing Analysis Role Account)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 8 Jan 2010 16:54:38 -0000 (GMT)
> From: "Pamela Pomary" <ppomary at ug.edu.gh>
> To: afnog at afnog.org
> Subject: [afnog] Adding Bandwidth
> Message-ID:
> <2911.192.168.57.49.1262969678.squirrel at mailsrv1.ug.edu.gh>
> Content-Type: text/plain;charset=iso-8859-1
>
> Hello Mark
>
> This topic seem interesting to me as we have a similar situation in our
> network.
> We have our own IPs from Afrinic. We have two ISPs we connect to with
> different IP blocks.
> I want you to clarify how doing BGP with the two different ISPs, can put
> all three or two different bandwidths into one pipe while
> maintaining ISP's ipblock on the border routers and keeping our own
> ipblock from Afrinic in the internal network?
>
> Thank You
>
> Pamela
>
> > Send afnog mailing list submissions to
> > afnog at afnog.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > http://afnog.org/mailman/listinfo/afnog
> > or, via email, send a message with subject or body 'help' to
> > afnog-request at afnog.org
> >
> > You can reach the person managing the list at
> > afnog-owner at afnog.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of afnog digest..."
> >
> >
> > Today's Topics:
> >
> > 1. Routing - Adding Bandwidth (Benjamin Cobblah)
> > 2. Re: Routing - Adding Bandwidth (Mark Tinka)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Thu, 7 Jan 2010 18:07:33 +0000 (GMT)
> > From: Benjamin Cobblah <cbnayai at yahoo.co.uk>
> > To: afnog <afnog at afnog.org>
> > Subject: [afnog] Routing - Adding Bandwidth
> > Message-ID: <981758.66982.qm at web25005.mail.ukl.yahoo.com>
> > Content-Type: text/plain; charset="iso-8859-1"
> >
> > I kind of have a challenge.
> >
> > I have 3 ISP,s?each suppling me with?a 4 MB?bandwidth of internet. All
> > work?perfectly for various services in their own respect.
> >
> > I have a failover (high availability)?setup for these 3 ISP's such that
> if
> > one fails another kicks in automatically.
> >
> > The challenge is that i would like to bundle all the 12MB in one pipe so
> > that at a given session i have 12 MB to distribute at will and also
> > maintain my failover solution.
> >
> > Is there a way to do this?
> >
> > Any help would be appreciated especially if it boils into the software
> > router solution.
> >
> > Best regards,
> >
> > Benjamin
> >
> >
> >
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL:
> > <
> http://afnog.org/pipermail/afnog/attachments/20100107/53563831/attachment.html
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Fri, 8 Jan 2010 02:37:04 +0800
> > From: Mark Tinka <mtinka at globaltransit.net>
> > To: Benjamin Cobblah <cbnayai at yahoo.co.uk>
> > Cc: afnog <afnog at afnog.org>
> > Subject: Re: [afnog] Routing - Adding Bandwidth
> > Message-ID: <201001080237.09265.mtinka at globaltransit.net>
> > Content-Type: text/plain; charset="us-ascii"
> >
> > On Friday 08 January 2010 02:07:33 am Benjamin Cobblah
> > wrote:
> >
> >> The challenge is that i would like to bundle all the 12MB
> >> in one pipe so that at a given session i have 12 MB to
> >> distribute at will and also maintain my failover
> >> solution.
> >
> > You don't mention how the links are being delivered...
> > Ethernet, PPP, e.t.c., nor what platforms you're using.
> >
> > What you need is load balancing, but there are 2 layers and
> > 3 issues to consider:
> >
> > * At Layer 2; if Ethernet, doubtful 802.1AX (Ethernet) or
> > ML-PPP would be useful since these are separate ISP's.
> >
> > * At Layer 3; if each of the ISP's are assigning you
> > addresses from their own allocations, directly putting
> > traffic on each link simultaneously won't be straight
> > forward. You could do it by placing different internal
> > devices on the different IP addresses, but I'm guessing
> > the bulk of your (inbound) traffic will be user-based web
> > browsing or the like.
> >
> > * The third issue is if you're using NAT. Multi-homing with
> > NAT is fairly doable. Multi-homing + load balancing with
> > NAT, a little more interesting :-). Cisco have a feature
> > called OER (Optimized Edge Routing), you could take a
> > look at it and see if it's close to what you need
> > (assuming you have NAT):
> >
> >
> http://www.cisco.com/en/US/tech/tk648/tk361/technologies_configuration_example09186a00808d2b72.shtml
> >
> > The easiest solution would be for your to run BGP with your
> > ISP's. This works best when you have your own address space
> > and ASN allocations from AfriNIC (in case you don't
> > already). But this depends on a number of things, one of
> > which is whether your ISP's support BGP for customers, and
> > if so, whether they'll run it with you, among other issues.
> >
> > More information about your setup, ISP environment, AfriNIC
> > allocation status (if any), e.t.c., would be helpful.
> >
> > Cheers,
> >
> > Mark.
> > -------------- next part --------------
> > A non-text attachment was scrubbed...
> > Name: not available
> > Type: application/pgp-signature
> > Size: 836 bytes
> > Desc: This is a digitally signed message part.
> > URL:
> > <
> http://afnog.org/pipermail/afnog/attachments/20100108/011dac69/attachment-0001.pgp
> >
> >
> > ------------------------------
> >
> > _______________________________________________
> > afnog mailing list
> >
> > End of afnog Digest, Vol 70, Issue 9
> > ************************************
> >
>
>
>
> -------------------------------------------------------------------------------------
> NOTE: This e-mail message is subject to the University of Ghana email
> disclaimer see http://www.ug.edu.gh/index1.php?linkid=271
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 8 Jan 2010 22:40:05 +0500
> From: Mukom TAMON <mukom.tamon at gmail.com>
> To: afnog <afnog at afnog.org>
> Subject: Re: [afnog] Routing - Adding Bandwidth
> Message-ID:
> <2fda4da31001080940g9ab9e66mf36cc4501500493b at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> If you are running all Cisco gear, you might want to look at GLBP (Gateway
> Load Balancing Procotol) ...it will spread all your users seamlessly
> accross
> your multiple egress links and they don't have to terminate at same ISP.
> You
> get load-balancing and redundancy with GLBP.
>
>
>
>
> On Thu, Jan 7, 2010 at 11:37 PM, Mark Tinka <mtinka at globaltransit.net
> >wrote:
>
> > On Friday 08 January 2010 02:07:33 am Benjamin Cobblah
> > wrote:
> >
> > > The challenge is that i would like to bundle all the 12MB
> > > in one pipe so that at a given session i have 12 MB to
> > > distribute at will and also maintain my failover
> > > solution.
> >
> > You don't mention how the links are being delivered...
> > Ethernet, PPP, e.t.c., nor what platforms you're using.
> >
> > What you need is load balancing, but there are 2 layers and
> > 3 issues to consider:
> >
> > * At Layer 2; if Ethernet, doubtful 802.1AX (Ethernet) or
> > ML-PPP would be useful since these are separate ISP's.
> >
> > * At Layer 3; if each of the ISP's are assigning you
> > addresses from their own allocations, directly putting
> > traffic on each link simultaneously won't be straight
> > forward. You could do it by placing different internal
> > devices on the different IP addresses, but I'm guessing
> > the bulk of your (inbound) traffic will be user-based web
> > browsing or the like.
> >
> > * The third issue is if you're using NAT. Multi-homing with
> > NAT is fairly doable. Multi-homing + load balancing with
> > NAT, a little more interesting :-). Cisco have a feature
> > called OER (Optimized Edge Routing), you could take a
> > look at it and see if it's close to what you need
> > (assuming you have NAT):
> >
> >
> >
> http://www.cisco.com/en/US/tech/tk648/tk361/technologies_configuration_example09186a00808d2b72.shtml
> >
> > The easiest solution would be for your to run BGP with your
> > ISP's. This works best when you have your own address space
> > and ASN allocations from AfriNIC (in case you don't
> > already). But this depends on a number of things, one of
> > which is whether your ISP's support BGP for customers, and
> > if so, whether they'll run it with you, among other issues.
> >
> > More information about your setup, ISP environment, AfriNIC
> > allocation status (if any), e.t.c., would be helpful.
> >
> > Cheers,
> >
> > Mark.
> >
> > _______________________________________________
> > afnog mailing list
> > http://afnog.org/mailman/listinfo/afnog
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://afnog.org/pipermail/afnog/attachments/20100108/6f3f76c5/attachment-0001.htm
> >
>
> ------------------------------
>
> Message: 3
> Date: Sat, 9 Jan 2010 01:46:06 +0800
> From: Mark Tinka <mtinka at globaltransit.net>
> To: "Pamela Pomary" <ppomary at ug.edu.gh>
> Cc: afnog at afnog.org
> Subject: Re: [afnog] Adding Bandwidth
> Message-ID: <201001090146.12708.mtinka at globaltransit.net>
> Content-Type: text/plain; charset="us-ascii"
>
> On Saturday 09 January 2010 12:54:38 am Pamela Pomary wrote:
>
> > Hello Mark
>
> Hi Pamela.
>
> > This topic seem interesting to me as we have a similar
> > situation in our network.
> > We have our own IPs from Afrinic. We have two ISPs we
> > connect to with different IP blocks.
> > I want you to clarify how doing BGP with the two
> > different ISPs, can put all three or two different
> > bandwidths into one pipe while maintaining ISP's ipblock
> > on the border routers and keeping our own ipblock from
> > Afrinic in the internal network?
>
> Since you have an AfriNIC allocation, do go ahead and apply
> for an ASN as well, if you haven't already. One note on
> ASN's, though, if you don't have one and apply for it today,
> you will only receive a 32-bit ASN from AfriNIC. This means
> you're better off having a border router that supports 4-
> byte ASN's.
>
> Having taken care of the above, since you have your own
> allocation, relegate the use of your ISP's IP addresses to
> the point-to-point link between your network and theirs,
> i.e., a /30 assignment to the point-to-point interfaces.
>
> With that done, use BGP to announce your AfriNIC allocation
> to your ISP's. Ensure that your ISP's support BGP (with
> you), and that they won't have problems handling 4-byte
> ASN's.
>
> On BGP and BGP Multi-homing, check out the following:
>
> http://ws.afnog.org/afnog2009/sie/detail.html#topic-240-bgp
> http://www.nanog.org/meetings/nanog28/presentations/smith.pdf
>
> It's likely you'll have a bunch of questions along the way.
> Feel free to post at anytime.
>
> Cheers,
>
> Mark.
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 836 bytes
> Desc: This is a digitally signed message part.
> URL: <
> http://afnog.org/pipermail/afnog/attachments/20100109/4b75b860/attachment-0001.pgp
> >
>
> ------------------------------
>
> Message: 4
> Date: Sat, 9 Jan 2010 04:43:43 +1000 (EST)
> From: Routing Analysis Role Account <cscora at apnic.net>
> To: apops at apops.net, nanog at nanog.org, routing-wg at ripe.net,
> afnog at afnog.org, ausnog at ausnog.net, sanog at sanog.org
> Subject: [afnog] Weekly Routing Table Report
> Message-ID: <201001081843.o08Ihhao021615 at thyme.apnic.net>
>
> This is an automated weekly mailing describing the state of the Internet
> Routing Table as seen from APNIC's router in Japan.
> Daily listings are sent to bgp-stats at lists.apnic.net
>
> For historical data, please see http://thyme.apnic.net.
>
> If you have any comments please contact Philip Smith <pfs at cisco.com>.
>
> Routing Table Report 04:00 +10GMT Sat 09 Jan, 2010
>
> Report Website: http://thyme.apnic.net
> Detailed Analysis: http://thyme.apnic.net/current/
>
> Analysis Summary
> ----------------
>
> BGP routing table entries examined: 307662
> Prefixes after maximum aggregation: 143300
> Deaggregation factor: 2.15
> Unique aggregates announced to Internet: 151565
> Total ASes present in the Internet Routing Table: 33037
> Prefixes per ASN: 9.31
> Origin-only ASes present in the Internet Routing Table: 28698
> Origin ASes announcing only one prefix: 14013
> Transit ASes present in the Internet Routing Table: 4339
> Transit-only ASes present in the Internet Routing Table: 103
> Average AS path length visible in the Internet Routing Table: 3.6
> Max AS path length visible: 22
> Max AS path prepend of ASN ( 9503) 20
> Prefixes from unregistered ASNs in the Routing Table: 731
> Unregistered ASNs in the Routing Table: 133
> Number of 32-bit ASNs allocated by the RIRs: 385
> Prefixes from 32-bit ASNs in the Routing Table: 335
> Special use prefixes present in the Routing Table: 0
> Prefixes being announced from unallocated address space: 186
> Number of addresses announced to Internet: 2169545344
> Equivalent to 129 /8s, 80 /16s and 162 /24s
> Percentage of available address space announced: 58.5
> Percentage of allocated address space announced: 66.3
> Percentage of available address space allocated: 88.2
> Percentage of address space in use by end-sites: 80.7
> Total number of prefixes smaller than registry allocations: 148143
>
> APNIC Region Analysis Summary
> -----------------------------
>
> Prefixes being announced by APNIC Region ASes: 73972
> Total APNIC prefixes after maximum aggregation: 25793
> APNIC Deaggregation factor: 2.87
> Prefixes being announced from the APNIC address blocks: 70662
> Unique aggregates announced from the APNIC address blocks: 31402
> APNIC Region origin ASes present in the Internet Routing Table: 3913
> APNIC Prefixes per ASN: 18.06
> APNIC Region origin ASes announcing only one prefix: 1071
> APNIC Region transit ASes present in the Internet Routing Table: 612
> Average APNIC Region AS path length visible: 3.7
> Max APNIC Region AS path length visible: 22
> Number of APNIC addresses announced to Internet: 486803488
> Equivalent to 29 /8s, 4 /16s and 8 /24s
> Percentage of available APNIC address space announced: 80.6
>
> APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431
> (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079
> 55296-56319, 131072-132095
> APNIC Address Blocks 43/8, 58/8, 59/8, 60/8, 61/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, 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,
>
> ARIN Region Analysis Summary
> ----------------------------
>
> Prefixes being announced by ARIN Region ASes: 129255
> Total ARIN prefixes after maximum aggregation: 67559
> ARIN Deaggregation factor: 1.91
> Prefixes being announced from the ARIN address blocks: 103380
> Unique aggregates announced from the ARIN address blocks: 39158
> ARIN Region origin ASes present in the Internet Routing Table: 13428
> ARIN Prefixes per ASN: 7.70
> ARIN Region origin ASes announcing only one prefix: 5201
> ARIN Region transit ASes present in the Internet Routing Table: 1323
> Average ARIN Region AS path length visible: 3.3
> Max ARIN Region AS path length visible: 22
> Number of ARIN addresses announced to Internet: 735019296
> Equivalent to 43 /8s, 207 /16s and 129 /24s
> Percentage of available ARIN address space announced: 64.4
>
> 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, 393216-394239
> 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, 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, 52/8, 54/8, 55/8,
> 56/8, 63/8, 64/8, 65/8, 66/8, 67/8, 68/8,
> 69/8, 70/8, 71/8, 72/8, 73/8, 74/8, 75/8,
> 76/8, 96/8, 97/8, 98/8, 99/8, 108/8, 173/8,
> 174/8, 184/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: 70912
> Total RIPE prefixes after maximum aggregation: 41459
> RIPE Deaggregation factor: 1.71
> Prefixes being announced from the RIPE address blocks: 64240
> Unique aggregates announced from the RIPE address blocks: 42763
> RIPE Region origin ASes present in the Internet Routing Table: 13948
> RIPE Prefixes per ASN: 4.61
> RIPE Region origin ASes announcing only one prefix: 7257
> RIPE Region transit ASes present in the Internet Routing Table: 2088
> Average RIPE Region AS path length visible: 3.9
> Max RIPE Region AS path length visible: 20
> Number of RIPE addresses announced to Internet: 409561344
> Equivalent to 24 /8s, 105 /16s and 105 /24s
> Percentage of available RIPE address space announced: 76.3
>
> 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, 196608-197631
> RIPE Address Blocks 2/8, 25/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, 178/8, 193/8, 194/8,
> 195/8, 212/8, 213/8, 217/8,
>
> LACNIC Region Analysis Summary
> ------------------------------
>
> Prefixes being announced by LACNIC Region ASes: 26966
> Total LACNIC prefixes after maximum aggregation: 6530
> LACNIC Deaggregation factor: 4.13
> Prefixes being announced from the LACNIC address blocks: 25329
> Unique aggregates announced from the LACNIC address blocks: 13780
> LACNIC Region origin ASes present in the Internet Routing Table: 1225
> LACNIC Prefixes per ASN: 20.68
> LACNIC Region origin ASes announcing only one prefix: 391
> LACNIC Region transit ASes present in the Internet Routing Table: 204
> Average LACNIC Region AS path length visible: 4.0
> Max LACNIC Region AS path length visible: 20
> Number of LACNIC addresses announced to Internet: 69899712
> Equivalent to 4 /8s, 42 /16s and 149 /24s
> Percentage of available LACNIC address space announced: 69.4
>
> LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247,
> 262144-263167 plus ERX transfers
> LACNIC Address Blocks 186/8, 187/8, 189/8, 190/8, 200/8, 201/8,
>
> AfriNIC Region Analysis Summary
> -------------------------------
>
> Prefixes being announced by AfriNIC Region ASes: 5994
> Total AfriNIC prefixes after maximum aggregation: 1610
> AfriNIC Deaggregation factor: 3.72
> Prefixes being announced from the AfriNIC address blocks: 4375
> Unique aggregates announced from the AfriNIC address blocks: 1592
> AfriNIC Region origin ASes present in the Internet Routing Table: 337
> AfriNIC Prefixes per ASN: 12.98
> AfriNIC Region origin ASes announcing only one prefix: 93
> AfriNIC Region transit ASes present in the Internet Routing Table: 69
> Average AfriNIC Region AS path length visible: 3.8
> Max AfriNIC Region AS path length visible: 21
> Number of AfriNIC addresses announced to Internet: 14742016
> Equivalent to 0 /8s, 224 /16s and 242 /24s
> Percentage of available AfriNIC address space announced: 43.9
>
> AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers
> AfriNIC Address Blocks 41/8, 197/8,
>
> APNIC Region per AS prefix count summary
> ----------------------------------------
>
> ASN No of nets /20 equiv MaxAgg Description
> 4766 1831 7509 473 Korea Telecom (KIX)
> 17488 1464 144 140 Hathway IP Over Cable Interne
> 4755 1281 289 144 TATA Communications formerly
> 18101 1033 220 38 Reliance Infocom Ltd Internet
> 4134 1018 19477 400 CHINANET-BACKBONE
> 9583 998 74 503 Sify Limited
> 7545 920 198 98 TPG Internet Pty Ltd
> 17974 844 271 55 PT TELEKOMUNIKASI INDONESIA
> 4808 836 1583 213 CNCGROUP IP network: China169
> 9829 835 679 22 BSNL National Internet Backbo
>
> Complete listing at http://thyme.apnic.net/current/data-ASnet-APNIC
>
> ARIN Region per AS prefix count summary
> ---------------------------------------
>
> ASN No of nets /20 equiv MaxAgg Description
> 6389 4165 3891 301 bellsouth.net, inc.
> 4323 3783 1068 400 Time Warner Telecom
> 1785 1796 699 134 PaeTec Communications, Inc.
> 7018 1589 5791 1028 AT&T WorldNet Services
> 20115 1537 1487 666 Charter Communications
> 2386 1294 617 930 AT&T Data Communications Serv
> 3356 1200 10929 423 Level 3 Communications, LLC
> 11492 1154 222 14 Cable One
> 22773 1124 2600 66 Cox Communications, Inc.
> 6478 1092 241 298 AT&T Worldnet Services
>
> Complete listing at http://thyme.apnic.net/current/data-ASnet-ARIN
>
> RIPE Region per AS prefix count summary
> ---------------------------------------
>
> ASN No of nets /20 equiv MaxAgg Description
> 30890 516 98 206 Evolva Telecom
> 35805 466 40 5 United Telecom of Georgia
> 3292 448 1903 393 TDC Tele Danmark
> 9198 426 202 13 Kazakhtelecom Data Network Ad
> 702 419 1837 337 UUNET - Commercial IP service
> 8551 396 353 37 Bezeq International
> 8866 374 110 23 Bulgarian Telecommunication C
> 3320 361 7068 307 Deutsche Telekom AG
> 3301 352 1412 307 TeliaNet Sweden
> 3215 350 3168 107 France Telecom Transpac
>
> Complete listing at http://thyme.apnic.net/current/data-ASnet-RIPE
>
> LACNIC Region per AS prefix count summary
> -----------------------------------------
>
> ASN No of nets /20 equiv MaxAgg Description
> 8151 1576 2899 232 UniNet S.A. de C.V.
> 10620 1004 224 130 TVCABLE BOGOTA
> 28573 832 674 85 NET Servicos de Comunicao S.A
> 7303 668 352 98 Telecom Argentina Stet-France
> 22047 546 302 14 VTR PUNTO NET S.A.
> 11830 472 308 59 Instituto Costarricense de El
> 6503 446 163 185 AVANTEL, S.A.
> 11172 444 99 69 Servicios Alestra S.A de C.V
> 14117 436 29 11 Telefonica del Sur S.A.
> 3816 431 193 69 Empresa Nacional de Telecomun
>
> Complete listing at http://thyme.apnic.net/current/data-ASnet-LACNIC
>
> AfriNIC Region per AS prefix count summary
> ------------------------------------------
>
> ASN No of nets /20 equiv MaxAgg Description
> 8452 1017 444 8 TEDATA
> 24863 719 143 53 LINKdotNET AS number
> 3741 273 857 233 The Internet Solution
> 2018 178 196 100 Tertiary Education Network
> 6713 177 167 12 Itissalat Al-MAGHRIB
> 29571 161 19 9 Ci Telecom Autonomous system
> 29975 134 506 15 Vodacom
> 33776 123 7 11 Starcomms Nigeria Limited
> 5536 121 8 18 Internet Egypt Network
> 5713 114 505 68 Telkom SA Ltd
>
> Complete listing at http://thyme.apnic.net/current/data-ASnet-AFRINIC
>
> Global Per AS prefix count summary
> ----------------------------------
>
> ASN No of nets /20 equiv MaxAgg Description
> 6389 4165 3891 301 bellsouth.net, inc.
> 4323 3783 1068 400 Time Warner Telecom
> 4766 1831 7509 473 Korea Telecom (KIX)
> 1785 1796 699 134 PaeTec Communications, Inc.
> 7018 1589 5791 1028 AT&T WorldNet Services
> 8151 1576 2899 232 UniNet S.A. de C.V.
> 20115 1537 1487 666 Charter Communications
> 17488 1464 144 140 Hathway IP Over Cable Interne
> 2386 1294 617 930 AT&T Data Communications Serv
> 4755 1281 289 144 TATA Communications formerly
>
> Complete listing at http://thyme.apnic.net/current/data-ASnet
>
> Global Per AS Maximum Aggr summary
> ----------------------------------
>
> ASN No of nets Net Savings Description
> 4323 3783 3383 Time Warner Telecom
> 1785 1796 1662 PaeTec Communications, Inc.
> 4766 1831 1358 Korea Telecom (KIX)
> 8151 1576 1344 UniNet S.A. de C.V.
> 17488 1464 1324 Hathway IP Over Cable Interne
> 11492 1154 1140 Cable One
> 4755 1281 1137 TATA Communications formerly
> 22773 1124 1058 Cox Communications, Inc.
> 18566 1059 1049 Covad Communications
> 8452 1017 1009 TEDATA
>
> Complete listing at http://thyme.apnic.net/current/data-CIDRnet
>
> List of Unregistered Origin ASNs (Global)
> -----------------------------------------
>
> Bad AS Designation Network Transit AS Description
> 16927 UNALLOCATED 12.0.252.0/23 7018 AT&T WorldNet
> Servic
> 15132 UNALLOCATED 12.9.150.0/24 7018 AT&T WorldNet
> Servic
> 32567 UNALLOCATED 12.14.170.0/24 7018 AT&T WorldNet
> Servic
> 13746 UNALLOCATED 12.24.56.0/24 7018 AT&T WorldNet
> Servic
> 32567 UNALLOCATED 12.25.107.0/24 7018 AT&T WorldNet
> Servic
> 26973 UNALLOCATED 12.39.152.0/24 7018 AT&T WorldNet
> Servic
> 26973 UNALLOCATED 12.39.154.0/23 7018 AT&T WorldNet
> Servic
> 26973 UNALLOCATED 12.39.159.0/24 7018 AT&T WorldNet
> Servic
> 32326 UNALLOCATED 12.40.49.0/24 7018 AT&T WorldNet
> Servic
> 25639 UNALLOCATED 12.41.169.0/24 7018 AT&T WorldNet
> Servic
>
> Complete listing at http://thyme.apnic.net/current/data-badAS
>
> Advertised Unallocated Addresses
> --------------------------------
>
> Network Origin AS Description
> 2.0.0.0/16 12654 RIPE NCC RIS Project
> 2.1.0.0/21 12654 RIPE NCC RIS Project
> 2.1.24.0/24 12654 RIPE NCC RIS Project
> 41.78.60.0/22 6762 Telecom Italia international
> 41.223.92.0/22 36936 >>UNKNOWN<<
> 41.223.188.0/24 22351 Intelsat
> 41.223.189.0/24 26452 Local Communications Networks
> 46.0.0.0/16 12654 RIPE NCC RIS Project
> 46.1.0.0/21 12654 RIPE NCC RIS Project
> 46.1.24.0/24 12654 RIPE NCC RIS Project
>
> Complete listing at http://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:21 /9:10 /10:25 /11:65 /12:181
> /13:382 /14:654 /15:1233 /16:10850 /17:5053 /18:8622
> /19:17725 /20:21661 /21:21549 /22:27892 /23:28054 /24:160791
> /25:915 /26:1147 /27:584 /28:221 /29:11 /30:8
> /31:0 /32:8
>
> Advertised prefixes smaller than registry allocations
> -----------------------------------------------------
>
> ASN No of nets Total ann. Description
> 6389 2723 4165 bellsouth.net, inc.
> 4323 2369 3783 Time Warner Telecom
> 4766 1476 1831 Korea Telecom (KIX)
> 1785 1263 1796 PaeTec Communications, Inc.
> 17488 1230 1464 Hathway IP Over Cable Interne
> 11492 1074 1154 Cable One
> 18566 1040 1059 Covad Communications
> 7018 960 1589 AT&T WorldNet Services
> 8452 913 1017 TEDATA
> 18101 913 1033 Reliance Infocom Ltd Internet
>
> Complete listing at http://thyme.apnic.net/current/data-sXXas-nos
>
> Number of /24s announced per /8 block (Global)
> ----------------------------------------------
>
> 2:1 4:13 8:242 12:2007 13:9 15:22
> 16:3 17:8 20:38 24:1301 32:49 38:635
> 40:99 41:1881 44:3 46:1 47:29 52:6
> 55:2 56:2 57:23 58:640 59:596 60:446
> 61:968 62:956 63:2005 64:3774 65:2358 66:4100
> 67:1841 68:1047 69:2832 70:688 71:231 72:1878
> 73:3 74:2075 75:225 76:359 77:871 78:604
> 79:406 80:961 81:803 82:469 83:440 84:521
> 85:1015 86:376 87:692 88:433 89:1561 90:65
> 91:2674 92:434 93:1151 94:1293 95:799 96:194
> 97:290 98:488 99:23 109:206 110:263 111:413
> 112:168 113:216 114:304 115:404 116:1126 117:596
> 118:380 119:812 120:141 121:684 122:1385 123:830
> 124:1029 125:1305 128:198 129:203 130:134 131:461
> 132:84 133:16 134:193 135:41 136:228 137:175
> 138:236 139:81 140:462 141:121 142:377 143:349
> 144:393 145:51 146:390 147:175 148:565 149:196
> 150:151 151:172 152:225 153:162 154:2 155:270
> 156:178 157:329 158:98 159:355 160:304 161:175
> 162:271 163:189 164:309 165:472 166:493 167:387
> 168:758 169:158 170:568 171:42 172:1 173:425
> 174:519 175:20 180:273 183:200 184:3 186:258
> 187:211 188:1138 189:615 190:3423 192:5722 193:4390
> 194:3352 195:2786 196:1192 198:3550 199:3390 200:5256
> 201:1450 202:8076 203:8300 204:3981 205:2167 206:2401
> 207:3042 208:3924 209:3394 210:2518 211:1170 212:1657
> 213:1650 214:248 215:58 216:4425 217:1390 218:481
> 219:416 220:1137 221:461 222:303
>
> End of report
>
>
>
> ------------------------------
>
> _______________________________________________
> afnog mailing list
>
> End of afnog Digest, Vol 70, Issue 10
> *************************************
>
--
Liban Mohamed
Global One Solution
www.globalonesolutions.net
CCIE#22493
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://afnog.org/pipermail/afnog/attachments/20100108/4f30904c/attachment-0001.htm>
More information about the afnog
mailing list