IP.CC
搜索
IP地址详细信息
AS47184
France-IX Toulouse ·www.franceix.net
IP地址详细信息
AS47184
France-IX Toulouse ·www.franceix.net
  • 摘要 IP.CC
  • 前缀
  • 同行
  • 上游
  • 下游
  • 世界地图
  • WHOIS详细信息
  • IX

摘要

  • ASN编号
    AS47184
  • 组织名称
    France-IX Toulouse
  • 国家
    France
  • 国家编码
    FR
  • 站点
  • 区域登记
    RIPE
  • 分配日期
    24th September 2009
  • 分配状态
    Allocated
  • Ipv4前缀
    0
  • Ipv6前缀
    0
  • Ipv4同行
    0
  • Ipv6同行
    0
  • Ipv4上游
    0
  • Ipv6上游
    0

前缀

此 ASN 有 0 个 IPv4 前缀。

国家
公布的前缀
描述
父前缀
RIR
暂无数据
  • 1
IP范围API
使用IP信息强大的IP范围 API获取这些数据和更多信息-快速轻松地识别公司拥有的IP范围。
有用的 游戏技术, 和 广告技术
IP范围API
使用IP信息强大的IP范围 API获取这些数据和更多信息-快速轻松地识别公司拥有的IP范围。
有用的 游戏技术, 和 广告技术

同行

此 ASN 有 0 个 IPv4 对等点。

国家
ASN
描述
IPv6
暂无数据
  • 1
ASN 数据
每个IP地址和每个ASN相关域的ASN详细信息、分配日期、注册表名称、IP地址总数和分配的前缀。
有用的 网络安全
ASN 数据
每个IP地址和每个ASN相关域的ASN详细信息、分配日期、注册表名称、IP地址总数和分配的前缀。
有用的 网络安全

上游

此 ASN 有 0 个 IPv4 上游。

国家
ASN
描述
IPv6
暂无数据
  • 1
ASN 数据
每个IP地址和每个ASN相关域的ASN详细信息、分配日期、注册表名称、IP地址总数和分配的前缀。
有用的 网络安全
ASN 数据
每个IP地址和每个ASN相关域的ASN详细信息、分配日期、注册表名称、IP地址总数和分配的前缀。
有用的 网络安全

下游

此 ASN 有 0 个 IPv4 下游。

国家
ASN
描述
IPv6
暂无数据
  • 1
ASN 数据
每个IP地址和每个ASN相关域的ASN详细信息、分配日期、注册表名称、IP地址总数和分配的前缀。
有用的 网络安全
ASN 数据
每个IP地址和每个ASN相关域的ASN详细信息、分配日期、注册表名称、IP地址总数和分配的前缀。
有用的 网络安全

世界地图

WHOIS详细信息

% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See https://docs.db.ripe.net/terms-conditions.html

% Information related to 'AS47184'

% Abuse contact for 'AS47184' is '[email protected]'

