Skip to main content

AS17143

WINNTELECOM

Winn Telecom

Registry

Authoritative registration data

AS number
17143
Name
WINNTELECOM
Organisation
Winn Telecom
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

1

Total announced

9

Announced prefixes

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

Prefixes announced by AS17143
67.209.240.0/20 IPv4 /20 not checked
216.111.200.0/21 IPv4 /21 not checked
67.209.240.0/21 IPv4 /21 not checked
67.209.248.0/21 IPv4 /21 not checked
216.207.206.0/23 IPv4 /23 not checked
63.150.214.0/23 IPv4 /23 not checked
63.238.122.0/24 IPv4 /24 not checked
67.209.254.0/24 IPv4 /24 not checked
2605:1600::/32 IPv6 /32 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 AS17143
Address families
CM-IX 10,000 Mbps IPv4 · IPv6
Equinix Chicago 10,000 Mbps IPv4 · 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 AS17143 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS17143 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 569 3,872
v4 v6
AS12129 330 965
v4 v6
AS46208 27 102
v4 v6
AS137409 GSLNETWORKS-AS-AP 3 12
v4

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS17143 in AS paths

Observed downstreams
Families
AS33539 271 1,508
v4
AS62968 75 101
v4
AS63083 CHAPINTELEPHONE 41 47
v4

No rows match “”.

Showing – of

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 3 39
v4 v6
AS49544 i3Dnet 3 26
v4 v6
AS36236 NETACTUATE 3 13
v4 v6
AS35280 F5 3 12
v4
AS1828 UNITAS 1 1
v6

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.