Skip to main content

AS209150

POINTER

TH.PAPAMICHAIL VAINAS - G.PSALTAKIS G.P

Registry

Authoritative registration data

AS number
209150
Name
POINTER
Organisation
TH.PAPAMICHAIL VAINAS - G.PSALTAKIS G.P
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

0

Total announced

8

Announced prefixes

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

Prefixes announced by AS209150
185.162.236.0/24 IPv4 /24 not checked
185.162.237.0/24 IPv4 /24 not checked
185.162.238.0/24 IPv4 /24 not checked
185.162.239.0/24 IPv4 /24 not checked
185.25.20.0/24 IPv4 /24 not checked
185.25.21.0/24 IPv4 /24 not checked
185.25.22.0/24 IPv4 /24 not checked
185.25.23.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

Internet Exchange memberships listed for AS209150
Address families
GR-IX::Athens: Peering Lan 1,024 Mbps IPv4 · IPv6
MIX Thessaloniki 10,240 Mbps IPv4 · IPv6
NetIX Greece 1,024 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 AS209150 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

18 networks seen before AS209150 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS209150 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

16 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.