Skip to main content

AS394710

TELMAX-INC

TelMAX Inc.

Registry

Authoritative registration data

AS number
394710
Name
TELMAX-INC
Organisation
TelMAX Inc.
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

2

Total announced

4

Announced prefixes

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

Prefixes announced by AS394710
209.216.96.0/19 IPv4 /19 not checked
142.46.66.0/23 IPv4 /23 not checked
2604:7a40::/32 IPv6 /32 not checked
2604:dc00:1015::/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 AS394710
Address families
TorIX 110,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 AS394710 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS394710 in AS paths

Observed upstreams
Families
AS6461 ZAYO-6461 345 1,360
v4 v6
AS6939 HURRICANE 92 114
v6
AS20473 AS-VULTR 2 2
v6
AS394256 CLOUDSINGULARITY 2 2
v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS394710 in AS paths

Observed downstreams
Families
AS11635 AS-ENVI-1 211 835
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 6
v6
AS1403 EBOX 2 4
v6
AS22652 FIBRENOIRE-INTERNET 2 2
v6
AS49544 i3Dnet 2 2
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.