Skip to main content

AS400426

SKYTECH

SKYTECH COMMUNICATIONS INC.

Registry

Authoritative registration data

AS number
400426
Name
SKYTECH
Organisation
SKYTECH COMMUNICATIONS INC.
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS400426
128.254.136.0/24 IPv4 /24 not checked
128.254.137.0/24 IPv4 /24 not checked
128.254.138.0/24 IPv4 /24 not checked
128.254.139.0/24 IPv4 /24 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 AS400426
Address families
CANIX Montreal 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 AS400426 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS400426 in AS paths

Observed upstreams
Families
AS21949 BEANFIELD 191 651
v4
AS33185 HIVE-DATA-CENTER 199 538
v4
AS6939 HURRICANE 25 108
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS400426 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
AS49544 i3Dnet 1 8
v4
AS1403 EBOX 1 4
v4
AS22652 FIBRENOIRE-INTERNET 1 4
v4
AS35280 F5 1 4
v4
AS36236 NETACTUATE 1 4
v4

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.