Data as of Nov 14, 2026

64.34.176.0/20

No anonymizer space · no proxy exits in 30 days

Aptum Technologies

Announcement
RPKI valid
Announced by
Type
Hosting

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
64.34.176.0/21
since Jun 2011
AS13768HostingAptum Technologies
via ServerBeach
64.34.184.0/22
since Jun 2011
AS13768HostingAptum Technologies
via ServerBeach
64.34.190.0/23
since Jun 2011
AS13768HostingAptum Technologies
via ServerBeach

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
64.34.96.0 - 64.34.255.25540,960PEER1-BLK-08Aptum Technologies (PER1) · CADirect AllocationJul 15, 2004abuse@aptum.com
└ 64.34.176.0/204,096PEER1-SERVERBEACH-02AServerBeach (SERVE-33) · USReallocatedJan 19, 2007abuse@serverbeach.com
└ 64.34.178.192/2664PEER1-MYINTERNETSERVICES-IAD--06unknown———
└ 64.34.187.0/25128PEER1-MYINTERNETSERVICES-IAD--05unknown———
└ 64.34.188.32/2816PEER1-MYINTERNETSERVICES-IAD--12unknown———
└ 64.34.188.64/2664PEER1-TREND-MICRO-INC-01unknown———
└ 64.34.188.128/2664PEER1-GAZZAG-SERVICOS-DE-INTERNET-LTDA-01unknown———
└ 64.34.188.192/2664PEER1-MYINTERNETSERVICES-IAD--09unknown———
└ 64.34.189.0/24256PEER1-MYINTERNETSERVICES-IAD--01unknown———
└ 64.34.190.0/2816PEER1-REMIXATION-INC-01unknown———
└ 64.34.190.16/2816PEER1-TOKBOX-01unknown———
└ 64.34.190.32/2732PEER1-100MEGABYTE-01unknown———
└ 64.34.190.128/25128PEER1-MYINTERNETSERVICES-IAD--02unknown———
└ 64.34.191.0/24256PEER1-MYINTERNETSERVICES-IAD--07unknown———

Network & registry

Routing timeline

Who has announced 64.34.160.0/19

64.34.160.0/19

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Jun 2011 · 15 yr
Origin networks
2
Last change of origin
Jun 2011
Recorded history

History

Handoffs
2