Data as of Nov 16, 2026

31.14.121.0/24

No anonymizer space · no proxy exits in 30 days

Afranet

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
31.14.112.0/20
since Jan 2017
AS25184Hosting1Afranet

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
31.14.112.0/204,096IR-AFRANET-20110418Afranet (ORG-AA32-RIPE) · IRALLOCATED PASep 17, 2014abuse@afranet.com
└ 31.14.121.0/2816Mehrdad-RoshanaeeunknownASSIGNED PAMar 2, 2024abuse@afranet.com
via IR-AFRANET-20110418
└ 31.14.121.32/2732Mehrdad-RoshanaeeunknownASSIGNED PAMar 2, 2024abuse@afranet.com
via IR-AFRANET-20110418
└ 31.14.121.120/304Bazisazan-Noavaran-ParsianunknownASSIGNED PAOct 7, 2026abuse@afranet.com
via IR-AFRANET-20110418
└ 31.14.121.176/298Targoman-MCI-GPU2unknownASSIGNED PAAug 18, 2024abuse@afranet.com
via IR-AFRANET-20110418
└ 31.14.121.200/298MCI-GPUunknownASSIGNED PAAug 17, 2024abuse@afranet.com
via IR-AFRANET-20110418

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

Summary

Routing history

Pattern
Stable
First seen
Oct 2022
Current origin since
Dec 2023 · 2.9 yr
Origin networks
1