aut-num: AS47184
as-name: TOUIX-AS
descr: France-IX Toulouse
descr: Previously known as TOUIX/TOUlouse Internet eXchange
org: ORG-TA434-RIPE
remarks: -----------------------------------------------------
remarks: The following communities can be used by members on our Route-Servers:
remarks: *****************************************************
remarks: ** Note: These communities are evaluated
remarks: ** on a "first match win" basis
remarks: *****************************************************
remarks: 0:peer-as = Don't send route to this peer as
remarks: 47184:peer-as = Send route to this peer as
remarks: 0:47184 = Don't send route to any peer
remarks: 47184:47184 = Send route to all peers (applied by default)
remarks: *****************************************************
remarks: CDN Control:
remarks: 40027:40000 - DO announce to Netflix OpenConnect Appliance in Marseille
remarks: *****************************************************
remarks: 65101:peer-as = Prepend 1x to this peer
remarks: 65102:peer-as = Prepend 2x to this peer
remarks: 65103:peer-as = Prepend 3x to this peer
remarks: 65201:peer-as = Set MED 50 to this peer
remarks: 65202:peer-as = Set MED 100 to this peer
remarks: 65203:peer-as = Set MED 200 to this peer
remarks: -----------------------------------------------------
remarks: Set peer-as value as listed below for 32 bits ASNs:
remarks: AS197422 -> AS64701 (Tetaneutral)
remarks: AS206059 -> AS64816 (Viviers Fibre)
remarks: -----------------------------------------------------
remarks: Communities that are in the public range
remarks: (1-64495:x) and (131072-4199999999:x)
remarks: will be preserved by the route-servers
remarks: -----------------------------------------------------
remarks: Well-known communities are not interpreted by the
remarks: route-servers and are propagated to all peers
remarks: BLACKHOLE community is interpreted
remarks: 65535:666 = BLACKHOLE [RFC7999]
remarks: only routes with valid IRR records are accepted
remarks: more details at https://www.franceix.net/en/technical/blackholing/
remarks: -----------------------------------------------------
remarks: The following communities are applied by the route-server:
remarks: 47184:64615 = Prefix received from a peer on RS1 Toulouse
remarks: 47184:64616 = Prefix received from a peer on RS2 Toulouse
remarks: 47184:64655 = Prefix received from a FranceIX Toulouse peer
remarks: 47184:65012 = Prefix has RPKI status: VALID
remarks: 47184:65022 = Prefix has RPKI status: INVALID (NOT re-announced)
remarks: 47184:65023 = Prefix has RPKI status: UNKNOWN
remarks: 47184:65011 = Prefix is present in an AS's announced AS/AS-SET
remarks: 47184:65021 = Prefix is not present in an AS's announced AS/AS-SET (NOT re-announced)
remarks: -----------------------------------------------------
remarks: Large BGP communities (RFC8092) :
remarks: Large communities peers can set on routes:
remarks: 47184:0:0 = Do not send route to any peer unless explicitly signaled
remarks: 47184:0:peeras = Do not send route to this peer AS
remarks: 47184:1:0 = [DEFAULT] Send route to all peers
remarks: 47184:1:peeras = Send route to this peer AS (if 47184:0:0 specified)
remarks: 47184:101:peeras = Prepend 1x to this peer AS
remarks: 47184:102:peeras = Prepend 2x to this peer AS
remarks: 47184:103:peeras = Prepend 3x to this peer AS
remarks: 47184:901:peeras = Set MED to 50 for this peer AS
remarks: 47184:902:peeras = Set MED to 100 for this peer AS
remarks: 47184:903:peeras = Set MED to 200 for this peer AS
remarks: Large communities on received routes:
remarks: 47184:1000:1 = RPKI : Valid ROA (ROA Valid)
remarks: 47184:1000:2 = RPKI : No ROA Present (RPKI Unknown)
remarks: 47184:1001:1 = IRR Valid (Origin in AS-Set and route object present)
remarks: 47184:1001:6 [*] = No IRR route object for prefix
remarks: Large communities for filtered routes, only visible on looking-glass:
remarks: (routes tagged with these communities are not re-announced to RS peers)
remarks: 47184:1000:4 = RPKI Invalid
remarks: 47184:1001:4 = IRR Invalid/NotFound
remarks: 47184:1001:5 = IRR NotFound - Origin AS not in peer's AS-Set
remarks: 47184:1101:9 = FILTERED : IRR Invalid/NotFound
remarks: 47184:1101:10 = FILTERED : IRR Invalid - Origin AS not in peer's AS-Set
remarks: 47184:1101:11 = FILTERED : IRR NotFound (No route and no valid ROA for prefix)
remarks: 47184:1101:13 = FILTERED : RPKI Invalid
remarks: 47184:1101:14 = FILTERED : "Never via RS" ASn in AS-Path
remarks: [*] = A route without a valid IRR route object is only re-announced if:
remarks: - the origin AS is in the peer's AS-Set
remarks: - AND there is a VALID ROA for the origin AS
remarks: -----------------------------------------------------
remarks: You can filters prefixes with our AS-SET :
remarks: All members AS-SETs : AS-FRANCEIX-TLS
remarks: All members AS List : AS-FRANCEIX-TLS-LIST
remarks: Route-Servers members AS-SETs : AS47184:AS-MEMBERS
remarks: Route-Servers members AS List : AS47184:AS-MEMBERS:AS-TLS-RS
remarks: Please make sure to have at least one of theses lines in your aut-num object :
remarks: export: to AS47184 announce ASxxxx
remarks: export-via: AS47184 to AS-ANY announce ASxxxx
remarks: export-via: afi ipv6.unicast AS47184 to AS-ANY announce ASxxxx
remarks: mp-export: afi ipv4.unicast,ipv6.unicast to AS47184 announce ASxxxx
remarks: (ASxxxx can be your ASN or your AS-SET)
remarks: -----------------------------------------------------
remarks: We support ADD-PATHS, you will receive extended NLRI,
remarks: i.e. several paths for the same destination,
remarks: if you have the capability
remarks: -----------------------------------------------------
remarks: Routes with Private ASN in the AS_PATH, bad NEXT_HOP,
remarks: IPv4 netmask </8 or >/24, IPv6 netmask </19 or >/48
remarks: Martians or RFC1918 ** are rejected ** on Route Servers
remarks: -----------------------------------------------------
import: from AS47184:AS-MEMBERS:AS-TLS-RS accept AS47184:AS-MEMBERS
export: to AS47184:AS-MEMBERS:AS-TLS-RS announce AS47184:AS-MEMBERS
admin-c: LG5563-RIPE
tech-c: FXAD1-RIPE
status: ASSIGNED
mnt-by: RIPE-NCC-END-MNT
mnt-by: MNT-FRANCEIX
mnt-by: TOUIX-MNT
notify: [email protected]
created: 2009-09-24T08:55:05Z
last-modified: 2024-02-19T09:10:27Z
source: RIPE
sponsoring-org: ORG-FISS1-RIPE

organisation: ORG-TA434-RIPE
org-name: TOUIX
country: FR
descr: TOUlouse Internet eXchange
org-type: OTHER
address: 11 bd des recollets, 31100 Toulouse
e-mail: [email protected]
abuse-c: AC29337-RIPE
mnt-ref: MNT-FRANCEIX
mnt-by: TOUIX-MNT
mnt-by: MNT-FRANCEIX
mnt-by: EUROFIBER-FR-MNT
created: 2009-09-14T15:10:46Z
last-modified: 2023-09-11T12:35:36Z
source: RIPE

