Concurrency

What is a concurrency signal?

A concurrency signal occurs when a user has two or more devices of the same type actively connected to a project at the exact same time from different IP addresses.

That definition is very nuanced, so let's break it down:

• Two or more devices: The user must have two or more devices connected.
• Same device type: If a user has a computer and a phone actively connected, even if they are not the same IP, we err on the side of caution and assume it could be the same person. But if two iPhones or two computers are connected at the same time from different IP addresses, it is a concurrency signal.
• Active connection: Rupt uses very light active connection detection, so if the connections are not active at the exact same time, it is not a concurrency signal.
• Different IP addresses: The devices must be connected from different IP addresses, if the same IP is used on multiple devices at the same time, it is not a concurrency signal.

How does it work?

When more than one device is actively connected to a single account at the same time, it is considered a concurrency signal.

How can I take action?

For automated concurrency enforcement, you can challenge the account in question by enabling the environment setting for your project.

If you want to manually take action on a concurrency signal, you can navigate to the account details page for the account in question and review the offending devices to determine if they are fraudulent or abusive.

Following your review, if you find that the devices are indeed fraudulent or abusive, you can take action by blocking the devices or by enforcing challenges on that account.

For more information on challenges, see the challenges documentation.