Data as of Nov 17, 2026

86.38.159.0/24

No anonymizer space · no proxy exits in 30 days

UAB Bacloud

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium
Recently moved
Recent change
New origin Oct 22, 2026
from AS2914 NTT America, Inc., after 1.5 years unannounced
registry: sub-allocated pa to a party the registry does not name by UAB Bacloud, Oct 21, 2026

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
86.38.158.0/23512LT-BACLOUD-20050519UAB Bacloud (ORG-ISIT5-RIPE) · LTALLOCATED PAFeb 13, 2026abuse@bacloud.com
└ 86.38.159.0/24256LT-BACLOUDunknownSUB-ALLOCATED PAOct 21, 2026abuse@bacloud.com
via LT-BACLOUD-20050519
└ 86.38.159.0/2732Lucas-Mille-NETunknownASSIGNED PANov 7, 2026lmille303@gmail.com
└ 86.38.159.32/2732Evan-Kaiger-NETunknownASSIGNED PANov 1, 2026EvanKaiger.15@proton.me
└ 86.38.159.64/2732Ferguson-rernandez-NETunknownASSIGNED PANov 8, 2026Ferguson.Salidi75@proton.me

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
Reactivated
First seen
Jan 2022
Current origin since
Oct 22, 2026 · under a month
Origin networks
3
Last change of origin
Oct 22, 2026
Recorded history

History

Handoffs
2