role: FranceIX Admin
org: ORG-FISS1-RIPE
address: 18 rue La Boetie
address: 75008 Paris
address: France
e-mail: [email protected]
admin-c: FS1578-RIPE
admin-c: SM5983-RIPE
tech-c: FS1578-RIPE
tech-c: SM5983-RIPE
tech-c: VM6401-RIPE
tech-c: RAF36-RIPE
tech-c: FR112233
nic-hdl: FXAD1-RIPE
abuse-mailbox: [email protected]
mnt-by: MNT-FRANCEIX
created: 2015-02-19T16:13:33Z
last-modified: 2024-04-05T15:42:00Z
source: RIPE
notify: [email protected]

person: LAURENT GUERBY
address: 10 chemin Tricou 31200 TOULOUSE FRANCE
phone: +0
e-mail: [email protected]
notify: [email protected]
remarks: http://guerby.org
nic-hdl: LG5563-RIPE
mnt-by: TETANEUTRAL-MNT
mnt-by: GUERBY-MNT
created: 2011-06-07T09:32:28Z
last-modified: 2024-11-01T21:39:07Z
source: RIPE

% This query was served by the RIPE Database Query Service version 1.114 (BUSA)


% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See https://docs.db.ripe.net/terms-conditions.html

% Information related to 'AS47184'

% Abuse contact for 'AS47184' is '[email protected]'

aut-num: AS47184
as-name: TOUIX-AS
descr: France-IX Toulouse
descr: Previously known as TOUIX/TOUlouse Internet eXchange
org: ORG-TA434-RIPE
remarks: -----------------------------------------------------
remarks: The following communities can be used by members on our Route-Servers:
remarks: *****************************************************
remarks: ** Note: These communities are evaluated
remarks: ** on a "first match win" basis
remarks: *****************************************************
remarks: 0:peer-as = Don't send route to this peer as
remarks: 47184:peer-as = Send route to this peer as
remarks: 0:47184 = Don't send route to any peer
remarks: 47184:47184 = Send route to all peers (applied by default)
remarks: *****************************************************
remarks: CDN Control:
remarks: 40027:40000 - DO announce to Netflix OpenConnect Appliance in Marseille
remarks: *****************************************************
remarks: 65101:peer-as = Prepend 1x to this peer
remarks: 65102:peer-as = Prepend 2x to this peer
remarks: 65103:peer-as = Prepend 3x to this peer
remarks: 65201:peer-as = Set MED 50 to this peer
remarks: 65202:peer-as = Set MED 100 to this peer
remarks: 65203:peer-as = Set MED 200 to this peer
remarks: -----------------------------------------------------
remarks: Set peer-as value as listed below for 32 bits ASNs:
remarks: AS197422 -> AS64701 (Tetaneutral)
remarks: AS206059 -> AS64816 (Viviers Fibre)
remarks: -----------------------------------------------------
remarks: Communities that are in the public range
remarks: (1-64495:x) and (131072-4199999999:x)
remarks: will be preserved by the route-servers
remarks: -----------------------------------------------------
remarks: Well-known communities are not interpreted by the
remarks: route-servers and are propagated to all peers
remarks: BLACKHOLE community is interpreted
remarks: 65535:666 = BLACKHOLE [RFC7999]
remarks: only routes with valid IRR records are accepted
remarks: more details at https://www.franceix.net/en/technical/blackholing/
remarks: -----------------------------------------------------
remarks: The following communities are applied by the route-server:
remarks: 47184:64615 = Prefix received from a peer on RS1 Toulouse
remarks: 47184:64616 = Prefix received from a peer on RS2 Toulouse
remarks: 47184:64655 = Prefix received from a FranceIX Toulouse peer
remarks: 47184:65012 = Prefix has RPKI status: VALID
remarks: 47184:65022 = Prefix has RPKI status: INVALID (NOT re-announced)
remarks: 47184:65023 = Prefix has RPKI status: UNKNOWN
remarks: 47184:65011 = Prefix is present in an AS's announced AS/AS-SET
remarks: 47184:65021 = Prefix is not present in an AS's announced AS/AS-SET (NOT re-announced)
remarks: -----------------------------------------------------
remarks: Large BGP communities (RFC8092) :
remarks: Large communities peers can set on routes:
remarks: 47184:0:0 = Do not send route to any peer unless explicitly signaled
remarks: 47184:0:peeras = Do not send route to this peer AS
remarks: 47184:1:0 = [DEFAULT] Send route to all peers
remarks: 47184:1:peeras = Send route to this peer AS (if 47184:0:0 specified)
remarks: 47184:101:peeras = Prepend 1x to this peer AS
remarks: 47184:102:peeras = Prepend 2x to this peer AS
remarks: 47184:103:peeras = Prepend 3x to this peer AS
remarks: 47184:901:peeras = Set MED to 50 for this peer AS
remarks: 47184:902:peeras = Set MED to 100 for this peer AS
remarks: 47184:903:peeras = Set MED to 200 for this peer AS
remarks: Large communities on received routes:
remarks: 47184:1000:1 = RPKI : Valid ROA (ROA Valid)
remarks: 47184:1000:2 = RPKI : No ROA Present (RPKI Unknown)
remarks: 47184:1001:1 = IRR Valid (Origin in AS-Set and route object present)
remarks: 47184:1001:6 [*] = No IRR route object for prefix
remarks: Large communities for filtered routes, only visible on looking-glass:
remarks: (routes tagged with these communities are not re-announced to RS peers)
remarks: 47184:1000:4 = RPKI Invalid
remarks: 47184:1001:4 = IRR Invalid/NotFound
remarks: 47184:1001:5 = IRR NotFound - Origin AS not in peer's AS-Set
remarks: 47184:1101:9 = FILTERED : IRR Invalid/NotFound
remarks: 47184:1101:10 = FILTERED : IRR Invalid - Origin AS not in peer's AS-Set
remarks: 47184:1101:11 = FILTERED : IRR NotFound (No route and no valid ROA for prefix)
remarks: 47184:1101:13 = FILTERED : RPKI Invalid
remarks: 47184:1101:14 = FILTERED : "Never via RS" ASn in AS-Path
remarks: [*] = A route without a valid IRR route object is only re-announced if:
remarks: - the origin AS is in the peer's AS-Set
remarks: - AND there is a VALID ROA for the origin AS
remarks: -----------------------------------------------------
remarks: You can filters prefixes with our AS-SET :
remarks: All members AS-SETs : AS-FRANCEIX-TLS
remarks: All members AS List : AS-FRANCEIX-TLS-LIST
remarks: Route-Servers members AS-SETs : AS47184:AS-MEMBERS
remarks: Route-Servers members AS List : AS47184:AS-MEMBERS:AS-TLS-RS
remarks: Please make sure to have at least one of theses lines in your aut-num object :
remarks: export: to AS47184 announce ASxxxx
remarks: export-via: AS47184 to AS-ANY announce ASxxxx
remarks: export-via: afi ipv6.unicast AS47184 to AS-ANY announce ASxxxx
remarks: mp-export: afi ipv4.unicast,ipv6.unicast to AS47184 announce ASxxxx
remarks: (ASxxxx can be your ASN or your AS-SET)
remarks: -----------------------------------------------------
remarks: We support ADD-PATHS, you will receive extended NLRI,
remarks: i.e. several paths for the same destination,
remarks: if you have the capability
remarks: -----------------------------------------------------
remarks: Routes with Private ASN in the AS_PATH, bad NEXT_HOP,
remarks: IPv4 netmask </8 or >/24, IPv6 netmask </19 or >/48
remarks: Martians or RFC1918 ** are rejected ** on Route Servers
remarks: -----------------------------------------------------
import: from AS47184:AS-MEMBERS:AS-TLS-RS accept AS47184:AS-MEMBERS
export: to AS47184:AS-MEMBERS:AS-TLS-RS announce AS47184:AS-MEMBERS
admin-c: LG5563-RIPE
tech-c: FXAD1-RIPE
status: ASSIGNED
mnt-by: RIPE-NCC-END-MNT
mnt-by: MNT-FRANCEIX
mnt-by: TOUIX-MNT
notify: [email protected]
created: 2009-09-24T08:55:05Z
last-modified: 2024-02-19T09:10:27Z
source: RIPE
sponsoring-org: ORG-FISS1-RIPE

