Skip to main content

AS208768

ConstV6

Constant Company

Registry

Authoritative registration data

AS number
208768
Name
ConstV6
Organisation
Constant Company
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

6

Total announced

7

Announced prefixes

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

Prefixes announced by AS208768
44.30.160.0/24 IPv4 /24 not checked
2a06:a005:2ca0::/45 IPv6 /45 not checked
2a06:a005:2caa::/48 IPv6 /48 not checked
2a06:a005:2cac::/48 IPv6 /48 not checked
2a06:a005:2cad::/48 IPv6 /48 not checked
2a06:a005:2caf::/48 IPv6 /48 not checked
2a10:4741:22::/48 IPv6 /48 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 AS208768
Address families
FogIXP 1,000 Mbps IPv6
ONIX 1,000 Mbps 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 AS208768 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS208768 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 236 1,005
v6
AS34927 iFog-GmbH 435 931
v4 v6
AS35487 255 524
v6
AS47498 FogIXP 3 12
v6
AS50869 FREEIX-REMOTE 3 12
v6
AS39351 ESAB-AS 2 7
v6
AS205794 RTTW-AS 1 5
v6
AS41051 FREETRANSIT 1 4
v6
AS209022 Tschajera-Limited 1 4
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS208768 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS8298 IPNG 1 4
v6
AS41666 1 4
v6
AS58299 OPENFACTORY-AS 1 4
v6
AS209823 1 4
v6
AS835 GOCODEIT-EDGE 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.