Data as of Nov 17, 2026

212.25.40.0/24

No anonymizer space · no proxy exits in 30 days

Vivacom Bulgaria EAD

Announcement
RPKI valid
Announced by
Type
Business

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.25.32.0/19
since Jan 2008
AS34569Residential30
3 always on
Vivacom Bulgaria EAD

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
212.25.32.0/198,192BG-BTC-20051025Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PAOct 25, 2005abuse-ip@vivacom.bg
└ 212.25.40.0/2732Rodina-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.40.32/2732zala-minimaxCustomer zala-minimax public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.40.64 - 212.25.40.14380Rodina-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.40.144/2816zala-ruchiCustomer zala-ruchi public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.40.160 - 212.25.40.25596Rodina-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025

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

Covering aggregate above, the prefix's own history below

212.25.40.0/23

Routing history

Pattern
Stable
First seen
Oct 2024
Current origin since
Oct 2024 · 2.1 yr
Origin networks
1