AS206652
GREEKSTREAM-AS
GREEKSTREAM NETWORKS
Registry
Authoritative registration data
- AS number
- 206652
- Name
- GREEKSTREAM-AS
- Organisation
- GREEKSTREAM NETWORKS
- Country
- —
- RIR
- RIPE
- Registered
Source:asn:rdap
retrieved
IPv4 prefixes
3
IPv6 prefixes
17
Total announced
20
Announced prefixes
Observed in BGP by route collectors, not a registry allocation list
matching
| 185.180.36.0/24 | IPv4 | /24 | not checked | |
| 185.180.37.0/24 | IPv4 | /24 | not checked | |
| 185.180.38.0/24 | IPv4 | /24 | not checked | |
| 2a0a:d180::/29 | IPv6 | /29 | not checked | |
| 2a0a:d180:100::/40 | IPv6 | /40 | not checked | |
| 2a0a:d180:200::/40 | IPv6 | /40 | not checked | |
| 2a0a:d180:300::/40 | IPv6 | /40 | not checked | |
| 2a0a:d180:400::/40 | IPv6 | /40 | not checked | |
| 2a0a:d180:500::/40 | IPv6 | /40 | not checked | |
| 2a0a:d180:600::/40 | IPv6 | /40 | not checked | |
| 2a0a:d180:700::/40 | IPv6 | /40 | not checked | |
| 2a0a:d180:800::/40 | IPv6 | /40 | not checked | |
| 2a0a:d180:900::/40 | IPv6 | /40 | not checked | |
| 2a0a:d180::/40 | IPv6 | /40 | not checked | |
| 2a0a:d180:a00::/40 | IPv6 | /40 | not checked | |
| 2a0a:d180:b00::/40 | IPv6 | /40 | not checked | |
| 2a0a:d180:c00::/40 | IPv6 | /40 | not checked | |
| 2a0a:d180:d00::/40 | IPv6 | /40 | not checked | |
| 2a0a:d180:e00::/40 | IPv6 | /40 | not checked | |
| 2a0a:d180:f00::/40 | IPv6 | /40 | not checked |
No rows match “”.
Showing – of
Source:ripestat:announced-prefixes
observed
Observed adjacencies
Networks seen next to AS206652 in BGP paths by route collectors.
Observed upstreams
9 networks seen before AS206652 in AS paths
Observed downstreams
4 networks seen after AS206652 in AS paths
Uncertain adjacencies
8 adjacencies that may be an artefact of collector peering
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.