Skip to main content

AS64444

RESEAU-THD

RESEAU THD SARL

Registry

Authoritative registration data

AS number
64444
Name
RESEAU-THD
Organisation
RESEAU THD SARL
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS64444
185.164.164.0/22 IPv4 /22 not checked
2a0a:a400::/29 IPv6 /29 RPKI valid

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 AS64444
Address families
France-IX AURA: lyonix-peering 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 AS64444 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS64444 in AS paths

Observed upstreams
Families
AS174 COGENT-174 320 525
v4 v6
AS6939 HURRICANE 156 228
v4 v6
AS8218 NEO-ASN 150 220
v4 v6
AS3215 AS3215 32 59
v4 v6
AS25091 IP-Max 12 16
v6
AS34019 HIVANE 6 16
v4 v6
AS35625 EUROFIBER-FRANCE 6 12
v4 v6
AS39801 FRANCE-IX-L3P 4 7
v4 v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS64444 in AS paths

Observed downstreams
Families
AS61984 RC-AS 337 542
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS29075 IELO 2 4
v4 v6
AS56987 AS-ABACLOUDA 2 4
v4 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.