organisation: ORG-TA434-RIPE
org-name: TOUIX
country: FR
descr: TOUlouse Internet eXchange
org-type: OTHER
address: 11 bd des recollets, 31100 Toulouse
e-mail: [email protected]
abuse-c: AC29337-RIPE
mnt-ref: MNT-FRANCEIX
mnt-by: TOUIX-MNT
mnt-by: MNT-FRANCEIX
mnt-by: EUROFIBER-FR-MNT
created: 2009-09-14T15:10:46Z
last-modified: 2023-09-11T12:35:36Z
source: RIPE

role: FranceIX Admin
org: ORG-FISS1-RIPE
address: 18 rue La Boetie
address: 75008 Paris
address: France
e-mail: [email protected]
admin-c: FS1578-RIPE
admin-c: SM5983-RIPE
tech-c: FS1578-RIPE
tech-c: SM5983-RIPE
tech-c: VM6401-RIPE
tech-c: RAF36-RIPE
tech-c: FR112233
nic-hdl: FXAD1-RIPE
abuse-mailbox: [email protected]
mnt-by: MNT-FRANCEIX
created: 2015-02-19T16:13:33Z
last-modified: 2024-04-05T15:42:00Z
source: RIPE
notify: [email protected]

person: LAURENT GUERBY
address: 10 chemin Tricou 31200 TOULOUSE FRANCE
phone: +0
e-mail: [email protected]
notify: [email protected]
remarks: http://guerby.org
nic-hdl: LG5563-RIPE
mnt-by: TETANEUTRAL-MNT
mnt-by: GUERBY-MNT
created: 2011-06-07T09:32:28Z
last-modified: 2024-11-01T21:39:07Z
source: RIPE

% This query was served by the RIPE Database Query Service version 1.114 (BUSA)


IX

国家
IX
IPv4
IPv6
端口速度
暂无数据
  • 1
国家
IX
IPv4
IPv6
端口速度
暂无数据
  • 1
IP.CC
搜索
IP地址详细信息
AS47184
France-IX Toulouse ·www.franceix.net
IP地址详细信息
AS47184
France-IX Toulouse ·www.franceix.net

摘要

  • ASN编号
    AS47184
  • 组织名称
    France-IX Toulouse
  • 国家
    France
  • 国家编码
    FR
  • 站点
  • 区域登记
    RIPE
  • 分配日期
    24th September 2009
  • 分配状态
    Allocated
  • Ipv4前缀
    0
  • Ipv6前缀
    0
  • Ipv4同行
    0
  • Ipv6同行
    0
  • Ipv4上游
    0
  • Ipv6上游
    0

前缀

此 ASN 有 0 个 IPv4 前缀。

