Skip to main content

AS22534

CS-TECH-INC

CS Technologies

Registry

Authoritative registration data

AS number
22534
Name
CS-TECH-INC
Organisation
CS Technologies
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

1

Total announced

6

Announced prefixes

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

Prefixes announced by AS22534
170.178.224.0/19 IPv4 /19 not checked
107.182.192.0/20 IPv4 /20 not checked
45.45.180.0/22 IPv4 /22 not checked
167.142.153.0/24 IPv4 /24 not checked
170.39.158.0/24 IPv4 /24 not checked
2605:b8c0::/32 IPv6 /32 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 AS22534
Address families
MICE: Shared Peering 20,000 Mbps IPv4 · IPv6
QCIX: Main 100,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 AS22534 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS22534 in AS paths

Observed upstreams
Families
AS10242 495 1,903
v4 v6
AS5056 290 622
v4
AS15129 8 8
v4

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS22534 in AS paths

Observed downstreams
Families
AS26017 186 260
v4

No rows match “”.

Showing of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS394414 2 6
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.