LAYER3 INTEL
Get started
Sign in
Data as of Nov 12, 2026

209.35.99.0/24

Anonymizer · Datacenter proxy

UAB code200 · space held by trafficforce, UAB

Announcement
this exact prefix
RPKI valid
Announced by
AS205964
Type
Datacenter proxy
Risk
85 / 100 · Critical
IPv4 market

Path

1 · Holder
trafficforce, UAB
record created Nov 22, 2021
2 · Leased from
not leased
3 · Announced by
AS205964 UAB code200
since May 2024 · 2.5 yr ago
4 · Use
Datacenter proxy
anonymizer space, operator not named

Lineage

How this block came to its use, oldest first. The whole IPv4 market →

209.35.99.0/24

From the registry to its use

  1. Nov 22, 2021
    Registry record
    trafficforce, UAB
    ALLOCATED PA
    209.35.99.0/24
  2. Dec 23, 2021– Feb 3, 2023
    Announced
    AS210906 UAB 'Bite Lietuva'
    Hosting
  3. Jun 16, 2023– May 4, 2024
    Announced
    AS210906 UAB 'Bite Lietuva'
    Hosting
  4. May 3, 2024
    Route object
    AS205964 UAB code200
    RIPE route object for AS205964 UAB code200, maintainer LIR-LT-TRAFFICFORCE-1-MNT
  5. May 17, 2024– today
    Announced
    AS205964 UAB code200
    Hosting

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
209.35.99.0/24256LT-TRAFFICFORCE-19990323trafficforce, UAB (ORG-TU38-RIPE) · LTALLOCATED PANov 22, 2021abuse@trafficforce.lt
└ 209.35.99.0 - 209.35.99.254255Fairfax-Community-ProviderunknownASSIGNED PANov 29, 2021abuse@trafficforce.lt
via LT-TRAFFICFORCE-19990323

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
Dec 2021
Current origin since
May 2024 · 2.5 yr
Origin networks
2
Last change of origin
May 2024
Recorded history

History

Handoffs
1