国家
公布的前缀
描述
父前缀
RIR
暂无数据
  • 1
IP范围API
使用IP信息强大的IP范围 API获取这些数据和更多信息-快速轻松地识别公司拥有的IP范围。
有用的 游戏技术, 和 广告技术
IP范围API
使用IP信息强大的IP范围 API获取这些数据和更多信息-快速轻松地识别公司拥有的IP范围。
有用的 游戏技术, 和 广告技术

同行

此 ASN 有 0 个 IPv4 对等点。

国家
ASN
描述
IPv6
暂无数据
  • 1
ASN 数据
每个IP地址和每个ASN相关域的ASN详细信息、分配日期、注册表名称、IP地址总数和分配的前缀。
有用的 网络安全
ASN 数据
每个IP地址和每个ASN相关域的ASN详细信息、分配日期、注册表名称、IP地址总数和分配的前缀。
有用的 网络安全

上游

此 ASN 有 0 个 IPv4 上游。

国家
ASN
描述
IPv6
暂无数据
  • 1
ASN 数据
每个IP地址和每个ASN相关域的ASN详细信息、分配日期、注册表名称、IP地址总数和分配的前缀。
有用的 网络安全
ASN 数据
每个IP地址和每个ASN相关域的ASN详细信息、分配日期、注册表名称、IP地址总数和分配的前缀。
有用的 网络安全

下游

此 ASN 有 0 个 IPv4 下游。

国家
ASN
描述
IPv6
暂无数据
  • 1
ASN 数据
每个IP地址和每个ASN相关域的ASN详细信息、分配日期、注册表名称、IP地址总数和分配的前缀。
有用的 网络安全
ASN 数据
每个IP地址和每个ASN相关域的ASN详细信息、分配日期、注册表名称、IP地址总数和分配的前缀。
有用的 网络安全

世界地图

WHOIS详细信息

% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See https://docs.db.ripe.net/terms-conditions.html

% Information related to 'AS47184'

% Abuse contact for 'AS47184' is '[email protected]'

