Data as of Nov 11, 2026

83.220.136.0/22

No anonymizer space · no proxy exits in 30 days

PlusServer GmbH

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

Announcements

Less specific

Covering announcements

PrefixOriginTypeHolderRPKI
83.220.128.0/19
since Dec 2018
AS61157HostingPlusServer GmbH

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
83.220.128.0/198,192DE-OPENIT-20040405PlusServer GmbH (ORG-OG2-RIPE) · DEALLOCATED PAApr 26, 2016abuse@plusserver.com
└ 83.220.136.72/298VESSELTRACKERvesseltracker.com GmbHASSIGNED PAFeb 24, 2016abuse@plusserver.com
via DE-OPENIT-20040405
└ 83.220.136.80/2816PS-CORE-NETkvm-ham1ASSIGNED PAOct 8, 2020abuse@plusserver.com
via DE-OPENIT-20040405
└ 83.220.137.64/2732DE-SUPREMENEWMEDIASupreme NewMedia GmbHASSIGNED PANov 11, 2005abuse@plusserver.com
via DE-OPENIT-20040405
└ 83.220.137.128/25128DE-VESSELTRACKERvesseltracker.com GmbHASSIGNED PAApr 20, 2005abuse@plusserver.com
via DE-OPENIT-20040405
└ 83.220.138.0/24256DE-SUPREMENEWMEDIASupreme NewMedia GmbHASSIGNED PAOct 5, 2009abuse@plusserver.com
via DE-OPENIT-20040405
└ 83.220.139.0/2732Assense_Customer2Assense Software Solutions GmbHASSIGNED PAOct 27, 2008abuse@plusserver.com
via DE-OPENIT-20040405

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
May 2005
Current origin since
Feb 2020 · 6.7 yr
Origin networks
2
Last change of origin
Feb 2020
Recorded history

History

Handoffs
1