1<!DOCTYPE html> 2<html lang="en"> 3<head> 4 <meta charset="utf-8" /> 5 <title>Europe | FogIXP</title> 6 7 <meta http-equiv="X-UA-Compatible" content="IE=edge"> 8 <meta name="viewport" content="width=device-width, initial-scale=1"> 9 <meta name="generator" content="GravCMS" /> 10 <meta name="description" content="FogIXP. An IXP in the Fog. A bit unclear." /> 11 12 <link rel="icon" type="image/png" href="/user/themes/quark/images/favicon.png" /> 13 <link rel="canonical" href="https://fogixp.org/our-ixps/europe" /> 14 15 16 17 <link href="/user/plugins/markdown-notices/assets/notices.css" type="text/css" rel="stylesheet"> 18<link href="/user/plugins/form/assets/form-styles.css" type="text/css" rel="stylesheet"> 19<link href="/user/plugins/login/css/login.css" type="text/css" rel="stylesheet"> 20<link href="/user/themes/quark/css-compiled/spectre.min.css" type="text/css" rel="stylesheet"> 21<link href="/user/themes/quark/css-compiled/theme.min.css" type="text/css" rel="stylesheet"> 22<link href="/user/themes/quark/css/custom.css" type="text/css" rel="stylesheet"> 23<link href="/user/themes/quark/css/line-awesome.min.css" type="text/css" rel="stylesheet"> 24 25
25<script src="/system/assets/jquery/jquery-3.x.min.js"></script>
vendor: 1 bytes, line 25
25
26<script> 27//<!-- Piwik --> 28 var _paq = _paq || []; 29 // tracker methods like "setCustomDimension" should be called before "trackPageView" 30 _paq.push(['trackPageView']); 31 _paq.push(['enableLinkTracking']); 32 (function() { 33 var u="//analytics.ifog.ch//"; 34 _paq.push(['setTrackerUrl', u+'piwik.php']); 35 _paq.push(['setSiteId', '21']); 36 var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0]; 37 g.type='text/javascript'; g.async=true; g.defer=true; g.src=u+'piwik.js'; s.parentNode.insertBefore(g,s); 38 })(); 39</script>
39 40<!-- Piwik Image Tracker--> 41<noscript><img src="//analytics.ifog.ch//piwik.php?idsite=21&rec=1" style="border:0" alt="" /></noscript> 42<!-- End Piwik -->
43<script type="text/javascript"> 44</script>
44 45 46</head> 47<body id="top" class=" header-fixed header-animated sticky-footer"> 48 <div id="page-wrapper"> 49 <section id="header" class="section"> 50 <section class="container grid-lg"> 51 <nav class="navbar"> 52 <section class="navbar-section logo"> 53 <a href="/" class="navbar-brand mr-10"> 54 <img src="/user/themes/quark/images/logo/fogixp - v4 -t.png" alt="FogIXP" /> 55</a> </section> 56 <section class="navbar-section desktop-menu"> 57 58 <nav class="dropmenu animated"> 59 60<ul > 61 <li> 62 <a href="/" class=""> 63 Home 64 </a> 65 </li> 66 <li> 67 <a href="/our-ixps" class="active"> 68 Our IXPs 69 </a> 70 <ul> 71 <li> 72 <a href="/our-ixps/europe" class="active"> 73 Europe 74 </a> 75 </li> 76 <li> 77 <a href="/our-ixps/frankfurt" class=""> 78 Frankfurt 79 </a> 80 </li> 81 <li> 82 <a href="/our-ixps/amsterdam" class=""> 83 Amsterdam 84 </a> 85 </li> 86 <li> 87 <a href="/our-ixps/zuerich" class=""> 88 Zürich 89 </a> 90 </li> 91 92 </ul> 93 </li> 94 <li> 95 <a href="/news" class=""> 96 News 97 </a> 98 </li> 99 <li> 100 <a href="/members" class=""> 101 Members 102 </a> 103 <ul> 104 <li> 105 <a href="/members/member-list-europe" class=""> 106 Member List - Europe 107 </a> 108 </li> 109 <li> 110 <a href="/members/member-list-fra" class=""> 111 Member List - FRA 112 </a> 113 </li> 114 <li> 115 <a href="/members/member-list-ams" class=""> 116 Member List - AMS 117 </a> 118 </li> 119 <li> 120 <a href="/members/member-list-zrh" class=""> 121 Member List - ZRH 122 </a> 123 </li> 124 125 </ul> 126 </li> 127 128</ul> 129 130 </nav> 131 132 133 </section> 134 </nav> 135 </section> 136 </section> 137 <div class="mobile-menu"> 138 <div class="button_container" id="toggle"> 139 <span class="top"></span> 140 <span class="middle"></span> 141 <span class="bottom"></span> 142 </div> 143 </div> 144 145 146 <section id="start"> 147 <section id="body-wrapper" class="section"> 148 <section class="container grid-lg"> 149 150 <h2>FogIXP Europe</h2> 151<p>FogIXP Europe is a distributed IXP operated by iFog GmbH with multiple POPs connected over a L2 VPLS, Waves and DF. Some L2 is donated by a generous sponsor and the Waves, Dark Fiber and L2 are provided by iFog. 152Originally build as a Peering LAN for customers only, now open to everyone! </p> 153<p><strong>Joining requirements:</strong> </p> 154<p>-Have a valid public ASN<br /> 155-Announce at minimum one IPv6 prefix<br /> 156-Have up-to-date PeeringDB information (preferably)<br /> 157-Have up-to-date RIR Whois information<br /> 158-Only send traffic to destinations advertised by BGP on the Peering LAN<br /> 159-Does not send any multicast (except ARP/IPv6 ND) packets<br /> 160-Will not advertise the FogIXP addressing space outside of the FogIXP infrastructure.<br /> 161-Will not abuse or use the Peering LAN for commercial services, eg. providing transit.<br /> 162-The my.ifog.ch account is in good standing.<br /> 163-Will not tunnel out the peering port or peering lan.<br /> 164-MTU on the client interface must be at least 1500. </p> 165<p><strong>Current PoP:</strong><br /> 166-NTT ZRH1 / iFog Switzerland (Core)<br /> 167-Interxion ZRH1 (Core)<br /> 168-ColoZüri (Core)<br /> 169-NIKHEF Amsterdam (room H140) (Core)<br /> 170-Interxion AMS17 / iFog Amsterdam (Core)<br /> 171-Cogent Halfweg Amsterdam (Core)<br /> 172-NTT FRA1 / iFog Frankfurt (Core)<br /> 173-Interxion Campus Frankfurt (Core)<br /> 174-iFog London (Core)<br /> 175-NTT Vienna 1 (Extension)<br />
176-iFog Barcelona / bitNAP (Extension)<br /> 177-iFog Norway (Extension) </p> 178<p><strong>Planned PoP:</strong><br /> 179Want to sponsor a location? - Contact us!</p> 180<p><strong>Ports:</strong><br /> 181-Until further notice 1/10GbE ports are free of cost in core locations.<br /> 182-1/10GbE ports in Extension locations are charged with a MRC or NRC fee.<br /> 183-Note that in NTT and Interxion we charge a one-time setup fee for cabling.<br /> 184-NO SLA is given on any port.<br /> 185-One port per organisation, exceptions are made on a case-by-case basis.<br /> 186-One peer per physical connection/port/vlan.<br /> 187-If the ASN requesting to join has no IPv4 prefixes announced, only IPv6 - only an IPv6 peering IP will be allocated.<br /> 188-For physical connections, bring your own optic or DAC and FogIXP does not cover the cost for the crossconnect.<br /> 189-Locations connected via extension switch may only be available from a specific access partner.<br /> 190-FogIXP is also avilable on <a href="https://ifog.ch/en/server">iFog Colocation, Dedicated and VMs</a> in Zurich, Frankfurt, Amsterdam, London. </p> 191<p><strong>Joining:</strong><br /> 192-If youâre interested in joining FogIXP, please open a request below.<br /> 193-Find our member list <a href="https://manager.fogixp.org/customer/details">here</a>.</p> 194<p><a href="https://fogixp.org/our-ixps/europe/request" type="button" class="btn btn-primary">Join FogIXP Europe</a></p> 195<hr /> 196<p></br></p> 197<p><strong>FAQ:</strong><br /> 198Q: Are there Route Servers?<br /> 199A: Yes!<br /> 200RS1: <em>AS47498 - 185.1.147.111 - 2001:7f8:ca:1::111</em><br /> 201RS2: <em>AS47498 - 185.1.147.222 - 2001:7f8:ca:1::222</em><br /> 202RS3: <em>AS47498 - 185.1.147.3 - 2001:7f8:ca:1::333</em> </p> 203<p>Q: Are there BGP Communities for the Route Servers?<br /> 204A: Yes!<br /> 2053x pre-pend to peer: <em>47498:103:peerasn</em><br /> 2062x pre-pend to peer: <em>47498:102:peerasn</em><br /> 2071x pre-pend to peer: <em>47498:101:peerasn</em><br /> 208Do-Not-Export to peer: <em>0:peerasn</em> </p> 209<p>Q: Can I have a second port?<br /> 210A: Additional ports are provided on a case-by-case basis, additional ports in different locations are only granted to networks with their own backbone. </p> 211<p>Q: Can i join over a tunnel?<br /> 212A: No! We dont support tunnels of any kind. You may connect over a crossconnect in one of the location FogIXP is present.</p> 213<p>Q: Why yet another IXP?<br /> 214A: Long story short: We do not aim to compete with other IXPs.<br /> 215FogIXP is an L2 Peering LAN that was originally thought to be an alternative to building dozen of P2P and shared VLANs between customers and networks in on-net networks for BGP peerings. As the idea grew in our social circle, other networks who are in the same DCs wanted to join, hence it's now an IXP where everyone is welcome (see rules). </p> 216<p>Q: Can i become a Partner/Reseller?<br /> 217A: Yes, you may reach out to us after reading our <a href="https://fogixp.org/access-partner-guidelines">Access Partner Guidelines</a>. </p> 218<hr /> 219<p></br></p> 220<p><strong>Architecture:</strong><br /> 221Currently there are three switches in Amsterdam, Frankfurt, Zurich connected over a L2 and Waves. Extension switchs are connected over a L2 or XC to the core Peering LAN.</p> 222 223 </section> 224 </section> 225 </section> 226 227 </div> 228 229 <section id="footer" class="section bg-gray"> 230 <section class="container grid-lg"> 231 <p>FogIXP by <a href="https://ifog.ch">iFog GmbH</a>.</p> 232 </section> 233</section> 234 235 <div class="mobile-container"> 236 <div class="overlay" id="overlay"> 237 <div class="mobile-logo"> 238 <a href="/" class="navbar-brand mr-10"> 239 <img src="/user/themes/quark/images/logo/fogixp - v4 -t.png" alt="FogIXP" /> 240</a> </div> 241 <nav class="overlay-menu"> 242 243<ul class="tree"> 244 <li> 245 <a href="/" class=""> 246 Home 247 </a> 248 </li> 249 <li> 250 <a href="/our-ixps" class="active"> 251 Our IXPs 252 </a> 253 <ul> 254 <li> 255 <a href="/our-ixps/europe" class="active"> 256 Europe 257 </a> 258 </li> 259 <li> 260 <a href="/our-ixps/frankfurt" class=""> 261 Frankfurt 262 </a> 263 </li> 264 <li> 265 <a href="/our-ixps/amsterdam" class=""> 266 Amsterdam 267 </a> 268 </li> 269 <li> 270 <a href="/our-ixps/zuerich" class=""> 271 Zürich 272 </a> 273 </li> 274 275 </ul> 276 </li> 277 <li> 278 <a href="/news" class=""> 279 News 280 </a> 281 </li> 282 <li> 283 <a href="/members" class=""> 284 Members 285 </a> 286 <ul> 287 <li> 288 <a href="/members/member-list-europe" class=""> 289 Member List - Europe 290 </a> 291 </li> 292 <li> 293 <a href="/members/member-list-fra" class=""> 294 Member List - FRA 295 </a> 296 </li> 297 <li> 298 <a href="/members/member-list-ams" class=""> 299 Member List - AMS 300 </a> 301 </li> 302 <li> 303 <a href="/members/member-list-zrh" class=""> 304 Member List - ZRH 305 </a> 306 </li> 307 308 </ul> 309 </li> 310 311</ul> 312 313 </nav> 314 </div> 315 </div> 316 317
317<script src="/user/themes/quark/js/jquery.treemenu.js"></script>
vendor: 1 bytes, line 317
317
318<script src="/user/themes/quark/js/site.js"></script>
318 319 320 321</body> 322</html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.