aut-num: AS47184
as-name: TOUIX-AS
descr: France-IX Toulouse
descr: Previously known as TOUIX/TOUlouse Internet eXchange
org: ORG-TA434-RIPE
remarks: -----------------------------------------------------
remarks: The following communities can be used by members on our Route-Servers:
remarks: *****************************************************
remarks: ** Note: These communities are evaluated
remarks: ** on a "first match win" basis
remarks: *****************************************************
remarks: 0:peer-as = Don't send route to this peer as
remarks: 47184:peer-as = Send route to this peer as
remarks: 0:47184 = Don't send route to any peer
remarks: 47184:47184 = Send route to all peers (applied by default)
remarks: *****************************************************
remarks: CDN Control:
remarks: 40027:40000 - DO announce to Netflix OpenConnect Appliance in Marseille
remarks: *****************************************************
remarks: 65101:peer-as = Prepend 1x to this peer
remarks: 65102:peer-as = Prepend 2x to this peer
remarks: 65103:peer-as = Prepend 3x to this peer
remarks: 65201:peer-as = Set MED 50 to this peer
remarks: 65202:peer-as = Set MED 100 to this peer
remarks: 65203:peer-as = Set MED 200 to this peer
remarks: -----------------------------------------------------
remarks: Set peer-as value as listed below for 32 bits ASNs:
remarks: AS197422 -> AS64701 (Tetaneutral)
remarks: AS206059 -> AS64816 (Viviers Fibre)
remarks: -----------------------------------------------------
remarks: Communities that are in the public range
remarks: (1-64495:x) and (131072-4199999999:x)
remarks: will be preserved by the route-servers
remarks: -----------------------------------------------------
remarks: Well-known communities are not interpreted by the
remarks: route-servers and are propagated to all peers
remarks: BLACKHOLE community is interpreted
remarks: 65535:666 = BLACKHOLE [RFC7999]
remarks: only routes with valid IRR records are accepted
remarks: more details at https://www.franceix.net/en/technical/blackholing/
remarks: -----------------------------------------------------
remarks: The following communities are applied by the route-server:
remarks: 47184:64615 = Prefix received from a peer on RS1 Toulouse
remarks: 47184:64616 = Prefix received from a peer on RS2 Toulouse
remarks: 47184:64655 = Prefix received from a FranceIX Toulouse peer
remarks: 47184:65012 = Prefix has RPKI status: VALID
remarks: 47184:65022 = Prefix has RPKI status: INVALID (NOT re-announced)
remarks: 47184:65023 = Prefix has RPKI status: UNKNOWN
remarks: 47184:65011 = Prefix is present in an AS's announced AS/AS-SET
remarks: 47184:65021 = Prefix is not present in an AS's announced AS/AS-SET (NOT re-announced)
remarks: -----------------------------------------------------
remarks: Large BGP communities (RFC8092) :
remarks: Large communities peers can set on routes:
remarks: 47184:0:0 = Do not send route to any peer unless explicitly signaled
remarks: 47184:0:peeras = Do not send route to this peer AS
remarks: 47184:1:0 = [DEFAULT] Send route to all peers
remarks: 47184:1:peeras = Send route to this peer AS (if 47184:0:0 specified)
remarks: 47184:101:peeras = Prepend 1x to this peer AS
remarks: 47184:102:peeras = Prepend 2x to this peer AS
remarks: 47184:103:peeras = Prepend 3x to this peer AS
remarks: 47184:901:peeras = Set MED to 50 for this peer AS
remarks: 47184:902:peeras = Set MED to 100 for this peer AS
remarks: 47184:903:peeras = Set MED to 200 for this peer AS
remarks: Large communities on received routes:
remarks: 47184:1000:1 = RPKI : Valid ROA (ROA Valid)
remarks: 47184:1000:2 = RPKI : No ROA Present (RPKI Unknown)
remarks: 47184:1001:1 = IRR Valid (Origin in AS-Set and route object present)
remarks: 47184:1001:6 [*] = No IRR route object for prefix
remarks: Large communities for filtered routes, only visible on looking-glass:
remarks: (routes tagged with these communities are not re-announced to RS peers)
remarks: 47184:1000:4 = RPKI Invalid
remarks: 47184:1001:4 = IRR Invalid/NotFound
remarks: 47184:1001:5 = IRR NotFound - Origin AS not in peer's AS-Set
remarks: 47184:1101:9 = FILTERED : IRR Invalid/NotFound
remarks: 47184:1101:10 = FILTERED : IRR Invalid - Origin AS not in peer's AS-Set
remarks: 47184:1101:11 = FILTERED : IRR NotFound (No route and no valid ROA for prefix)
remarks: 47184:1101:13 = FILTERED : RPKI Invalid
remarks: 47184:1101:14 = FILTERED : "Never via RS" ASn in AS-Path
remarks: [*] = A route without a valid IRR route object is only re-announced if:
remarks: - the origin AS is in the peer's AS-Set
remarks: - AND there is a VALID ROA for the origin AS
remarks: -----------------------------------------------------
remarks: You can filters prefixes with our AS-SET :
remarks: All members AS-SETs : AS-FRANCEIX-TLS
remarks: All members AS List : AS-FRANCEIX-TLS-LIST
remarks: Route-Servers members AS-SETs : AS47184:AS-MEMBERS
remarks: Route-Servers members AS List : AS47184:AS-MEMBERS:AS-TLS-RS
remarks: Please make sure to have at least one of theses lines in your aut-num object :
remarks: export: to AS47184 announce ASxxxx
remarks: export-via: AS47184 to AS-ANY announce ASxxxx
remarks: export-via: afi ipv6.unicast AS47184 to AS-ANY announce ASxxxx
remarks: mp-export: afi ipv4.unicast,ipv6.unicast to AS47184 announce ASxxxx
remarks: (ASxxxx can be your ASN or your AS-SET)
remarks: -----------------------------------------------------
remarks: We support ADD-PATHS, you will receive extended NLRI,
remarks: i.e. several paths for the same destination,
remarks: if you have the capability
remarks: -----------------------------------------------------
remarks: Routes with Private ASN in the AS_PATH, bad NEXT_HOP,
remarks: IPv4 netmask </8 or >/24, IPv6 netmask </19 or >/48
remarks: Martians or RFC1918 ** are rejected ** on Route Servers
remarks: -----------------------------------------------------
import: from AS47184:AS-MEMBERS:AS-TLS-RS accept AS47184:AS-MEMBERS
export: to AS47184:AS-MEMBERS:AS-TLS-RS announce AS47184:AS-MEMBERS
admin-c: LG5563-RIPE
tech-c: FXAD1-RIPE
status: ASSIGNED
mnt-by: RIPE-NCC-END-MNT
mnt-by: MNT-FRANCEIX
mnt-by: TOUIX-MNT
notify: [email protected]
created: 2009-09-24T08:55:05Z
last-modified: 2024-02-19T09:10:27Z
source: RIPE
sponsoring-org: ORG-FISS1-RIPE

organisation: ORG-TA434-RIPE
org-name: TOUIX
country: FR
descr: TOUlouse Internet eXchange
org-type: OTHER
address: 11 bd des recollets, 31100 Toulouse
e-mail: [email protected]
abuse-c: AC29337-RIPE
mnt-ref: MNT-FRANCEIX
mnt-by: TOUIX-MNT
mnt-by: MNT-FRANCEIX
mnt-by: EUROFIBER-FR-MNT
created: 2009-09-14T15:10:46Z
last-modified: 2023-09-11T12:35:36Z
source: RIPE

role: FranceIX Admin
org: ORG-FISS1-RIPE
address: 18 rue La Boetie
address: 75008 Paris
address: France
e-mail: [email protected]
admin-c: FS1578-RIPE
admin-c: SM5983-RIPE
tech-c: FS1578-RIPE
tech-c: SM5983-RIPE
tech-c: VM6401-RIPE
tech-c: RAF36-RIPE
tech-c: FR112233
nic-hdl: FXAD1-RIPE
abuse-mailbox: [email protected]
mnt-by: MNT-FRANCEIX
created: 2015-02-19T16:13:33Z
last-modified: 2024-04-05T15:42:00Z
source: RIPE
notify: [email protected]

person: LAURENT GUERBY
address: 10 chemin Tricou 31200 TOULOUSE FRANCE
phone: +0
e-mail: [email protected]
notify: [email protected]
remarks: http://guerby.org
nic-hdl: LG5563-RIPE
mnt-by: TETANEUTRAL-MNT
mnt-by: GUERBY-MNT
created: 2011-06-07T09:32:28Z
last-modified: 2024-11-01T21:39:07Z
source: RIPE

