Data as of Nov 17, 2026

207.244.216.0/22

Anonymizer · ISP proxy

trafficforce, UAB

Announcement
this exact prefix
RPKI valid
Announced by
Type
ISP proxy
Risk
90 / 100 · Critical
IPv4 market

Path

1 · Holder
record created Nov 30, 2021
2 · Leased from
not leased
3 · Announced by
AS133944 trafficforce, UAB
since Feb 2023 · 3.7 yr ago
4 · Use
ISP proxy
anonymizer space, operator not named

Lineage

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

207.244.216.0/22

From the registry to its use

  1. Nov 30, 2021
    Registry record
    trafficforce, UAB
    ALLOCATED PA
    207.244.216.0/22
  2. Dec 23, 2021– Feb 3, 2023
    Announced
    AS210906 UAB 'Bite Lietuva'
    Hosting
  3. Feb 9, 2023
    Route object
    AS133944 trafficforce, UAB
    RIPE route object for AS133944 trafficforce, UAB, maintainer LIR-LT-TRAFFICFORCE-1-MNT
  4. Feb 16, 2023– today
    Announced
    AS133944 trafficforce, UAB
    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
207.244.216.0/221,024LT-TRAFFICFORCE-19961120trafficforce, UAB (ORG-TU38-RIPE) · LTALLOCATED PANov 30, 2021abuse@trafficforce.lt
└ 207.244.216.0 - 207.244.219.2541,023Dulles-Town-Fiber-ServiceunknownASSIGNED PADec 1, 2021abuse@trafficforce.lt
via LT-TRAFFICFORCE-19961120

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

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
Dec 2021
Current origin since
Feb 2023 · 3.7 yr
Origin networks
2
Last change of origin
Feb 2023
Recorded history

History

Handoffs
1