Skip to main content

AS22296

VORSK

Vorsk LLC

Registry

Authoritative registration data

AS number
22296
Name
VORSK
Organisation
Vorsk LLC
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

2

Total announced

7

Announced prefixes

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

Prefixes announced by AS22296
169.128.232.0/22 IPv4 /22 not checked
205.207.133.0/24 IPv4 /24 not checked
23.155.8.0/24 IPv4 /24 not checked
44.31.248.0/24 IPv4 /24 not checked
44.32.62.0/24 IPv4 /24 not checked
2001:470:8f::/48 IPv6 /48 not checked
2602:2e5::/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 AS22296
Address families
FCIX 10,000 Mbps IPv4 · IPv6
MegaIX Bay Area 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 AS22296 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS22296 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 499 2,372
v4 v6
AS6140 37 231
v4 v6
AS60011 3 18
v4 v6
AS58057 SECUREBIT 1 5
v4 v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS22296 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS36236 NETACTUATE 1 5
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.