Data as of Nov 21, 2026

70.33.216.0/21

No anonymizer space · no proxy exits in 30 days

Aptum Technologies

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

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
70.33.200.0 - 70.33.255.25514,336PEER1-BLK-14Aptum Technologies (PER1) · CADirect AllocationOct 9, 2008abuse@aptum.com
└ 70.33.216.0/25128PEER1-NXSYSTEMS-01unknown———
└ 70.33.216.128/25128PEER1-TIMESTELECOM-03unknown———
└ 70.33.217.128/2816PEER1-EXWARE-01unknown———
└ 70.33.217.144/2816PEER1-CLAIMTOOLS-01unknown———
└ 70.33.217.160/2732PEER1-EXACT-03unknown———
└ 70.33.217.224/2816PEER1-ATIADVERTISING-03unknown———
└ 70.33.217.240/2816PEER1-PIERPROGRAMMING-01unknown———
└ 70.33.218.0/2816PEER1-LAYERX-01unknown———
└ 70.33.219.0/24256PEER1-SEQUENTIAL-01unknown———
└ 70.33.221.0/24256PEER1-BRAVENET-16unknown———
└ 70.33.223.0/24256PEER1-BRAVENET-18unknown———

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Nov 2008
Current origin since
Nov 2008 · 18 yr
Origin networks
1