Skip to main content

AS208608

REDACTED

Registry

Authoritative registration data

AS number
208608
Name
REDACTED
Organisation
REDACTED
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

2

Total announced

5

Announced prefixes

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

Prefixes announced by AS208608
45.128.16.0/24 IPv4 /24 not checked
45.128.18.0/24 IPv4 /24 not checked
45.128.19.0/24 IPv4 /24 not checked
2a0e:1540::/29 IPv6 /29 not checked
2a0e:3bc0::/29 IPv6 /29 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 AS208608
Address families
Frys-IX 100,000 Mbps IPv4 · IPv6
INTERIX 10,000 Mbps IPv4 · IPv6
Speed-IX: SPEED-IX 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 AS208608 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

23 networks seen before AS208608 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 260 753
v4 v6
AS63473 300 731
v4
AS212477 183 237
v4
AS5405 5 7
v4
AS34019 HIVANE 3 5
v4
AS14840 ASN14840 2 5
v4
AS20764 RASCOM-AS 4 4
v4
AS25091 IP-Max 2 4
v4
AS3214 XTOM 2 3
v4
AS137409 GSLNETWORKS-AS-AP 2 3
v4
AS1103 SURFNET-NL 2 2
v4
AS8298 IPNG 2 2
v4
AS39351 ESAB-AS 2 2
v4
AS56911 2 2
v4
AS61049 2 2
v4
AS62000 2 2
v4
AS1031 PEER1-1031 1 1
v4
AS6204 1 1
v4
AS9498 BBIL-AP 1 1
v4
AS20766 1 1
v4
AS22356 1 1
v4
AS39686 1 1
v4
AS50869 1 1
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS208608 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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