AS21501 MAINLAB-AS Autonomous System Mainlab GmbH, Germany See www.mainlab.net or www.rackbase.com
 aut-num: AS21501 as-name: MAINLAB-AS descr: Autonomous System Mainlab GmbH, Germany descr: See www.mainlab.net or www.rackbase.com remarks: ----------------------------------------------------- remarks: SPAM/ABUSE mailto: SPAMabuse(at)mainlab.de remarks: complaints to any other addresses will be discarded remarks: ----------------------------------------------------- remarks: Peering Questions ? mailto: SPAMpeering(at)mainlab.de remarks: Peerings at FraNAP www.FraNAP.net welcome :-) remarks: If you would like to peer at the DE-CIX please have a remarks: look at our partner BELLAXA NETWORKS (AS34088). remarks: Available at InterXion & RedBus, Frankfurt, Germany remarks: ----------------------------------------------------- remarks: Our 24/7/365 emergency contact / NOC remarks: is mailto: SPAMnoc(at)mainlab.de remarks: remove SPAM before sending messages of course! remarks: ----------------------------------------------------- remarks: remarks: remarks: ----------------------------------------------------- remarks: UPSTREAMS remarks: ----------------------------------------------------- remarks: remarks: BELLAXA NETWORKS GMBH AS34088 remarks: is supplying us with the following upstreams: remarks: DEUTSCHE TELEKOM / AS3320 remarks: LAMBDANET / AS13237 remarks: LEVEL3,MESH / AS3356,AS25074 remarks: and a lot of peers... import: from AS34088 accept ANY export: to AS34088 announce AS-MAINLAB remarks: See AS34088 too - it's our affiliate :-) remarks: remarks: TELIA Sonera International Carrier AS1299 import: from AS1299 accept ANY export: to AS1299 announce AS-MAINLAB remarks: remarks: TISCALI AS3257 import: from AS3257 accept ANY export: to AS3257 announce AS-MAINLAB remarks: remarks: regio.net AS8804 import: from AS8804 accept ANY export: to AS8804 announce AS-MAINLAB remarks: remarks: ----------------------------------------------------- remarks: PEERS remarks: ----------------------------------------------------- remarks: remarks: remarks: Internal connection to MAINLAB AS in AMSTERDAM, NL import: from AS35329 accept ANY export: to AS35329 announce ANY remarks: remarks: ##### FraNAP ##### remarks: MPLA with AS24876 at FraNAP - www.FraNAP.net remarks: We're peering with a lot of ASes via the routeserver import: from AS24876 accept AS-FRANAP export: to AS24876 announce AS-MAINLAB remarks: remarks: remarks: ----------------------------------------------------- remarks: DOWNSTREAMS remarks: ----------------------------------------------------- remarks: remarks: CUST-HS AS29140 import: from AS29140 accept AS29140 export: to AS29140 announce ANY remarks: remarks: FraNAP AS24876 - the FraNAP itself import: from AS24876 accept AS24876 export: to AS24876 announce ANY remarks: remarks: CUST-BIO AS34531 import: from AS34531 accept AS-BIOS export: to AS34531 announce ANY remarks: remarks: CUST-PIT AS47488 import: from AS47488 accept AS47488 export: to AS47488 announce ANY remarks: remarks: remarks: ----------------------------------------------------- remarks: remarks: BGP-COMMUNITIES - FOR OUR IP-TRANSIT/BGP CUSTOMERS remarks: ----------------------------------------------------- remarks: UPSTREAM-Codes (abc) 200 to 299 remarks: 200 = MAINLAB AMSTERDAM remarks: 201 = TELIA remarks: 202 = BELLAXA NETWORKS remarks: 203 = DTAG remarks: 204 = TISCALI remarks: 205 = REGIONET remarks: ----------------------------------------------------- remarks: ORIGIN-Communities (tags routes you receive from us) remarks: read community 21501:40abc remarks: remarks: with abc = Upstream-code (see above) remarks: or one of the following more abstract codes: remarks: 100 = prefixes announced by AS21501/"static customers" remarks: 101 = prefixes received from BGP customers remarks: 111 = OUR prefixes (100 and 101) remarks: 120 = prefixes received from UPSTREAMS remarks: 121 = prefixes received from PEERS remarks: 333 = prefixes we can reach and route BEST remarks: ----------------------------------------------------- remarks: PREPEND-Communities (you can tag routes we receive) remarks: remarks: Prepend communities to modify announcements to peers remarks: set community 21501:3abcn remarks: remarks: with abc = Upstream-code (see above) remarks: or abc = 120 for all UPSTREAMS remarks: or abc = 121 for all PEERS remarks: remarks: with n = 0,1,2,3 meaning remarks: n = 0 do not announce to peer remarks: n = 1 prepend "AS21501" remarks: n = 2 prepend "AS21501 AS21501" remarks: n = 3 prepend "AS21501 AS21501 AS21501" remarks: ...in addition to possibly pre-defined prepends. remarks: ----------------------------------------------------- remarks: BLACKHOLE-Communities remarks: Blackhole a prefix so that it get's blocked within remarks: our backbone and maybe at our upstream's backbone. remarks: You can announce prefixes up to /32s that are within remarks: your own netblocks (le 32 match) remarks: remarks: set community 21501:666 remarks: It is your own responsibility to remove the blackhole remarks: community after the (D)DOS-attack has been stopped! remarks: BLACKHOLE COMMUNITY NOT YET READY! remarks: ----------------------------------------------------- admin-c: MADM-RIPE tech-c: MLAB-RIPE mnt-by: MAINLAB-MNT mnt-routes: MAINLAB-MNT changed: hostmaster(at)ripe.net 20020104 changed: NOSPAMgs(at)mainlab.de 20020803 changed: NOSPAMgs(at)mainlab.de 20021223 changed: NOSPAMgs(at)mainlab.de 20030331 changed: NOSPAMgs(at)mainlab.de 20030801 changed: NOSPAMgs(at)mainlab.de 20040219 changed: NOSPAMgs(at)mainlab.de 20050313 changed: NOSPAMgs(at)mainlab.de 20050520 changed: NOSPAMgs(at)mainlab.de 20050721 changed: NOSPAMgs(at)mainlab.de 20050721 changed: NOSPAMgs(at)mainlab.de 20051128 changed: NOSPAMgs(at)mainlab.de 20060116 changed: NOSPAMgs(at)mainlab.de 20060213 changed: NOSPAMgs(at)mainlab.de 20060819 changed: NOSPAMgs(at)mainlab.de 20070515 changed: NOSPAMgs(at)mainlab.de 20071102 changed: NOSPAMgs(at)mainlab.de 20080126 changed: NOSPAMgs(at)mainlab.de 20080903 changed: NOSPAMgs(at)mainlab.de 20080904 changed: NOSPAMpg(at)mainlab.de 20081128 source: RIPE
