User Tools

Site Tools


page:network

Network

Looking glass: here

Statistics (IPv6 only)

Daily/Weekly/Monthly/Yearly

Warsaw node:

Frankfurt node:

KleyRex node:

AS-IX node:

Moscow node:

London node:

Session list

Peering partner ASN Type Protocol Encap. Where
Hurricane Electric, Inc. 6939 Full Upstream IPv6 Direct KleyRex and AS-IX
Init7 (Switzerland) Ltd. 13030 Full Upstream IPv6 Sit Frankfurt and Warsaw
Choopa LLC 20473 Full Upstream IPv6 Direct Frankfurt
IP-Max SA 25091 Full Upstream IPv6 Sit Frankfurt
Radom IXP 58307 Full Upstream IPv6 Gre Warsaw
United Peering UPIXP 8268 Full Upstream IPv6 Sit Frankfurt
Melbikomas UAB 56630 Full Upstream IPv6 Direct Moscow
VMHaus Network 136620 Full Upstream IPv6 Direct London
Bodems 200490 Peering IPv6 Sit Frankfurt
SNAPSERV LTD 200753 Peering IPv6 Sit Frankfurt
aaNetworks 207036 Peering IPv6 Sit and Direct Frankfurt and KleyRex
Zaledia.com networks 207149 Peering IPv6 Sit Frankfurt
M-M-NETWORKS.NET 206499 Peering IPv6 Sit Frankfurt
Jan-Philipp Benecke 206479 Peering IPv6 Gre and Direct Frankfurt and AS-IX
Joey-Network 49697 Peering IPv6 Direct KleyRex
Marek-Krolikowski 205593 Peering IPv6 Direct KleyRex and AS-IX
oja.at GmbH 39912 Peering IPv6 Direct KleyRex
MK Netz. GmbH & Co. KG 25394 Peering IPV6 Direct KleyRex
CloudFlare, Inc. 13335 Peering IPv6 Direct KleyRex
Patrick Velder 62078 Peering IPv6 Direct KleyRex
Google Inc. 15169 Peering IPv6 Direct KleyRex
Basil-Fillan 207080 Peering IPv6 Direct KleyRex
TOMMYBOWDITCH 51391 Peering IPv6 Direct KleyRex
Packet Brewery 205446 Peering IPv6 Direct KleyRex
Mitsuha Networks 205590 Peering IPv6 Direct KleyRex
Thomas Glass 205777 Peering IPv6 Direct KleyRex
Freifunk Nordwest e.V. 206313 Peering IPv6 Direct KleyRex
VMHaus Network 136620 Peering IPv6 Direct KleyRex
Zxity Ltd 205942 Peering IPv6 Direct KleyRex
Mr Florian Riehm 57821 Peering IPv6 Direct KleyRex
AS-IX route server peers 41441 Peering IPv6 Direct AS-IX
Jacob Slater 203729 Peering IPv6 Direct KleyRex
DARZ GmbH 201213 Peering IPv6 Direct KleyRex
Netwerkvereniging Coloclue 8283 Peering IPv6 Direct AS-IX
Comsave BV 202120 Peering IPv6 Direct AS-IX
JSR IT B.V. 202796 Peering IPv6 Direct AS-IX
Servperso-Systems 205523 Peering IPv6 Direct KleyRex
myLoc managed IT AG 24961 Peering IPv6 Direct AS-IX
KleyReX Internet Exchange 31142 Peering IPv6 Direct KleyRex
Krzysztof Krych 205036 Peering IPv6 Direct KleyRex
Metaliance ISP Systems e.k 205388 Peering IPv6 Direct KleyRex

Legend

  • Full Upstream - We getting full BGP table from that peer
  • Peering - Depends, mostly clear peering between ASNs but it can be also a little transit in both ways but not full table
  • Warsaw - BGP session established on e-utp.net's Warsaw node
  • Frankfurt - BGP session established on e-utp.net's Frankfurt node
  • Moscow - BGP session established on e-utp.net's Moscow node
  • London - BGP session established on e-utp.net's London node
  • KleyRex - BGP session established on e-utp.net's KleyRex node
  • AS-IX - BGP session established on e-utp.net's AS-IX node

Peering policy

AS56662 has an open peering policy, however we do have several basic requirements.

Peering requirements

  • Route exchanges are done via BGPv4
  • Technical contact information must be provided
  • AS56662 requires that peers announce the same routing policy at all points where they peer with us, unless other arrangements are made
  • Peers must enforce strict filtering policies to prevent route leaks
  • Peers must cooperate in the troubleshooting of any peering related issues, denial of service attacks, UCE, hacking or virus penetration
  • Peers are prohibited from abusing our peering relationship by pointing default or resetting any next-hop
  • Peers are requested to peer at all common peering points
  • AS56662 reserves the right to not peer with anyone as we see fit and to terminate any peering at any time with 30 days notice.
  • AS56662 reserves the right to change this policy with 30 days notice
  • Whenever two peering contacts meet in person they are encouraged to raise glases in a toast to their successful peering

Requesting peering to AS56662

An ISP seeking peering should submit its request in writing via email providing the following information:

  • A brief description of its network (we just want to know who you are)
  • Peering-point(s) [IPv6-in-IPv4 tunnel / GRE] or KleyRex or AS-IX
  • AS-Number
  • AS-set (if available)
  • Prefix limit we should use
  • Contact data

Applications for peering should be submitted to email.

page/network.txt ยท Last modified: 2017/12/11 15:08 by drixter

Page Tools