% This query was served by the RIPE Database Query Service version 1.114 (BUSA)


% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See https://docs.db.ripe.net/terms-conditions.html

% Information related to 'AS47184'

% Abuse contact for 'AS47184' is '[email protected]'

aut-num: AS47184
as-name: TOUIX-AS
descr: France-IX Toulouse
descr: Previously known as TOUIX/TOUlouse Internet eXchange
org: ORG-TA434-RIPE
remarks: -----------------------------------------------------
remarks: The following communities can be used by members on our Route-Servers:
remarks: *****************************************************
remarks: ** Note: These communities are evaluated
remarks: ** on a "first match win" basis
remarks: *****************************************************
remarks: 0:peer-as = Don't send route to this peer as
remarks: 47184:peer-as = Send route to this peer as
remarks: 0:47184 = Don't send route to any peer
remarks: 47184:47184 = Send route to all peers (applied by default)
remarks: *****************************************************
remarks: CDN Control:
remarks: 40027:40000 - DO announce to Netflix OpenConnect Appliance in Marseille
remarks: *****************************************************
remarks: 65101:peer-as = Prepend 1x to this peer
remarks: 65102:peer-as = Prepend 2x to this peer
remarks: 65103:peer-as = Prepend 3x to this peer
remarks: 65201:peer-as = Set MED 50 to this peer
remarks: 65202:peer-as = Set MED 100 to this peer
remarks: 65203:peer-as = Set MED 200 to this peer
remarks: -----------------------------------------------------
remarks: Set peer-as value as listed below for 32 bits ASNs:
remarks: AS197422 -> AS64701 (Tetaneutral)
remarks: AS206059 -> AS64816 (Viviers Fibre)
remarks: -----------------------------------------------------
remarks: Communities that are in the public range
remarks: (1-64495:x) and (131072-4199999999:x)
remarks: will be preserved by the route-servers
remarks: -----------------------------------------------------
remarks: Well-known communities are not interpreted by the
remarks: route-servers and are propagated to all peers
remarks: BLACKHOLE community is interpreted
remarks: 65535:666 = BLACKHOLE [RFC7999]
remarks: only routes with valid IRR records are accepted
remarks: more details at https://www.franceix.net/en/technical/blackholing/
remarks: -----------------------------------------------------
remarks: The following communities are applied by the route-server:
remarks: 47184:64615 = Prefix received from a peer on RS1 Toulouse
remarks: 47184:64616 = Prefix received from a peer on RS2 Toulouse
remarks: 47184:64655 = Prefix received from a FranceIX Toulouse peer
remarks: 47184:65012 = Prefix has RPKI status: VALID
remarks: 47184:65022 = Prefix has RPKI status: INVALID (NOT re-announced)
remarks: 47184:65023 = Prefix has RPKI status: UNKNOWN
remarks: 47184:65011 = Prefix is present in an AS's announced AS/AS-SET
remarks: 47184:65021 = Prefix is not present in an AS's announced AS/AS-SET (NOT re-announced)
remarks: -----------------------------------------------------
remarks: Large BGP communities (RFC8092) :
remarks: Large communities peers can set on routes:
remarks: 47184:0:0 = Do not send route to any peer unless explicitly signaled
remarks: 47184:0:peeras = Do not send route to this peer AS
remarks: 47184:1:0 = [DEFAULT] Send route to all peers
remarks: 47184:1:peeras = Send route to this peer AS (if 47184:0:0 specified)
remarks: 47184:101:peeras = Prepend 1x to this peer AS
remarks: 47184:102:peeras = Prepend 2x to this peer AS
remarks: 47184:103:peeras = Prepend 3x to this peer AS
remarks: 47184:901:peeras = Set MED to 50 for this peer AS
remarks: 47184:902:peeras = Set MED to 100 for this peer AS
remarks: 47184:903:peeras = Set MED to 200 for this peer AS
remarks: Large communities on received routes:
remarks: 47184:1000:1 = RPKI : Valid ROA (ROA Valid)
remarks: 47184:1000:2 = RPKI : No ROA Present (RPKI Unknown)
remarks: 47184:1001:1 = IRR Valid (Origin in AS-Set and route object present)
remarks: 47184:1001:6 [*] = No IRR route object for prefix
remarks: Large communities for filtered routes, only visible on looking-glass:
remarks: (routes tagged with these communities are not re-announced to RS peers)
remarks: 47184:1000:4 = RPKI Invalid
remarks: 47184:1001:4 = IRR Invalid/NotFound
remarks: 47184:1001:5 = IRR NotFound - Origin AS not in peer's AS-Set
remarks: 47184:1101:9 = FILTERED : IRR Invalid/NotFound
remarks: 47184:1101:10 = FILTERED : IRR Invalid - Origin AS not in peer's AS-Set
remarks: 47184:1101:11 = FILTERED : IRR NotFound (No route and no valid ROA for prefix)
remarks: 47184:1101:13 = FILTERED : RPKI Invalid
remarks: 47184:1101:14 = FILTERED : "Never via RS" ASn in AS-Path
remarks: [*] = A route without a valid IRR route object is only re-announced if:
remarks: - the origin AS is in the peer's AS-Set
remarks: - AND there is a VALID ROA for the origin AS
remarks: -----------------------------------------------------
remarks: You can filters prefixes with our AS-SET :
remarks: All members AS-SETs : AS-FRANCEIX-TLS
remarks: All members AS List : AS-FRANCEIX-TLS-LIST
remarks: Route-Servers members AS-SETs : AS47184:AS-MEMBERS
remarks: Route-Servers members AS List : AS47184:AS-MEMBERS:AS-TLS-RS
remarks: Please make sure to have at least one of theses lines in your aut-num object :
remarks: export: to AS47184 announce ASxxxx
remarks: export-via: AS47184 to AS-ANY announce ASxxxx
remarks: export-via: afi ipv6.unicast AS47184 to AS-ANY announce ASxxxx
remarks: mp-export: afi ipv4.unicast,ipv6.unicast to AS47184 announce ASxxxx
remarks: (ASxxxx can be your ASN or your AS-SET)
remarks: -----------------------------------------------------
remarks: We support ADD-PATHS, you will receive extended NLRI,
remarks: i.e. several paths for the same destination,
remarks: if you have the capability
remarks: -----------------------------------------------------
remarks: Routes with Private ASN in the AS_PATH, bad NEXT_HOP,
remarks: IPv4 netmask </8 or >/24, IPv6 netmask </19 or >/48
remarks: Martians or RFC1918 ** are rejected ** on Route Servers
remarks: -----------------------------------------------------
import: from AS47184:AS-MEMBERS:AS-TLS-RS accept AS47184:AS-MEMBERS
export: to AS47184:AS-MEMBERS:AS-TLS-RS announce AS47184:AS-MEMBERS
admin-c: LG5563-RIPE
tech-c: FXAD1-RIPE
status: ASSIGNED
mnt-by: RIPE-NCC-END-MNT
mnt-by: MNT-FRANCEIX
mnt-by: TOUIX-MNT
notify: [email protected]
created: 2009-09-24T08:55:05Z
last-modified: 2024-02-19T09:10:27Z
source: RIPE
sponsoring-org: ORG-FISS1-RIPE