| in bgp | route record | prefix | description |
|---|
| | 80.242.128.0/19 | MAIN-Route for our allocation 80-242-128-0---slash19 | | (unannounced) | AS21501
| 80.242.128.0/20 | DE-MAINLAB-80-242-128-0---slash-20 www.Mainlab.net - abuse@mainlab.de Peering ? Ask peering@mainlab.de | | | 80.242.130.0/24 | DE-MAINLAB-80-242-130-0---slash-24 www.Mainlab.net - abuse@mainlab.de Peering ? Ask peering@mainlab.de | | | 89.19.224.0/19 | MAIN-Route for our allocation 89-19-224-0---slash19 www.Mainlab.net - NOSPAMabuse@mainlab.de Peering ? Ask NOSPAMpeering@mainlab.de Our 24/7/365 emergency contact / NOC is NOSPAMnoc@mainlab.de | | | 89.207.248.0/21 | Viprinet GmbH | | | 193.36.227.0/24 | www.server-4-gamer.de | | | 195.66.102.0/24 | RACKBASE-KN-PISPACE 195.66.102.0---slash24 | | | 195.245.104.0/23 | formativ.net | | (unannounced) | AS21501
| 195.245.104.0/24 | formativ.net | | (unannounced) | AS21501
| 195.245.105.0/24 | formativ.net |
Peer and upstream distributionThe information on these tabs was generated on Thu, 19 Nov 2009, the underlying information might be older
We are working to improve the freshness, thank you for your patience
 Brief information | |
randomdate20091125 rtsakmarka rtsakmark2