Skip to main content

AS215956

MYIP-AS

MyIP.be ~ AS215956

Registry

Authoritative registration data

AS number
215956
Name
MYIP-AS
Organisation
MyIP.be ~ AS215956
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

31

Total announced

31

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS215956
2a0e:8f02:2270::/44 IPv6 /44 not checked
2a0e:b107:1194::/46 IPv6 /46 not checked
2a14:7580:ed00::/46 IPv6 /46 not checked
2a14:7580:ed08::/46 IPv6 /46 not checked
2a14:7580:ed0c::/46 IPv6 /46 not checked
2a14:7580:ed10::/46 IPv6 /46 not checked
2a14:7580:ed14::/46 IPv6 /46 not checked
2a14:7580:ed44::/46 IPv6 /46 not checked
2a14:7580:ed54::/46 IPv6 /46 not checked
2a14:7580:ed5c::/46 IPv6 /46 not checked
2a14:7580:edf0::/46 IPv6 /46 not checked
2a0e:b107:1190::/47 IPv6 /47 not checked
2a0e:b107:1192::/47 IPv6 /47 not checked
2a14:7580:ed40::/47 IPv6 /47 not checked
2a14:7580:ed50::/47 IPv6 /47 not checked
2a14:7580:ed60::/47 IPv6 /47 not checked
2a14:7580:ed62::/47 IPv6 /47 not checked
2a14:7580:ed64::/47 IPv6 /47 not checked
2a14:7580:edc0::/47 IPv6 /47 not checked
2a14:7580:edc2::/47 IPv6 /47 not checked
2001:67c:688::/48 IPv6 /48 not checked
2a14:7580:ee00::/48 IPv6 /48 not checked
2a14:7580:ee02::/48 IPv6 /48 not checked
2a14:7580:ee04::/48 IPv6 /48 not checked
2a14:7580:ee05::/48 IPv6 /48 not checked
2a14:7580:ee07::/48 IPv6 /48 not checked
2a14:7580:ee08::/48 IPv6 /48 not checked
2a14:7580:ee09::/48 IPv6 /48 not checked
2a14:7580:ee0a::/48 IPv6 /48 not checked
2a14:7580:ee0c::/48 IPv6 /48 not checked
2a14:7580:ee0f::/48 IPv6 /48 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS215956
Address families
4b42 Internet Exchange Point: Switzerland 1,000 Mbps IPv6
AMS-IX 1,000 Mbps IPv6
BGP.Exchange - Amsterdam 2,500 Mbps IPv6
BGP.Exchange - Barcelona 1,000 Mbps IPv6
BGP.Exchange - Chicago 100 Mbps IPv6
BGP.Exchange - Dallas 11,000 Mbps IPv6
BGP.Exchange - Dusseldorf 11,000 Mbps IPv6
BGP.Exchange - Frankfurt 11,500 Mbps IPv6
BGP.Exchange - Fremont 1,000 Mbps IPv6
BGP.Exchange - Hong Kong 20,000 Mbps IPv6
BGP.Exchange - London 1,700 Mbps IPv6
BGP.Exchange - Los Angeles 3,000 Mbps IPv6
BGP.Exchange - Lyon 1,000 Mbps IPv6
BGP.Exchange - Miami 1,100 Mbps IPv6
BGP.Exchange - New York 1,000 Mbps IPv6
BGP.Exchange - Paris 100 Mbps IPv6
BGP.Exchange - Rome 1,000 Mbps IPv6
BGP.Exchange - Zurich 11,500 Mbps IPv6
DataSphere Internet Exchange (Hong Kong) 10,000 Mbps IPv6
EVIX: Peering LAN 2,500 Mbps IPv6
FogIXP 2,000 Mbps IPv6
HN Internet Exchange (Main) 10,000 Mbps IPv6
IXP FI HEL: Finland 1,000 Mbps IPv6
IXP LI VAD: Main 1,000 Mbps IPv6
IXP NL DRO: Indonesia 100 Mbps IPv6
IXP UK LON: United Kingdom 500 Mbps IPv6
Lynqia IX Vilnius 1,000 Mbps IPv6
NorthIX 1,000 Mbps IPv6
ONIX 1,000 Mbps IPv6
PeersIX Amsterdam 3,000 Mbps IPv6
Poema IX 500 Mbps IPv6
Protocol 7 IX - Hong Kong 10,000 Mbps IPv6
ZXIX Hong Kong 10,000 Mbps IPv6

No rows match “”.

Showing of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS215956 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

29 networks seen before AS215956 in AS paths

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS215956 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

53 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.