organisation: ORG-TA434-RIPE
org-name: TOUIX
country: FR
descr: TOUlouse Internet eXchange
org-type: OTHER
address: 11 bd des recollets, 31100 Toulouse
e-mail: [email protected]
abuse-c: AC29337-RIPE
mnt-ref: MNT-FRANCEIX
mnt-by: TOUIX-MNT
mnt-by: MNT-FRANCEIX
mnt-by: EUROFIBER-FR-MNT
created: 2009-09-14T15:10:46Z
last-modified: 2023-09-11T12:35:36Z
source: RIPE

role: FranceIX Admin
org: ORG-FISS1-RIPE
address: 18 rue La Boetie
address: 75008 Paris
address: France
e-mail: [email protected]
admin-c: FS1578-RIPE
admin-c: SM5983-RIPE
tech-c: FS1578-RIPE
tech-c: SM5983-RIPE
tech-c: VM6401-RIPE
tech-c: RAF36-RIPE
tech-c: FR112233
nic-hdl: FXAD1-RIPE
abuse-mailbox: [email protected]
mnt-by: MNT-FRANCEIX
created: 2015-02-19T16:13:33Z
last-modified: 2024-04-05T15:42:00Z
source: RIPE
notify: [email protected]

person: LAURENT GUERBY
address: 10 chemin Tricou 31200 TOULOUSE FRANCE
phone: +0
e-mail: [email protected]
notify: [email protected]
remarks: http://guerby.org
nic-hdl: LG5563-RIPE
mnt-by: TETANEUTRAL-MNT
mnt-by: GUERBY-MNT
created: 2011-06-07T09:32:28Z
last-modified: 2024-11-01T21:39:07Z
source: RIPE

% This query was served by the RIPE Database Query Service version 1.114 (BUSA)


IX

国家
IX
IPv4
IPv6
端口速度
暂无数据
  • 1
国家
IX
IPv4
IPv6
端口速度
暂无数据
  • 1
相关网络
  • AS47194
    Oblcom Swiss AG
  • AS47210
    Djivaya Voda Ltd.
  • AS47211
    OOO Kolpinskie Internet-Seti
  • AS47216
    TookanTech
  • AS47217
    Planetel SPA
  • AS47222
    Atlantic Grand doo Beograd
  • AS47223
    Lukman Multimedia Sp. z o.o
  • AS47224
    Telecom Italia S.p.A.
什么是ASN?
自治系统号(ASN)被分配给控制IP地址块的实体,如互联网服务提供商和其他大型组织。此网络页面以及显示在主IP地址信息页面上并在地理位置API中返回的组织字段基于ASN。
IP.CC

API,建立在安全、网络个性化、营销等方面

对于金融服务业和金融科技公司,IP。CC是一个非常宝贵的工具。我们在金融行业的客户喜欢我们的工作,我们很高兴向您展示原因。
IP.CC

我们的IP工具

探索所有工具IP.CC
  • IP.CCPing

    Ping是一个免费工具,可以帮助您找到可以使用ICMP协议Ping的IP地址。您可以查找IP地址或CIDR块。

    尝试 PingIP.CC
  • IP.CCDNS

    DNS是一种用于确定与IP地址关联的主机名的技术。这是在主机名注册表和注册器表中搜索PTR记录完成的。

    尝试 DNSIP.CC
  • IP.CCPort

    Port是一个免费工具,用于检测设备上的开放端口。它会自动检测IP地址并扫描您的设备,识别黑客通过的开放和易受攻击的端口。

    尝试 PortIP.CC
常见问题