Skip to main content

AS206186

EPIX-KTW-Local

Stowarzyszenie e-Poludnie

Registry

Authoritative registration data

AS number
206186
Name
EPIX-KTW-Local
Organisation
Stowarzyszenie e-Poludnie
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS206186
185.170.225.0/24 IPv4 /24 not checked
188.241.28.0/24 IPv4 /24 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS206186 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS206186 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 537 2,076
v4 v6
AS9141 AS9141 18 66
v4 v6
AS50607 EPIX-KTW-GlobalMix 12 24
v4
AS201054 EPIX-PolMix 3 6
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS206186 in AS paths

Observed downstreams
Families
AS63293 FACEBOOK-OFFNET 306 1,436
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 18
v4
AS49544 i3Dnet 1 4
v4
AS36236 NETACTUATE 1 2
v4

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.