Ravensight

Traffic sources and the block list

See which connecting addresses a game's sessions and events come from, tell a keen player from a bot, and block an address that is abusing a key. It works for every key, live and public.

What is kept

A raw IP address is never stored. For each game, address and UTC day, Ravensight keeps a keyed hash of the address and a masked form a person can read (an IPv4 address as its /24, like 203.0.113.0/24, an IPv6 address as its first 48 bits), with that day's sessions, accepted events, refused events, how many devices opened sessions from it (counted up to 50, then shown as 50 or more), and a short, sampled list of its most frequent event names. Device ids are kept only as short digests. These rows are deleted after 30 days; a block keeps the hash and masked form for as long as the block stands. Refused events count only when the address caused them (invalid events, policy refusals, its own session's or device's limits, a block), never when the game is out of funds, at a key's ceiling, switched off or at its game-wide limit. A session also keeps the hash and masked form of the address it was opened from, until the session expires. Playtest and doctor sessions are left out.

Shapes

Each address's day gets one shape. Events means accepted events; refused events are counted apart.

ShapeWhenWhat happens
many_devices10 or more devices opened sessions from the address that day.A warning on the Implementation card, and the day's traffic email to the studio owner (one per game and day, listing up to ten addresses). It may be a bot or a shared network, such as a school or a cafe.
rejectionsAt least 50 refused events, and at least 30 percent of everything the address sent.A warning, listed in the same daily email.
heavy_playerAt least 1,000 events and at least 20 percent of the game's day, from one or two devices.Information only: a heavy player at a steady pace. No email, no action suggested.
normalEverything else.Nothing.

Blocking an address

Block an address from its row in the traffic list, or by typing it; a typed address is hashed and masked and never stored. A block carries a reason (abuse, bot, testing or other), an optional note of up to 500 characters, and an optional expiry from one hour to 90 days. A blocked address gets 403 ip_blocked on POST /api/v1/session, /track and /track/batch, before any rate limit or allowance check, so a refused request is free and never billed. Each block counts the requests it refused. A block or an unblock takes effect within 30 seconds on every server. An SDK treats the 403 as a stop, like any other 403.

The honest limit: one address can be many people (a school, an office, a mobile carrier), and a determined sender can change addresses. Block what looks like abuse, and pair it with a public key's allowlist and limits.

API and MCP

  • GET /api/v1/games/:gameId/traffic/sources?day=YYYY-MM-DD: the day's totals and the 50 busiest addresses by events, each with ipHash, ipDisplay, counts, sampled names, shape and blocked.
  • GET, POST and DELETE /api/v1/games/:gameId/traffic/blocks: list, add ({ ipHash or ip, reason, note?, expiresInSeconds? }) and remove blocks. Adding or removing one needs a role that may change game settings.
  • Over MCP: list_traffic_sources, list_ip_blocks, and with a write token block_ip and unblock_ip. get_integration_status carries today's ten busiest addresses and the block list as traffic.